Vincent Untz | 1 Sep 09:21 2007
Picon

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.
Olav Vitters | 1 Sep 10:29 2007

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
Gustavo J. A. M. Carneiro | 1 Sep 14:20 2007
Picon

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  <at> 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
<gjc <at> inescporto.pt> <gustavo <at> users.sourceforge.net>
"The universe is always one step beyond logic" -- Frank Herbert
Olav Vitters | 1 Sep 14:49 2007

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  <at> 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
(Continue reading)

Murray Cumming | 1 Sep 16:06 2007

Re: MAINTAINERS in svn -- have it or no commit for you


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  <at> 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.

I hope that I can still include a comment telling people to use the
appropriate mailing list instead of emailing me directly.

--

-- 
murrayc <at> murrayc.com
www.murrayc.com
www.openismus.com
Olav Vitters | 1 Sep 16:31 2007

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  <at> 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).

(Continue reading)

Jeff Waugh | 2 Sep 03:39 2007

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 2007                    http://live.gnome.org/Boston2007

       o/~ In spite of all those keystrokes, you're addicted to vim.
                              *ka-ching!* o/~
Gustavo J. A. M. Carneiro | 2 Sep 14:09 2007
Picon

Re: quick question regarding bonobo-activation-server-ior file

On Sáb, 2007-08-25 at 10:39 -0700, Gabriel M. Elder wrote:
> My apologies if this is the wrong list.
> 
> Would someone be so kind as to tell me what executable
> and/or library is responsible for handling the corba
> object reference file
> /tmp/orbit-$USER/bonobo-activation-server-ior that
> gets created when a user starts a gnome desktop
> session? I'm assuming that this would be a
> higher-level executable calling bonobo and/or orbit
> library functions. I'm looking for the program
> responsible for handling this file during the login
> process, where it creates the file if it doesn't
> exist, and where it decides to read in the file if it
> does (to retrieve the object reference). BTW - what is
> the relationship between this object reference and the
> X virtual terminal number/assignment, and whence is
> this relationship/association established and stored?
> Is it stored in the bonobo-activation-server-ior file
> itself, or is it handled by ORBit and/or bonobo?
> 
> OK, so maybe these weren't such "quick questions"
> after all... But it'd be a real time-saver and a big
> help if someone would answer these. If you answer on
> this list, or prefer that i redirect my question
> elsewhere, please also cc: my personal email account,
> so i get the message right away.

Gabiral, quite simply /tmp/orbit-$USER/bonobo-activation-server-ior is
created when bonobo-activation-server is started, which is a daemon that
(Continue reading)

Gustavo J. A. M. Carneiro | 2 Sep 14:12 2007
Picon

Re: quick question regarding bonobo-activation-server-ior file


On Dom, 2007-09-02 at 13:09 +0100, Gustavo J. A. M. Carneiro wrote:
> On Sáb, 2007-08-25 at 10:39 -0700, Gabriel M. Elder wrote:
> > My apologies if this is the wrong list.
> > 
> > Would someone be so kind as to tell me what executable
> > and/or library is responsible for handling the corba
> > object reference file
> > /tmp/orbit-$USER/bonobo-activation-server-ior that
> > gets created when a user starts a gnome desktop
> > session? I'm assuming that this would be a
> > higher-level executable calling bonobo and/or orbit
> > library functions. I'm looking for the program
> > responsible for handling this file during the login
> > process, where it creates the file if it doesn't
> > exist, and where it decides to read in the file if it
> > does (to retrieve the object reference). BTW - what is
> > the relationship between this object reference and the
> > X virtual terminal number/assignment, and whence is
> > this relationship/association established and stored?
> > Is it stored in the bonobo-activation-server-ior file
> > itself, or is it handled by ORBit and/or bonobo?
> > 
> > OK, so maybe these weren't such "quick questions"
> > after all... But it'd be a real time-saver and a big
> > help if someone would answer these. If you answer on
> > this list, or prefer that i redirect my question
> > elsewhere, please also cc: my personal email account,
> > so i get the message right away.
> 
(Continue reading)

Elijah Newren | 3 Sep 05:39 2007
Picon

Re: MAINTAINERS in svn -- have it or no commit for you

On 9/1/07, Jeff Waugh <jdub <at> perkypants.org> 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

Gmane