[csw-maintainers] Our core values: providing straightforward experience to the user

Maciej (Matchek) Blizinski maciej at opencsw.org
Fri Dec 31 18:02:39 CET 2010


No dia 28 de Dezembro de 2010 16:59, Philip Brown <phil at bolthole.com> escreveu:
> On Sun, Dec 26, 2010 at 8:51 AM, Maciej (Matchek) Blizinski
> <maciej at opencsw.org> wrote:
>> No dia 27 de Novembro de 2010 06:18, Philip Brown <phil at bolthole.com> escreveu:
>>> A bit of a delayed reply on this one... I wanted to let it sit for a bit.
>>> This is mostly in reply to Maciej's email, but the very last bit
>>> addresses Peter's concerns about 'discretionary' release management.
>>>
>>> Maciej, you made claims that resistance to package manager concerns is
>>> because the maintainer wants to "avoid low quality"
>>>
>>> however, the examples you give, seem to mostly be in the flavor of
>>> "maintainer wants to avoid doing more work".
>>
>> Let me try to summarize.
>>
>> It seems like you see yourself as someone who makes maintainers do
>> more work. ...
>
> Err... its not that I "like" seeing the package release manager that
> way. It seems merely a statement of fact.

I wanted to avoid drilling down to what facts are, but I have no choice.

Merely a statement of fact, you say.  That's what I'm asking: is it
really a fact?  Something like "on the 30th of December 2010, user
wahwah has committed a new revision to gar subversion repository,
which builds xcbproto package in /opt/csw" would be a fact.  What you
call here a fact, is a causal connection.  Causal connections can
potentially achieve the status of facts, but not before you find good
evidence for them.  What you see in our case is that (1) the release
manager refuses to include a package in the repository, and then (2)
the maintainer makes changes to the package.  These two are facts, no
issues here.  But you don't see the release manager causing
maintainer's actions.

Perhaps anybody could make the same suggestion to the maintainer, and
the result would be the same?  Perhaps the package maintainer can
simply walk away, and even the release manager is ultimately impotent?


More information about the maintainers mailing list