http://www.djangoproject.com/documentation/faq/#who-s-behind-this
but I'm missing information about the further team member and their roles.
Is such a document available, which lists e.g.
* committers
* subsystem leads (or component leads)
* code level contributors
* documentation contributors
* others
?
.
Not that I'm aware of.
> * subsystem leads (or component leads)
Except for the i18n system, there really aren't "component leads" for Django.
> * code level contributors
The AUTHORS file.
> * documentation contributors
The AUTHORS file.
> * others
The above covers pretty much everybody.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
Thank you for the information.
http://code.djangoproject.com/browser/django/trunk/AUTHORS
"The PRIMARY AUTHORS are (and/or have been):"
-
Is is possible to have an overview of the currently _active_ team,
including roles? e.g. on a page on the project wiki?
.
The Django project defines pretty much two roles: "core developers"
and "everybody else". Again, with the exception of Georg steering the
i18n system, there are no other officially defined positions within
the project. IMHO, we haven't had enough need for that sort of
bureaucracy to justify its overhead.
ok, 2 roles, .
So, is it possible to have an overview of the _active_ "core developers"
and "other contributors"?
.
> ok, 2 roles, .
>
> So, is it possible to have an overview of the _active_ "core
> developers"
> and "other contributors"?
what for?
--
regards
kg
http://lawgon.livejournal.com
http://avsap.org.in
please!
.
I'm not sure if core developers have such _activeness-awared_
directory of contributors (I suppose NO since that's trifling,
relative to writing or fixing code to keep Django evolved and stable).
But you may have some idea on it, by carefully reading django-dev
archives (who are posting to it actively) or project trac timeline
at http://code.djangoproject.com/timeline (who are processing
tickets, discussing on it, and committing code changes).
If you are just curious about the profile of _active_ developer
community, it should be sufficient...
-- Yasushi Masuda http://ymasuda.jp/
There is no such list or overview.
Again, I think that maintaining such lists is a level of bureaucracy
which would not provide the project enough benefit to justify the time
and effort of maintaining it; Django welcomes contributions from
anyone, and anyone who writes good, useful code can get it committed.
Can you elaborate on why, other than its presence on some checklist of
yours, this is such an apparently important factor for you?
of course this is an process to obtain the active team information.
but I think it would be gentle, if the project would provide such an
overview, thus any intrested party can retrieve this information easily.
anyway, this is not something that has priority to me.
Thank you for the feedback.
.