As (mostly) a lurker on this list, I'll put in my EUR 0,02
As long as people have problems with the current unstable development drivers, I would expect any questions related to these drivers to be best at home in the ivtv-devel mailing list.
Once a driver becomes stable all questions apart from bug reports relating to that driver should go to ivtv-user.
Just my opinion, feel free to disagree ;-)
Cheers,
Luud
On 9/8/05, Greg Hormann <[EMAIL PROTECTED]> wrote:
On Wed, 7 Sep 2005, Axel Thimm wrote:
> On Wed, Sep 07, 2005 at 12:04:22PM +0100, Philip Rowlands wrote:
> > On Wed, 7 Sep 2005, Axel Thimm wrote:
> >
> > >a) Ask people on ivtv-devel to consider switching to ivtv-users, and
> > > follow-up discussions pertaining to user content to the user
> > > list. Diverting threads is cumbersome and requires discipline.
> > >
> > >b) subscribe all back to the users' list and have the people
> > > interested in ivtv-development resubscribe to the emptied
> > > ivtv-devel
> > >
> > >c) merge the two lists to simply ivtv (e.g. drop ivtv-users and rename
> > > ivtv-devel to ivtv while moving the few users accounts over).
> > >
> > >d) leave it as it is
> > >
> > >Your vote?
> >
> > ivtv: In case of problems please include the debug info
> > ivtv: between the START INIT IVTV and END INIT IVTV lines when
> > ivtv: mailing the ivtv-devel mailinglist.
> >
> > I personally came straight to ivtv-devel because of that instruction.
> > Looking through the last month of ivtv-users, there seem to be a good
> > number of bug reports which probably belong on ivtv-devel, a few
> > unanswered queries, even fewer resolved issues. And spam.
> >
> > I'm quite happy with the list setup as-is, and would encourage
> > ivtv-users to come over here. Frequently Asked Questions are easily
> > dealt with, and the searchable history of questions with useful answers
> > is a valuable user resource whether they subscribe or not.
> >
> > Vote: c/d, preserving ivtv-devel because of the printk message.
>
> In the long run (if trac's ticketing system is deemed to be of real
> benefit) this should be replaced with (a pointer to) instructions on
> how to submit a bug report.
>
> But still this is a very valid point, thanks for bringing it up!
> --
> Axel.Thimm at ATrpms.net
>
In my experience, pointing to a bug tracking system is a bad idea. Most of
the time installation issues are not related to bugs but rather user
error. Personally, I'm all for spliting the two again.
Just my $.02
Greg.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
