Re: User Visible Terminology

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

Re: User Visible Terminology

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

Re: User Visible Terminology

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

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

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

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

Re: User Visible Terminology

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

Re: User Visible Terminology

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. > > >

Re: User Visible Terminology

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

Re: User Visible Terminology

"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

Re: User Visible Terminology

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

Re: User Visible Terminology

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

User Visible Terminology

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 common functions. Some of the more debated options include: *