Date: Mon, 14 Dec 2015 08:54:43 +0100 From: =?UTF-8?Q?Torsten_Z=c3=bchlsdorff?= <mailinglists@toco-domains.de> To: Matthew Seaman <matthew@FreeBSD.org>, freebsd-ports@freebsd.org Subject: Re: Gogs port: A painless self-hosted Git service Message-ID: <566E75C3.9090601@toco-domains.de> In-Reply-To: <566D5B3C.4040602@FreeBSD.org> References: <566D38ED.7050406@rawbw.com> <566D5B3C.4040602@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Aloha, On 13.12.2015 12:49, Matthew Seaman wrote: > 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. I did this often for different processes. I won't work on the issue this year - there is do much open to do. But please write me a desired workflow and the needed requirements and i will do this in the next year. Just 3 weeks to go :D Greetings, Torsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?566E75C3.9090601>