[GenABEL-dev] formulating rules and providing guidelines

[Yurii Aulchenko]

Dear All,

I am going to come up with a series of posts on GenABEL-project's
fundamentals, like What is it? What is the philosophy behind? What is
the ideology? How is it governed? How one can join?

I would love to have these formulated in open discussion, but someone
needs to start. I also understand there is not a huge interest in that
right now in the team - I think we all use some implicit rules, which
boil down to open-source and common-sense, and we trust each other,
which is enough. Still, we need the rules of the game explicitly
formulated: the absence of clearly expressed rules hampers the growth
of the developers' community, as new people are hesitant to join to
the unknown.

What I thought of was to work out principles and rules to an explicit
form, and posting them to this list. If there is discussion and we
arrive to consensus opinion, particular set of rules / guidance will
be made available as part of the project documentation, to be hosted
at our web-site.

If there is no discussion, then we will keep these statements as
working rules until the discussion is brought up again. These rules
will be hosted at my professional blog, and a link will be made on
"for developer" page of genabel.org. It will be made clear that these
are current working rules, open for the community discussion.

Please let me know what you think of the above proposal.

Best wishes,
Yurii