[gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[Mart Raudsepp]

Ühel kenal päeval, L, 18.02.2017 kell 19:47, kirjutas Michał Górny:
> commit:     7207a292b2591dde5cbd336470bed3c11617a8e1
> Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
> CommitDate: Sat Feb 18 19:47:25 2017 +0000
> URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7207
> a292
> 
> dev-util/wxglade: python-single-r1, EAPI=6

While I appreciate work done to do this conversion finally, what was
the reason to bypass the maintainers after being explicitly told on IRC
to not do so?
Since when have we entered a free-for-all state of maintenance in
Gentoo?
I would like to know the state of affairs, so I know for future
reference what can I expect and what I can do to packages that I do not
explicitly maintain either.

And yes, I am aware there was a pending bump request for a couple
years. I'm still dealing with backlog after getting back to tree
maintenance.


Mart Raudsepp,
thoroughly confused about current maintenance policies

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[M. J. Everitt]

[-- Attachment #1.1: Type: text/plain, Size: 1577 bytes --]

On 18/02/17 20:03, Mart Raudsepp wrote:
> Ühel kenal päeval, L, 18.02.2017 kell 19:47, kirjutas Michał Górny:
>> commit:     7207a292b2591dde5cbd336470bed3c11617a8e1
>> Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
>> CommitDate: Sat Feb 18 19:47:25 2017 +0000
>> URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7207
>> a292
>>
>> dev-util/wxglade: python-single-r1, EAPI=6
> While I appreciate work done to do this conversion finally, what was
> the reason to bypass the maintainers after being explicitly told on IRC
> to not do so?
> Since when have we entered a free-for-all state of maintenance in
> Gentoo?
> I would like to know the state of affairs, so I know for future
> reference what can I expect and what I can do to packages that I do not
> explicitly maintain either.
>
> And yes, I am aware there was a pending bump request for a couple
> years. I'm still dealing with backlog after getting back to tree
> maintenance.
>
>
> Mart Raudsepp,
> thoroughly confused about current maintenance policies
>
I would also argue why wasn't this revbumped at the same time, if the
package was touched -at all-. This is a package I've been interested in
as a user for a couple of years now, but not having the required
knowledge, hadn't touched it to update. 0.6.3 is -ancient- and
unsupported upstream. In fact, I have been instrumental in fixing a few
bugs in the 0.7-series upstream, but could not bring these releases to
Gentoo because of the reasons mentioned.

Equally mystified,
Michael/veremit.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[Mart Raudsepp]

Ühel kenal päeval, L, 18.02.2017 kell 22:03, kirjutas Mart Raudsepp:
> Ühel kenal päeval, L, 18.02.2017 kell 19:47, kirjutas Michał Górny:
> > commit:     7207a292b2591dde5cbd336470bed3c11617a8e1
> > Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
> > CommitDate: Sat Feb 18 19:47:25 2017 +0000
> > URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=72
> > 07
> > a292
> > 
> > dev-util/wxglade: python-single-r1, EAPI=6
> 
> While I appreciate work done to do this conversion finally, what was
> the reason to bypass the maintainers after being explicitly told on
> IRC
> to not do so?
> Since when have we entered a free-for-all state of maintenance in
> Gentoo?
> I would like to know the state of affairs, so I know for future
> reference what can I expect and what I can do to packages that I do
> not
> explicitly maintain either.
> 
> And yes, I am aware there was a pending bump request for a couple
> years. I'm still dealing with backlog after getting back to tree
> maintenance.
> 
> 
> Mart Raudsepp,
> thoroughly confused about current maintenance policies


Hello?

wxglade was just one example that affected me, and actually a bad
example, but I see constant commits to anything and everything by
people not maintaining something, to teams that have not declared their
packages open for fixing by anyone nor without Acked-by's; coupled with
constant talks of everything being crap, ebuilds being retarded and
whatnot. Not a very motivational speak, I must add.

What is going on? Do I need to revise how I would judge an ebuild quiz
question 12 answer for any future mentees?


Mart Raudsepp

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[Mike Gilbert]

On Sat, Feb 18, 2017 at 3:03 PM, Mart Raudsepp <leio@gentoo.org> wrote:
> Ühel kenal päeval, L, 18.02.2017 kell 19:47, kirjutas Michał Górny:
>> commit:     7207a292b2591dde5cbd336470bed3c11617a8e1
>> Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
>> CommitDate: Sat Feb 18 19:47:25 2017 +0000
>> URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7207
>> a292
>>
>> dev-util/wxglade: python-single-r1, EAPI=6
>
> While I appreciate work done to do this conversion finally, what was
> the reason to bypass the maintainers after being explicitly told on IRC
> to not do so?
> Since when have we entered a free-for-all state of maintenance in
> Gentoo?
> I would like to know the state of affairs, so I know for future
> reference what can I expect and what I can do to packages that I do not
> explicitly maintain either.
>
> And yes, I am aware there was a pending bump request for a couple
> years. I'm still dealing with backlog after getting back to tree
> maintenance.
>
> Mart Raudsepp,
> thoroughly confused about current maintenance policies
>

At some point, if the maintainer isn't doing his job, he gets
bypassed. Especially when dealing with a conversion like python.eclass
where few people know or care how it works. If we waited for
individual maintainers it will never get done.

Unless you have some reason to slow him down, please get out of his
way and let him work.

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[Mart Raudsepp]

Ühel kenal päeval, E, 20.02.2017 kell 13:50, kirjutas Mike Gilbert:
> On Sat, Feb 18, 2017 at 3:03 PM, Mart Raudsepp <leio@gentoo.org>
> wrote:
> > Ühel kenal päeval, L, 18.02.2017 kell 19:47, kirjutas Michał Górny:
> > > commit:     7207a292b2591dde5cbd336470bed3c11617a8e1
> > > Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
> > > CommitDate: Sat Feb 18 19:47:25 2017 +0000
> > > URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=
> > > 7207
> > > a292
> > > 
> > > dev-util/wxglade: python-single-r1, EAPI=6
> > 
> > While I appreciate work done to do this conversion finally, what
> > was
> > the reason to bypass the maintainers after being explicitly told on
> > IRC
> > to not do so?
> > Since when have we entered a free-for-all state of maintenance in
> > Gentoo?
> > I would like to know the state of affairs, so I know for future
> > reference what can I expect and what I can do to packages that I do
> > not
> > explicitly maintain either.
> > 
> > And yes, I am aware there was a pending bump request for a couple
> > years. I'm still dealing with backlog after getting back to tree
> > maintenance.
> > 
> > Mart Raudsepp,
> > thoroughly confused about current maintenance policies
> > 
> 
> At some point, if the maintainer isn't doing his job, he gets
> bypassed. Especially when dealing with a conversion like
> python.eclass
> where few people know or care how it works. If we waited for
> individual maintainers it will never get done.
> 
> Unless you have some reason to slow him down, please get out of his
> way and let him work.

I am talking about the general attitude and approach as well.

But if we want to be stuck in this concrete case then the tracker bug
for eclass removal and conversion was filed less than 3 hours prior to
maintainer bypassing commit. The blocker to wxglade was marked also
less than 3 hours prior to maintainer bypassing commit, and the commit
was pushed at the same time as talking about how this and that thing is
crap and other demotivational speech with the actual maintainer around
and active, saying to contribute a patch to review and push in together
with other changes (like that version bump).
This is very demotivational, and in fact I ended up doing no gentoo
work afterwards over the weekend, primarily because of all this nasty
experience.

Have respect towards others and their wishes and their maintenance and
don't run over other people and maintainers. Do not run over
maintainers after a 3 hour period of bug filing (or rather marking a
wrong bug as a blocker to the eclass removal, receiving instant replies
to that, so clearly an "inactive" maintainer, and then still ignoring
everything and committing and pushing regardless). You are not special.


Mart

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-util/wxglade/files/, dev-util/wxglade/

[Kristian Fiskerstrand]

[-- Attachment #1.1: Type: text/plain, Size: 473 bytes --]

On 02/20/2017 08:50 PM, Mart Raudsepp wrote:
> Have respect towards others and their wishes and their maintenance and
> don't run over other people and maintainers. Do not run over
> maintainers after a 3 hour period of bug filing 

This seems like an overall good recommendation to remember after reading
this thread

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]