Re: [Exist-development] Some rules to start with

[Adam R. <ad...@ex...>]

The "eXist-db Developers Manifesto" is now available for reading. Just
committed to trunk as revision 11572 - devguide_manifesto.xml - liked
to from the main documentation page.

I would ask that each contributor to eXist read this and pay head to it.

So far it has had input from the core developers, if you have input or
changes that you wish to make to it, then please bring them to me for
discussion rather than changing that document directly.

I will also post a new thread for this purpose...

On 24 March 2010 20:03, Wolfgang Meier <wol...@ex...> wrote:
> Hi guys,
>
> Adam is currently writing a draft for a general eXist-db Developers
> Manifesto, which will be available for your reading and discussion
> within the next days. In the meantime, I'd like to ask every
> contributor to adhere to some basic rules:
>
> * new features should be announced and discussed on exist-development
> *before* they are committed. In particular, you should try to explain
> why the feature will be beneficial to the project as a whole. I think
> we are a very open community, so nobody has to fear that he will be
> outright rejected. We may just have some suggestions.
>
> * new code must always be accompanied by test cases. Integration tests
> can be written in XQuery.
>
> * you must run the test suite(s) before committing. Changes to
> anything XQuery-related require the XQTS to be run. After major
> changes, make sure all the demo applications which ship with eXist are
> still working as before.
>
> * we want all commits to be checked by as many people as possible. It
> is thus important that related commits are kept together where
> possible. For example, I made only 2 commits to trunk during the past
> 2 days, while Evgeny did 13! This inflation of commits makes it
> difficult to detect problems.
>
> Please limit your changes to the necessary minimum. Don't touch code
> unless you really have to modify it. The less classes are changed, the
> easier it is for other people to understand the purpose of the commit.
> If you want to cleanup something, do it in a separate commit and mark
> it as "cleaning up".
>
> Wolfgang
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb