183
edits
Difference between revisions of "Sam Whited for Council 2020"
Jump to navigation
Jump to search
m
Sam Whited for Council 2020 (view source)
Revision as of 14:29, 5 November 2020
, 14:29, 5 November 2020Add a section on fixing the document lifecycle
m (Add I-Ds and minor changes.) |
m (Add a section on fixing the document lifecycle) |
||
| Line 34: | Line 34: | ||
I would like to use my position on the XSF council to further this discussion. I see the councils role in this discussion as being a purely advisory one. We would facilitate discussion in the community, try to come to consensus among ourselves, and then make a recommendation to the board who would make any final decisions. | I would like to use my position on the XSF council to further this discussion. I see the councils role in this discussion as being a purely advisory one. We would facilitate discussion in the community, try to come to consensus among ourselves, and then make a recommendation to the board who would make any final decisions. | ||
=== The Document Lifecycle === | |||
One of the big problems with the XEP series of documents is that, as previously mentioned, new documents often aren't implementable and older documents often sit in experimental long after they are widely used and deployed. Draft documents are also somewhat confusing: I have heard a number of times "I can't implement that, it's just a draft". | |||
I would like to begin a discussion about how we can fix this. | |||
I suspect the answer is some mix of modifying the name of the document statuses, creating policies around what documents are allowed to go into each status, and/or simple fixes to the document template to make the intent more obvious. | |||