Hi Alex, I'm sure you know your project specific better, and probably separate list is the best/only solution. I don't see any problems if the community agrees about it and a new list is well documented.
But uniformity of mailing lists between Apache projects helps a lot to contribute to different projects. You always know where to write. If you will to contribute to the project - you can write to a dev. If you just use it - to a user. I would like to propose to use user list with some mark in emails. Then some filtered view can be prepared for emails related to upstream. I hope it helps. Sincerely, Dmitriy Pavlov ср, 26 сент. 2018 г. в 1:05, Alexandre Rafalovitch <arafa...@gmail.com>: > In my mind, there are three differentiation: > 1) The Solr Users mailing list traffic is quite large and diverse. So, > it can be both overwhelming (for everybody) and hard to notice > messages that are possibly of much higher impact than others. An > upstream framework that is suddenly broken or wants to adopt a new > feature has a larger impact on overall user experience, then one > person's individual journey through Solr features and its current > limitations. So, there is a multiplier effect of attention if handled > right. > 2) The upstream implementer's questions are usually a mix of > super-technical details and potentially not complete understanding of > Solr. So, they could benefit - in my mind - of having space of their > own being more technical an/or in-depth than Users list and less > Solr-tuned than Dev list. > 3) The other people on such list would be other implementers with > similar questions (e.g. new schema configuration API specifics) and so > they could benefit from each other's questions in the way people on > the Solr Users mailing list do much less frequently. > > I hope this clarifies my reasoning. > Alex. > > On 25 September 2018 at 17:49, Luciano Resende <luckbr1...@gmail.com> > wrote: > > On Tue, Sep 25, 2018 at 5:30 PM Alexandre Rafalovitch > > <arafa...@gmail.com> wrote: > >> > >> Hi, > >> > >> I have an idea that I would love to get feedback on to see if it makes > >> sense, feasible, has been tried, is currently being done by somebody, > >> etc. > >> > ... > >> Would it make sense to have a mailing list where committers of > >> upstream projects could ask questions related to their implementation > >> of API, interface, feature dependency, etc? The list would need to be > >> backed by a couple of primary project committers (preferably with a > >> wide rather than deep feature knowledge) that can explain new > >> features, translate the jargon, help troubleshoot the failures, etc. > >> > .... > > > > > > Wouldn't these type of questions also be beneficial for general users? > > > > I see your scenario more like advanced users versus regular users, but > > I also see regular users becoming advanced users at some point (but > > probably in a smaller percentage). > > > > -- > > Luciano Resende > > http://twitter.com/lresende1975 > > http://lresende.blogspot.com/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
