On 14.01.2011, at 13:19, Albrecht Schlosser wrote: > MacArthur, Ian (SELEX GALILEO, UK) wrote: > >> There seem to have been quite a few posts direct to fltk.bugs recently >> by users unfamiliar with our ways... Some of these even seem to have >> been of some merit (so it's good that Matt reads them!) >> >> However, I still wonder why fltk-bugs is not just made "read only" so >> that only the STR stuff goes there, and forcing users and contributors >> to post to fltk.general or fltk.dev instead... >> >> Anyone? > > +1, but _maybe_ with one exception: developer status enabling posting > to fltk.bugs seems like a good idea to me. Sometimes we're posting > comments that are not intended for the STR as side notes or for extended > conversation. But this could probably also be done in fltk.development, > as it is done for fltk.commit: there is a header "Followup-To: > fltk.development" > included. > > Okay, my final(? ;-)) suggestion: make it read-only and set "Followup-To" > header to fltk.development.
We could also just open it to the public... . This has two advantages: 1. we never have to explain anymore why the user should not post there 2. we not only have a dedicated bugs, area, but the users would see the STR messages, realizing how much activity there is in this product, and that their bugs are activaly being fixed The disadvantage would be one more group to read, which makes no difference to me, because I use the email interface. It may annoy the news-reader users and it sure will annoy the web interface users... . +1 on opening it to the public. - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
