[LP0004] Updates based on review manager meeting #84
Conversation
This updates the proposal with changes discussed during the review manager meeting. The changes are: * Update references to code owners to reflect the new maintainer role. * Clarify that the project council will serve as a catch all for issues not covered by an area team. * Explicitly state that area teams must communicate a timeline for decision making. * Update voting contributor identification based on recent developer policy changes around email addresses. * Add additional language around this document being living, and explicitly require the project council to annually review feedback and evolve the process. * Include a timeline for initial adoption that includes testing voter identification scripting.
llvm-beanz
requested review from
rnk,
tstellar,
echristo,
ldionne,
joker-eph,
AaronBallman,
lattner,
dwblaikie,
cyndyishida and
MaskRay
Co-authored-by: Cyndy Ishida <[email protected]>
Co-authored-by: Aaron Ballman <[email protected]>
There was a problem hiding this comment.
(again, approving as incremental improvement of this draft, not as approval of the proposal)
Improvements look good to me - though please wait for at least one or two other approvals (@cyndyishida and @AaronBallman perhaps, though their suggestions so far seem small enough that they're easily validated without necessarily waiting on their individual confirmation specifically).
llvm-beanz
changed the title
|
|
||
| On adoption this proposal will be a living document. Changes to the process will be proposed through PRs and reviewed through the [Decision Making process](https://github.com/llvm/llvm-www/blob/main/proposals/LP0001-LLVMDecisionMaking.md). This proposal is not perfect, and should never be assumed to be static or fixed. | ||
|
|
||
| Each year, the _Project Council_ will collect feedback from _area teams_, _maintainers_, and the wider community on what is working, not working, or could be improved. That feedback will be discussed and this proposal will evolve to meet the needs of the community. |
There was a problem hiding this comment.
I would expand on "feedback will be discussed" to say something active, like "the project council will collect that feedback and present it at the developer meeting before each election cycle."
There was a problem hiding this comment.
We discussed dropping the mention of the developer meeting, which I think is fine. Just "shared ahead of the election cycle" seems good. We also used the words "transparency report" with possible operational changes.
This updates the proposal with changes discussed during the review manager meeting. The changes are: