Sign in Join
Wiki copytemporary

How to become Lazarus developer (committer): what changed

Revision 0 to 1. Removed lines have a minus sign; added lines have a plus sign.

Title: How to become Lazarus developer (committer)

OldNewLine
1+You need to contribute at least 10-20 non-trivial and good quality patches (they can fix some bugs from the tracker or implement the new features). Better if your patches will be reviewed by more than one developer - more voices will support you candidacy. After that ask some developer to give you write access.
2+
3+By creating patches you will demonstrate your
4+
5+- commitment to the project (10+ good patches requires a lot of your valuable time),
6+- ability to collaborate with the team,
7+- understanding of Lazarus code base,
8+- ability to write good code
9+
10+A current developer asks for your candidacy by sending an email to the developer mailing list with an explanation of why you should be a developer and links to your patches. If no one objects in 3 days, you're a developer.
11+
12+If anyone objects or wants more information, the developers discuss and usually come to a consensus. If issues can't be resolved, there's a vote among current developers.
13+
14+Once you get approval from the existing developers, we'll send you instructions for write access to SVN. You'll also get a subscription to the developer mailing list and developer status for the bug tracker.
15+
16+Most of this text is taken from [Become a Chromium Committer](http://dev.chromium.org/getting-involved/become-a-committer)
17+
18+---
19+*From the Free Pascal wiki, page "How to become Lazarus developer (committer)", as it stood on 2015-07-25 after a change by FTurtle, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).*
20+Category: Community

Back to history