On 10/17/2014 03:12 PM, sebb wrote:
On 17 October 2014 19:49, Ole Ersoy <ole.er...@gmail.com> wrote:
Hi,
I'm following the discussion of how MATH-1138 was handled (Which I enjoy
reading because I'm very impressed with how eloquently everyone communicates
their points of view).
Just a warning that I might be ignoring [2] (Stolen from Gilles), because I
have suggested this before:
==================================
Keep discussions in Github issues
==================================
This would have the following benefits:
- All Github users can follow the project just by clicking "Watch" (Which is
what a lot of developers (World outside of Apache) are becoming accustomed
to, and they might be confused by the fact that this is not the workflow)
- The mailing list could watch the Github issue so that trivial discussions
could be kept on the list, and the really important points / final decisions
summarized in the issue.
- It makes it easy to lookup workflow history. All the information /
history is bound to the issue (Design, debate, links to pull requests,
etc.).
- It eliminates missed communication.
- The commons math communication would be automatically filtered (Currently
it's bundled with all Commons communication)
- You can have it all:
https://github.com/joeyh/github-backup
Even though the agreed upon protocol right now is to discuss everything on
the mailing list, in practice it's both the mailing list and issues, and
this is causing the type of extra work effort we are seeing with respect to
MATH-1138, in addition to every now and then individuals have to be reminded
to move discussion from JIRA to the list.
A major disadvantage is that Github is external.
It may not last as long as the ASF.
If it disappears or moves, all the history is potentially lost.
All of us and the ASF can backup of everything:
https://github.com/joeyh/github-backup
It also looks like (Need to play with it) commit hooks can be used to sync the
apache git repository, ensure that the apache mailing list is update with all
communication, and trigger backups to multiple locations:
http://git-scm.com/book/en/Customizing-Git-Git-Hooks
Some projects hooks to trigger instant web site updates whenever the
documentation is updated.
Cheers,
- Ole
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
