opencity NMU to mentors

2007-09-12 Thread Thanasis Kinias
Greetings,

I've put a NMU of the opencity pacakge on mentors.  I'm not looking to
hijack the package, just fix some serious policy violations.  

The package was breaking FHS, so I rebuilt it for my own system after I
filed a bug.  In doing so I noticed a couple of copyright problems and
filed those bugs too.  Rather than mucking with patches or explaining
the issues I figured the easiest thing to do is to do a non-DD NMU and
let the Games Team sponsor it if they want...  it seemed silly to
duplicate the work.

Best regards,
-- 
Thanasis Kinias
Doctoral Candidate, Department of History, and
  Instructor, Professional Enhancement Programs
Arizona State University, Tempe, Arizona, U.S.A.
.
Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
  -- Amin Maalouf, _Léon l'Africain_


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: opencity NMU to mentors

2007-09-12 Thread Neil Williams
On Wed, 12 Sep 2007 13:10:25 -0700
Thanasis Kinias <[EMAIL PROTECTED]> wrote:

> The package was breaking FHS, 

Details? Is the breakage RC?

> so I rebuilt it for my own system after I
> filed a bug. 

Number?

> In doing so I noticed a couple of copyright problems and
> filed those bugs too.  

Numbers?

> Rather than mucking with patches or explaining
> the issues 

? Pardon ? The bug reports have to explain the issue behind the report
and for an NMU the bug reports must also include patches. What are the
bug report numbers?

> I figured the easiest thing to do 

Easy is not the objective.

> is to do a non-DD NMU and
> let the Games Team sponsor it if they want...  it seemed silly to
> duplicate the work.

No URL, no bug reports, no detail - how do you propose that it gets
sponsored?

There is no duplication involved in an NMU - but you must engage with
the maintainer, explain your proposals, detail your patches and allow
time for the maintainer to either do the upload themselves. From your
request, I have no way to tell if you have done any of those essential
things.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpn9vaS9Z8HL.pgp
Description: PGP signature


Re: opencity NMU to mentors

2007-09-12 Thread Cyril Brulebois
Neil Williams <[EMAIL PROTECTED]> (13/09/2007):
> > The package was breaking FHS, 
> 
> Details? Is the breakage RC?

Two docs files outside /usr/share/doc. He probably couldn't read
“should” in Policy 12.3.

> Number?

#442029

Please note that I didn't reach the retitle[1] when I answered.

 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;bug=442029

My questions about the exact content of the bug remains, because “FHS
violations” isn't self-explanatory.

> Numbers?

#442034, #442056

> > Rather than mucking with patches or explaining the issues 
> 
> ? Pardon ? The bug reports have to explain the issue behind the report
> and for an NMU the bug reports must also include patches. What are the
> bug report numbers?

At least #442029 doesn't explain anything. I didn't look at the other
reports yet, though.

BTW, if you have patches, post them, and mark them as such so as to ease
RC bug handling. Thanks.

> > I figured the easiest thing to do 
> 
> Easy is not the objective.

The Right Thing to do is to contact the maintainers first. And it is not
like the Games Team were totally unresponsive, especially when it comes
to handling copyright-related problems (see Miriam's — in particular but
not only — incredible work bugging upstreams to clarify their license /
consider relicensing).

> > is to do a non-DD NMU and let the Games Team sponsor it if they
> > want...  it seemed silly to duplicate the work.

What about letting the team some time to react and fix its package?

> There is no duplication involved in an NMU - but you must engage with
> the maintainer, explain your proposals, detail your patches and allow
> time for the maintainer to either do the upload themselves. From your
> request, I have no way to tell if you have done any of those essential
> things.A

Agreed, thanks for summarizing my thoughts.

Cheers,

-- 
Cyril Brulebois


pgp3EY1ebAoj9.pgp
Description: PGP signature


Re: opencity NMU to mentors

2007-09-12 Thread Cyril Brulebois
[ I bounced the two previous mails to
  [EMAIL PROTECTED]
  and put the list back in the loop with this mail. ]

Cyril Brulebois <[EMAIL PROTECTED]> (12/09/2007):
> My questions about the exact content of the bug remains, because “FHS
> violations” isn't self-explanatory.

For the sake of completeness, posting the following here, so as to
demonstrate how many points of the Policy the opencity package violates.

There are explanations actually. Let's see:

| AUTHORS -- doesn't ship, must be in $(DOCDIR)
Must? What about the copyright file?

| ChangeLog -- OK
| COPYING, COPYRIGHT, INSTALL -- don't ship, that's OK
| NEWS -- empty file, doesn't ship, that's OK
You say they are OK.

| OpenCity.desktop -- double-installed in /usr/share/applications
| (correct) and $(DATADIR) (redundant)
Bug, OK. What violation is that?

| OpenCity.png -- double-installed in /usr/share/pixmaps (correct) and
| $(DATADIR) (redundant)
Maybe a bug, OK. What violation is that?

| README, TODO -- don't ship, must be in $(DOCDIR)
See Policy 12.3 again. What violation is that?

| autopackage/ -- ships in $(DATADIR), no reason to ship at all
Maybe a bug, OK. What violation is that?

| config/* -- ship in $(DATADIR)/config; must be in $(CONFDIR)
Not if it is not meant to be modified by the local admin. That
configuration files, although in a directory called “config” can be
static data. What violation is that, then?

| docs/* -- ship in $(DATADIR)/docs; must be in $(DOCDIR)
Policy 12.3 againt, must != should.

| graphism/, model/, sound/, texture/ -- correctly ship in $(DADADIR)
You say they are OK.


How many policy violations remain?

-- 
Cyril Brulebois


pgp8KZMggaQHq.pgp
Description: PGP signature


Re: opencity NMU to mentors

2007-09-13 Thread Thanasis Kinias
scripsit Neil Williams:

[...]
> No URL, no bug reports, no detail - how do you propose that it gets
> sponsored?
> 
> There is no duplication involved in an NMU - but you must engage with
> the maintainer, explain your proposals, detail your patches and allow
> time for the maintainer to either do the upload themselves. From your
> request, I have no way to tell if you have done any of those essential
> things.

(1) I was not addressing you, Neil.

(2) I was not requesting sponsorship.

I CC'd the mentors list because I was using the mentors server to make a
package available to the Games Team, whose work I thought it might help.

That's twice now, Neil, that you have replied in a very rude and
aggressive to my posts to this list.  I don't know if you are confusing
me with someone else or if you just have very poor social skills in
general, but since you seem to have an inability to respond politely and
constructively I guess I'd just prefer you ignored my posts.  Killfile
me if I offend you so.  I'm just trying to contribute to this project
and I don't need to deal with your attitude problems.

Regards,
-- 
Thanasis Kinias
Doctoral Candidate, Department of History, and
  Instructor, Professional Enhancement Programs
Arizona State University, Tempe, Arizona, U.S.A.
.
Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
  -- Amin Maalouf, _Léon l'Africain_


signature.asc
Description: Digital signature


Re: opencity NMU to mentors

2007-09-13 Thread Thanasis Kinias
scripsit Cyril Brulebois:
[...]
> The Right Thing to do is to contact the maintainers first. And it is not
> like the Games Team were totally unresponsive, especially when it comes
> to handling copyright-related problems (see Miriam's — in particular but
> not only — incredible work bugging upstreams to clarify their license /
> consider relicensing).
> 
> > > is to do a non-DD NMU and let the Games Team sponsor it if they
> > > want...  it seemed silly to duplicate the work.
> 
> What about letting the team some time to react and fix its package?
[...]

Hey Games Team,

I'm sorry about the confusion here.  Neil's perplexing hostility toward
me seems unfortunately to have set the tone for discussion.  Let me
clarify a few things:

1) I'm not a DD so I can't _really_ do an NMU.  I made an NMU package
for my own personal use, fixing the problems I identified.  I filed
bugs, assigning severity as I understood was appropriate (and I stand by
assigning Serious severity to violating policy MUSTs).  The I uploaded
my package to mentors.debian.net and sent e-mails mentioning that it was
there, and that if they wanted to the Games Team could simply sponsor
the upload -- or do whatever they wanted to with it.  I specifically did
_not_ request to have anyone else sponsor the upload; that would have
been grossly inappropriate and I am displeased to think that anyone
should have thought that was my objective.  

2) I could have posted three separate patches to the three bugs I'd
filed -- or I could just upload a package from which the maintainer
could do a quick diff and see what's there.  I thought making a
ready-to-upload package available might ease the workload on the Games
Team -- but only, of course, if the Team accepted it.

Again, I'm sorry about the confusion.  I'm just trying to be helpful :)

-- 
Thanasis Kinias
Doctoral Candidate, Department of History, and
  Instructor, Professional Enhancement Programs
Arizona State University, Tempe, Arizona, U.S.A.
.
Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
  -- Amin Maalouf, _Léon l'Africain_


signature.asc
Description: Digital signature


Re: opencity NMU to mentors

2007-09-13 Thread Neil Williams
On Thu, 13 Sep 2007 13:19:09 -0700
Thanasis Kinias <[EMAIL PROTECTED]> wrote:

> is to do a non-DD NMU and
> let the Games Team sponsor it if they want...  it seemed silly to
> duplicate the work.
> > No URL, no bug reports, no detail - how do you propose that it gets
> > sponsored?

Sounds like a request for sponsorship to me - and one that was lacking
the most basic information.

> > There is no duplication involved in an NMU - but you must engage with
> > the maintainer, explain your proposals, detail your patches and allow
> > time for the maintainer to either do the upload themselves. From your
> > request, I have no way to tell if you have done any of those essential
> > things.
> 
> (1) I was not addressing you, Neil.

You were addressing this list and I am part of the list, so I replied.
Seems straightforward enough. If your mail was for a subset of this
list, maybe that should have been clearer in the original mail or sent
direct?

> (2) I was not requesting sponsorship.

See above. It looked like it to me. YMMV.
 
> I CC'd the mentors list because I was using the mentors server to make a
> package available to the Games Team, whose work I thought it might help.

I was just pointing out that important information was missing.
 
> That's twice now, Neil, that you have replied in a very rude and
> aggressive to my posts to this list. 

? Huh ? You misinterpret.

> I don't know if you are confusing
> me with someone else or if you just have very poor social skills in
> general, but since you seem to have an inability to respond politely and
> constructively I guess I'd just prefer you ignored my posts.  Killfile
> me if I offend you so.  I'm just trying to contribute to this project
> and I don't need to deal with your attitude problems.

You appear confused. I have not done anything of the sort and if you
have misread my requests due to who knows what reason, it is nothing to
do with me.

I don't killfile anyone. I'm not impolite although sometimes direct. If
you see attitude problems where none exist, I can't do much about that
except continue to contribute in a constructive and efficient manner as
I have done for some time. Nothing I have said on this list or any
other public list should be contorted into the meaning you appear to
ascribe.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpstj53ae3yg.pgp
Description: PGP signature


Re: opencity NMU to mentors

2007-09-13 Thread Neil Williams
On Thu, 13 Sep 2007 13:43:35 -0700
Thanasis Kinias <[EMAIL PROTECTED]> wrote:

> scripsit Cyril Brulebois:
> [...]
> > The Right Thing to do is to contact the maintainers first. And it is not
> > like the Games Team were totally unresponsive, especially when it comes
> > to handling copyright-related problems (see Miriam's — in particular but
> > not only — incredible work bugging upstreams to clarify their license /
> > consider relicensing).
> > 
> > > > is to do a non-DD NMU and let the Games Team sponsor it if they
> > > > want...  it seemed silly to duplicate the work.
> > 
> > What about letting the team some time to react and fix its package?
> [...]
> 
> Hey Games Team,
> 
> I'm sorry about the confusion here.  Neil's perplexing hostility toward
> me seems unfortunately to have set the tone for discussion.

Not at all. I have no hostility to you or anyone else on this list or
any other public list to which I post. I can't help it if you see
something that does not exist, except to put the record straight that
you must be mistook. No wonder you are perplexed.

> 1) I'm not a DD so I can't _really_ do an NMU. 

(I guessed that much.)

> I made an NMU package
> for my own personal use, fixing the problems I identified. 

(Something I do myself - rough and ready packages that are nowhere near
release, but the patches always go to the BTS.)

The only reason to upload packages to mentors.debian.net is to request
sponsoring - if your changes are just patches and not a request to take
over or start maintenance of the package yourself then all I can say is
that you made the wrong choice. I see no need to upload the package
anywhere, the BTS is quite sufficient for patches, NMU's or any other
change to a package where the maintainer of the package is not going to
change.

> I filed
> bugs, assigning severity as I understood was appropriate (and I stand by
> assigning Serious severity to violating policy MUSTs).  The I uploaded
> my package to mentors.debian.net and sent e-mails mentioning that it was
> there, and that if they wanted to the Games Team could simply sponsor
> the upload -- or do whatever they wanted to with it. 

Doesn't the Games Team have a team packaging mailing list?

> I specifically did
> _not_ request to have anyone else sponsor the upload; that would have
> been grossly inappropriate and I am displeased to think that anyone
> should have thought that was my objective.  

Now that's clearer - a lot clearer than the original request which was,
IMHO, overly casual and omitted lots of relevant data.

> 2) I could have posted three separate patches to the three bugs I'd
> filed -- or I could just upload a package from which the maintainer
> could do a quick diff and see what's there.  I thought making a
> ready-to-upload package available might ease the workload on the Games
> Team -- but only, of course, if the Team accepted it.

Generally, patches to the BTS are the established way and for good
reason. Getting patches back out of a .diff.gz is not nice, it isn't
regarded as being helpful; it is regarded as being obtuse, awkward or
just plain mistaken. Just think that not everyone prepares or handles
patches as you do in the package so prising each patch out of the
whole .diff.gz is usually a complete waste of time. There is a reason
why Policy specifies that patches are uploaded to the BTS and that they
reside there for some time period before an upload.

> Again, I'm sorry about the confusion.  I'm just trying to be helpful :)

I'd suggest sticking to multiple patches to multiple bugs next time.
Saves a lot of hassle. Honest.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpYu78CKCakl.pgp
Description: PGP signature


Re: opencity NMU to mentors

2007-09-13 Thread Thanasis Kinias
scripsit Neil Williams:
> On Thu, 13 Sep 2007 13:19:09 -0700
> Thanasis Kinias <[EMAIL PROTECTED]> wrote:
> 
> > is to do a non-DD NMU and let the Games Team sponsor it if they
> > want...  it seemed silly to duplicate the work.
> > > No URL, no bug reports, no detail - how do you propose that it
> > > gets sponsored?
> 
> Sounds like a request for sponsorship to me - and one that was lacking
> the most basic information.

Well, I expect if I were requesting sponsorship I would have entitled
the e-mail `RFS: ...' and set the seeking-sponsors flag on the mentors
upload to `yes'.  And I would not have specified that it was the
package maintainer I was addressing.

> > (1) I was not addressing you, Neil.
> 
> You were addressing this list and I am part of the list, so I replied.
> Seems straightforward enough. If your mail was for a subset of this
> list, maybe that should have been clearer in the original mail or sent
> direct?

I see now I transposed the `To:' and the `CC:' headers in my original
post:  I was e-mailing the maintainer and CCing this list out of
courtesy since I was using the mentors server to hold the files.  I can
see how it might have been confusing since I in fact did set `To:' to
this list and `CC:' to the maintainer.

> > (2) I was not requesting sponsorship.
> 
> See above. It looked like it to me. YMMV.

Indeed, YMMV.

> > That's twice now, Neil, that you have replied in a very rude and
> > aggressive to my posts to this list. 
> 
> ? Huh ? You misinterpret.
> 
> > I don't know if you are confusing me with someone else or if you
> > just have very poor social skills in general, but since you seem to
> > have an inability to respond politely and constructively I guess I'd
> > just prefer you ignored my posts.  Killfile me if I offend you so.
> > I'm just trying to contribute to this project and I don't need to
> > deal with your attitude problems.
> 
> You appear confused. I have not done anything of the sort and if you
> have misread my requests due to who knows what reason, it is nothing
> to do with me.
> 
> I don't killfile anyone. I'm not impolite although sometimes direct.
> If you see attitude problems where none exist, I can't do much about
> that except continue to contribute in a constructive and efficient
> manner as I have done for some time. Nothing I have said on this list
> or any other public list should be contorted into the meaning you
> appear to ascribe.

Directness is a popular excuse for rudeness.  You go beyond that,
however.

I direct you to reread your response to my RFS for cinepaint, where you
not only were hostile, accused me of lying by omission, and abused me
for using a template on the mentors Web site.

You wrote:
] This just isn't good enough - not by a long way. Packages are not 
] removed from unstable without due cause so be OPEN about the cause - 
] this is open source, this is Debian - "we don't hide problems".

You could, of course, simply have looked at the bug the upload closed,
which would have explained in detail what was going on.  But you didn't
do that; you made a very clear implication that I was hiding the reason
the package was removed and trying to sneak something (harmful?) back
into Debian.

You could have very tersely said something like `You need to give us a
full report of bugs and reason for the package's removal' in your
response, which would have been direct and not unnecessarily padded with
_politesse_.  Instead you chose to characterize my request as `woeful',
accusing me of treating mentors as `a dumping ground for bad packages',
and informed me that I was `going to have to do a LOT more to make up
for such a bad start', since I was `starting from a deeply negative
position', and that my `responses had better be very good'.  Finally,
you were kind enough to sign off by saying you were `not going to do
[my] work for [me] on this one'.

I suppose that might not strike you as hostile or abusive.  As you said,
YMMV.  But I don't think it takes much for this to be `contorted into
the meaning [I] appear to ascribe' (your words), i.e. a `rude and
aggressive' reply (my words).

Incidentally, when I pointed out where you were mistaken about the
presence of RC bugs in the package, you simply failed to respond.
That's fine; I prefer that to further abuse.

-- 
Thanasis Kinias
Doctoral Candidate, Department of History, and
  Instructor, Professional Enhancement Programs
Arizona State University, Tempe, Arizona, U.S.A.
.
Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
  -- Amin Maalouf, _Léon l'Africain_


signature.asc
Description: Digital signature


Re: opencity NMU to mentors

2007-09-13 Thread Thanasis Kinias
scripsit Neil Williams:

> (Something I do myself - rough and ready packages that are nowhere
> near release, but the patches always go to the BTS.)
> 
> The only reason to upload packages to mentors.debian.net is to request
> sponsoring - if your changes are just patches and not a request to
> take over or start maintenance of the package yourself then all I can
> say is that you made the wrong choice. I see no need to upload the
> package anywhere, the BTS is quite sufficient for patches, NMU's or
> any other change to a package where the maintainer of the package is
> not going to change.

I stand corrected.  I will avoid such use in future.

> Doesn't the Games Team have a team packaging mailing list?

Yes. I mailed their devel list as well as mentors in the post to which
you just replied, but you cut them out of your response for some reason.

[snip]
> Generally, patches to the BTS are the established way and for good
> reason. Getting patches back out of a .diff.gz is not nice, it isn't
> regarded as being helpful; it is regarded as being obtuse, awkward or
> just plain mistaken. Just think that not everyone prepares or handles
> patches as you do in the package so prising each patch out of the
> whole .diff.gz is usually a complete waste of time. There is a reason
> why Policy specifies that patches are uploaded to the BTS and that
> they reside there for some time period before an upload.
> 
> > Again, I'm sorry about the confusion.  I'm just trying to be helpful :)
> 
> I'd suggest sticking to multiple patches to multiple bugs next time.
> Saves a lot of hassle. Honest.

Understood.  Thanks for the constructive response; this is very helpful.

-- 
Thanasis Kinias
Doctoral Candidate, Department of History, and
  Instructor, Professional Enhancement Programs
Arizona State University, Tempe, Arizona, U.S.A.
.
Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
  -- Amin Maalouf, _Léon l'Africain_


signature.asc
Description: Digital signature


Re: opencity NMU to mentors

2007-09-13 Thread Neil Williams
On Thu, 13 Sep 2007 15:09:55 -0700
Thanasis Kinias <[EMAIL PROTECTED]> wrote:

> > Sounds like a request for sponsorship to me - and one that was lacking
> > the most basic information.
> 
> Well, I expect if I were requesting sponsorship I would have entitled
> the e-mail `RFS: ...' 

Not always.

> and set the seeking-sponsors flag on the mentors
> upload to `yes'. 

That setting doesn't get as far as the mailing list. I don't go hunting
around on mentors.debian.net until *after* the package has peaked my
interest and I have sufficient information in the RFS to make a
sensible decision about sponsoring the package.

> I see now I transposed the `To:' and the `CC:' headers in my original
> post:  I was e-mailing the maintainer and CCing this list out of
> courtesy since I was using the mentors server to hold the files.  I can
> see how it might have been confusing since I in fact did set `To:' to
> this list and `CC:' to the maintainer.

OK.
 
> Directness is a popular excuse for rudeness.  You go beyond that,
> however.

Me thinks a 'IMHO' is missing in that sentence.

> You wrote:
> ] This just isn't good enough - not by a long way. Packages are not 
> ] removed from unstable without due cause so be OPEN about the cause - 
> ] this is open source, this is Debian - "we don't hide problems".

It wasn't good enough. The onus is on the person requesting sponsorship
to provide the information for the sponsor. The sponsor is not there to
be a gopher. The bare RFS template is inadequate 95% of the time - it
is not a fault of the template, it is a problem with the maintainer not
"filling in the gaps" with sufficient detail. This applies to most RFS
emails, it's not specific to any one maintainer.

> Incidentally, when I pointed out where you were mistaken about the
> presence of RC bugs in the package, you simply failed to respond.

Would that just possibly be because I tend to be very busy with things
elsewhere in Debian? A request for sponsorship needs to invite the
sponsor to engage with the maintainer, to be appealing and provide all
the information necessary - it is an advertisement, a request, an
invitation - not a command, instruction, direction or stipulation.

Please take on board that there are other things sponsors are doing and
that your requests need to HELP the sponsor, not burden them. You are
the one making the requests - you do the work and you must put the
information in the RFS email that the sponsor will need. The template
is just a guide, it is meant to be embellished. Be verbose, explain
things, remember that there are 19,000 packages in Debian and the
sponsor has probably never heard of your pet project so explain what it
does and what you have done, clearly and fully. No template can cover
all the data required for an RFS so *think* and make any request
enticing and attractive - not burdensome, tedious or incomplete.

I offer sponsorship during what little of my free time is still
available to Debian *after* I have done all my priority tasks relating
to my own packages. It would be good to hear that such efforts are
appreciated and that those requesting sponsorship accept that getting a
package sponsored is a partnership, not a right. Those that I have
sponsored know me and I know that they appreciate my help. I am not
"against" you, I am not out to persecute you - I would like to be able
to help but I need the information and a decent explanation of what you
have done with a particular package.

Don't perpetuate this sub-thread. Whatever you think I meant is not
what I intended but I did consider your cinepaint request to be
inadequate and your reactions since then have done nothing to change
that. Accept the criticism for what it was and move on. Then apply what
you have learnt and what I have proposed, in your next RFS.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpGJcSJJ976r.pgp
Description: PGP signature


Re: opencity NMU to mentors

2007-09-13 Thread Miriam Ruiz
I would beg everyone in the thread to keep calm. There seems to have
been a miscomunication among all of us, so lets let it that way and
forget about it, please. It won't do any good for anyone to keep
discissing this. To be honest, when I read the first mail I thought
"How can this be? They're doing us an NMU for some bugs that are not
extremelly urgent, they haven't even notified us about it, and they
haven't sent eny patches to the BTS?". I guess that's why everyone in
the mailing list was so shocked, because we (me, at least) didn't
understand what was happening. In fact the letters NMU have a very
clear and concise meaning, that's an upload to Debian's repositories,
from a person that's not the maintainer, to solve a problem in the
minimal disruptive form. The usage of the word NMU for a different
thing, as in this case, seems to have confused us all.

For the future, I'd prefer that whoever wants to help the Games Team
send patches to the BTS. It's much easier for everyone. We're handling
all the packages in a subversion server, and it's not as simple as to
get the package and upload it as it is, we have to commit the changes
there too. Furthermore, there might be changes already there that
might not be uploaded yet, so those should also be added to the
package to be uploaded. To sum up, it's quite a big amount of work for
us to extract the patches from the already made packege.

Now that all the situation has been clarified, lets all continue with
our work :)

Greetings,
Miry


2007/9/13, Thanasis Kinias <[EMAIL PROTECTED]>:
> scripsit Cyril Brulebois:
> [...]
> > The Right Thing to do is to contact the maintainers first. And it is not
> > like the Games Team were totally unresponsive, especially when it comes
> > to handling copyright-related problems (see Miriam's — in particular but
> > not only — incredible work bugging upstreams to clarify their license /
> > consider relicensing).
> >
> > > > is to do a non-DD NMU and let the Games Team sponsor it if they
> > > > want...  it seemed silly to duplicate the work.
> >
> > What about letting the team some time to react and fix its package?
> [...]
>
> Hey Games Team,
>
> I'm sorry about the confusion here.  Neil's perplexing hostility toward
> me seems unfortunately to have set the tone for discussion.  Let me
> clarify a few things:
>
> 1) I'm not a DD so I can't _really_ do an NMU.  I made an NMU package
> for my own personal use, fixing the problems I identified.  I filed
> bugs, assigning severity as I understood was appropriate (and I stand by
> assigning Serious severity to violating policy MUSTs).  The I uploaded
> my package to mentors.debian.net and sent e-mails mentioning that it was
> there, and that if they wanted to the Games Team could simply sponsor
> the upload -- or do whatever they wanted to with it.  I specifically did
> _not_ request to have anyone else sponsor the upload; that would have
> been grossly inappropriate and I am displeased to think that anyone
> should have thought that was my objective.
>
> 2) I could have posted three separate patches to the three bugs I'd
> filed -- or I could just upload a package from which the maintainer
> could do a quick diff and see what's there.  I thought making a
> ready-to-upload package available might ease the workload on the Games
> Team -- but only, of course, if the Team accepted it.
>
> Again, I'm sorry about the confusion.  I'm just trying to be helpful :)
>
> --
> Thanasis Kinias
> Doctoral Candidate, Department of History, and
>   Instructor, Professional Enhancement Programs
> Arizona State University, Tempe, Arizona, U.S.A.
> .
> Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
> route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
>   -- Amin Maalouf, _Léon l'Africain_
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFG6aD3Pw5095PItGURAtq5AKCHyfqfTLppKzUkGQw8YttM+a+/AwCg3F3m
> 38UFLcDiXM0h+cFoAHcA7ak=
> =2Bid
> -END PGP SIGNATURE-
>
>



Re: opencity NMU to mentors

2007-09-13 Thread Thanasis Kinias
scripsit Miriam Ruiz:
> I would beg everyone in the thread to keep calm. There seems to have
> been a miscomunication among all of us, so lets let it that way and
> forget about it, please. 

I like that idea very much.  We have better things to do.

[snip]
> To be honest, when I read the first mail I thought "How can this be?
> They're doing us an NMU for some bugs that are not extremelly urgent,
> they haven't even notified us about it, and they haven't sent eny
> patches to the BTS?". I guess that's why everyone in the mailing list
> was so shocked, because we (me, at least) didn't understand what was
> happening. In fact the letters NMU have a very clear and concise
> meaning, that's an upload to Debian's repositories, from a person
> that's not the maintainer, to solve a problem in the minimal
> disruptive form. The usage of the word NMU for a different thing, as
> in this case, seems to have confused us all.

I understand that.  I should not have used NMU in the title; I honestly
really wasn't thinking about the emotional impact of the term.  (Funny
how three little letters, completely meaningless to all but a few
thousand human beings, can inspire such a strong emotional reaction!
There's got to be a paper in there somewhere...)

I need to avoid using 'x.y' debian version numbers when I make my own
builds, because things like dch and debuild then throw `NMU' around a
lot...

> For the future, I'd prefer that whoever wants to help the Games Team
> send patches to the BTS.
[snip]

Understood.

> Now that all the situation has been clarified, lets all continue with
> our work :)

Having continued with my work, I've submitted a patch to bug #442029
containing all the changes between my quasi-pseudo-misnamed `NMU' and
the current -2 version, except for those related to #442034 and #442056
(which bugs Cyril tagged as fixed in SVN).

I hope that is more useful than my previous effort :)

-- 
Thanasis Kinias
Doctoral Candidate, Department of History, and
  Instructor, Professional Enhancement Programs
Arizona State University, Tempe, Arizona, U.S.A.
.
Je ne viens d'aucun pays, d'aucune cité, d'aucune tribu.  Je suis fils de la
route, ma patrie est caravane, et ma vie la plus inattendue des traversées.
  -- Amin Maalouf, _Léon l'Africain_


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]