[Systems] Policy for non-responsive maintainers
Bernie Innocenti
bernie at sugarlabs.org
Thu Jan 10 15:23:46 EST 2013
On Thu, 2013-01-10 at 16:37 -0300, Gonzalo Odiard wrote:
>
> Adding permission in ASLO is easy.In GIT is not so easy, maybe only
> Bernie and Alsroot have permission?
>
>Is true we can create a cloned repo, but that have more problems. We
>need point pootle to the new repo
>(and we had this problem a lot in the past), and can be difficult
>finally know where is the last code.
The version of Gitorious that we're running did not come with a web
interface to perform administrative tasks.
I wrote a bunch of SQL queries to change owners for projects and
repositories. Later on, Aleksey figured out how to manipulate the
database from an interactive Ruby prompt. Slightly cleaner, but still
into the sysadmin realm:
http://wiki.sugarlabs.org/go/Service/git
Looking forward, Aleksey and I have planned to rebuild the VM from
scratch and install the latest Gitorious. Migrating the data may turn
out to be difficult and at this point I'm not even sure whether the
latest code comes with a robust admin interface similar to ASLO.
For the time being, please ask alsroot. If he's unavailable, I'll try to
do it. We'd also like to invest some time traning new volunteers for the
Infrastructure Team, but since the learning curve is a little steep I'm
asking in exchange for a bit of commitment to help maintain the service
and respond to emergencies:
http://wiki.sugarlabs.org/go/Infrastructure_Team/Getting_Involved
--
Bernie Innocenti
Sugar Labs Infrastructure Team
http://wiki.sugarlabs.org/go/Infrastructure_Team
More information about the Systems
mailing list