Hi Andrew, Right now, Google Project Hosting is only offered for open source projects. So, you need to have some source code available. However, there are certainly many open source projects that release a small amount of code at first and gradually add more over time. If there is any part of your project's source code that could be released now, that would be a start. I'd really encourage you to do it. Please don't want until you can release everything in a big bang, that's not a good way to build community around your project anyway.
As for restricted issues, again the assumption is that what you are doing is open source so most things don't need any restrictions. However, if you have issues related to sensitive topics, e.g., security holes or parts of the code that you have not released yet, you can restrict access to them. The simplest way to do it is to add the Restrict-View-Commit label to the issue. That means that only users who have permission to commit source code changes will have permission to view that issue. You can get more fine-grained by making up your own custom permissions and granting them to certain project members and not others. E.g., Restrict-View-SecurityTeam and then grant the SecurityTeam custom permission to a subset of project members. You can also make specific issues completely need-to-know by using a custom permission that you have not granted to anyone, e.g., Restrict-View-NoOneHasThis. The issue owner and Cc'd users will still have the ability to view such issues. Project owners are not blocked by Restrict-* labels, so there is no way to lock yourself out of an issue. All the details are here: http://code.google.com/p/support/wiki/Permissions Thanks, jason! On Wed, Sep 22, 2010 at 3:05 PM, AndrewTheArt <[email protected]> wrote: > Hello - > > We are developing a web application for a public university that will > be used by the staff and students to manage advising appointments, > course requests, etc. > > At this stage, we have not decided to open source yet - it will take > work to removing the branding / logos from the product, and the > product is not yet 100% complete (maybe 90% complete, including > extensive testing). We very well might consider open-sourcing the > product when it is in RC condition and we have the time to remove the > branding. > > Question is: can we use Google Code as a bug tracker for this > application, without having any code uploaded to our project homepage? > Right now, we are using Google Docs as a bug tracking system - > specifically, we are entering bugs in a spreadsheet. It works, but it > would be much nicer to have a legitimate system in place to track > bugs. > > The other question is: how do you make bugs private to specific > people? I believe this feature has been implemented, but I cannot > figure out how to do it. > > Regards, > Andrew > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" 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/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" 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/google-code-hosting?hl=en.
