GitHub migration procedure

Discussion about the project in general, organization, website, or any other details that aren't directly about the game.
Message
Author
User avatar
adrian_broher
Programmer
Posts: 1072
Joined: Fri Mar 01, 2013 9:52 am
Location: Germany

Re: GitHub migration procedure

#196 Post by adrian_broher » Fri Jun 05, 2015 12:50 pm

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.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz

User avatar
Geoff the Medio
Programming, Design, Admin
Posts: 12243
Joined: Wed Oct 08, 2003 1:33 am
Location: Munich

Re: GitHub migration procedure

#197 Post by Geoff the Medio » Fri Jun 05, 2015 2:11 pm

adrian_broher wrote:* Could we please move the fo-svn-mirror repository to the freeorion-archive organization?
How would I do that?

User avatar
adrian_broher
Programmer
Posts: 1072
Joined: Fri Mar 01, 2013 9:52 am
Location: Germany

Re: GitHub migration procedure

#198 Post by adrian_broher » Fri Jun 05, 2015 3:06 pm

Geoff the Medio wrote:How would I do that?
Go to the 'Settings' menu of the repository. Go there to the 'Transfer Ownership' entry of the 'Danger Zone'.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz

User avatar
Vezzra
Release Manager, Design
Posts: 4605
Joined: Wed Nov 16, 2011 12:56 pm
Location: Sol III

Re: GitHub migration procedure

#199 Post by Vezzra » Sun Jun 07, 2015 12:53 pm

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.
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...?
* 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.
Done.

User avatar
adrian_broher
Programmer
Posts: 1072
Joined: Fri Mar 01, 2013 9:52 am
Location: Germany

Re: GitHub migration procedure

#200 Post by adrian_broher » Sun Jun 07, 2015 2:57 pm

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...?
Not really. I create 'new' issues anyway. The github API doesn't allow anything else.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz

User avatar
Vezzra
Release Manager, Design
Posts: 4605
Joined: Wed Nov 16, 2011 12:56 pm
Location: Sol III

Re: GitHub migration procedure

#201 Post by Vezzra » Sun Jun 07, 2015 3:20 pm

Apparently Geoff already activated the issue tracker (he has already opened a ticket), so everyone, please make use of this feature.

User avatar
Vezzra
Release Manager, Design
Posts: 4605
Joined: Wed Nov 16, 2011 12:56 pm
Location: Sol III

Re: GitHub migration procedure

#202 Post by Vezzra » Sun Jun 07, 2015 3:36 pm

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)?

User avatar
Dilvish
AI Lead, Programmer
Posts: 4683
Joined: Sat Sep 22, 2012 6:25 pm

Re: GitHub migration procedure

#203 Post by Dilvish » Mon Jun 08, 2015 5:38 pm

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

User avatar
mem359
Dyson Forest
Posts: 214
Joined: Sun Jun 08, 2014 1:18 am

Re: GitHub migration procedure

#204 Post by mem359 » Fri Mar 24, 2017 2:22 pm

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.
What is the desired action, now that the transition from SVN to GitHub is over?

User avatar
Vezzra
Release Manager, Design
Posts: 4605
Joined: Wed Nov 16, 2011 12:56 pm
Location: Sol III

Re: GitHub migration procedure

#205 Post by Vezzra » Fri Mar 24, 2017 2:29 pm

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.
Well, ouch. That needs updating, we obviously missed that one.
What is the desired action, now that the transition from SVN to GitHub is over?
Creating a pull request for the master branch on our github repo.

User avatar
Vezzra
Release Manager, Design
Posts: 4605
Joined: Wed Nov 16, 2011 12:56 pm
Location: Sol III

Re: GitHub migration procedure

#206 Post by Vezzra » Fri Mar 24, 2017 2:35 pm

Vezzra wrote:Well, ouch. That needs updating, we obviously missed that one.
Done.

User avatar
adrian_broher
Programmer
Posts: 1072
Joined: Fri Mar 01, 2013 9:52 am
Location: Germany

Re: GitHub migration procedure

#207 Post by adrian_broher » Sun Apr 30, 2017 12:01 pm

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

User avatar
Dilvish
AI Lead, Programmer
Posts: 4683
Joined: Sat Sep 22, 2012 6:25 pm

Re: GitHub migration procedure

#208 Post by Dilvish » Sun Apr 30, 2017 5:15 pm

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)?
OK, Done.
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0

User avatar
adrian_broher
Programmer
Posts: 1072
Joined: Fri Mar 01, 2013 9:52 am
Location: Germany

Re: GitHub migration procedure

#209 Post by adrian_broher » Sun Apr 30, 2017 5:29 pm

Dilvish wrote:OK, Done.
Thanks.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz

User avatar
Vezzra
Release Manager, Design
Posts: 4605
Joined: Wed Nov 16, 2011 12:56 pm
Location: Sol III

Re: GitHub migration procedure

#210 Post by Vezzra » Mon May 01, 2017 1:13 pm

adrian_broher wrote:However there are still lose ends on the SourceForge side of things.
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.

Well, I guess thanks for cleaning up my mess. :oops:

Post Reply