A more stable place would be to put it in the Master tab. I copied and pasted from the git repo yesterday but the descriptions were weak. Miriam On 2/1/13 9:39 AM, "Thomas Brettin" <[email protected]> wrote:
Hi Elizabeth,
I'm building the list of modules for attempted release next week. I got a one sentence to paragraph size description of the service from a lot of the module owners. I'm just pasting those into the kbase services spread sheet "Feb 4 Major' tab. Take what ever you want. We can reorganize later.
Tom On Jan 31, 2013, at 11:49 AM, Elizabeth M. Glass <[email protected]> wrote:
Can we also add in a column on what science domains these services work for? M, MC, P
Elizabeth
----- Original Message ----- From: Thomas Brettin <[email protected]> To: Miriam L. Land <[email protected]> Cc: [email protected], Nomi Harris <[email protected]> Sent: Thu, 31 Jan 2013 07:09:21 -0600 (CST) Subject: Re: [Release-team] Adding columns to services spreadsheet
I want to keep all tabs. I plan to mine this data for research on the progression of the development of a release infrastructure.
Tom
On Jan 31, 2013, at 7:05 AM, "Land, Miriam L." <[email protected]> wrote:
I'm in favor of a master tab. It would be very useful when I need to look up something that was somewhere in an earlier build.
I also don't have a problem deleting the tabs that came before Nov Build, as long as we capture information on old modules that may come up again.
I think the git repo is a great place to start parsing out the descriptions.
Until the redeploy happens this morning, I have time to get this started.
Miriam
On 1/30/13 5:50 PM, "Nomi Harris" <[email protected]> wrote:
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=0Ana5oznWypH2 dFp paE 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
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team
Thomas Brettin 865-603-7760 (cell) [email protected]
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team
Thomas Brettin 865-603-7760 (cell) [email protected]