Moving source code to GitHub from SVN

Do you have a question or problem? Read this forum first! Someone has probably already asked the same thing in the past. Do not ASK questions here!

Moderators: Moderators, Documentation Writers

Are you excited?

Git ROCKS!
30
70%
SVN is the BEST!!!
7
16%
Meh
3
7%
About time...
3
7%
 
Total votes: 43

Message
Author
itsrachelfish
Developers
Developers
Posts: 50
Joined: 27 Feb 2012, 12:50
Noob?: No

Moving source code to GitHub from SVN

#1 Post by itsrachelfish »

Hi all, this is a public discussion thread so feel free to reply.

Edit:
The OpenKore project has to moved to GitHub as of Feburary 28th 2016. You can see the new project here: https://github.com/openkore/openkore

The old SVN repo has been made read-only and will remain online for now. The entire project has been converted from SVN to Git and restructured to allow people to simply clone the repo and start using kore. Plugins are now also included in the main repo but only specific plugins are enabled by default (like the macro plugin).

Edit 2:
If you were a developer with svn access who wants to be added as an official developer in git, please open an issue on GitHub with your SourceForge username or post here in this thread with both your GitHub account and SourceForge username.

Original Post:
If you've ever contributed to the OpenKore project and want the contributions to appear in your GitHub account, please post in this thread with your username on SourceForge and the email for your GitHub account. We can update this information automatically when the import is initially run. After that, we won't be able to change the history. All developers who haven't replied to this thread will fall back to using their SourceForge email address. Because of the conversion from CVS to SVN, there are a few users who do not have SourceForge accounts. To account for them, we've created fallback emails [username]@openkore.com. Though it's worth noting these users haven't been active since 2003-2007, so they probably won't mind anyway...

For the record, SVN is going to be locked from new changes on February 28th!
Tired of waiting for answers on the forums?
Want to talk to OpenKore experts?

Hang out on the #OpenKore IRC!

ChrstphrR
Testers Team
Testers Team
Posts: 42
Joined: 09 May 2010, 17:30
Noob?: No
Location: Northern Alberta, Canada

Re: Moving to GitHub

#2 Post by ChrstphrR »


otaku
Human
Human
Posts: 28
Joined: 29 Nov 2013, 21:50
Noob?: No
Location: Brazil
Contact:

Re: Moving to GitHub

#3 Post by otaku »

Great news. I hope this brings Openkore development back from the dead. :D

I was wondering why "breaking" the project in multiple repositories is better than having all in a single one? Say, like having a main repository with the core stuff (confpack, tablepack, fieldpack and src) and have optional stuff in their own repositories like: plugins, tools, etc.
I'm watching my TV or is it watching me?

itsrachelfish
Developers
Developers
Posts: 50
Joined: 27 Feb 2012, 12:50
Noob?: No

Re: Moving to GitHub

#4 Post by itsrachelfish »

otaku wrote:Great news. I hope this brings Openkore development back from the dead. :D

I was wondering why "breaking" the project in multiple repositories is better than having all in a single one? Say, like having a main repository with the core stuff (confpack, tablepack, fieldpack and src) and have optional stuff in their own repositories like: plugins, tools, etc.


Hey, great question and thanks for bringing it up.

Originally the idea was to keep the project structure the same way it is in SVN, but after a long conversation on IRC with ChrstphrR and allanon, we've decided that the way the project is set up now is seriously unnecessary.

Our plan is to convert the project to git and then rearrange everything so we'll be able to simply clone the repo and start running kore. Plugins are going to be included as well, but we'll be changing sys.txt to only load specific plugins by default.

I'm going to edit my original post now to include the changes we discussed.
Tired of waiting for answers on the forums?
Want to talk to OpenKore experts?

Hang out on the #OpenKore IRC!

Kaspy
OpenKore Monk
OpenKore Monk
Posts: 401
Joined: 08 Jun 2012, 15:42
Noob?: No
Location: Brazil

Re: Moving to GitHub

#5 Post by Kaspy »

Many plugins have a struct folder with snv-pattern: brach, tag and trunk.
What to do?
Image

itsrachelfish
Developers
Developers
Posts: 50
Joined: 27 Feb 2012, 12:50
Noob?: No

Re: Moving to GitHub

#6 Post by itsrachelfish »

Kaspy wrote:Many plugins have a struct folder with snv-pattern: brach, tag and trunk.
What to do?


In the main openkore repo we're going to rearrange everything to only use the trunk version of subprojects. If you're actively maintaining a plugin and want to preserve the versions, we have a couple options:

    - Make a single "archives" repo which contains all of the branches and tags from every project in SVN (Easiest)
    - Convert individual subprojects into their own repo and preserve the tag / branch structure (Cleanest)

Is there a particular plugin you're concerned about?
Tired of waiting for answers on the forums?
Want to talk to OpenKore experts?

Hang out on the #OpenKore IRC!

4epT
Developers
Developers
Posts: 592
Joined: 30 Apr 2008, 14:17
Noob?: No
Location: Moskow (Russia)
Contact:

Re: Moving to GitHub

#7 Post by 4epT »

username on SourceForge: ya4ept
email for GitHub account: ya4ept@ya.ru
All my posts are made by machine translator!
¤ Manual ¤ Anti BotKiller ¤ Packet Extractor v3 ¤
Image
Image

lututui99
Developers
Developers
Posts: 30
Joined: 18 Sep 2012, 22:27
Noob?: No

Re: Moving to GitHub

#8 Post by lututui99 »


kLabMouse
Administrator
Administrator
Posts: 1301
Joined: 24 Apr 2008, 12:02

Re: Moving to GitHub

#9 Post by kLabMouse »

If anything try to use our Dev's e-mail from board or SourceForge. Also. We tried to move OpenKore to GitHub long time ago. so there is a team and members there already.

itsrachelfish
Developers
Developers
Posts: 50
Joined: 27 Feb 2012, 12:50
Noob?: No

Re: Moving to GitHub

#10 Post by itsrachelfish »

kLabMouse wrote:If anything try to use our Dev's e-mail from board or SourceForge. Also. We tried to move OpenKore to GitHub long time ago. so there is a team and members there already.


Yep! isieo gave me admin access in the GitHub organization and we've been doing all of our work in there. I added a few people's github accounts manually and the rest of the accounts were based on the SourceForge forwarding emails.

I made a new page on the wiki as well: http://openkore.com/index.php/Git

It's so nice to see you around kLab, you should drop by IRC some time. :)
Tired of waiting for answers on the forums?
Want to talk to OpenKore experts?

Hang out on the #OpenKore IRC!

Post Reply