GitHub migration procedure
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: GitHub migration procedure
After using now github for several month I would like to point out some things:
* I created a `freeorion-utilities` repository were developers can put projects related to FreeOrion into. It's intended for utilities, that should be versioned and documented, but should not be part of the application source and are not big enough to warrant an own repository. For now I just uploaded the svn2git migration scripts there and I intend to upload the ticket migration scripts in the near future.
* No progress for the ticket migration so far. It's a lot of effort with minimal reward (for me: 'fun stuff to code') so please don't expect results anytime soon. This, however, should not further limit the usage of the builtin github issue tracker. So if anyone wants to use it feel free to enable the issues for the freeorion/freeorion repository.
* Could we please move the fo-svn-mirror repository to the freeorion-archive organization? It's irritating for me to see an outdated and, by purpose, duplicate repository in the organization overview and it could mislead other people.
* I created a `freeorion-utilities` repository were developers can put projects related to FreeOrion into. It's intended for utilities, that should be versioned and documented, but should not be part of the application source and are not big enough to warrant an own repository. For now I just uploaded the svn2git migration scripts there and I intend to upload the ticket migration scripts in the near future.
* No progress for the ticket migration so far. It's a lot of effort with minimal reward (for me: 'fun stuff to code') so please don't expect results anytime soon. This, however, should not further limit the usage of the builtin github issue tracker. So if anyone wants to use it feel free to enable the issues for the freeorion/freeorion repository.
* Could we please move the fo-svn-mirror repository to the freeorion-archive organization? It's irritating for me to see an outdated and, by purpose, duplicate repository in the organization overview and it could mislead other people.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: GitHub migration procedure
How would I do that?adrian_broher wrote:* Could we please move the fo-svn-mirror repository to the freeorion-archive organization?
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: GitHub migration procedure
Go to the 'Settings' menu of the repository. Go there to the 'Transfer Ownership' entry of the 'Danger Zone'.Geoff the Medio wrote:How would I do that?
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Re: GitHub migration procedure
I already wanted to inquire about the status of that task, because I really want to enable the issue tracker on github. If we do that now, won't that complicate the ticket migration from SF? You'd have to somehow merge the migrated tickets with the ones that got created on github in the meantime...?adrian_broher wrote:* No progress for the ticket migration so far. It's a lot of effort with minimal reward (for me: 'fun stuff to code') so please don't expect results anytime soon. This, however, should not further limit the usage of the builtin github issue tracker. So if anyone wants to use it feel free to enable the issues for the freeorion/freeorion repository.
Done.* Could we please move the fo-svn-mirror repository to the freeorion-archive organization? It's irritating for me to see an outdated and, by purpose, duplicate repository in the organization overview and it could mislead other people.
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: GitHub migration procedure
Not really. I create 'new' issues anyway. The github API doesn't allow anything else.Vezzra wrote:I already wanted to inquire about the status of that task, because I really want to enable the issue tracker on github. If we do that now, won't that complicate the ticket migration from SF? You'd have to somehow merge the migrated tickets with the ones that got created on github in the meantime...?
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Re: GitHub migration procedure
Apparently Geoff already activated the issue tracker (he has already opened a ticket), so everyone, please make use of this feature.
Re: GitHub migration procedure
Ok, I've updated the OP with things that got decided/done in the meantime.
One question came up for me: github offers a feature for publishing releases, where you can also offer binaries to download. Looks pretty neat, and I'm wondering if we should use it and offer our release installer packages on github too (in addition to SF)?
One question came up for me: github offers a feature for publishing releases, where you can also offer binaries to download. Looks pretty neat, and I'm wondering if we should use it and offer our release installer packages on github too (in addition to SF)?
Re: GitHub migration procedure
If it's not too much trouble, sounds like a good idea to me.
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
Re: GitHub migration procedure
I was looking at the FO Programming wiki page http://www.freeorion.org/index.php/Programming and noticed this line.
What is the desired action, now that the transition from SVN to GitHub is over?
Code: Select all
To submit code changes, make an SVN diff patch file and post it on the forums. Be sure to note that you release your changes under the GPL 2.0 (or later) license.
Re: GitHub migration procedure
Well, ouch. That needs updating, we obviously missed that one.mem359 wrote:I was looking at the FO Programming wiki page http://www.freeorion.org/index.php/Programming and noticed this line.Code: Select all
To submit code changes, make an SVN diff patch file and post it on the forums. Be sure to note that you release your changes under the GPL 2.0 (or later) license.
Creating a pull request for the master branch on our github repo.What is the desired action, now that the transition from SVN to GitHub is over?
Re: GitHub migration procedure
Done.Vezzra wrote:Well, ouch. That needs updating, we obviously missed that one.
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: GitHub migration procedure
After almost two years I'm inclined to say that all developers and contributors have acclimated with git and GitHub. However there are still lose ends on the SourceForge side of things. None of the project pages points to the preferred location for project communication (e.g. this forum or the GitHub issue tracker) and there are other problematic places where an unknowing user could get lost. Could someone with administrative rights give me permissions for the SF project so I can clean up there (SF username marcel_metz)?
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Re: GitHub migration procedure
OK, Done.adrian_broher wrote:Could someone with administrative rights give me permissions for the SF project so I can clean up there (SF username marcel_metz)?
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: GitHub migration procedure
Thanks.Dilvish wrote:OK, Done.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Re: GitHub migration procedure
Yep, my bad, I didn't finish the cleanup back then. The problem was the cleanup of the old SF bug/issue/feature trackers. We wanted to try to migrate the open items to the github issue tracker, but got stuck with this (IIRC you wanted to experiment with some tool, can't remember why that didn't work out). Somewhere down the road it got pushed down on the priority list, and I never got back to it.adrian_broher wrote:However there are still lose ends on the SourceForge side of things.
Well, I guess thanks for cleaning up my mess.