Move part of macports infrastructure to GitHub

[Mark Anderson]

Yeah, I agree with Ivan, the big deal is Github. Git is great, but hg
offers a lot of the same stuff. As to Ryan's objections, I too had those
same objections after working with SVN and CVS for almost 2 decades. But
once I switched, I wondered why I hadn't switched earlier. I'm sure those
of us in the community would be more than happy to help move things over, I
know I would. I've been wanting to get more and more involved for a while.
And I know Github pretty well. I also use Github Enterprise at work.

Not for nothing, but that search turned up roughly 22 pages of personal
Macports repos. (alhtough a few referenced "Macports sucks" which I don't
like, but eh. It was more positive than negative.

Mark





—Mark
_______________________
Mark E. Anderson <emer at emer.net>


On Sun, Mar 16, 2014 at 3:13 PM, Ivan Larionov <xeron.oskom at gmail.com>wrote:

> Actually main thing here isn’t git, but github. It’s interface and features
> take contribution process to the next level. It’s so easy — just fork,
> commit
> and send pull request.
>
> I understand that someone could like mercurial more and we have bitbucket,
> but actually, I see people use github more and like it.
>
> --
> With best regards, Ivan Larionov.
>
> On 16 марта 2014 г., at 22:42, Sean Farley <sean at macports.org> wrote:
>
>
> Ivan Larionov <xeron.oskom at gmail.com> writes:
>
> I want to start this discussion mainly about ports tree, but actually base
> and some other stuff could use github and infra around it as well. I
> understand this is not so easy and may be you already discussed it and may
> be already decided not to do, but there are huge pros:
>
> * git >> svn
> * pull requests are awesome! No need to poke around with patch files
> attached to tickets
> * nice UI, tools and infra around
>
> which will result in more pros:
>
> * people will look at macports more positively
> * and will contribute more!
>
> Actually I see lot of people keeping their local ports at github:
> https://github.com/search?q=macports&type=Repositories&ref=searchresults
>
> What do you think?
>
>
> I know this is a hot topic but I will try to avoid any flame wars.
>
> If MacPorts really wants to switch to distributed version control, then
> I would suggest Mercurial. I have experimented with using Mercurial for
> the MacPorts repo and found that the mercurial UI is much, much more
> consistent than git coming from Subversion.
>
> I've actually maintained a repo with merges, tags, and branches
> correctly merged in here:
>
> https://smf.io/macports
>
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140316/d32be815/attachment-0001.html>