Oh, one other thing is that each GPH project has just one wiki. So, all your project docs could go there.
You could keep the documents separate by (a) following a page naming convention that puts the subproject name into each page name, (b) using a label like Proj-Web or Proj-Android and exposing that label value in the default columns for the wiki page list *you can apply multiple labels to the pages that apply to multiple subprojects), and/or (c) manually creating an "intro" wiki page for each subproject that has links to the pages relevant to that project. The word "manual" makes it sound like a lot of work, but that's exactly what you would do with most other wiki systems. Thanks, jason! On Wed, Jan 12, 2011 at 4:32 PM, Ryan Panning <[email protected]> wrote: > Thanks for the feedback Jason! > > The branches and trunk checkout settings are what I was thinking about > with option 1. Just wasn't sure how much Google Project Hosting really > cares about folder structure. If anything I'd set the /web/branches as > the default branches view as that would be the "main" piece of the > project. For now I think I'll setup option 2 just to keep things in > the same project but yet somewhat separate. The complete separation > wouldn't be needed to begin with. Thanks again for your input, just > helps hearing others opinions. > > ~ Ryan > > On Jan 12, 4:07 pm, Jason Robbins <[email protected]> wrote: >> Hi Ryan, >> >> Go with whatever works for you. Option 2 seems fine. >> >> Why do you say that Google Project Hosting would prefer that you did >> option 1? The only reason that I can think of is that the branch >> review view defaults to assuming that your branches all live under >> /branches. But, that is easily worked around if you choose option 2, >> just go to your Administer tab, Source subtab and set the location of >> your branches to "/". Then you can do branch reviews anywhere. >> >> As for option 3, it is true that separate projects might separate >> things too much. A couple of features help to tie separate projects >> back together a bit. You can define user groups on groups.google.com >> and then make those groups members of your projects, so that adding a >> new developer to the group gives them permissions in all the projects >> that have that user group. Also, you can't see a combined issue list >> yet, but you can have issues in one project autolink to or block on >> issues in another project using the syntax "issue >> projectname:issue_id". >> >> Thanks, >> jason! >> -- >> Google me at:http://www.google.com/profiles/jrobbins >> >> On Wed, Jan 12, 2011 at 12:40 PM, Ryan Panning <[email protected]> wrote: >> > Hi, I'm starting a project which will have several "apps" associated >> > with the one project. Looking for opinions / feedback on the best way >> > to organize the folder structure in my Google Code SVN. From what I >> > could find, there are 3 different options. >> >> > 1. Create sub-folders in the existing folder structure. >> > /branches/web >> > /branches/android >> > /branches/ios >> > /tags/web >> > /tags/android >> > /tags/ios >> > /trunk/web >> > /trunk/android >> > /trunk/ios >> >> > 2. Create new root folders for each app and the SVN folders inside. >> > /web/branches >> > /web/tags >> > /web/trunk >> > /android/branches >> > /android/tags >> > /android/trunk >> > /ios/branches >> > /ios/tags >> > /ios/trunk >> >> > 3. Create separate Google Projects for each app. >> >> > I am leaning towards option 2 as they will have almost completely >> > separate code bases. However, I'm thinking the Google Code system >> > would probably like option 1 better. And I just don't like option 3 >> > because I'd like everything somewhat together. Any personal thoughts? >> > Thanks for any feedback! >> >> > -- >> > 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 >> > athttp://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. > > -- 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.
