My preference is for a master tab on the same document (but am fine with either). ----- Original Message ----- From: Nomi Harris <[email protected]> To: Dan Olson <[email protected]> Cc: [email protected] Sent: Wed, 30 Jan 2013 16:50:42 -0600 (CST) Subject: Re: [Release-team] Adding columns to services spreadsheet Right, I don't want to add another doc either! That's why I was asking if I could just add these two columns to the Services doc. I think they'd be useful to the people who are on the Build teams as well (maybe not so much to the people on the release team, since we already pretty much know the info that will be in those columns). I'm ok with either adding it to the Feb tab or making a new "master" tab. Nomi Harris Project Manager, KBase On Jan 30, 2013, at 1:33 PM, Dan Olson <[email protected]> wrote:

I'm all for adding a "master" tab to the services spreadsheet with the static information that doesn't change every release.

I really don't want to add another doc - right now we have - A punch list doc An email template doc A trac wiki page A services spreadsheet

As time goes on the more info repositories we have the more opportunity for them to diverge and confusion to occur.

----- Original Message -----

...

From: "Miriam L. Land" <[email protected]> To: "Nomi Harris" <[email protected]>, [email protected] Sent: Wednesday, January 30, 2013 3:25:48 PM Subject: Re: [Release-team] Adding columns to services spreadsheet

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

_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team

_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team