I would love to see a GitLab trial at Apache infrastructure - I feel uncomfortable at directing other developers to look at http://git-wip-us.apache.org/ - the rendering of a repository does not even tell you where to clone from!
GitLab Installation is fairly easy, there's also a GitLab docker image that is pretty easy to test: https://registry.hub.docker.com/u/genezys/gitlab/ On 5 March 2015 at 00:14, Niclas Hedhman <nic...@hedhman.org> wrote: > On this note; Git without Github is like sex without a partner, sufficient > but not very satisfactory. Github option has been explored in the past, and > due to various reasons, it was not possible to achieve. > But, during my last 2-3 year absence, has the GitLab[1] option been > discussed and/or tried? GitLab is open sourced, can run on our infra and > has many of the essential features of Github. > But perhaps people are satisfied enough with the Github mirroring that is > already in place, but with GitLab in house, we could (in theory) add > features around licensing (like ICLA style assurance, similar to Jira), and > non-committers could(!) be allowed a direct route to the horse's mouth... > > Although the Enterprise system cost money, my guess is that GitLab would be > happy to waive fees and give us access to EE. > > > Just a thought. > > [1] https://about.gitlab.com/features/ > > // Niclas > > > > On Thu, Mar 5, 2015 at 5:06 AM, Christopher <ctubb...@apache.org> wrote: > >> All, >> >> Has any thought been put into leveraging GitHub pages for project >> documentation, static site hosting? A lot of www.apache.org is simple >> static content, as are project pages. Since a lot of projects are now using >> git, and we mirror projects in GitHub, perhaps we can help the individual >> projects maintain their site's static content by simply committing to a >> gh-pages branch for their project? >> >> Since it's just static content which is still hosted and controlled by ASF, >> but simply placed in a way that GitHub can render it from the mirrors, I >> don't think there's too many issues of concern, but wasn't sure if >> anybody's put any thought into it. I know it would certainly be easier for >> some projects than using the existing CMS system with SVN (especially those >> otherwise developing exclusively with Git). >> >> It might "just work" today, but I haven't tried it. I'd be willing to work >> with INFRA to help experiment with it, though (especially if we wanted to >> try out the CNAME feature). >> >> More info: https://pages.github.com/ >> >> -- >> Christopher L Tubbs II >> http://gravatar.com/ctubbsii >> > > > > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
