With the increased traffic as of late, I'm wondering if it is time to split the list again. Specifically I am wondering if it should be split along the various VoIP protocols and zap hardware, then leave a general list that does configuration other than VoIP related? The hope is that those asking SIP or H323 questions could get help from the various supporters while the main list can deal with transport neutral content like extension logic and voicemail configs. -- Steven Critchfield <critch@basesys.com>
On Fri, 2003-08-08 at 12:25, Steven Critchfield wrote:> With the increased traffic as of late, I'm wondering if it is time to > split the list again. Specifically I am wondering if it should be split > along the various VoIP protocols and zap hardware, then leave a general > list that does configuration other than VoIP related? > > The hope is that those asking SIP or H323 questions could get help from > the various supporters while the main list can deal with transport > neutral content like extension logic and voicemail configs.I second the motion.
I think that's a very good idea. When I started to become active in * last December the list was much less congested and Mark usually responded to requests, comments and patches within a few hours. Now things are clearly taking off - good for * and Digium but it's sort of losing the community spirit. Splitting the lists by the channel drivers seems to be a good idea but I think there needs to be a strong link with the development team. In the case of SIP, it is clearly becoming the protocol for VoIP and many people would like the channel driver enhanced or may have patches for it. I'm not sure the bug tracker is the right place for this. It would be better to have a SIP list moderated by a developer where changes could be discussed. Doubtless the same reasoning could apply to ISDN, IAX etc. Iain --On Friday, August 08, 2003 13:25:10 -0500 Steven Critchfield <critch@basesys.com> wrote:> With the increased traffic as of late, I'm wondering if it is time to > split the list again. Specifically I am wondering if it should be split > along the various VoIP protocols and zap hardware, then leave a general > list that does configuration other than VoIP related? > > The hope is that those asking SIP or H323 questions could get help from > the various supporters while the main list can deal with transport > neutral content like extension logic and voicemail configs. > > -- > Steven Critchfield <critch@basesys.com> > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users >
My concern with wanting to split the list into so many mini-lists is that some will die from lack of membership and it will mean that people with problems in that area will be left in the cold.. Similar to how so many news groups just sit there unused now days.. If there is really a need to split the list into so many components then somthing like phpbb may be better so that there is no management of list membership.. I know the topic of a BB style system has come up before and many did not like the idea but if one or two mailing lists become 10+ then mailing lists can become a headache to look after where a BB system will do it all for you.. especually the poor "MS Outbreak" users.. :) Just my thoughts...> > I think that's a very good idea. When I started to become active in * last > December the list was much less congested and Mark usually responded to > requests, comments and patches within a few hours. Now things are clearly > taking off - good for * and Digium but it's sort of losing the community > spirit. > > Splitting the lists by the channel drivers seems to be a good idea but I > think there needs to be a strong link with the development team. In the > case of SIP, it is clearly becoming the protocol for VoIP and many people > would like the channel driver enhanced or may have patches for it. I'm not > sure the bug tracker is the right place for this. It would be better to > have a SIP list moderated by a developer where changes could be discussed. > > Doubtless the same reasoning could apply to ISDN, IAX etc. > > Iain > > > > --On Friday, August 08, 2003 13:25:10 -0500 Steven Critchfield > <critch@basesys.com> wrote: > > > With the increased traffic as of late, I'm wondering if it is time to > > split the list again. Specifically I am wondering if it should be split > > along the various VoIP protocols and zap hardware, then leave a general > > list that does configuration other than VoIP related? > > > > The hope is that those asking SIP or H323 questions could get help from > > the various supporters while the main list can deal with transport > > neutral content like extension logic and voicemail configs. > > > > -- > > Steven Critchfield <critch@basesys.com> > > > > _______________________________________________ > > Asterisk-Users mailing list > > Asterisk-Users@lists.digium.com > > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users-- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze
I'd still vote for phpbb. Then we could have catagories. Hardware Digim Cisco Other Software Scripts ... Wish List ... Services Active Gateways Commercial Networks We can still be all part of this big Asterisk "community" but sorting through it is easier. =====================================================And yes, my mail client does allow viewing by threads. =====================================================It's still a lot to wade through. If hosting or bandwidth is a problem, I have both bandwith and server space. James Taylor jltaylor@metrotel.net 903-793-1953 ---------- Original Message ---------------------------------- From: "Andy Powell" <andy@beagles-den.demon.co.uk> Reply-To: asterisk-users@lists.digium.com Date: Sat, 09 Aug 2003 15:08:22 +0200> > >I was pondering on this question, and have to agree, splittingmailing list just means yet another list to join (since there may one day be something relavant) and filter locally. What might appear to be a good solution is a privately run newsgroup on a digium server eg news.digium.com the groups would be the same as the lists plus one of two more> >asterisk-announce >asterisk-groups >asterisk-dev >asterisk-users >asterisk-forsale >asterisk-consultants > >of course then you have the potential problem that people can'tread these groups because of blocked firewall ports at their offices etc..> >all IMHO > >Andy > > > > >*********** REPLY SEPARATOR *********** > >On 09/08/2003 at 10:28 WipeOut . wrote: > >>My concern with wanting to split the list into so many mini-lists is that>>some will die from lack of membership and it will mean thatpeople with>>problems in that area will be left in the cold.. Similar to howso many>>news groups just sit there unused now days.. >> >>If there is really a need to split the list into so manycomponents then>>somthing like phpbb may be better so that there is no managementof list>>membership.. >> >>I know the topic of a BB style system has come up before andmany did not>>like the idea but if one or two mailing lists become 10+ thenmailing>>lists can become a headache to look after where a BB system willdo it all>>for you.. especually the poor "MS Outbreak" users.. :) >> >>Just my thoughts... >> >>> >>> I think that's a very good idea. When I started to becomeactive in *>>last >>> December the list was much less congested and Mark usuallyresponded to>>> requests, comments and patches within a few hours. Now thingsare>>clearly >>> taking off - good for * and Digium but it's sort of losing thecommunity>>> spirit. >>> >>> Splitting the lists by the channel drivers seems to be a goodidea but I>>> think there needs to be a strong link with the developmentteam. In the>>> case of SIP, it is clearly becoming the protocol for VoIP andmany>>people >>> would like the channel driver enhanced or may have patches forit. I'm>>not >>> sure the bug tracker is the right place for this. It would bebetter to>>> have a SIP list moderated by a developer where changes could be >>discussed. >>> >>> Doubtless the same reasoning could apply to ISDN, IAX etc. >>> >>> Iain >>> >>> >>> >>> --On Friday, August 08, 2003 13:25:10 -0500 Steven Critchfield >>> <critch@basesys.com> wrote: >>> >>> > With the increased traffic as of late, I'm wondering if itis time to>>> > split the list again. Specifically I am wondering if itshould be split>>> > along the various VoIP protocols and zap hardware, thenleave a general>>> > list that does configuration other than VoIP related? >>> > >>> > The hope is that those asking SIP or H323 questions couldget help from>>> > the various supporters while the main list can deal withtransport>>> > neutral content like extension logic and voicemail configs. >>> > >>> > -- >>> > Steven Critchfield <critch@basesys.com> >>> > >>> > _______________________________________________ >>> > Asterisk-Users mailing list >>> > Asterisk-Users@lists.digium.com >>> > http://lists.digium.com/mailman/listinfo/asterisk-users >>> > >>> >>> >>> >>> >>> _______________________________________________ >>> Asterisk-Users mailing list >>> Asterisk-Users@lists.digium.com >>> http://lists.digium.com/mailman/listinfo/asterisk-users >> >>-- >>______________________________________________ >>http://www.linuxmail.org/ >>Now with e-mail forwarding for only US$5.95/yr >> >>Powered by Outblaze >>_______________________________________________ >>Asterisk-Users mailing list >>Asterisk-Users@lists.digium.com >>http://lists.digium.com/mailman/listinfo/asterisk-users > > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >________________________________________________________________ Sent via the KillerWebMail system at mail.metrotel.net
Perhaps there is another way to cut down on increased traffic... Specifically, I would go back to the suggestion of a collaborative website for documentation. Collecting info and organizing into Howto's would reduce the number of times people ask the same questions. Also, the documentation could grow as quickly as the project. Unfortunately, I don't have a place to host it currently. Ideally, the list would just be for issues that aren't already addressed. Any one else interested in this? Sincerely, Andy Hester Consero> -----Original Message----- > From: asterisk-users-admin@lists.digium.com > [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Steven > Critchfield > Sent: Friday, August 08, 2003 1:25 PM > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] list proposal > > > With the increased traffic as of late, I'm wondering if it is time to > split the list again. Specifically I am wondering if it should be split > along the various VoIP protocols and zap hardware, then leave a general > list that does configuration other than VoIP related? > > The hope is that those asking SIP or H323 questions could get help from > the various supporters while the main list can deal with transport > neutral content like extension logic and voicemail configs. > > -- > Steven Critchfield <critch@basesys.com> > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users