Propose "why" folder that we will keep as "advisors" knowledge base #16
Conversation
There was a problem hiding this comment.
Interesting idea. Yeah, I like this. It also gives us something to point to when projects push back, in a "this isn't personal, it's just the way things are" kind of way. Especially in conjunction with the notion that we're also there to learn, and possibly improve the process/rules.
100% agree. There is a huge value in something being publicly stated in "semi-official" way. Just writing things down and pointing to it as a link is enough to stop treating things as personal opinion but something that is "commonly understood". Also when we connect it with the gorup of advisors who are mostly a "group ASF members who actually care enough to spend their personal time on helping other projects" has additional benefit that it is not seen as something that is "top-> bottom" but more like "group of peers agreed this is how it is". |
I would like to propose the "why" folder, where we will keep a (very) short summary about some of the rules and policies that we will be - as Advisors - discussing with the projects we will advise. I think we need something like that - also as a place where we - advisors - will be able to update and exchange our understanding on why there are certain rules and policies. Also to discuss future variations and changes to those rules, possibly resulting from interactions with multiple PMCs when we will learn from them how they are applying certain rules and policies in their environment. I gave an example of how I see such "why" captured information could look like - starting with the most familiar (for me) release process and I am curious what others think about it.
potiuk
force-pushed
the
propose-why-folder
branch
from
1a04551
to
c00a139
Compare
|
Ready for the next round of reviews. |
|
If there are no more comments. I'd love to get this one merged and then maybe others (I can do as well) add a bit more why's for different areas. I think also - when we have a few whys we might actually regroup the "red-flags" and have them groupped according to the |
I would like to propose the "why" folder, where we will keep a (very) short summary about some of the rules and policies that we will be - as Advisors - discussing with the projects we will advise.
I think we need something like that - also as a place where we
I gave an example of how I see such "why" captured information could look like - starting with the most familiar (for me) release process and I am curious what others think about it.