Hi, I'd certainly like to help with this, but I don't have a lot of spare time - as everyone else here, I guess. (I will be on a (business) trip almost all of June, for instance.)
Anyways, it should also discussed what is being moved and how projects are organized. 1. I'd propose to create a new user "argouml" and then create several repositories for the different projects. 2. I think we should not move the bug tracker; there are too many tickets open that nobody ever dealt with and the new issue system would instantaneously become a mess. If someone wants to fix open bugs, check tigris.org for that. If someone enters a bug again on GitHub, it means "someone really cares about this". 3. We should decide on the CI issue before making the move. 4. Is everyone familiar with the workflow of git? That is, topic branches and Pull Requests? I'd propose only very few people get access to the main repositories and they then accept the PRs. Best regards Christian On Thu, 2015-05-21 at 16:00 +0200, Christian López Espínola wrote: > I agree that moving there would be "a good thing" (TM) > > CollabNet as far as I know has not added new features or evolutions, > and looking at how other competitors closed I see that there could be > an announcement anytime soon. > So doing that now without much pressure is better than later. > > > But we need a plan for moving there, our build is complex enough so we > need to be sure that everything will work. In case there is agreement, > do you would like to lead the initiative? > > On Thu, May 21, 2015 at 3:21 PM, Christian Heinrich > <[email protected]> wrote: > 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]] > > > > > -- > Cheers, > > Christian López Espínola <penyaskito AT computer DOT org> > http://twitter.com/penyaskito | http://penyaskito.com ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=3118564 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]]
signature.asc
Description: This is a digitally signed message part
