Re: User Visible Terminology

2016-09-22 Thread Jan Kaluža
On 09/21/2016 03:08 PM, Honza Silhan wrote: Hi On Fri, Sep 16, 2016 at 5:02 PM, Petr Šabata wrote: On Thu, Sep 15, 2016 at 10:59:55AM -0400, Matthew Miller wrote: On Thu, Sep 15, 2016 at 02:25:52PM -, Mary Clarke wrote: * enable vs install vs select select is the worst :) It's what I

Re: User Visible Terminology

2016-09-22 Thread Jan Kaluža
On 09/22/2016 09:04 AM, Garrett Holmstrom wrote: On 2016-09-16 08:43, Matthew Miller wrote: On Fri, Sep 16, 2016 at 05:02:04PM +0200, Petr Šabata wrote: This is for the labeling of, for example, separate PHP 5, 6, and 7 modules? Yes. Or even variations of the same upstream version. I'm real

Re: User Visible Terminology

2016-09-22 Thread Garrett Holmstrom
On 2016-09-16 08:43, Matthew Miller wrote: On Fri, Sep 16, 2016 at 05:02:04PM +0200, Petr Šabata wrote: This is for the labeling of, for example, separate PHP 5, 6, and 7 modules? Yes. Or even variations of the same upstream version. I'm really pro-stream here because these identifiers have

Re: User Visible Terminology

2016-09-21 Thread Petr Šabata
On Fri, Sep 16, 2016 at 11:43:35AM -0400, Matthew Miller wrote: > On Fri, Sep 16, 2016 at 05:02:04PM +0200, Petr Šabata wrote: > > > This is for the labeling of, for example, separate PHP 5, 6, and 7 > > > modules? > > > > Yes. Or even variations of the same upstream version. > > > > I'm really

Re: User Visible Terminology

2016-09-21 Thread Honza Silhan
Hi On Fri, Sep 16, 2016 at 5:02 PM, Petr Šabata wrote: > On Thu, Sep 15, 2016 at 10:59:55AM -0400, Matthew Miller wrote: >> On Thu, Sep 15, 2016 at 02:25:52PM -, Mary Clarke wrote: >> > * enable vs install vs select >> >> select is the worst :) > > It's what I half-jokingly suggested during t

Re: User Visible Terminology

2016-09-16 Thread Stephen Gallagher
On 09/16/2016 11:43 AM, Matthew Miller wrote: > On Fri, Sep 16, 2016 at 05:02:04PM +0200, Petr Šabata wrote: >>> This is for the labeling of, for example, separate PHP 5, 6, and 7 >>> modules? >> >> Yes. Or even variations of the same upstream version. >> >> I'm really pro-stream here because thes

Re: User Visible Terminology

2016-09-16 Thread Matthew Miller
On Fri, Sep 16, 2016 at 05:02:04PM +0200, Petr Šabata wrote: > > This is for the labeling of, for example, separate PHP 5, 6, and 7 > > modules? > > Yes. Or even variations of the same upstream version. > > I'm really pro-stream here because these identifiers have > nothing to do with upgrade pa

Re: User Visible Terminology

2016-09-16 Thread Petr Šabata
On Thu, Sep 15, 2016 at 06:41:10PM +0300, Alexander Ploumistos wrote: > On Thu, Sep 15, 2016 at 5:25 PM, Mary Clarke wrote: > > > > The Modularity working group is looking to standardize terminology that > > users use to interact with functionality around modules. > > > Perhaps it would be bett

Re: User Visible Terminology

2016-09-16 Thread Petr Šabata
On Thu, Sep 15, 2016 at 10:59:55AM -0400, Matthew Miller wrote: > On Thu, Sep 15, 2016 at 02:25:52PM -, Mary Clarke wrote: > > The Modularity working group is looking to standardize terminology that > > users use to interact with functionality around modules. There are some > > generally acc

Re: User Visible Terminology

2016-09-16 Thread Björn Persson
"Mary Clarke" wrote: > * List-enabled: lists all enabled modules If this is terminology to be displayed in a user interface, not technical identifiers, then this hyphen is wrong. "List enabled" is a verb applied to an object, and is a reasonable short form of "list all enabled modules". "List-ena

Re: User Visible Terminology

2016-09-15 Thread Alexander Ploumistos
On Thu, Sep 15, 2016 at 5:25 PM, Mary Clarke wrote: > > The Modularity working group is looking to standardize terminology that users > use to interact with functionality around modules. Perhaps it would be better if someone provided some examples for the functions described here - at least for

Re: User Visible Terminology

2016-09-15 Thread Matthew Miller
On Thu, Sep 15, 2016 at 02:25:52PM -, Mary Clarke wrote: > The Modularity working group is looking to standardize terminology that users > use to interact with functionality around modules. There are some generally > accepted terms, but there are also some that have multiple choices for comm