[DISCUSS] User mailing list for Fluo

[Mike Walch <mw...@apache.org>]

When Fluo started incubation, a user mail listing wasn't created to limit
the number of mailing lists.  However, I think we are due for one. Does
anyone have any views on one being created?  If there are no objections, I
will create a user mailing list this week.

RE: [DISCUSS] User mailing list for Fluo

[Alan Camillo <al...@blueshift.com.br>]

I agree! It was a lit bit difficult to find out how to use the project
without any help.
The user group could help increase the adoption and consequently the
contributors.

-----Original Message-----
From: Keith Turner [mailto:keith@deenlo.com]
Sent: Tuesday, December 19, 2017 2:55 PM
To: fluo-dev <de...@fluo.apache.org>
Subject: Re: [DISCUSS] User mailing list for Fluo

I am in favor.  A user list would follow the pattern of many other projects
making it easier on someone new to contact us.

On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
> When Fluo started incubation, a user mail listing wasn't created to
> limit the number of mailing lists.  However, I think we are due for
> one. Does anyone have any views on one being created?  If there are no
> objections, I will create a user mailing list this week.

Re: [DISCUSS] User mailing list for Fluo

[kenneth mcfarland <ke...@gmail.com>]

I'm in favor of a user list, it models other projects but I also see in the
future a need for separation when there are more users.

Documenting current list to make it easier to get involved is a good thing
too, I like both ideas.

On Dec 19, 2017 2:38 PM, "Josh Elser" <el...@apache.org> wrote:

> Yeah, I'd agree with Christopher. It seems like the real problem is that
> there is lacking documentation for how users should interact with the
> community, less of a "not enough mailing lists" :)
>
> On 12/19/17 12:34 PM, Christopher wrote:
>
>> I think the main reason for a separate list is to keep some organization
>> of
>> high traffic lists. Another reason is separation of concerns (users don't
>> necessarily care about dev concerns). The former doesn't really apply
>> because we're so low traffic, but the latter might. I'm +0.
>>
>> On Tue, Dec 19, 2017, 11:54 Keith Turner <ke...@deenlo.com> wrote:
>>
>> I am in favor.  A user list would follow the pattern of many other
>>> projects making it easier on someone new to contact us.
>>>
>>> On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
>>>
>>>> When Fluo started incubation, a user mail listing wasn't created to
>>>> limit
>>>> the number of mailing lists.  However, I think we are due for one. Does
>>>> anyone have any views on one being created?  If there are no objections,
>>>>
>>> I
>>>
>>>> will create a user mailing list this week.
>>>>
>>>
>>>
>>

Re: [DISCUSS] User mailing list for Fluo

[Christopher <ct...@apache.org>]

On Tue, Dec 19, 2017 at 6:13 PM Mike Walch <mw...@apache.org> wrote:

> I am OK with only having one mailing list for Fluo discussion but it
> shouldn't be called 'dev'. If we have a 'dev' list, we should also have a
> 'user' list so we don't confuse users.  If we want just one list, it should
> be named something like 'general'.
>

I had thought that all ASF projects must have a "dev" list, but I can't
find policy. In any case, "dev" is the norm, and I wouldn't want to change
that.

I was previously +0 on adding a "user@" list, but if the choice is between
two lists and one list that is not called "dev", I choose two lists. I'm
sure there's other "3rd options", but the quickest and easiest thing to do
is just create the second list. I'm switching my opinion to +1 for creating
a "user@" list.

Re: [DISCUSS] User mailing list for Fluo

[Keith Turner <ke...@deenlo.com>]

On Tue, Dec 19, 2017 at 6:13 PM, Mike Walch <mw...@apache.org> wrote:
> I am OK with only having one mailing list for Fluo discussion but it
> shouldn't be called 'dev'. If we have a 'dev' list, we should also have a
> 'user' list so we don't confuse users.  If we want just one list, it should
> be named something like 'general'.
>
> There is a 'Contact Us' page on our website that provides a lot of
> documentation for interacting with the community.
>
> https://fluo.apache.org/contactus/
>
> However, it could be more visible on the main page.  It's buried under the
> 'Community' tab. We could put add a 'Contact Us' or 'Contact' link in the
> navbar to make it more visible.

The main pages does have a link to contact us page.  This was added as
a result of feedback from incubator.

>
> On Tue, Dec 19, 2017 at 5:38 PM Josh Elser <el...@apache.org> wrote:
>
>> Yeah, I'd agree with Christopher. It seems like the real problem is that
>> there is lacking documentation for how users should interact with the
>> community, less of a "not enough mailing lists" :)
>>
>> On 12/19/17 12:34 PM, Christopher wrote:
>> > I think the main reason for a separate list is to keep some organization
>> of
>> > high traffic lists. Another reason is separation of concerns (users don't
>> > necessarily care about dev concerns). The former doesn't really apply
>> > because we're so low traffic, but the latter might. I'm +0.
>> >
>> > On Tue, Dec 19, 2017, 11:54 Keith Turner <ke...@deenlo.com> wrote:
>> >
>> >> I am in favor.  A user list would follow the pattern of many other
>> >> projects making it easier on someone new to contact us.
>> >>
>> >> On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
>> >>> When Fluo started incubation, a user mail listing wasn't created to
>> limit
>> >>> the number of mailing lists.  However, I think we are due for one. Does
>> >>> anyone have any views on one being created?  If there are no
>> objections,
>> >> I
>> >>> will create a user mailing list this week.
>> >>
>> >
>>

Re: [DISCUSS] User mailing list for Fluo

[Mike Walch <mw...@apache.org>]

I am OK with only having one mailing list for Fluo discussion but it
shouldn't be called 'dev'. If we have a 'dev' list, we should also have a
'user' list so we don't confuse users.  If we want just one list, it should
be named something like 'general'.

There is a 'Contact Us' page on our website that provides a lot of
documentation for interacting with the community.

https://fluo.apache.org/contactus/

However, it could be more visible on the main page.  It's buried under the
'Community' tab. We could put add a 'Contact Us' or 'Contact' link in the
navbar to make it more visible.

On Tue, Dec 19, 2017 at 5:38 PM Josh Elser <el...@apache.org> wrote:

> Yeah, I'd agree with Christopher. It seems like the real problem is that
> there is lacking documentation for how users should interact with the
> community, less of a "not enough mailing lists" :)
>
> On 12/19/17 12:34 PM, Christopher wrote:
> > I think the main reason for a separate list is to keep some organization
> of
> > high traffic lists. Another reason is separation of concerns (users don't
> > necessarily care about dev concerns). The former doesn't really apply
> > because we're so low traffic, but the latter might. I'm +0.
> >
> > On Tue, Dec 19, 2017, 11:54 Keith Turner <ke...@deenlo.com> wrote:
> >
> >> I am in favor.  A user list would follow the pattern of many other
> >> projects making it easier on someone new to contact us.
> >>
> >> On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
> >>> When Fluo started incubation, a user mail listing wasn't created to
> limit
> >>> the number of mailing lists.  However, I think we are due for one. Does
> >>> anyone have any views on one being created?  If there are no
> objections,
> >> I
> >>> will create a user mailing list this week.
> >>
> >
>

Re: [DISCUSS] User mailing list for Fluo

[Josh Elser <el...@apache.org>]

Yeah, I'd agree with Christopher. It seems like the real problem is that 
there is lacking documentation for how users should interact with the 
community, less of a "not enough mailing lists" :)

On 12/19/17 12:34 PM, Christopher wrote:
> I think the main reason for a separate list is to keep some organization of
> high traffic lists. Another reason is separation of concerns (users don't
> necessarily care about dev concerns). The former doesn't really apply
> because we're so low traffic, but the latter might. I'm +0.
> 
> On Tue, Dec 19, 2017, 11:54 Keith Turner <ke...@deenlo.com> wrote:
> 
>> I am in favor.  A user list would follow the pattern of many other
>> projects making it easier on someone new to contact us.
>>
>> On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
>>> When Fluo started incubation, a user mail listing wasn't created to limit
>>> the number of mailing lists.  However, I think we are due for one. Does
>>> anyone have any views on one being created?  If there are no objections,
>> I
>>> will create a user mailing list this week.
>>
> 

Re: [DISCUSS] User mailing list for Fluo

[Christopher <ct...@apache.org>]

I think the main reason for a separate list is to keep some organization of
high traffic lists. Another reason is separation of concerns (users don't
necessarily care about dev concerns). The former doesn't really apply
because we're so low traffic, but the latter might. I'm +0.

On Tue, Dec 19, 2017, 11:54 Keith Turner <ke...@deenlo.com> wrote:

> I am in favor.  A user list would follow the pattern of many other
> projects making it easier on someone new to contact us.
>
> On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
> > When Fluo started incubation, a user mail listing wasn't created to limit
> > the number of mailing lists.  However, I think we are due for one. Does
> > anyone have any views on one being created?  If there are no objections,
> I
> > will create a user mailing list this week.
>

Re: [DISCUSS] User mailing list for Fluo

[Keith Turner <ke...@deenlo.com>]

I am in favor.  A user list would follow the pattern of many other
projects making it easier on someone new to contact us.

On Tue, Dec 19, 2017 at 11:40 AM, Mike Walch <mw...@apache.org> wrote:
> When Fluo started incubation, a user mail listing wasn't created to limit
> the number of mailing lists.  However, I think we are due for one. Does
> anyone have any views on one being created?  If there are no objections, I
> will create a user mailing list this week.