Hi Peter On Thu, Mar 5, 2009 at 5:22 AM, Peter <[email protected]> wrote: > Private projects are protected by using a random slug name, instead of > depending on the project name. As long as the owner of the project and > the collaborators can keep this name secret, the project is safe. I > recognize this is not the best way to do this, but at least for my > small team it works. Look at the FAQ (http://www.gitcentral.com/about/ > faq) and the tutorial (http://www.gitcentral.com/tutorials) pages for > more info.
I think that it's not a very good security measure. But if your "private" project can handle being discovered, then I guess it's enough. I'm currently working on a big (big!) update of gitorious, but it's part of a consulting gig and as such it's not out in the open yet (as per their request). But there's some functionality in place there for managing roles on projects, that you could hook into once it's released. > If anyone wants to quickly have a look, I am hosting this Gitorious > clone at www.gitcentral.com. The source code is available on both > Gitcentral (public project - > http://www.gitcentral.com/projects/gitcentral/repos/mainline) > and Gitorious (http://www.gitorious.com/projects/gitorious/repos/ftsk- > gitorious). Note that on the Gitcentral site I have also provided SSL > protection for sensitive information pages, like the sign-in and > profile pages. Looks nice, what's the idea behind this? You're planning on taking it in a significantly other direction than gitorious.org? I'm not slamming you here on this (gitorious is OSS for a reason), just curious. JS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
