We should leave the dev for both dev and user discussions since the community is quite small. Thanks!
On Wed, Jan 14, 2015 at 8:48 AM, Jean-Baptiste Onofré <[email protected]> wrote: > Fully agree. Devs should subscribe to all lists. > The point is more for end-users. > > Regards > JB > > > On 01/14/2015 05:36 PM, Srikanth Sundarrajan wrote: > >> Perhaps we should go the full distance and create @issues, @user and >> segregate them. However, It is important that dev subscribes to both of >> them, otherwise risk of not responding to user queries is high. >> >> Regards >> Srikanth Sundarrajan >> >> Date: Wed, 14 Jan 2015 15:35:56 +0000 >>> From: [email protected] >>> To: [email protected] >>> Subject: Re: Back in the business, user mailing list ? >>> >>> I think the Apache suggestion is to combine them at first because most >>> users are also devs and because it's useful to the devs to know what users >>> are asking about. >>> I don't know that there's enough purely user discussion on the existing >>> list to make a separate list worthwhile. The vast bulk of the existing >>> traffic is from JIRA updates and commits, rather than discussion and how-to >>> kinds of questions. >>> On the other hand, having a separate list might encourage more of that >>> kind of discussion and make the user-oriented discussion and answers more >>> visible to people who aren't engaged in the source base. >>> I think the nature of the traffic on the existing lists discourages new >>> people from getting involved, so the lack of a users@ list may be a >>> barrier to adoption of the project. >>> scott >>> >>> On Wednesday, January 14, 2015 4:43 AM, Srikanth Sundarrajan < >>> [email protected]> wrote: >>> >>> >>> I dont have a strong opinion on user@ mailing list, but we avoided >>> creating one during incubation due to recommendations below. I dont know >>> what the threshold is when @user becomes necessary. Looks like there are >>> enough folks feeling that it is necessary now. May be we can file an Infra >>> ticket to create it. >>> >>> http://wiki.apache.org/incubator/MailingListOptions >>> http://incubator.apache.org/guides/proposal.html#template-mailing-lists >>> >>> Regards >>> Srikanth Sundarrajan >>> >>> From: [email protected] >>>> Date: Wed, 14 Jan 2015 14:19:55 +0530 >>>> Subject: Re: Back in the business, user mailing list ? >>>> To: [email protected] >>>> >>>> I think we should. It will be easy to filter and give due importance to >>>> usage questions and help users on priority. Another reason is that the >>>> users by default look for users list to ask for usage questions, not >>>> having >>>> one can be confusing for them. It will also make easier for users to >>>> search >>>> for existing usage questions and even subscribe to it without being >>>> dumped >>>> with all the JIRA updates. If there are no disadvantages to bifurcating >>>> the >>>> mailing lists then I believe we shouldn't wait for the community to be >>>> large to ensure this discipline. >>>> >>>> On Wed, Jan 14, 2015 at 1:45 PM, Srikanth Sundarrajan < >>>> [email protected]> >>>> wrote: >>>> >>>> At this time, the community is still small. Do we really want to >>>>> bifurcate >>>>> the mailing list ? >>>>> >>>>> Regards >>>>> Srikanth Sundarrajan >>>>> >>>>> Date: Wed, 14 Jan 2015 12:16:02 +0530 >>>>>> Subject: Re: Back in the business, user mailing list ? >>>>>> From: [email protected] >>>>>> To: [email protected] >>>>>> >>>>>> Some thoughts on user mailing list : >>>>>> >>>>>> Trying to put what should go in user mailing list and what not >>>>>> (started >>>>>> doing this nowdays) >>>>>> >>>>>> What should go >>>>>> >>>>>> - A question from user - regarding usage? >>>>>> - Announcements to users - new feature/new release and etc. >>>>>> - Not sure people will only subscribe to user list and not dev >>>>>> list. >>>>>> >>>>> If >>>>> >>>>>> there are people, I'm thinking they will mostly interested in >>>>>> announcements >>>>>> on what is happening. >>>>>> - The main use of user mailing list would to separate out user >>>>>> discussions and development discussions, assuming jira related >>>>>> >>>>> updates are >>>>> >>>>>> put in proper filters. >>>>>> >>>>>> What should not go >>>>>> >>>>>> - Jenkins updates >>>>>> - Jira updates >>>>>> - Reviw board updates >>>>>> >>>>>> One challenge we always see is to find where should a post from user >>>>>> >>>>> should >>>>> >>>>>> go - whether to user list or dev list and redirect them accordingly. >>>>>> >>>>>> Overall, +1 for user mailing list - useful when project becomes big >>>>>> and >>>>>> there are many users. >>>>>> >>>>>> Thanks >>>>>> Amareshwari >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jan 14, 2015 at 11:56 AM, Jean-Baptiste Onofré < >>>>>> [email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi all, >>>>>>> >>>>>>> After a couple of crazy months (due to a bunch of customer >>>>>>> >>>>>> engagements), >>>>> >>>>>> I'm now back in the business and happy to be back on Falcon >>>>>>> >>>>>> contribution \o/ >>>>> >>>>>> >>>>>>> By the way, now that Falcon is TLP, what do you think: >>>>>>> 1/ create an user mailing list ? >>>>>>> 2/ "normally", we use to promote all PPMC/Mentor/IPMC involved during >>>>>>> >>>>>> the >>>>> >>>>>> incubation to be PMC on the project (at least we ask if they want to >>>>>>> >>>>>> be). >>>>> >>>>>> WDYT ? >>>>>>> >>>>>>> Regards >>>>>>> JB >>>>>>> -- >>>>>>> Jean-Baptiste Onofré >>>>>>> [email protected] >>>>>>> http://blog.nanthrax.net >>>>>>> Talend - http://www.talend.com >>>>>>> >>>>>>> >>>>> >>>>> >>> >>> >>> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry
