Thanks both - this is good feedback. We have been moving more traffic to
our esme-dev list, but you are right to point out the need to document
the results of any significant real-time discussions back on the mailing
list.
To be honest, thus far we have been making up the whole process as we go
along, and one of the benefits to us of moving to Apache is to learn
these good practices from people who have been there before.
Cheers,
Darren
William A. Rowe, Jr. wrote:
Craig L Russell wrote:
My only concern is that from the description, the project appears to be
run in real time, with decisions made "through collaborative
decision-making on the mailing list, through daily scrum calls, via
Twitter and using open discussion on ESME itself."
Good points. If the project remembers one cardinal rule --- "If it didn't
happen on the dev@ list, it didn't happen", then all of these additional
tools can certainly be used to advance the project.
They simply aren't decision-making mechanisms, and are not valid as some
ordinal reference to "but we decided that..."
For example, httpd and apr use IRC to suppliment but never to replace the
dev@ developer forums. Once an idea is hashed out, if it needs to be
presented to the developers, dev@ is the ***one and only*** forum.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
