We've had a similar idea / discussion on dev@subversion.a.o a year ago, w.r.t. downstream from Subversion [1].
The idea was to set up a dedicated mailinglist waterway@s.a.o for them, where topics could be discussed that would be of interest to downstreamers (packagers / distributors, integrators, people building all kinds of software on top of Subversion, ...). Not only one-way interaction like with an announce list, but both ways (hoping to get feedback from them regarding API's that are in development, desires from their side, etc ...), and also trying to create interaction between the downstreamers themselves. A concrete use-case at that time was also to ask them for help in getting beta's into the hands of users (in appropriate ways, to get feedback back to us). Anyway, apart from that one discussion on dev@ (on which at least one downstreamer responded with "yes, I'd be interested"), we never did bring it to fruition unfortunately. So it's still just an idea in the back of our heads. I'd be interested to know what other communities think or perhaps have already set up for something like this. Using specific prefixes on mails on users@ could be an alternative, or even putting some known people's email addresses specifically in the recipients list, in addition to users@. [1] https://lists.apache.org/thread.html/0f8c363ea7b24b0e62616895a5bdac73d89e7dc56cfd540d6bb41db6@%3Cdev.subversion.apache.org%3E -- Johan On Wed, Sep 26, 2018 at 11:53 AM Dmitriy Pavlov <dpavlov....@gmail.com> wrote: > > 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 > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
