Thank you for the feedback. Removing and adding repositories might be something we need to vote separately.
One option is that we make that a PMC level vote, instead of Committer level. Happy to hear feedback on this. My worry is that we even at this point have repositories that do not see updates, yet it would only take one person to -1 removing a repository like that without any requirement for that person to maintain that repo. Toni On Wed, Apr 2, 2025 at 5:43 PM Francisco Javier Tirado Sarti <ftira...@redhat.com.invalid> wrote: > Hi, > In general, I think removing stuff requires consensus (basically because, > as common sense dictates, it affects functionality that is already there). > For example, we currently have consensus to remove/deprecate Infinispan > support (we disagree on the details, but we are certainly getting rid of > Infinispan one way or the other) > Consensus should also be required for tasks affecting the whole repo > structure ( I think this is "common sense" too, a proposal that affects > every contributor work requires consensus) > Which I do not feel requires consensus is to add certain functionality to a > particular area (basically because, in my experience, many people might not > be interested at all and consider it unneeded, but, at the end of the day, > this addition do not really affect them). Of course, common sense apply > here too, the new functionality has to be related with the KIE domain > (implementing Arkanoid in node.js will be new functionality that will > require and will not get consensus ;)) > PS: I understand consensus is different from unanimity. Consensus means a > broad majority with small-not blocking opposition. Common sense should be > applied in the determination of consensus too. > Just two examples, already mentioned, we currently have consensus to > remove/deprecate Infinispan, we do not have consensus on going to mono/dual > repo (but we probably have consensus on the need of improving CI situation) > > On Wed, Apr 2, 2025 at 10:41 AM Gabriele Cardosi < > gabriele.card...@gmail.com> > wrote: > > > Hi Tony, > > first of all, many thanks for all your efforts and dedication! > > I'm late on the discussion, but reading the RTC table, IIUC, it seems > that > > for -> > > > > A decision on a specific proposal to alter KIE in a significant way. > > > Includes adding or removing code bases and repositories. > > > > > > > only Majority Approval is required. I've the impression, on the other > side, > > that this would be exactly the case where Consensus Approval would be > > needed. > > > > WDYT ? > > > > > > Il giorno mer 2 apr 2025 alle ore 10:11 Toni Rikkola > > <trikk...@redhat.com.invalid> ha scritto: > > > > > Good point. I changed "Who can vote" to "Who has binding vote" to > > clarify. > > > The goal is to give the community more power on community actions, but > > also > > > you can vote even if your vote is not binding. Non-binding votes are > > > allowed to signal wans, needs and intentions. > > > > > > Toni > > > > > > On Wed, Apr 2, 2025 at 5:35 AM Toshiya Kobayashi < > > > toshiyakobaya...@gmail.com> > > > wrote: > > > > > > > Thank you, Toni! > > > > > > > > The KIE version guidelines introduce good clarifications to the > default > > > > one. > > > > > > > > One question: > > > > > > > > Is "binding" defined? > > > > > > > > A) Always only PMC members have binding votes. (like > > > > https://www.apache.org/foundation/voting.html#binding-votes) > > > > > > > > or > > > > > > > > B) "Who can vote" in the table have binding vote > > > > > > > > I guess it's B), but it's better to mention that in the guide. > > > > > > > > Regards, > > > > Toshiya > > > > > > > > On Fri, Mar 28, 2025 at 7:11 PM Toni Rikkola <t...@rikkola.net> > wrote: > > > > > > > > > Hello, > > > > > > > > > > Based on comments from our mentor I am redoing the ByLaws proposal > as > > > > > this Guidelines proposal. The back story is in the wiki page > > comments. > > > > > > > > > > Link to what the proposed wiki page would look like: > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/KIE/%5BPROPOSAL%5D+Basic+Apache+KIE+Guidelines > > > > > > > > > > The proposal page contains the Apache default guideline matching > this > > > > > page. Please review and let me know if the current version is good > to > > > > > go. > > > > > > > > > > Toni Rikkola > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > > > > > For additional commands, e-mail: dev-h...@kie.apache.org > > > > > > > > > > > > > > > > > > > >
