I support a an osgi-users list but I think a specific OSGi enRoute list is wrong since the far majority of questions is from developers that want have problems developing with OSGi.
Kind regards,
Peter Kriens
> On 20 okt. 2016, at 15:56, BJ Hargrave <hargr...@us.ibm.com> wrote:
>
> Maybe we need an osgi-users list for more general help type questions and
> osgi-dev can stay more focussed on spec related discussions?
>
> I could create the osgi-users list and intially subscribe everyone on
> osgi-dev to it. Then people can unsubscribe from either (or both) lists as
> they see fit.
>
> But, in general, there is a tension between being too fine and too coarse.
> Much like designing the modularity of your bundles... :-)
>
> --
>
> BJ Hargrave
> Senior Technical Staff Member, IBM // office: +1 386 848 1781
> OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
> hargr...@us.ibm.com
>
>
> ----- Original message -----
> From: Raymond Auge <raymond.a...@liferay.com>
> Sent by: osgi-dev-boun...@mail.osgi.org
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
> Cc:
> Subject: Re: [osgi-dev] Help
> Date: Thu, Oct 20, 2016 8:46 AM
>
> Since I pushed at the OSGi board level to move enRoute discussion here, let
> me take this back (meeting this coming week) and see what we can do. It's not
> intended to alienate anyone who were enjoying the list as it was. The idea
> was simply to coalesce two already low volume channels into one... but
> perhaps that wasn't a good idea after all.
>
> Sincerely,
> - Ray
>
> On Thu, Oct 20, 2016 at 8:39 AM, erwindl0 <erwin...@gmail.com
> <mailto:erwin...@gmail.com>> wrote:
> +1
>
> Op 10/20/2016 om 2:35 PM schreef Simon Chemouil:
>
> Hi Peter,
>
>
> Peter Kriens a écrit le 20/10/2016 13:52 :
> I did a quick check on the last messages on this list:
> [snip]
> So out of more than 60 messages, there were only 5 messages related
> to OSGi enRoute. Are these your problem? Since I will spend much less
> time on OSGi enRoute a new release is unlikely.
> Maybe I am wrong to characterize it as enRoute. I don't know.
>
> I do count those Zigbee messages, the native library
> loading, and so on, as enRoute support. Mostly because the authors come
> with a "Help me solve my whole problem" mindset, and I believe they came
> to post here because they are trying enRoute (because they said so).
>
> Karaf's ML has a lot of similar "general questions about Java/shell
> help/OSGi" threads, because many Karaf users consider the whole of it as
> a stack and often don't know where to ask (or don't care since they get
> help wherever they ask anyway!). I believe Karaf has split their lists
> between karaf-users@ for general purpose and karaf-devs@ and for more
> specific spec/higher-level discussion.
>
>
> By my count since it moved here more than 30% of all mail count has been
> posted here because osgi-dev is the enRoute support list. (~180 mails
> since ~20th of september, 60+ very basic "Help me" requests).
>
> My problem is with the quality of the discussed content. I stayed 2 days
> on Karaf's users@ ML before unregistering because of the amount of
> StackOverflow/IRC kind of questions. My problem is seing the content
> quality of osgi-dev@ decreasing, and because the quality was satisfying
> before: mostly spec discussion on specific points, not "Help me I'm
> lost" questions.
>
> If no one else has that feeling, fine. I'm asking if others do. Łukasz
> Dywicki seemed to say so quite early on I suppose he and maybe other
> share the sentiment.
>
>
> Best regards,
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
>
> --
> Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000)
> Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance)
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
