Re: MAINTAINERS in svn -- have it or no commit for you
On Mon, 2007-09-10 at 23:41 +0200, Olav Vitters wrote: On Mon, Sep 10, 2007 at 05:09:59PM +0200, Murray Cumming wrote: Yes, gnomemm has no top-level trunk/ directory, and I don't want to add one because that would cause confusion. Ok.. seems you have a very weird SVN repos structure. Not even /trunk exists.. ehr, I'd rather make seperate SVN Repos out of them. This was agreed already when we moved from cvs to svn. We didn't want to confuse the list of modules with all these modules which are named so similarly to the modules that they wrap. But we can move things around if you like - just tell me what to do and when. I can perhaps make an exception for gnomemm, but that will mean the repos will not be listed on Mango (meaning, you will not be listed as a maintainer in LDAP, nor can accounts be requested for gnomemm). As this block dev I'll add the exception asap. Thanks. -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
Could you please turn this off now? I can't commit to either libsigc++ (I emailed you about that already) or gconfmm. For instance: [EMAIL PROTECTED]:~/svn/gnome220/gconfmm$ more MAINTAINERS Murray Cumming E-mail: [EMAIL PROTECTED] Userid: murrayc [EMAIL PROTECTED]:~/svn/gnome220/gconfmm$ svn commit -m Added MAINTAINERS Adding MAINTAINERS Transmitting file data .svn: Commit failed (details follow): svn: 'pre-commit' hook failed with error output: A valid MAINTAINERS file is required. See http://live.gnome.org/MaintainersCorner#maintainers (1083-1) -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
Murray Cumming wrote: Could you please turn this off now? I can't commit to either libsigc++ (I emailed you about that already) or gconfmm. For instance: [EMAIL PROTECTED]:~/svn/gnome220/gconfmm$ more MAINTAINERS Murray Cumming E-mail: [EMAIL PROTECTED] Userid: murrayc It's in the wrong directory, it must be in the /trunk directory of your repository. I guess the administrator scripts are not compatible with the directory layout of gnomemm. Johan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Mon, 2007-09-10 at 12:02 -0300, Johan Dahlin wrote: Murray Cumming wrote: Could you please turn this off now? I can't commit to either libsigc++ (I emailed you about that already) or gconfmm. For instance: [EMAIL PROTECTED]:~/svn/gnome220/gconfmm$ more MAINTAINERS Murray Cumming E-mail: [EMAIL PROTECTED] Userid: murrayc It's in the wrong directory, it must be in the /trunk directory of your repository. I guess the administrator scripts are not compatible with the directory layout of gnomemm. Yes, gnomemm has no top-level trunk/ directory, and I don't want to add one because that would cause confusion. -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Mon, Sep 10, 2007 at 05:09:59PM +0200, Murray Cumming wrote: On Mon, 2007-09-10 at 12:02 -0300, Johan Dahlin wrote: Murray Cumming wrote: Could you please turn this off now? I can't commit to either libsigc++ (I emailed you about that already) or gconfmm. For instance: I think I missed that email.. can't seem to find it. [EMAIL PROTECTED]:~/svn/gnome220/gconfmm$ more MAINTAINERS Murray Cumming E-mail: [EMAIL PROTECTED] Userid: murrayc It's in the wrong directory, it must be in the /trunk directory of your repository. I guess the administrator scripts are not compatible with the directory layout of gnomemm. Yes, gnomemm has no top-level trunk/ directory, and I don't want to add one because that would cause confusion. Ok.. seems you have a very weird SVN repos structure. Not even /trunk exists.. ehr, I'd rather make seperate SVN Repos out of them. I can perhaps make an exception for gnomemm, but that will mean the repos will not be listed on Mango (meaning, you will not be listed as a maintainer in LDAP, nor can accounts be requested for gnomemm). As this block dev I'll add the exception asap. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Fwd: Fwd: MAINTAINERS in svn -- have it or no commit for you
Hi, Daniel took care of his (libxml, libxslt, gamin) --Ray -- Forwarded message -- From: Daniel Veillard [EMAIL PROTECTED] Date: Sep 4, 2007 4:25 AM Subject: Re: Fwd: MAINTAINERS in svn -- have it or no commit for you To: Ray Strode [EMAIL PROTECTED] On Mon, Sep 03, 2007 at 07:57:04PM -0400, Ray Strode wrote: Hey Daniel, Have you seen this thread? Most of the modules left are yours, yea? Can you commit the MAINTAINERS file changes? The info is here: http://live.gnome.org/MaintainersCorner#maintainers Okay done, note that gamin is not part of Gnome releases, and for libxml2 and libxslt it's a bit controversial too, it's more part of the base OS now in my opinion, but I understand the files are needed for the management of teh CVS base too, at least as a point of contact, Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Sun, Sep 02, 2007 at 11:42:44PM -0400, Behdad Esfahbod wrote: On Sun, 2007-09-02 at 21:39 -0600, Elijah Newren wrote: I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? I can delay; just tell me so clearly. Then it will be Dec/Jan ish for the new system. However, based on the current account creation speed, I don't think that is advisable. How hard would it be for someone to intersect all the modules in the GNOME release with the list of those missing a correct MAINTAINERS file and add the missing ones? Assuming 'jhbuild list' gives the SVN name (might not be true): gnome-doc-utils, nautilus, gnome-themes, libxml2, zenity, gnome-netstatus, libart_lgpl, gnome-backgrounds, nautilus-cd-burner, gnome-devel-docs, sabayon, libcroco, gnome-common, libglade, gnome-mime-data, gtk-doc, fast-user-switch-applet, gamin, gnome-media, libgnomekbd, libsigc++2, gtkmm, libgnomecanvas, libxslt, libgnomecups -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
quote who=Olav Vitters I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? I can delay; just tell me so clearly. Then it will be Dec/Jan ish for the new system. However, based on the current account creation speed, I don't think that is advisable. Why the delay to Dec/Jan? It could be done the week after 2.20, or October if we wanted to give some breathing space. - Jeff -- GNOME Boston Summit 2007http://live.gnome.org/Boston2007 Everyone says they like Free Software - not everyone is ready to make the tough choices to make it happen. - Maciej Stachowiak ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
man, 03.09.2007 kl. 08.09 +0200, skrev Olav Vitters: On Sun, Sep 02, 2007 at 11:42:44PM -0400, Behdad Esfahbod wrote: On Sun, 2007-09-02 at 21:39 -0600, Elijah Newren wrote: I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? I can delay; just tell me so clearly. Then it will be Dec/Jan ish for the new system. However, based on the current account creation speed, I don't think that is advisable. How hard would it be for someone to intersect all the modules in the GNOME release with the list of those missing a correct MAINTAINERS file and add the missing ones? Assuming 'jhbuild list' gives the SVN name (might not be true): gnome-doc-utils, nautilus, gnome-themes, libxml2, zenity, gnome-netstatus, libart_lgpl, gnome-backgrounds, nautilus-cd-burner, gnome-devel-docs, sabayon, libcroco, gnome-common, libglade, gnome-mime-data, gtk-doc, fast-user-switch-applet, gamin, gnome-media, libgnomekbd, libsigc++2, gtkmm, libgnomecanvas, libxslt, libgnomecups I've taken care of all the modules containing translations in this list at least. The others can be handled by the maintainers themselves if the module is still maintained that is :-) Cheers Kjartan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Mon, 2007-09-03 at 16:53 +1000, Jeff Waugh wrote: quote who=Olav Vitters I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? I can delay; just tell me so clearly. Then it will be Dec/Jan ish for the new system. However, based on the current account creation speed, I don't think that is advisable. Why the delay to Dec/Jan? It could be done the week after 2.20, or October if we wanted to give some breathing space. I guess Olav refers when he will have some spare time to do it (work in the new system, not only a policy's change). IMVHO, there is not so much modules involved (in the release) and certainly is easy and quick to fix. Regards, -- Germán Poó Caamaño Concepción - Chile ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Mon, Sep 03, 2007 at 11:01:08AM +0200, Kjartan Maraas wrote: man, 03.09.2007 kl. 08.09 +0200, skrev Olav Vitters: Assuming 'jhbuild list' gives the SVN name (might not be true): gnome-doc-utils, nautilus, gnome-themes, libxml2, zenity, gnome-netstatus, libart_lgpl, gnome-backgrounds, nautilus-cd-burner, gnome-devel-docs, sabayon, libcroco, gnome-common, libglade, gnome-mime-data, gtk-doc, fast-user-switch-applet, gamin, gnome-media, libgnomekbd, libsigc++2, gtkmm, libgnomecanvas, libxslt, libgnomecups I've taken care of all the modules containing translations in this list at least. The others can be handled by the maintainers themselves if the module is still maintained that is :-) Thanks! Note that all commits including a .po file are exempt from the MAINTAINER check, per request from Vincent (so translators should generally not be affected). -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Mon, Sep 03, 2007 at 08:48:41AM -0400, Germán Poó Caamaño wrote: On Mon, 2007-09-03 at 16:53 +1000, Jeff Waugh wrote: quote who=Olav Vitters I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? I can delay; just tell me so clearly. Then it will be Dec/Jan ish for the new system. However, based on the current account creation speed, I don't think that is advisable. Why the delay to Dec/Jan? It could be done the week after 2.20, or October if we wanted to give some breathing space. I guess Olav refers when he will have some spare time to do it (work in the new system, not only a policy's change). Yes, that is what I meant. I will have some spare time soon (before 2.20). I'm likely spending this on making some progress on Bugzilla 3.0 (mainly helping others to help me), clearing some of the sysadmin tickets (does not include account tickets), and getting Mango working for account creation (need to audit it + set it up, etc). Ehr, this is not in order of priority... main thing I want to work on is Mango. IMVHO, there is not so much modules involved (in the release) and certainly is easy and quick to fix. New list of missing modules (again, by comparing with jhbuild list): gamin, libxml2, zenity, libsigc++2, libart_lgpl, libxslt In total, 196 SVN repos have these maintainer files now (was 79 on Aug 31). -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On 9/3/07, Olav Vitters [EMAIL PROTECTED] wrote: New list of missing modules (again, by comparing with jhbuild list): gamin, libxml2, zenity, libsigc++2, libart_lgpl, libxslt Wow, I figured the list would be far larger and not drop so quickly either. That's a small enough list that I'm not worried anymore. Thanks, Elijah ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On 9/3/07, Olav Vitters [EMAIL PROTECTED] wrote: New list of missing modules (again, by comparing with jhbuild list): gamin, libxml2, zenity, libsigc++2, libart_lgpl, libxslt Of these, only zenity has translations, righ? Lucas? Are all the others unmaintained? Looks so to me. libart_lgpl is Ok as everyone should be moving to cairo. Not sure about gamin. Is it fading out due to inotify too? Is libsigc++2 maintained by gtkmm maintainers? And what to do with the XML libraries. Is DV still maintaining them? -- behdad http://behdad.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin, 1759 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
quote who=Elijah Newren On 9/3/07, Olav Vitters [EMAIL PROTECTED] wrote: New list of missing modules (again, by comparing with jhbuild list): gamin, libxml2, zenity, libsigc++2, libart_lgpl, libxslt Wow, I figured the list would be far larger and not drop so quickly either. That's a small enough list that I'm not worried anymore. Concur. :-) - Jeff -- Open Source in Mobile 2007: Madrid, Spain http://www.osimconference.com/ Perl: Making thick Windows admins redundant since 1987. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
Hi, 2007/9/3, Behdad Esfahbod [EMAIL PROTECTED]: On 9/3/07, Olav Vitters [EMAIL PROTECTED] wrote: New list of missing modules (again, by comparing with jhbuild list): gamin, libxml2, zenity, libsigc++2, libart_lgpl, libxslt Of these, only zenity has translations, righ? Lucas? Done. :-) --lucasr ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
quote who=Olav Vitters I do understand this is heavy handed way of getting that information. I'd suggest the heavy-handedness is just mistimed -- it would be totally OK to announce that this would happen immediately *after* the release of 2.20, as then it would simply be a property of the next release cycle. Doing it now, during the final and arguably most crucial stages of the cycle (during which, confusion may have a serious impact on the quality of our release), is pretty risky. An infrastructure change such as this is not important enough to inflict at critical points of the release cycle, but it will be great to fix for the next. - Jeff -- GNOME Boston Summit 2007http://live.gnome.org/Boston2007 o/~ In spite of all those keystrokes, you're addicted to vim. *ka-ching!* o/~ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On 9/1/07, Jeff Waugh [EMAIL PROTECTED] wrote: quote who=Olav Vitters I do understand this is heavy handed way of getting that information. I'd suggest the heavy-handedness is just mistimed -- it would be totally OK to announce that this would happen immediately *after* the release of 2.20, as then it would simply be a property of the next release cycle. Doing it now, during the final and arguably most crucial stages of the cycle (during which, confusion may have a serious impact on the quality of our release), is pretty risky. An infrastructure change such as this is not important enough to inflict at critical points of the release cycle, but it will be great to fix for the next. I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? Elijah ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Sun, 2007-09-02 at 21:39 -0600, Elijah Newren wrote: I'm with Jeff and Vincent on this; I'm worried about the adverse affect this could have on the release, given how close it is. Can we consider delaying it until after 2.20 is out? How hard would it be for someone to intersect all the modules in the GNOME release with the list of those missing a correct MAINTAINERS file and add the missing ones? Elijah -- behdad http://behdad.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin, 1759 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
Le samedi 01 septembre 2007, à 00:02 +0200, Olav Vitters a écrit : Does it also make it impossible for translators to commit? If yes, can we postpone this to after 2.20.0? Depends on what you are asking. Someone interpreted this as you have to be in MAINTAINERS or you cannot commit ...which is not true. It is just that nobody cannot do a commit in a module until it has a valid MAINTAINERS file. That's what I understood :-) Further, anyone can commit a proper MAINTAINERS file. As soon that is done all commits will work (you could even combine the MAINTAINERS commit with a bug fix)... but I can understand translators not wanting to deal with that. Maybe we can change the pre-commit script to allow commits in the po directory? I'm just worried that this might create problems for translators because we've just entered string freeze. Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Sat, Sep 01, 2007 at 09:21:10AM +0200, Vincent Untz wrote: Le samedi 01 septembre 2007, à 00:02 +0200, Olav Vitters a écrit : Further, anyone can commit a proper MAINTAINERS file. As soon that is done all commits will work (you could even combine the MAINTAINERS commit with a bug fix)... but I can understand translators not wanting to deal with that. Maybe we can change the pre-commit script to allow commits in the po directory? I'm just worried that this might create problems for translators because we've just entered string freeze. Sort of done. It allows commits as soon as a '.po' file is committed (anywhere). -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Sex, 2007-08-31 at 19:55 +0200, Olav Vitters wrote: On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. It is not nice to do this like this; you should make the pre-commit script give only a warning, for a few months, but still allow commit. Only after the warning period should commit be denied. -- Gustavo J. A. M. Carneiro [EMAIL PROTECTED] [EMAIL PROTECTED] The universe is always one step beyond logic -- Frank Herbert ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Sat, Sep 01, 2007 at 01:20:08PM +0100, Gustavo J. A. M. Carneiro wrote: On Sex, 2007-08-31 at 19:55 +0200, Olav Vitters wrote: On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. It is not nice to do this like this; you should make the pre-commit I've asked everyone to update the files around 3 weeks ago. I've had a complaint that I should've mailed the maintainers directly, but that is exactly the problem I'm trying to solve. I do understand this is heavy handed way of getting that information. script give only a warning, for a few months, but still allow commit. Only after the warning period should commit be denied. You cannot generate a warning. Everything printed to stderr is ignored. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Sat, Sep 01, 2007 at 04:06:07PM +0200, Murray Cumming wrote: On Fri, 2007-08-31 at 19:55 +0200, Olav Vitters wrote: On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. [snip] Could you post that URL here, please, so we know the acceptable format for a MAINTAINERS file. http://live.gnome.org/MaintainersCorner#maintainers I hope that I can still include a comment telling people to use the appropriate mailing list instead of emailing me directly. Yes. See above URL for how to do it. The intention is to put all maintainer info in LDAP and ensuring the email addresses are correct. This so you can be privately contacted regarding account creation (and other maintainer related info in future as well). Note that having this info is not meant as a replacement for things like devel-announce-list. Just regarding contacting the maintainer(s) of a specific module... and knowing who they are. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
MAINTAINERS in svn -- have it or no commit for you
On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. You will be able to commit a proper MAINTAINERS file of course. Note: that has to live in /trunk/MAINTAINERS! Nowhere else (well, ok if you have it, but the pre-commit script doesn't look at it)! Current stats: Valid modules: 46 Invalid format: 229 (file exists, just has the old format or is invalid) Lacks file: 343 Total: 618 Valid modules: 79 Invalid format: 201 Lacks file: 337 Total: 617 (hrm.. one module less than before) -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Fri, Aug 31, 2007 at 04:20:04PM -0400, Claudio Saavedra wrote: On Fri, 2007-08-31 at 19:55 +0200, Olav Vitters wrote: On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. You will be able to commit a proper MAINTAINERS file of course. Note: that has to live in /trunk/MAINTAINERS! Nowhere else (well, ok if you have it, but the pre-commit script doesn't look at it)! Current stats: Valid modules: 46 Invalid format: 229 (file exists, just has the old format or is invalid) Lacks file: 343 Total: 618 Valid modules: 79 Invalid format: 201 Lacks file: 337 Total: 617 (hrm.. one module less than before) Do you have a list of modules like the one you had before? See attached. Claudio, who may have screwed his MAINTAINERS file. It it not a complete check. -- Regards, Olav ApplicationManager ERR_LACKS_MAINTAINERS CWordHelper ERR_LACKS_MAINTAINERS GGADERR_LACKS_MAINTAINERS Mocca ERR_LACKS_MAINTAINERS NetworkManager ERR_MAINTAINERS_INVALID ORBit2 ERR_MAINTAINERS_INVALID OpenApplet ERR_LACKS_MAINTAINERS SashComponents ERR_LACKS_MAINTAINERS SashWDE ERR_LACKS_MAINTAINERS SashXB ERR_LACKS_MAINTAINERS Share ERR_MAINTAINERS_INVALID accerciser ERR_MAINTAINERS_INVALID address-editor ERR_LACKS_MAINTAINERS alacarteERR_LACKS_MAINTAINERS alleyoopERR_LACKS_MAINTAINERS anjuta ERR_MAINTAINERS_INVALID anjuta2 ERR_MAINTAINERS_INVALID aptivateERR_LACKS_MAINTAINERS art-web ERR_MAINTAINERS_INVALID asbestosERR_LACKS_MAINTAINERS assetmlweb ERR_LACKS_MAINTAINERS astrolabe ERR_LACKS_MAINTAINERS asyncworker ERR_LACKS_MAINTAINERS at-poke ERR_MAINTAINERS_INVALID at-spi VALID atk VALID atomato ERR_LACKS_MAINTAINERS atomix ERR_MAINTAINERS_INVALID bablERR_LACKS_MAINTAINERS bakery ERR_LACKS_MAINTAINERS balsa ERR_MAINTAINERS_INVALID banshee ERR_LACKS_MAINTAINERS banter ERR_MAINTAINERS_INVALID barefootERR_LACKS_MAINTAINERS bb-snapshot-confs ERR_LACKS_MAINTAINERS beagle VALID beast ERR_LACKS_MAINTAINERS binary-snapsERR_LACKS_MAINTAINERS blamERR_MAINTAINERS_INVALID blogs-web ERR_LACKS_MAINTAINERS bonobo-support ERR_LACKS_MAINTAINERS bonsai ERR_LACKS_MAINTAINERS bookmark-applet ERR_MAINTAINERS_INVALID bookwormERR_LACKS_MAINTAINERS bprobe VALID brasero ERR_MAINTAINERS_INVALID bug-buddy VALID bugmasters ERR_LACKS_MAINTAINERS bugzilla-buddy ERR_LACKS_MAINTAINERS bugzilla-newer ERR_MAINTAINERS_INVALID bugzilla.gnome.org VALID build ERR_LACKS_MAINTAINERS byzanz ERR_MAINTAINERS_INVALID camoramaERR_LACKS_MAINTAINERS camtrackERR_LACKS_MAINTAINERS canna-extdicERR_LACKS_MAINTAINERS caosERR_LACKS_MAINTAINERS chessclock ERR_LACKS_MAINTAINERS chronojump ERR_LACKS_MAINTAINERS classique-engineERR_LACKS_MAINTAINERS coaster ERR_LACKS_MAINTAINERS conglomerateERR_MAINTAINERS_INVALID contact-lookup-applet ERR_LACKS_MAINTAINERS corkboard ERR_LACKS_MAINTAINERS cowbell ERR_MAINTAINERS_INVALID crescendo ERR_LACKS_MAINTAINERS criawipsERR_LACKS_MAINTAINERS cupid ERR_LACKS_MAINTAINERS cvs-web ERR_LACKS_MAINTAINERS damned-lies VALID dashboard ERR_MAINTAINERS_INVALID dasher ERR_MAINTAINERS_INVALID daybook ERR_LACKS_MAINTAINERS dbus-hook ERR_LACKS_MAINTAINERS dbus-inspector ERR_LACKS_MAINTAINERS dbusfs ERR_LACKS_MAINTAINERS dedit ERR_LACKS_MAINTAINERS denzil ERR_LACKS_MAINTAINERS deskbar-applet VALID deskscribe ERR_MAINTAINERS_INVALID devhelp VALID devilspie ERR_LACKS_MAINTAINERS dia ERR_MAINTAINERS_INVALID dia-newcanvas ERR_LACKS_MAINTAINERS dia-web ERR_LACKS_MAINTAINERS divifundERR_MAINTAINERS_INVALID dogtail ERR_MAINTAINERS_INVALID dogtail-tests ERR_LACKS_MAINTAINERS dongnomeERR_LACKS_MAINTAINERS dr-genius ERR_LACKS_MAINTAINERS drgeo ERR_LACKS_MAINTAINERS drivel ERR_MAINTAINERS_INVALID drwrightERR_LACKS_MAINTAINERS eazel-tools ERR_MAINTAINERS_INVALID eel ERR_MAINTAINERS_INVALID eggcups ERR_LACKS_MAINTAINERS ekiga VALID empathy VALID encompass ERR_LACKS_MAINTAINERS encompass-htmlview ERR_LACKS_MAINTAINERS eog VALID eog-plugins ERR_MAINTAINERS_INVALID epiphanyVALID epiphany-extensions VALID epiphany-mono ERR_MAINTAINERS_INVALID epittance ERR_LACKS_MAINTAINERS erdos ERR_LACKS_MAINTAINERS esound ERR_MAINTAINERS_INVALID
Re: MAINTAINERS in svn -- have it or no commit for you
Le vendredi 31 août 2007, à 19:55 +0200, Olav Vitters a écrit : On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. You will be able to commit a proper MAINTAINERS file of course. Note: that has to live in /trunk/MAINTAINERS! Nowhere else (well, ok if you have it, but the pre-commit script doesn't look at it)! Does it also make it impossible for translators to commit? If yes, can we postpone this to after 2.20.0? Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MAINTAINERS in svn -- have it or no commit for you
On Fri, Aug 31, 2007 at 11:17:40PM +0200, Vincent Untz wrote: Le vendredi 31 août 2007, à 19:55 +0200, Olav Vitters a écrit : On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote: On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote: Note that the userid is really important. Otherwise ensure that the E-mail address is the one your @svn.g.o alias forwards to. I've made an pre-commit script which detects if a module has a valid /trunk/MAINTAINERS file. This currently isn't activated, however I might do this in future. This has now been enabled. Means you cannot commit to modules without a proper MAINTAINERS file. The rejection message points to an URL explaining this. You will be able to commit a proper MAINTAINERS file of course. Note: that has to live in /trunk/MAINTAINERS! Nowhere else (well, ok if you have it, but the pre-commit script doesn't look at it)! Does it also make it impossible for translators to commit? If yes, can we postpone this to after 2.20.0? Depends on what you are asking. Someone interpreted this as you have to be in MAINTAINERS or you cannot commit ...which is not true. It is just that nobody cannot do a commit in a module until it has a valid MAINTAINERS file. Further, anyone can commit a proper MAINTAINERS file. As soon that is done all commits will work (you could even combine the MAINTAINERS commit with a bug fix)... but I can understand translators not wanting to deal with that. Oh, and for those who didn't see the initial discussion. The intention with knowing exactly who our maintainers are (in a machine readable way), is that we can contact these maintainers. This won't happen right away, because we'll be using the $USERNAME at svn.gnome.org email aliases. Meaning, if that alias points to the wrong email address isn't up to date it'll still fail (which I hope to detect by checking the email address in MAINTAINERS). I don't want to postpone the pre-commit just yet. My goal (should be achievable) is to have the new accounts system working by end of September. If we don't have the maintainers machine readable *now*, it means [EMAIL PROTECTED] will have to correct each module when a maintainer requests it... which won't happen realistically. Oh, and it is end of September because before that I'll have some time to do it. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
