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?

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

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.

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

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?

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?

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.

Who is online

Users browsing this forum: No registered users and 0 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum