Hi, I agree on moving plugin repositories into github. I think we can learn from how to manage Jenkins plugin (https://github.com/jenkinsci). I heard that Jenkins organization has all users including each owners/maintainers and give proper permission to ones for their plugin repository.
thanks, Tetsuya On Sunday, June 22, 2014 6:22:49 PM UTC+9, RjOllos wrote: > > Many users have chosen to host their plugins on GitHub, with a stub page > on trac-hacks that points to the GitHub project. The idea of creating a > trac-hacks organization on GitHub (0) came to mind again when discussing > with a user whether to move some plugins to GitHub (1). > > The general idea I have is to try to add users hosting plugins on GitHub > to the organization, and to associate their repository with the > organization. The aim will be to leave users in control of their > repositories, but also allow the trac-hacks admin team to assist with > passing ownership of repositories and granting access to other users, in > cases that the repository owner gives permission for access or chooses to > abandon the repository. This would give us the ability to extend the > AdoptingHacks (3) policies to plugins hosted on GitHub. > > Other advantages would be, making it easier for users to find plugins > hosted on GitHub, and allow us to extend our index (3) to plugins hosted on > GitHub. > > It's not clear to me yet what is going to work best as far as creating > teams. We could create a single developers team, have a team for each > trac-hacks user (e.g. team "mitar" for mitar's plugins [4]) or a team for > each plugin. Having a team for each plugin would give the most control over > granting access to a single user for a single repository. Later on, I hope > we can extend the capabilities to integrate trac-hacks with GitHub and sync > repositories between trac-hacks and GitHub. There are lots of possibilities > there and hopefully there is interest from developers to create the > features. > > I'm hoping to get feedback from other developers and users, in terms of > what the best approaches might be. If we develop a good approach for > handling plugins on GitHub, we can later extend it in a similar way to > BitBucket, SourceForget, GoogleCode or whatever other sites are relevant > and provide the necessary organization capabilities. > > (0) https://github.com/orgs/trac-hacks > (1) http://trac-hacks.org/ticket/11832#comment:1 > (2) http://trac-hacks.org/wiki/AdoptingHacks > (3) http://trac-hacks.org/wiki/HackIndex > (4) http://trac-hacks.org/wiki/mitar > -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
