# Do we need a new list for commits on the Java project? **Category:** [Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154) **Created:** 2007-09-05 10:49 UTC **Views:** 1 **Replies:** 10 **URL:** https://discourse.openehr.org/t/do-we-need-a-new-list-for-commits-on-the-java-project/11999 --- ## Post #1 by @system Dear all, Recently we have discussed the need for a new dedicated email list for receiving SVN commits on the Java development project. Right now, we only have one common list for both discussions and details of all SVN commits on the java project. It seems to be difficult to follow and find discussions which are mixed with large amount of commits. On the other hand, Thomas suggested one could configure email clients to sort out commits using filters. It is of course some extra work to subscribe to yet another list and monitor it. I did bit research on some open source projects and found both approaches are used. For example. Apache has dedicated lists for commits: [http://xml.apache.org/mail.html](http://xml.apache.org/mail.html) And Eclipse has common dev lists for both commits and discussions: [http://www.eclipse.org/mail/index_all.php](http://www.eclipse.org/mail/index_all.php) What's your opinion on this? By the way, the Java list will be no longer be closed, if you have any object to this please let us know asap. Regards, Rong --- ## Post #2 by @helmavdl I opt for separate lists. Bye, Helma --- ## Post #3 by @sebastian.garde I am quite happy with the way it is, but wouldn’t mind the other option too much either, especially with the list archives being searchable on the web. Sebastian --- ## Post #4 by @thomas.beale Rong Chen wrote: > Dear all, > > Recently we have discussed the need for a new dedicated email list for receiving SVN commits on the Java development project. Right now, we only have one common list for both discussions and details of all SVN commits on the java project. It seems to be difficult to follow and find discussions which are mixed with large amount of commits. On the other hand, Thomas suggested one could configure email clients to sort out commits using filters. It is of course some extra work to subscribe to yet another list and monitor it. > > I did bit research on some open source projects and found both approaches are used. For example. Apache has dedicated lists for commits: > [http://xml.apache.org/mail.html](http://xml.apache.org/mail.html) > > And Eclipse has common dev lists for both commits and discussions: > [http://www.eclipse.org/mail/index_all.php](http://www.eclipse.org/mail/index_all.php) > > What's your opinion on this? > > By the way, the Java list will be no longer be closed, if you have any object to this please let us know asap. my suggestion was a single list, since it is easy to filter SVN commits to another folder, or delete them. Having 2 lists means doubling the number of lists for all implementation groups, and more subcriptions to worry about. - thomas --- ## Post #5 by @system > Having 2 lists means doubling the number of lists for all > implementation groups, and more subcriptions to worry about\. My opinion: Make them extra lists, gives me the opportunity to move them in a special local mailfolder automatically without having to create complicated filters --- ## Post #6 by @thomas.beale Bert Verhees wrote: > > ``` > > Having 2 lists means doubling the number of lists for all > > implementation groups, and more subcriptions to worry about. > > > > ``` > > ``` > My opinion: > Make them extra lists, gives me the opportunity to move them in a > special local mailfolder automatically without having to create > complicated filters > > ``` I wouldn't call e-mail filters complicated - each one takes about 30 sec to set up in Thunderbird. I have about 20. You just filter on sender = [svn@openehr.org](mailto:svn@openehr.org) in this case. - thomas --- ## Post #7 by @system Thomas Beale wrote: > Bert Verhees wrote: >>> Having 2 lists means doubling the number of lists for all >>> implementation groups, and more subcriptions to worry about\. >>>     >> >> My opinion: >> Make them extra lists, gives me the opportunity to move them in a >> special local mailfolder automatically without having to create >> complicated filters >>   > > I wouldn't call e\-mail filters complicated \- each one takes about 30 > sec to set up in Thunderbird\. I have about 20\. You just filter on > sender = svn@openehr\.org in this case\. Stupid, haven't thought about that\. Another argument could be that the technical looking SVN\-emails can scare non\-technical people off the list\. But maybe that isn't valid either, because what should a non technical person look for at the f\.e\. ref\_inpl\_java\-list Bert --- ## Post #8 by @Thilo_Schuler1 I am with Sebastian in separating as this is easier for searching on the web\. Thilo --- ## Post #9 by @erik.sundvall Hi\! Great having the list archives available\! This can reduce possible repeated discussions by newcomers\. \(That is if they easily can find anything in the archive, see below\.\.\.\) I think having everything on one list is OK since this is a developer list where one can expect some computer literacy when it comes to mail handling\. The problem is the web archive for this list, look at it now, horrible from a usability standpoint with svn\-commits everywhere\. Some suggestions/alternatives: 1\. Put a filter on the input stream to \_web\-archive\_ we don't need the svn\-messages there\* \(but we do need discussions possibly written as reply to a svn\-message, so filter on sender, not subject\) and/or 2\. Get that promised wiki working and let the community maintain some page pointing directly to interesting threads in the svn\-message\-infected web archive to aid newcomers in finding relevant threads\. or 3\. Go for separate lists and archive only the discussion \*\) The svn messages are safely kept already and are available through any svn\-client anyway\. Best regards, Erik Sundvall erisu@imt\.liu\.se http://www.imt.liu.se/~erisu/ Tel: \+46\-13\-227579 --- ## Post #10 by @thomas.beale Erik, I like this suggestion the best - I am asking Anthony (our sysadmin) about filtering them out of the archive. - thomas Erik Sundvall wrote: [details="(attachments)"] ![OceanC\_small.png|74x72](upload://5I367QG2SMJUp18Pt3jF6yz13Ey.png) [/details] --- ## Post #11 by @system I also like the idea of archiving discussions on the list only to make it easy to browse. Another thing to consider here: soon, we will need to let the build server to send alerts on build failures to somewhere. Since we don't have a list for the committers yet, it's likely we use this common list for receiving them. Those who don't want to receive them can filter them out in their email client. We should also filter them out of the archive. Cheers, Rong [details="(attachments)"] ![OceanC\_small.png|74x72](upload://5I367QG2SMJUp18Pt3jF6yz13Ey.png) [/details] --- **Canonical:** https://discourse.openehr.org/t/do-we-need-a-new-list-for-commits-on-the-java-project/11999 **Original content:** https://discourse.openehr.org/t/do-we-need-a-new-list-for-commits-on-the-java-project/11999