From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-text/cuneiform
Date: Sun, 24 Mar 2013 14:40:43 +0100 [thread overview]
Message-ID: <20130324134043.14941.qmail@stuge.se> (raw)
In-Reply-To: <514EED78.2030601@gentoo.org>
Markos Chandras wrote:
> The masks are sort of announcements as you have 30 days to revert that
> decision.
You don't seem to recognize the quite significant psychological
impact of you having already made the decision, compared to, say,
having an actually inclusive package removal process.
Bugzilla does not count as inclusive in this case.
I mean something like a process where users who have this package
installed are notified about the change in status, as opposed to
having to monitor a developer mailing list or portage.mask in order
to get those news. It would probably be a part of emerge --sync.
I think that might do far more good than any web page.
You might argue that such a thing is completely outside your
department, but please consider that what you do can't be seen
in isolation, because users don't care at all about the isolated
particulars which result in their package being masked and cleaned,
they just see that the package is gone one day. You should care
because what you do is the trigger for that user experience.
Improving UX should be your priority too, even if it isn't formally
part of what you do. (Should be everyone's priority.)
//Peter
next prev parent reply other threads:[~2013-03-24 13:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 23:03 [gentoo-dev] Last rites: app-text/cuneiform Markos Chandras
2013-03-23 19:52 ` James Cloos
2013-03-23 20:06 ` Markos Chandras
2013-03-23 20:13 ` James Cloos
2013-03-23 20:21 ` Markos Chandras
2013-03-23 20:29 ` Rich Freeman
2013-03-23 21:40 ` James Cloos
2013-03-24 9:45 ` Rich Freeman
2013-03-24 13:02 ` Sergei Trofimovich
2013-03-23 21:33 ` Alec Warner
2013-03-24 13:24 ` Peter Stuge
2013-03-24 13:38 ` Rich Freeman
2013-03-24 13:52 ` Peter Stuge
2013-03-24 14:12 ` Rich Freeman
2013-03-24 14:35 ` Peter Stuge
2013-03-24 14:54 ` Markos Chandras
2013-03-24 15:19 ` Peter Stuge
2013-03-24 19:24 ` Ian Stakenvicius
2013-03-24 23:40 ` Rich Freeman
2013-03-25 7:05 ` Róbert Čerňanský
2013-03-25 7:46 ` Alec Warner
2013-03-24 9:15 ` Róbert Čerňanský
2013-03-24 10:43 ` Markos Chandras
2013-03-24 11:22 ` Rich Freeman
2013-03-24 12:11 ` Markos Chandras
2013-03-24 12:18 ` Rich Freeman
2013-03-24 12:31 ` Markos Chandras
2013-03-24 12:40 ` Rich Freeman
2013-03-24 14:48 ` Markos Chandras
2013-03-25 10:22 ` Ben de Groot
2013-03-24 19:00 ` Róbert Čerňanský
2013-03-24 13:40 ` Peter Stuge [this message]
2013-03-24 13:48 ` Rich Freeman
2013-03-24 14:14 ` Alan McKinnon
2013-03-24 14:51 ` Peter Stuge
2013-03-25 0:23 ` Patrick Lauer
2013-03-25 0:26 ` Rich Freeman
2013-03-25 3:17 ` [gentoo-dev] " Duncan
2013-03-25 7:08 ` [gentoo-dev] " Róbert Čerňanský
2013-03-25 6:25 ` Sergey Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130324134043.14941.qmail@stuge.se \
--to=peter@stuge.se \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox