On Thu, 2010-12-16 at 13:21 +0100, Jaroslav Reznik wrote: > > It's simply the opposite of what has happened: > > * If you are about to make changes that affect a large number of > > packages and maintainers, announce them on time. This is already > > in the wiki at [1]. > > * Do not make fundamental changes late in the release cycle, not a > > few days and not after *after* beta freeze [2]. > > * Do not hardcode dependencies too much. [3]. > > * Do not hardcode dependencies on themes. This is useless because > > you will never know if people are actually using this particular > > theme. > > * Respond to bugs in a timely manner [4]. > > * Communicate, reply to questions and critisism. > > I agree - but these points are more FESCo point and tasks for FESCo. But... > > I think we all agree on these points. They are ether part of our > > guidelines or common sense. The question is why some people still don't > > care. We had this discussion in the past a couple of times but so far > > nothing has really changed. this part isn't. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board