> To support our existing, semi-centralized development model, we'd like > to give have multiple people ownership of the same project.
This is a need we also discussed at my day job. For now, we don't mind if a project is only allowed to have one owner. If ever we want to change the ownership of a project to someone else, we decided to directly fiddle it in the database every time that it's needed, because as of now, we didn't need to implement any other in- house changes to Gitorious to make it work for us, so we decided for the Least Maintenance Effort Road. As we hopefully establish our git practice more solidly over time, we will probably reconsider implementing a proper multiple-ownership strategy for our Gitorious instance. One bad thing, though, is that our employee contracts forbid us to contribute to the public. ...One way around this might be for me to implement the new functionality on personal time, from home, and use that at work. I think there would be no problems this way. Who knows, maybe it's already been implemented in one of the clones? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Gitorious" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gitorious?hl=en -~----------~----~----~----~------~----~------~--~---
