Axel Thimm (Axel.Thimm@xxxxxxxxxx) said: > But Thorsten has a point: All packagers need to know what happens over > there - same is true for some other lists, too. > > So I suggest to have a developer/packager "announce" list, where > various boards, sigs and so on can *tersly* communicate *results*, > e.g. important board/fesco decisions, packaging guidelines changes, > infrastructure/buildsystem changes etc., but keep the discussions in > separate lists as happens now. fedora-devel-news? > > But before continuing on thinking about mailing lists structure, > perhaps one should wait to see what the upcoming organisational > structures will look like to start mapping them to lists, or to deduce > some list structure out of it. I guess the most important and > communicative organs do need to keep dedicated lists for a good SNR. Makes sense to me. Bill _______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board _______________________________________________ fedora-advisory-board-readonly mailing list fedora-advisory-board-readonly@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board-readonly
