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
