Gogs port: A painless self-hosted Git service

Matthew Seaman matthew at FreeBSD.org
Sun Dec 13 11:49:21 UTC 2015


On 13/12/2015 09:22, Yuri wrote:
> Some time back it was a discussion on this ML about how to best submit
> patches to FreeBSD ports and base system.
> One of the problems standing in the way of improvements was the lack of
> open source web software to manage public submissions.
> 
> This problem is now addressed. I created a port for Gogs: "A painless
> self-hosted Git service". It is the open source equivalent of GitHub,
> with pretty much similar functionality.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205283
> 
> Can FreeBSD use it for the pull requests? Maybe using git ⇆subversion
> convertor?
> 
> Anyway, Gogs is among the nicest web-based systems I saw.
> 

Gogs looks pretty cool, and having it in the ports tree seems like a
very good idea to me.  However, there's a big difference between
'working like github' and 'being github.'

The big advantage of being able to use pull requests on Github is that
so many people who work on open source projects are already setup to use
Github.  They've already jumped through all the hoops necessary for them
to be able to easily clone a repo, develop some changes and submit them
back to the original project.  Having a low barrier to entry like that
is a really big deal.

Now, once a pull request has been submitted, so long as it gets dealt
with somehow, that will satisfy the original submitter.  It doesn't just
have to be merged into the cloned repository on github directly.

There was some talk about taking each pull request and automatically
feeding the diffs into Phabricator[+] and/or raising tickets in
Bugzilla[*] which would be a really neat thing, but it hasn't happened
yet.  Anyone coming up with workable code to be able to do that would be
welcomed with cries of joy.

	Cheers,	

	Matthew

[+] You can use oauth to log into the FreeBSD Phabricator instance using
your credentials from Github.  It's almost like they were planning for
this sort of workflow...

[*] Maybe that was in the context of the base system, but the same
mechanisms would work for ports or docs.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 957 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20151213/40721fb3/attachment.sig>


More information about the freebsd-ports mailing list