Re: Driver for CVS?
On Sat, Feb 22, 2003 at 10:15:59PM +0100, Thomas Zander wrote: Hi, I have been finetuning a driver for the paceblade touchscreen for a long time now; and it has been publicaly available in the pacebook CVS (on sourceforge). I feel that the only proper place to place this driver is in the XFree CVS. Is it possible that I get an CVS account so I can place and maintain the driver in the XFree CVS tree? XFree86 commit access isn't given out like this. Please feel free to submit your driver to XFree86 (via [EMAIL PROTECTED]) after 4.3. Would be super if that can happen before 4.3; with the argument that a new driver is hardly going to break other stuff :) I can see the appeal of that argument, but my experience with XFree86 releases tells me otherwise. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Driver for CVS?
On Sun, Feb 23, 2003 at 07:22:02PM +0100, Thomas Zander wrote: On Sun, Feb 23, 2003 at 01:00:23PM -0500, David Dawes wrote: On Sat, Feb 22, 2003 at 10:15:59PM +0100, Thomas Zander wrote: Hi, I have been finetuning a driver for the paceblade touchscreen for a long time now; and it has been publicaly available in the pacebook CVS (on sourceforge). I feel that the only proper place to place this driver is in the XFree CVS. Is it possible that I get an CVS account so I can place and maintain the driver in the XFree CVS tree? XFree86 commit access isn't given out like this. Please feel free to submit your driver to XFree86 (via [EMAIL PROTECTED]) after 4.3. Does that mean the code I submit can not be changed by me without sending a diff to the fixes email? Yes, that's correct. Who is the one that decides to add features and code changes then? In other words; who is responsible for that driver (and incidently, for all drivers in CVS). There's no equivalence between maintaining a driver and committing its changes to the XFree86 CVS repository. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Driver for CVS?
On Sun, Feb 23, 2003 at 01:46:37PM -0500, David Dawes wrote: On Sun, Feb 23, 2003 at 07:22:02PM +0100, Thomas Zander wrote: On Sun, Feb 23, 2003 at 01:00:23PM -0500, David Dawes wrote: On Sat, Feb 22, 2003 at 10:15:59PM +0100, Thomas Zander wrote: Hi, I have been finetuning a driver for the paceblade touchscreen for a long time now; and it has been publicaly available in the pacebook CVS (on sourceforge). I feel that the only proper place to place this driver is in the XFree CVS. Is it possible that I get an CVS account so I can place and maintain the driver in the XFree CVS tree? XFree86 commit access isn't given out like this. Please feel free to submit your driver to XFree86 (via [EMAIL PROTECTED]) after 4.3. Does that mean the code I submit can not be changed by me without sending a diff to the fixes email? Yes, that's correct. Why the extra step? It poses an extra boundry for the developer that I don't like to work with. I can't work without CVS, committing for each small change so I get the advantages CVS was meant to have. Going back to a former version if I made too many changes that I don't like. Not possible without being able to commit a dozen times an hour. Who is the one that decides to add features and code changes then? In other words; who is responsible for that driver (and incidently, for all drivers in CVS). There's no equivalence between maintaining a driver and committing its changes to the XFree86 CVS repository. Just for my perception; how is the maintainer suppost to see which features are added, and by whom. Sending an email to fixes means the original authors name will not be in CVS.. Why this burdon on the developers and I think being a maintainer is not very easy either.. You are aware of the concept of cvs-acl, right? -- Thomas Zander ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Driver for CVS?
On Sun, Feb 23, 2003 at 02:30:15PM -0500, David Dawes wrote: On Sun, Feb 23, 2003 at 08:00:06PM +0100, Thomas Zander wrote: Why this burdon on the developers and I think being a maintainer is not very easy either.. There are many different development models, and everyone has their own view on which are better than others. Thats only natural; and I certainly don't have a problem with a different view on things. But with your answers I can never understand your way of working; my queries for the reasoning behind many of the things I see are negative compared to 'other' methods have not been answered. I'm just trying to find arguments of why you do the things you do, please don't feel like I am putting you down.. I feel xfree can use some of the advances in several different technologies, but with the limits imposed by the 'fixes' email address that will not happen, people will not try to create changes they are not quite sure will be committed. -- Thomas Zander ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
