some more FAQs #2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Re: development:
"How does Lix work? How can I contribute or help out?"
The Lix codebase is comprised of a few parts, which you can see a description of here, along with what we want to improve in them. We also have a lot of areas we are working on other than C++ code that we would love help on, from documentation to compiling lists of resources, web design, bug tracker triage, and more. If you're looking for an idea to get started on, we have triaged some tasks that we believe should be straightforward. To read more about which tasks we recommend taking on, see Freezes and recommended contributions.
Feel free to ask for help in the Lix development channel. Especially feel free to ask for us to write down more work that we would like help with, or to write contribution information that is missing; it is a goal of the project for it to be easy to get up to speed. Also, if you need additional access to do some task, such as fixing a typo in the wiki, let us know and we will figure it out.
You can find out more about how we organise information here.
"How do I submit changes to the Lix project?"
For the main Lix codebase, Lix uses Gerrit Code Review as its primary code review tool. Gerrit makes reviewing large changes much easier as it encourages breaking them down into steps and tracking the evolution of single commits, which greatly improves our review quality and timeliness as a team. This tool can be intimidating, and we have a guide to get started here.
It is also possible to submit changes as normal GitHub pull requests on lix-project/lix. These are also welcome, and we will FIXME convert them to Gerrit changes for you for review. However, there are limitations to the GitHub flow such as PRs needing to be squashed into one change. For larger changes than about 150 lines of normal code, or if necessary, we may ask for a change to be submitted to Gerrit directly so we can review it commit-by-commit.
"What is a Lix account? What do I need one for?"
Lix has a central accounts system for all its services. These accounts allow access to Forgejo (the Lix bug tracker and repositories), Gerrit Code Review, the wiki and other collaboration software we use.
To get started contributing to Lix, you need a Lix account. The easiest way to obtain one is to use GitHub for login, as it will let you get started immediately. We also have local accounts available for those who wish not to use GitHub; if you would like one, please speak to a member of the Lix team on Matrix and we will gladly make you one manually.
Added; thanks!
Unsure if intentional, but just in case:
The FIXME in jade's copy links to something, the one in the site does not.