I advocate for "Shared" (or something even better, if we'll find), since 
"Public" are most of tools that are on Toolserver...

Danny B.

> ------------ Původní zpráva ------------
> Od: Krinkle <[email protected]>
> Předmět: Re: [Toolserver-l] Rename MMPs to "public tools" [was: Toolserver 
> user
> phe account expired]
> Datum: 23.5.2012 20:49:30
> ----------------------------------------
> On Wed, May 23, 2012 at 6:09 PM, Ilmari Karonen <[email protected]> wrote:
> 
> > On Tue, 2012-05-22 at 11:22 +0200, Merlijn van Deen wrote:
> > >   - easier creation of mmp's? I can imaging people don't move their
> > > tools because it takes time to organise everything.
> >
> > I hereby propose that we retire the term "multi-maintainer project" or
> > "MMP", and just start calling them "public tools" (with an appropriate
> > qualifier where necessary, as in "public tool account"), as opposed to
> > "private tools" that run on users' personal accounts.  I do realize that
> > these names are not perfectly descriptive, but IMO they're at least
> > better than what we have right now.
> >
> >
> >
> I agree with Ilmari.
> 
> Except I don't see the problem with the word "project" and "Public Tool
> Account" is asking for more scary abbreviations.
> 
> I'd recommend the name "Public projects" or "Shared projects" (instead of
> "Public tools"). Most accounts contain multiple tools. Since an MMP is just
> a shared account, it can perfectly contain multiple (related) scripts, or a
> framework, or collection of interconnected tools.
> 
> "Creating a public tool" (where one would previously say "Creating a MMP")
> sounds a bit off to me. "Creating a public project" or "Creating a shared
> project" sounds more natural to me.
> 
> Anyway, that's just terminology. I agree with Ilmari's reasoning.
> 
> -- Krinkle
> 
> 
> 

_______________________________________________
Toolserver-l mailing list ([email protected])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Reply via email to