So, some general thoughts here. ;) I think gitlabhq is nice looking and could be very handy to have around and popular with Fedora folks. The first thing to overcome will be to package it up. The hangup there is likely to be mod-passenger, which is needed for rails. See: https://bugzilla.redhat.com/show_bug.cgi?id=470696 There is progress though, so not all hope is lost. ;) So, packaging it and it's deps is the first step. There's no telling if/when this might be done, so this could be bad for a summer coding project where you have to be done in X time. Next, the process of getting something deployed is outlined in: http://fedoraproject.org/wiki/Request_For_Resources https://fedoraproject.org/wiki/Request_for_resources_SOP It's really important while testing things in a dev instance, and staging that we get a _group_ of people who understand the application and how it works and how to maintain it. We really really really don't want to deploy something just to have no one around to keep it alive and vibrant down the road. A final note is that we have 0 ruby applications currently. So would likely be a learning curve on how best to deploy things or manage them. :) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
