toggle quoted messageShow quoted text
That makes a lot of sense.
Going to be an exciting Monday for both SSC and TSC. Looking forward to seeing everyone. Workflowy agendas will be locked before the 10am us eastern TSC call monday,.
Exactly. Just as was mentioned on the last SSC call, my apologies I don't remember who, mentioned that it's best practice to open a branch as a "sandbox." Then once we all gain approval, we can then merge to master (in this case it'll be the location you mentioned
Showing great initiative, as always. Right on.
The current location for the specification doc is:
Regardless of branch, the docs in this folder are the location we should use for specs, unless we decide otherwise. (There is an open question of whether we should do docs, epics and other planning in a separate repo, but so far, the consensus is to keep
it all in the same repo.)
All - just a follow up. Brian C just created a branch of us to create a "Specification" sandbox. I just merged the NFR document. I'll work on a Functional document shortly. Please see below quick link.
I'll keep my fork updated with this branch and will PR into master when we are all in agreement.
Thanks. Any preference on .md or .doc?
-------- Original message --------
Date: 4/2/20 7:34 PM (GMT-05:00)
Subject: Re: [baseline-ssc] Action Item from 1st Meeting: Daniel Norkin
Should be ready now for you to commit something to docs folder. Once merged to master, should be in docs.
will do. then we will wait for the completion from Brian C and I'll bring that specification document into the doc folder in the baseline repo
It's a good thing for docs. Stand by on that. Brian is doing some git surgery to optimize the docs. Long story. Should be resolved today.
additionally, it can also go into the docs section of the repo