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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120120/b4562759/attachment.html>

Reply via email to