#1422: Subscribing to commit notifications for the ET should be made easier --------------------------+------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Other | Version: development version Resolution: | Keywords: --------------------------+-------------------------------------------------
Comment (by hinder):
I forgot that this was already discussed about a month ago. See http://lists.einsteintoolkit.org/pipermail/users/2013-July/003077.html:
there is a desire to have fewer (ideally) one mailing lists for all
commit messages or to be able to forward Cactus commits to the ET list. Problematic to allow users to Reply to these messages and have the answer forwarded to the original list. Shelved for now.
I would like to open the discussion again. For me, the value of having a single source of commit messages outweighs the disadvantage of the reply- to header not pointing to the original mailing list.
Having said that, it should be possible to configure the lists so that the reply-to header points to the appropriate mailing list. If the reply-to header is set in the VCS commit hook to the mailing list of the corresponding project, rather than in Mailman, and Mailman is configured to preserve the Reply-to header for the commits lists, we can still have the reply-to header of the commits mailing list point to the project- specific lists. i.e. you would have two commit hooks. e.g. for Cactus, one would send to the Cactus commits list, and the other to the ET commits list. Both would specify a reply-to header pointing to the Cactus users list.
This assumes that the commit hooks are sophisticated enough to add such a header. I believe this is possible using svnnotify (http://search.cpan.org/dist/SVN-Notify/bin/svnnotify) and the multimail Git hook (https://github.com/git/git/tree/master/contrib/hooks/multimail). If using a repository host with its own hooks (BitBucket or GitHub, for example), this might not be possible. In that case, procmail could be used on the ET Mailman server to add a suitable reply-to header based on the corresponding project. Frank already indicated that he was interested in integrating spam filtering into Mailman, so this could be done at the same time.
For reference, I believe that these are the current sources of commit notifications for all components of the ET. If we don't decide to send all commit notifications to the ET list (which I think we should, independent of the reply-to issue), then this information should be added to the ET webpage (http://einsteintoolkit.org/community/support/).
|| Repositories @ einsteintoolkit.org, Carpet, EinsteinExact, McLachlan || http://lists.einsteintoolkit.org/mailman/listinfo/commits || || Repositories @ cactuscode.org, GetComponents || http://cactuscode.org/mailman/listinfo/commits || || SimFactory || Email Erik Schnetter to be added (maybe also CCT support directly?) || || Outflow || "Watch" the GitHub repository https://github.com/rhaas80/Outflow (is there also an email hook?) || || Boost || "Watch" the GitHub repository https://github.com/dradice/Boost (is there also an email hook?) || || AEIThorns (5) || Email subversion at aei and ask to be added || || LSUThorns (4) || Email CCT IT support and ask for notifications (?) || || Kranc || "Watch" the GitHub repository (https://github.com/ianhinder/Kranc) or subscribe to the Kranc google group (kranc-commits) ||