Asger Ottar Alstrup <[EMAIL PROTECTED]> writes:
| I propose that LyX adopts a direct-commit policy for developers who
| have demonstrated that they know the rules AND are competent, AND can
| commit time to work on LyX.
Knowing the rules are not enough. You must at least try to follow them
as well.
[...]
| 1) Only commit release quality stuff: It should compile, run, the code
| should be maintainable, high quality, useful and portable.
|
| 2) Write concise and short patch summaries.
|
| 3) Commit early and often. When doing a sprint, commit each logical,
| working change rather than one big commit at the end.
|
| 4) State when you have time to work on any issues that might appear.
| If you know you wont have time in the near future to address issues,
| send a patch to the list instead of committing directly.
|
| If in doubt, send a patch instead.
Which is of course essentially how we have tried to do things for
quite some time.
--
Lgb
