Hi Tom, Recently, the author of Antlr started a similar discussion regarding the software version control options of the project. This topic has lots of useful feedback and important factors (it extends to second page, a bit hard to see) : http://antlr.1301665.n2.nabble.com/anybody-care-to-comment-on-bitbucket-org-td7169167.html
The established system with mailman is working. It has quite good spam protection, which is hard to get these days, and there is know how that allows the community to keep it running with minimum effort. A switch would mean moving the archives, ensuring we have the same quality of service etc. We'll spend time to figure out stuff, develop new maintenance know how, you know the drill.. I say we keep the lists in mailman; all of them. Regards Seref On Fri, Jan 20, 2012 at 1:41 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > On 20/01/2012 11:10, Koray Atalag wrote: > > Hi Tom, **** > > ** ** > > I used SourceForge before to host projects (yes that?s correct not just > software development but collaborative project sites) in past which offers > for free lists and many more, such as Web pages, SVN/Mercurial, blog and > Wiki and many more. I reckon the licensing might be an issue for non FOSS > projects but I believe in the case of openEHR that?s a non issue?? I must > admit the SVN is not as fast and there?s limited administration capability > but hey it?s still great value for nothing. Plus the platform also allows > for ?donations? which I think might create few bucks to look after things > like administration etc. until an appropriate funding mechanism becomes > available.**** > > ** ** > > Cheers,**** > > ** ** > > > some of us have been thinking of moving to Github for software > development. This is more modern than SVN, but essentially the same idea. > Now that you mention it, I think the lists in such a place might actually > be a good enough replacement for the technology / project specific lists we > have, i.e. java, Eiffel, .Net and so on. > > It would be interesting to know what the interest is in moving to GIT, > staying with SVN, doing something else, etc is. > > However, we still have some main community lists which have large > memberships, are not attached to any particular project, and have to have > good admin and spam management, so (as a part-time admin) I am very loathe > to let go of mailman lists for these. This applies to openehr-technical, > openehr-clinical, openehr-announce, openehr-implementers, > openehr-decisionsupport and the forthcoming openehr-13606 lists - 6 in all. > The above strategy would mean we can locate the java / python / ruby / > eiffel / .Net lists on GIT / other FOSS sites, so it certainly helps. > > Further thoughts? > > - thomas > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120120/eb56a2a1/attachment.html>
