Hi all, And, as possibly some here are not quite familiar with how projects at the ASF work: The ASF only deals with individuals. Companies only exist as sponsors, that give us the money to operate ;-) However, do we know that companies exist, as everyone needs to earn a living somehow. Some people contribute without any link to the company that pays their salary (Like the Pilot, that likes to code in his free time). Some are paid but do stuff they use in their company in their free time. And yet another group is paid to work on open-source as part of their job.
All of this is fine from an ASF point of view. However, it gets problematic as soon as a company uses their employees to control the projects. Things like: * Voting in co-workers but objecting or side-tracking other contributors * Delaying or deniying PRs that are not in line with the corporate interests (Which often not are the same as the communities) As soon as we detect a pattern of this, in the worst case the ASF Board steps in. And in the worst case the board uses the “Board Hammer”, which simply removes people from the PMC, taking the control away from the ones who were abusing it. So, if you are fearing corporate interests could interfere with the project … just know: The ASF is probably the best place to not worry about that. It has happened before and will happen again, but be assured: It’s not going to stay unhandled. Chris Von: Justin Mclean <[email protected]> Datum: Mittwoch, 26. Juli 2023 um 02:05 An: [email protected] <[email protected]> Betreff: Re: [DISCUSS] PMC Structure and Leadership for KIE Hi, My first thought is that this is not a correct way for an ASF project to operate. The (P)PMC with the community does set the technical direction. You should not be going down the path of assigning "leaders" to areas of your code or creating other positions. Just use the existing committer and (P)PMC members assignments. Kind Regards, Justin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
