Poll: mirror code on github?

8 views
Skip to first unread message

Fabio R.

unread,
Dec 22, 2009, 6:48:42 PM12/22/09
to Outlet ORM
Hi all,

Let's say that I'm a Git / Github lover and I'm willing to start mirroring our SVN repository on github in order to ease code contributions and help out build an even better framework.

So, how many of you are familiar with git? Would you contribute more with the framework if the code was hosted github?

For those who has never heard about git and github, you might be interested in reading:
  http://whygitisbetterthanx.com
  http://learn.github.com/
  http://quiteuseful.co.uk/post/128007163/introduction-to-git


Regards,
--
Fábio Rehm

Jonathan Ariel

unread,
Dec 22, 2009, 8:39:39 PM12/22/09
to outle...@googlegroups.com
+1

--

You received this message because you are subscribed to the Google Groups "Outlet ORM" group.
To post to this group, send email to outle...@googlegroups.com.
To unsubscribe from this group, send email to outlet-orm+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/outlet-orm?hl=en.

Richard Quadling

unread,
Dec 23, 2009, 11:06:00 AM12/23/09
to outle...@googlegroups.com
2009/12/22 Fabio R. <fgr...@gmail.com>:
> --
>
> You received this message because you are subscribed to the Google Groups
> "Outlet ORM" group.
> To post to this group, send email to outle...@googlegroups.com.
> To unsubscribe from this group, send email to
> outlet-orm+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/outlet-orm?hl=en.
>

As someone who has only ever contributed to existing OS projects
(rather than creating/maintaining one), I'd be interested in an honest
opinion on why NOT to choose GIT over a pre-existing brand X. At least
from a technical perspective.

I'd say issues related to learning the new tools would be the biggest
non technical hurdle, but given that's nothing perfect, I'd guess
there are places where git does not excel.

And, as a Windows user, who is quite happy with mainly using
TortoiseSVN via explorer and the occasional svn via the command line,
git (I believe) is cli only at the moment.


Regards,

Richard.

--
-----
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling

Jonathan Ariel

unread,
Dec 23, 2009, 12:59:36 PM12/23/09
to outle...@googlegroups.com
Richard,
It's really hard to keep track on patches sent and branches. And if you want to contribute it's much easier for the developer.
Also you have things like http://www.mercadolibre.com.ar/org-img/keywords to be able to use git in windows. :)

Jonathan

Jonathan Ariel

unread,
Dec 23, 2009, 1:00:02 PM12/23/09
to outle...@googlegroups.com
Upss... sorry... the link is: http://code.google.com/p/tortoisegit/

Fabio R.

unread,
Dec 23, 2009, 2:03:44 PM12/23/09
to outle...@googlegroups.com
Hi Richard,

Thanks for the feedback. Just to make things clear, the idea is to MIRROR the code on github, not MIGRATE, people would still be able to checkout the code from SVN. But on github you'll also be able to download a Zip package of any branch directly from the site :-)


As said by Jonathan, the main reason to mirror the code on github is that it will simplify A LOT contributions to the framework. The process would be like this:
  1. fork our repository
  2. git clone (same as svn checkout) your repository
  3. work on your local repository
  4. push changes to github
  5. send us a pull request on github or an email to the list explaining your work
Then we can merge your code to our main repository and other people can start using it. Thats about it, we can find out exactly what you've done and we dont need to give you write permission on our repository. That's a lot better than sending patches and explaining all the changes on the mailing list, we'd just have a look at your commits and log messages. What do you think?

I'm also available to help out those interested in learning how to use it.


As a personal experience, I used to have Windows as my main SO and also got used to SVN and TortoiseSVN (to be honest, I've never used SVN from the command line), nowadays i pretty much use Git / Github for all of my stuff and I don't miss SVN at all.
Because of its distributed nature, Git encourages you to do smaller commits and I end up I commiting all the time. That means I pretty much just do 'git commit -a "commit message"' all the time. Because of that I don't miss a GUI at all, I'm happy with just gitk (which I think works on windows) to look at diffs, log messages and commit graphs.
The other reason for moving to git is that I'm able to version control my code when I'm disconnected (inside an air plane for example).

A reason not to chose GIT over other brand apart from having to learn it... Sorry but I cant think of any right now.


Cheers,
--
Fábio Rehm

Richard Quadling

unread,
Dec 31, 2009, 8:27:54 AM12/31/09
to outle...@googlegroups.com
2009/12/23 Fabio R. <fgr...@gmail.com>:

> Hi Richard,
>
> Thanks for the feedback. Just to make things clear, the idea is to MIRROR
> the code on github, not MIGRATE, people would still be able to checkout the
> code from SVN. But on github you'll also be able to download a Zip package
> of any branch directly from the site :-)
>
>
> As said by Jonathan, the main reason to mirror the code on github is that it
> will simplify A LOT contributions to the framework. The process would be
> like this:
>   1. fork our repository
>   2. git clone (same as svn checkout) your repository
>   3. work on your local repository
>   4. push changes to github
>   5. send us a pull request on github or an email to the list explaining
> your work
> Then we can merge your code to our main repository and other people can
> start using it. Thats about it, we can find out exactly what you've done and
> we dont need to give you write permission on our repository. That's a lot
> better than sending patches and explaining all the changes on the mailing
> list, we'd just have a look at your commits and log messages. What do you
> think?

Aha. I see. That sounds extremely useful. By not having a local server
(just a repository), it is easier for me to log my own changes (many
and small).

If I so wish I can then push all my changes to github when I'm happy to share.

Hmmm. Lots of possibilities.

Thank you for your reply.

Reply all
Reply to author
Forward
0 new messages