Hi Ryan It's better not to include the podling’s community list on an IPMC vote thread. This can make record-keeping less clear and cause other problems: - Auditability and traceability: ASF decisions, especially release approvals, must be clearly linked to the right governance group. If votes appear on more than one list, it can be hard to tell which are official. - Authority boundaries: The IPMC vote is for ASF-level oversight, while the podling vote checks for community agreement. Mixing these can blur the lines and make it seem as if podling members are part of the IPMC decision-making. - Potential for confusion: New contributors or outside observers might think the podling’s +1s count toward the official ASF vote if the threads are combined. This has caused confusion before. • Consistency: The ASF has clear rules for how votes should happen and be recorded. Keeping things consistent for all podlings makes training, mentoring, and tools easier, and helps avoid unexpected problems.
Because of these reasons, the simpler way is: - Podling holds its own internal (community) vote on the dev list. - The IPMC holds its formal approval vote only on the IPMC list, referencing the dev-list result via a link. Kind regards, Justin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
