Justin, Thanks for the advice. I did not foresee potential new contributors issue. We do want to make contribution seamless.
Thks, Amol On Tue, Nov 17, 2015 at 4:45 PM, Chris Nauroth <[email protected]> wrote: > I see no specific benchmark defined for justification of a user@ list. > > > > http://incubator.apache.org/guides/proposal.html#template-mailing-lists > > > "If this project is new to open source, then starting with these minimum > lists is the best approach. The initial focus needs to be on recruiting > new developers. Early adopters are potential developers. As momentum is > gained, the community may decide to create commit and user lists as they > become necessary." > > "New mailing lists can be added <http://www.apache.org/dev/infra-contact> > by a VOTE <http://www.apache.org/foundation/voting.html> on the Podling > list." > > > > http://wiki.apache.org/incubator/MailingListOptions > > > "The ASF encourages shunting user-discussion traffic to the dev@ list at > first for the sake of community building. However, projects with sustained > high volume on their dev lists may request a separate user@ list." > > > > > All of this phrasing is qualitative, not quantitative, so the Apex > community is free to decide via a VOTE if it wants to add a user@ list. > > In my own opinion, I think a user@ list is justified. The level of > activity on the dev@ list is quite high now, even surpassing many of the > top-level projects I follow. My only other recommendation would be to > continue to watch for signs of potential new contributors in the user@ > list threads. Steady users have a vested interest in the quality of the > product, so they are often a good pool for patches, documentation > improvements, and of course helping respond to fellow users' questions. > > --Chris Nauroth > > > > > On 11/17/15, 4:30 PM, "Amol Kekre" <[email protected]> wrote: > > >Apache Apex community is growing steadily. We now have over 700 folks on > >our meetups and over 1000 following ApacheApex twitter handle. I am trying > >to see if we can get them on apache email forum, where they can discuss > >their use cases etc. The issue with asking them to be on dev@apex is that > >they may not want to be on dev. Most of them will be more on users side > >(current or future users) and may be more comfortable with users@apex... > > > >Is there a guideline on when to create users@apex... forum? > >Does Apache Apex need to wait till it is a top level project? > > > >Thks, > >Amol > >
