[Smwg] CSSM CWE Directory Structure

[John Pietras]

Karen and CSSMWG colleagues,

I took a very quick glance over the proposed directory structure, and one thing that struck me was the presence of the Functional Resources Tech Note under the CSS SM : Public : Tech Notes subdirectory. That particular tech note is actually an area-level tech note, and over a year ago I began posting the updated versions under the CSS Area : CWE Private : Functional Resources and Service Components subdirectory, with Erik’s concurrence. There is also a (public) CSS Area : CSSA Technical Notes subdirectory that had a much older (2014) draft version that I have since deleted and replaced with a text READ_ME file that states “There are no documents in the public CSS Area : CSSA Technical Notes subdirectory at this time”.

I propose that the Functional Resource Reference Model (FR RM) Tech Note stay somewhere under the broader CSS Area umbrella, and leave the CSS SM : Public : Tech Notes to tech notes that are strictly confined to CSSM concerns/activities/products. Assuming that we all agree on this, the next question is whether the FR RM Tech Note drafts should be in a public or private subdirectory. The most recent draft is particularly “drafty”, in that a number of decisions were made in Cleveland that had significant impact on the Tech Note, but I was unable to make those changes. The most-recently posted version has an extensive preamble that identifies what kinds of changes are needed/planned, but those changes have not been made. I propose that the current Tech Note version be kept in a CSS Area : CWE Private : Functional Resources subdirectory (the current subdirectory name is no longer accurate since we dropped the “Service Component” concept in Cleveland). CCSDS members can still get to it, but presumably anyone accessing it (i.e., members of other Areas) would be forewarned of the degree of draftiness. If and when the Tech Note can be brought to a degree of completeness that it can stand on its own, then it could be moved to the CSS Area : CSSA Technical Notes public subdirectory.  If we agree to this approach, I can create the new CSS Area : CWE Private : Functional Resources subdirectory, re-post the latest Tech Note draft there, and delete the existing CSS Area : CWE Private : Functional Resources and Service Components subdirectory.

Finally, this begs the question – who is doing a similar exercise for the CSS Area subdirectory organizations? And with that, I’ll sign off ☺.

Best wishes to you all for the holidays and the new year!

Best regards,
John

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Tuttle, Karen L. (GRC-MSI0)
Sent: Tuesday, December 06, 2016 12:47 PM
To: smwg at mailman.ccsds.org
Subject: [Smwg] CSSM CWE Directory Structure

Dear Colleagues,

Please see the proposed CSSM CWE Directory Structure and provide comments. Once I get any updates and the WG approved, I will begin creating and moving files as described. This will probably take some time (rest of my career!? ☺) because of SharePoint.

If I find a file that does not fit into this structure, I’ll let you know and/or create a new folder. We can discuss this further if we have time at the next telecom.

Regards,
Karen
--
Karen L. Tuttle
NASA Glenn ISS Payload Operations Center, Project Manager
216 433-5297 (Office)
216 308-6922 (Work Cell)

________________________________

Spam<https://filter.gst.com/canit/b.php?i=01SgGaCWW&m=e6d739e8c814&c=s>
Not spam<https://filter.gst.com/canit/b.php?i=01SgGaCWW&m=e6d739e8c814&c=n>
Forget previous vote<https://filter.gst.com/canit/b.php?i=01SgGaCWW&m=e6d739e8c814&c=f>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20161213/3ce69d31/attachment.html>