Hi,

I just raised this question in another e-mail to this list but I think a
dedicated thread might be good. I quickly used my mail client to search
for this topic but I couldn't find anythin; so bare with me if I'm
mistaken.

GitHub has clearly become one of the most popular platforms for
collaboration on Open Source projects; I dare say, it's todays most
popular platform.

Many projects have moved there and use the infrastructure plus the vast
user base to improve their projects.

A quick search for "ArgoUML" yields that there are currently 27
repositories on GitHub that deal with Argo. (Link:
https://github.com/search?p=1&q=argouml&type=Repositories&utf8=%E2%9C%93
)

I'm not saying that by moving there thousands of people will currently
join ArgoUML, but I think that the barrier will be significantly lower:

- One can easily fork the project and commit changes; signing up on   
  tigris.org is not necessary and might hold some people back from 
  contributing a quick patch.

- Issue tracker is nicely integrated into the interface; discussion on 
  Pull Requests possible.

- Contributing made simple: A simple click will create a pull request   
  and hence notify the ArgoUML team of a new feature someone might have 
  developed.

- Other tools support GitHub, such as travis-ci.org, which might be 
  interesting for the CI issue we're currently having.

- One can easily use the Git workflow, no SVN needed.

- Use GitHub pages to build a decent website.



Personally, I'd like to see ArgoUML on GitHub but I haven't been very
active for more than 6 years now (I still want to say a quick "Hi
Thomas!").


I'm curious what you think.

Best regards
Christian

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=3118546

To unsubscribe from this discussion, e-mail: 
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email: 
[[email protected]]

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to