Page 1 of 2

Moving to GitHub.com: Call for developers - CVS/SVN affected

Posted: Wed Oct 05, 2011 5:28 pm
by garvinhicking
Hi!

As you might have read on the Serendipity blog, the SVN code repository on BerliOS will be going away in December.
Serendipity currently uses the SVN service on their service, so we need to switch.

In the opinion of a few core developers on the forums, the most desirable place to be is GitHub, which has the most promising future and userbase currently, as well as easy-to-use tools.

This posting goes out to the code contributors of the last year. I would like to know your feedback on the move, and if you are interested in becoming a member of the new development place at github.

Basically, anyone familiar with CVS or SVN should easily be able to move to the new code.

The new development idea is like this:

1. People become a member of the "s9y" organization on github: https://github.com/organizations/s9y

2. Those people have full maintaining rights of the Repository: https://github.com/s9y/Serendipity

3. To contribute, you need to first create a user account on github, manage your SSH user keys and then check out the repository:
cd ~
git config --global user.name 'John Doe'
git config --global user.email johndoe@example.com
git clone git@github.com:s9y/Serendipity.git

4. In the "Serendipity" working directory you can now contribute code and merge it simply with
git commit
git push

5. The advantage of git will be for foreign people to easier contribute code, without the need to be a member of the project; we can then simply acknowledge "pull requests" to import foreign changes.


In the first step we will maintain the SVN core portion of Serendipity. In the near future I would like to also maintain the additional templates and plugins on github. Since we are in need of the SourceForge infrastructure to publish those changes, we will setup an automatic process that pushes changes from GIT automatically to CVS. That will also mean that all changes will only occur in GIT, and no longer in CVS. This will then move all development work to a central place, which should motivate people for easier code contributions.

The current list of people that this invitation goes to are:

CVS (plugins, themes) contributors:
fugazza
don_chambers
brockhaus
elf2000
fadoe
ffaat
jhermanns
kleinerchemiker
laemmy
lstrojny
matthiasmees
mgroeninger
mgutjahr
nesges
nightly
omidmottaghi
onli
pigslipstick
slothman
webcompas

Core (SVN) contributors:
brockhaus
donchambers
elf2000
fugazza
jannis
omidmottaghi
slothman
yellowled


Please feel free to discuss this process here, this is also were you can easily tell us that you want to become a member of the github organization!


Regards,
Garvin

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Wed Oct 05, 2011 6:20 pm
by onli
I already am on github and would like to be a part of that group.

ps: username: onli

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Wed Oct 05, 2011 6:26 pm
by Timbalu
I am not at GitHub yet - but would like to be part of it too! Yes, please! :-)

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Wed Oct 05, 2011 6:33 pm
by garvinhicking
I need your usernames :)

(Currently the repo is not there yet, but it'll be populated soon)

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Wed Oct 05, 2011 10:30 pm
by chrisbra
Could I be also part of that group?
Username: chrisbra (Surprise, surprise ;))

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Wed Oct 05, 2011 11:13 pm
by kleinerChemiker
I think I don't need access. I'll send changes in "my" plugin as pm to you.

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Wed Oct 05, 2011 11:48 pm
by oxygenws
Hi Garvin :-)

I am "omidmottaghi" and my username in github is "omid".

Regards.

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Fri Oct 07, 2011 12:27 am
by LazyBadger
Just side opinions of foreigner:
Git+GitHub are overvalued last time... Good and logical infrastructure and team can be formed in another locations (maybe - even more easy)

PS - I'm github (git)|bitbucket (mercurial) user, but prefer groupwork in Assempla Spaces (with any of supported by Assembla SCM)

PPS - if git on github, I'll ask to separate translations (of all) into submodule for easy communication

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Sat Oct 08, 2011 6:47 pm
by blog.brockha.us
I've created an account at github. It's "brockhaus" again. :)

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Tue Oct 11, 2011 7:29 am
by RobA
I had CVS access as "ffaat". I do have an account on GitHub already as "RobAnt"

I have not contributed much to s9y recently, though I do keep aware of the blog and forums, so it is up to the core and current devs if you want to renew my access once migrated to GitHub.

Thanks,

-Rob A>

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Sun Nov 13, 2011 11:06 am
by VladaAjgl
Hi,
I am also on GitHub - "fugazza" again - and ready to commit new translations.
Vlad

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Mon Nov 21, 2011 11:36 am
by blog.brockha.us
Is the plugin repo moved to GitHub already, too?
Or the core repo only yet?

I would like to do some changes on plugins and I don't know where I should fetch the newest version from. :)

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Mon Nov 21, 2011 11:42 am
by Timbalu
As far as I know, they are still at Sourceforge.
I'd like to have them at GitHub too... :-)

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Mon Nov 21, 2011 12:06 pm
by blog.brockha.us
Thanks for the info. So I'll do my plugin updates in the old cvs for now. :)

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Posted: Tue Nov 22, 2011 5:11 pm
by garvinhicking
Hi!

There wasn't much feedback on contributing code yet, so spartacus is still on CVS.

If that picks up and some people want to contribue, I can try to migrate spartacus to github in the near future...

Regards,
Garvin