Rooba
/
lapce
mirror of https://github.com/lapce/lapce.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove unnecessary document (#2658) 

* Remove unnecessary document

* Remove dev contributing file
This commit is contained in:
Jakub Panek 2023-10-08 22:39:17 +01:00 committed by GitHub
parent 507e9e4de8
commit 8f596cc6f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 0 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/new-contributor-guide-developer.md
View File

@ -1,23 +0,0 @@
# New Contributor Guide **Developers**
This document contains some useful resources for anyone wishing to contribute to the Lapce project by contributing code.
## Quick Start
1. Get an overview of the architecture from [`docs/why-lapce.md`](why-lapce.md) and [Architecture](https://docs.lapce.dev/development/architecture).
2. Explore the rope data structure, a key part of Lapce's architecture. The crate used is [xi_rope](https://crates.io/crates/xi-rope).
3. Review both open and closed [issues](https://github.com/lapce/lapce/issues), there may be others working on a similar feature.
4. [Get cracking](https://dictionary.cambridge.org/dictionary/english/get-cracking)!
5. Be aware that unless you explicitly state otherwise, contributions you make to this project will be under the Apache License Version 2.
## Resources
The [Wikipedia article on ropes](https://en.wikipedia.org/wiki/Rope_(data_structure)) provides an overview of the data structure.
For some context, also see [Ropes: an Alternative to Strings](https://www.cs.tufts.edu/comp/150FP/archive/hans-boehm/ropes.pdf) by Boehm, Atkinson, and Plass.

23
docs/new-contributor-guide-user.md
View File

@ -1,23 +0,0 @@
# New Contributor Guide **Users**
This document contains some useful resources for anyone wishing to contribute to the Lapce project by suggesting improvements, requesting features, or supporting the community. Where it says _question_ in this document, it can also apply to _suggestions_, _requests_, etc.
## Quick Start
1. Open a text editor
2. Write out your question (or request, or suggestion).
3. _Revise_ your question
4. Choose where to post your question
5. Post it!
## Resources
For general information about open source software, [see these FAQs](https://opensource.org/faq) by the Open Source Initiative.
We don't have a specified code of conduct yet, but for some reasonable guidelines see the [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/).
[This guide](http://www.catb.org/~esr/faqs/smart-questions.html), by Eric Steven Raymond, is about how to ask excellent questions. You can apply the same techniques (such as _Use meaningful, specific subject headers_) to suggestions and bug reports. The more specific (and helpful!) you can be with your question, the more it helps us to provide a solution.