Now that no objection to using MPMC as an abbreviation, I file this draft
[1] so that we can improve the wording and start to spread the word.

[1] https://github.com/apache/www-site/pull/388

Interestingly, I noticed that the glossary already has a section:

> Avoid referring to a member of a PMC as "a PMC", as it can cause
confusion about
> whether you are talking about the group or an individual.

I'd send this notice to members@ later today to call for attentions; does
it sound right?

Best,
tison.


Jon Malkin <jmal...@apache.org> 于2024年7月8日周一 16:21写道:

> I was initially thinking I liked the M suffix more in that it gives info on
> the relevant body first, but the MP example swayed me.
>
>   jon
>
>
> On Mon, Jul 8, 2024, 2:45 PM sebb <seb...@gmail.com> wrote:
>
> > On Mon, 8 Jul 2024 at 18:21, Craig Russell <apache....@gmail.com> wrote:
> > >
> > > So, I agree with Greg (! I know) that there is real potential for
> > confusion and we should try to fix it.
> > >
> > > Now what we need to do is to bikeshed the name. Either MPMC or PMCM
> > captures the spirit. None of these conflict with any commonly used
> > acronyms. Which of these works best with PPMC and IPMC?
> > >
> > > I personally prefer MPMC, MIPMC, and MPPMC. Because we want people to
> > think of member first when writing the acronym. And anyone familiar with
> > governing bodies knows MP for Member of Parliament, MEP for Member of
> > European Parliament.
> >
> > +1
> >
> > > Once we decide on the acronym, we need to socialize it by updating all
> > of our "how it works" pages to mention and explain it. Then, when people
> > misuse PMC, we can include a link to the explanation.
> >
> > Should also be mentioned in the Glossary [1], which should also have
> > PPMC and IPMC added.
> >
> > However, we should remember that people outside the ASF also read
> > mailing lists, so ideally use 'member' wherever possible, at least for
> > the first mention.
> > Yes, it's a bit more work for the author, but less effort for the
> > readers (and there are generally multiple readers versus 1 author).
> >
> > Sebb
> > [1] https://apache.org/foundation/glossary.html
> > > Craig
> > >
> > >
> > > > On Jul 8, 2024, at 03:37, Greg Stein <gst...@gmail.com> wrote:
> > > >
> > > > On Sun, Jul 7, 2024 at 10:47 PM Joe Witt <joew...@apache.org> wrote:
> > > >
> > > >> Greg
> > > >>
> > > >> It isnt wrong to correct improper usage particularly when there is a
> > > >> specific case that caused actual confusion.
> > > >>
> > > >
> > > > I appreciate the concept of "correct the usage when you see it", and
> I
> > > > *have* been doing that for several years now. Probably once a month
> or
> > two,
> > > > over and over for years. The improper usage isn't stopping, so I'm
> > raising
> > > > the concern here. The wider community simply needs to understand the
> > > > acronym means a committee, and stop using it for individuals. It is a
> > > > simple definitional solution to this longstanding problem that I feel
> > has
> > > > not improved since my first whack-a-mole message to correct the
> > improper
> > > > usage.
> > > >
> > > > Cheers,.
> > > > -g
> > >
> > > Craig L Russell
> > > c...@apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Reply via email to