Would it make sense to put the common name, repo name, contact(s), and description in a doc by itself? It could be cumulative across all releases. Miriam On 1/30/13 3:39 PM, "Nomi Harris" <[email protected]> wrote:
Today I talked to Elizabeth, who is starting to work on materials for the User Zone on the website, which will include tutorials, a new User Guide, and more. She is also helping to write the text about the individual services that is currently on http://www.kbase.us/developer-zone/services/ . Elizabeth asked me for two pieces of information for each service: the git repo name and corresponding "human language" name of each service (for example, Central Store Service is in the kb_seed repo--you'd never guess that if you didn't already know), and also whether the service is internal-only or user-facing. I think this information would be useful to have on the Services spreadsheet (in fact, that spreadsheet used to have the human and git repo names for each service, but lost that at some point), but it already has a lot of columns, so I'd like permission to add those two. The Feb 4 Major tab (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaE JzOUdfMV8zN0Y3Vm5YM095aWc#gid=14) is empty so far, so maybe we can start from scratch and think about what columns make sense. There were some on the previous tabs that we probably don't need anymore. Thanks, Nomi Harris Project Manager, KBase
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team