Other people modifying specfiles...

[Darryl L. Pierce]

I've a question/issue.

This morning I came into work to find that one of my packages had been
updated by someone other than myself or anybody on my team. Several
changes were made on two branches (F18 and master) without the person so
much as notifying me in advance or even asking me if it was okay.

What is the proper way of handling this? I would much prefer that even
proven packagers just taking it upon themselves to update packages
without at least having the courtesy of notifying the package maintainer
first.

Not a territorial thing, but I would like to at least have some notice
before someone is going to arbitrarily change a package for which I'm
responsible.

-- 
Darryl L. Pierce <mcpierce(a)gmail.com&gt;
http://mcpierce.multiply.com/
"What do you care what people think, Mr. Feynman?"

[Rex Dieter]

On 08/20/2012 07:45 AM, Darryl L. Pierce wrote:
>  What is the proper way of handling this? I would much prefer that
> even
>  proven packagers just taking it upon themselves to update packages
>  without at least having the courtesy of notifying the package maintainer
>  first. 
Probably more of a fedora-devel type issue, but at that point the main 
thing to do is to simply ask the person(s) responsible for such commits 
to explain themselves.

that said, personally, as long as the commits weren't wrong or break 
anything, I'd welcome it in general.  else we risk slower development if 
the expectation is always to wait for confirmation or feedback on 
everything.

-- rex

[Dan Horák]

Darryl L. Pierce píše v Po 20. 08. 2012 v 08:45 -0400: 
>  I've a question/issue.
>  
>  This morning I came into work to find that one of my packages had been
>  updated by someone other than myself or anybody on my team. Several
>  changes were made on two branches (F18 and master) without the person so
>  much as notifying me in advance or even asking me if it was okay.
>  
>  What is the proper way of handling this? I would much prefer that even
>  proven packagers just taking it upon themselves to update packages
>  without at least having the courtesy of notifying the package maintainer
>  first.
>  
>  Not a territorial thing, but I would like to at least have some notice
>  before someone is going to arbitrarily change a package for which I'm
>  responsible. 
the maintainers of secondary arches are usually touching all packages in
the cases when the primary arch is not influenced, for larger changes
bugs are being open, for situation between it depends. The nature of
secondary arches when they are always catching the primary arch require
the ability to fix their build issues quickly.


Dan aka Fedora/s390x maintainer

[Stanislav Ochotnicky]

Quoting Darryl L. Pierce (2012-08-20 14:45:31)
>  I've a question/issue.
>  
>  This morning I came into work to find that one of my packages had been
>  updated by someone other than myself or anybody on my team. Several
>  changes were made on two branches (F18 and master) without the person so
>  much as notifying me in advance or even asking me if it was okay.
>  
>  What is the proper way of handling this? I would much prefer that even
>  proven packagers just taking it upon themselves to update packages
>  without at least having the courtesy of notifying the package maintainer
>  first.
>  
>  Not a territorial thing, but I would like to at least have some notice
>  before someone is going to arbitrarily change a package for which I'm
>  responsible. 
I have to admit that I use my provenpackager "powers" like this from
time to time (i.e. commit in other people's packages without
emailing them beforehand/bugreport). 

However in my defence this is mostly due to:
 * Good nature of our Java ecosystem maintainers who actually like that
   I help out from time to time even on their packages
 * Me fixing packaging bugs or updating spec files to latest guidelines.

I've never had a problem with this and I am aware of some people trying
to keep their spec files in sync with EPEL (even though I don't
necessarily agree) so I take that into account when doing modifications.

If it was me, I'd prefer a private "warning" email first so I could
explain myself before having to defend my changes in front of whole
devel@ :-)

-- 
Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;
Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com

[Peter Lemenkov]

Hello All

2012/8/20 Darryl L. Pierce <mcpierce(a)gmail.com&gt;:

>  Not a territorial thing, but I would like to at least have some
> notice
>  before someone is going to arbitrarily change a package for which I'm
>  responsible. 
Agree with Rex Dieter - if we start blaming people for touching stuff
we definitely slow down things. To start with it's simply not yours so
you're not in a position to blame anyone (unless they broke
something).
-- 
With best regards, Peter Lemenkov.

[Michael Schwendt]

On Mon, 20 Aug 2012 08:45:31 -0400, Darryl L. Pierce wrote:

>  I've a question/issue.
>  
>  This morning I came into work to find that one of my packages had been
>  updated by someone other than myself or anybody on my team. Several
>  changes were made on two branches (F18 and master) without the person so
>  much as notifying me in advance or even asking me if it was okay.
>  
>  What is the proper way of handling this? I would much prefer that even
>  proven packagers just taking it upon themselves to update packages
>  without at least having the courtesy of notifying the package maintainer
>  first.
>  
>  Not a territorial thing, but I would like to at least have some notice
>  before someone is going to arbitrarily change a package for which I'm
>  responsible. 
There is

  http://fedoraproject.org/wiki/Who_is_allowed_to_modify_which_packages

which might explain what has happened.

-- 
Fedora release 17 (Beefy Miracle) - Linux 3.5.2-1.fc17.x86_64
loadavg: 0.27 0.19 0.20