Re: Red5 on GitHub

Yeah, Git really is more designed for single project repositories, which makes more sense to me at least. One project per repository means clean separation of goals. With my Maven integration, everything will be separated into different Maven modules anyway, so it makes sense.

Is there any good reason why we have one massive tree in SVN for every thing that's ever had anything to do with Red5? Wouldn't it make more sense to have red5-server, red5-webapp-root, red5-webapp-installer, red5-webapp-*, red5-plugin-admin, red5-plugin-auth, red5-plugin-*, etc? This also makes issue reporting a lot easier as if each is a separate repository, we get separate error reporting for each project. 

Other than bad experiences and than the the initial hurdle of migrating everything to separate Git repositories, do you guys have any other problems with the migration?

Paul, I'd be more than happy to get you up to speed on migrating between SVN and Git, ie: git clone == svn checkout, etc. 

Thanks,

 - TK

On Tue, Jan 17, 2012 at 2:44 PM, Mondain <mondain@...> wrote:

I'm the opposite, I despise git at-the-moment; but that may be because I started working with it in a repo that had submodules. What a nightmare.

On Tue, Jan 17, 2012 at 9:14 AM, Tyler Kocheran <rfkrocktk@...> wrote:

On Tue, Jan 17, 2012 at 12:08 PM, Mondain <mondain@...> wrote:

We already had a github repo but its empty. 

https://github.com/mondain/red5 

Not in a big hurry to move off of google though ;)

I figured you might say something like that ;) Well, looks like I have my task cut out for me. I can't stand using SVN ever since I learned Git, so at the very least, this will encourage me to work on Red5.

 

Paul

On Tue, Jan 17, 2012 at 7:44 AM, Tyler Kocheran <rfkrocktk@...> wrote:

Jon,

No, sorry, this isn't official. I love Git and would like to see Red5 migrate to Git at some point, so I did it myself. Maybe the team will ultimately want to get over to Git and GitHub. In any case, I've done the legwork. Due to the way I've done things, I can still pull changes from Google Code over SVN into my Git repository to keep this up to data with Google Code. 

Using Git and GitHub makes Red5 even more available to the general public, as being able to fork Red5 is just a button-click away on GitHub. 

Thanks,

 - TK

On Tue, Jan 17, 2012 at 10:41 AM, Jon V. <sybersnake@...> wrote:

Is this a policy change or do you just want to use git instead of svn?

On Tue, Jan 17, 2012 at 10:38 AM, Tyler Kocheran <rfkrocktk@...> wrote:

Team,

As a part of my started Maven migration, I've also pulled Red5 into a Git repository (all commits, branches, and tags are intact) and have pushed it to GitHub. I have a few things left to do like fix commit author names and emails, but this is in the near future.

We have a TON of old, stale branches which I'd like to delete, but I'm going to wait until I get some feedback from the team. 

If you'd like to check out my Maven migration, you can see it in the "maven" branch. 

GitHub: github.com/rfkrocktk/red5-server

Thanks,

 - TK

--
http://gregoire.org/
http://code.google.com/p/red5/

--
http://gregoire.org/
http://code.google.com/p/red5/