Open DBees opened 1 year ago
Following a talk with Duncan: "If the project remains in the PC approved state for more than 6 months, the TWG chair will propose its cancellation and removal from the OpenHW dashboard, subject to TWG approval". This is to avoid projects forever in the PC state.
Well if we had done this, we would now have no SW TG projects! I think we often need to keep PC there to indicate a project that we need, but which can progress no further until it is resourced. A regular review is fine, but I would expect many projects, at least on the software side to sit at PC for a long time.
Following a talk with Duncan: "If the project remains in the PC approved state for more than 6 months, the TWG chair will propose its cancellation and removal from the OpenHW dashboard, subject to TWG approval". This is to avoid projects forever in the PC state.
Well if we had done this, we would now have no SW TG projects! I think we often need to keep PC there to indicate a project that we need, but which can progress no further until it is resourced. A regular review is fine, but I would expect many projects, at least on the software side to sit at PC for a long time.
I'd prefer projects that we need, but can't launch, to be in a roadmap rather than sitting too long, maybe forever, at PC.
@DBees One more comment. Your content is really useful commentary. You might like to provide it as Markdown comment, which won't then appeared in the rendered document.
There is no explicit comment syntax in MarkDown, but the following blog suggests a number of convenient ways: https://www.jamestharpe.com/markdown-comments/
Personally I would go for the HTML style.
There is one above this line - look at this as source code to see it :-)
@DBees One more comment - you have assorted training whitespace. Just found this while I am using the template for the first time.
…rojects which have a sub-project structure