On Tue, 2002-07-30 at 21:46, Dan Harkless wrote: > Mike Noyes <[EMAIL PROTECTED]> writes: > > > I suspect what you had in mind when you said "and/or" was that important > > > stuff, including, but not limited to, security advisories, should go to > > > leaf-announce, and less important stuff, like announcements of interesting > > > potential LEAF hardware platforms, should be website posts. > > > > That is not what I had in mind. The person making the announcement needs > > to decide the target audience. Our mailing lists reach a different set > > of users than our web site. > > I think you're making the criteria more vague and complicated than need be.
Dan, There is nothing vague about what I said above. > Bottom-line, stuff that's important for most or all LEAF users to hear, > including, but not limited to, security advisories, should definitely be > posted to leaf-announce. I will not force people to do this. The announce list needs to be seen as useful on it's own merits. > > > That just wasn't clear from your statement, > > > > I hope this message clarifies matters. > > Well, since you've redirected the thread off of leaf-user, it's partially a > moot point. It wasn't clarification for me personally that I was driving > for, but for others. But I suppose most of the people who are likely to > have posts worthy of leaf-announce subscribe to leaf-devel. It was cross posted by you. I pruned leaf-user as the topic wasn't relevant to that list. You seem to have a problem with the way I'm managing our mailing lists. I admit there are many other people that are more qualified for the job, but I'm the one that volunteered. Do you wish to take over our mailing list management job? It requires approximately 15min to 1 1/2 hours a day. You'll need to understand mail headers, and Mailman management. Please send your credentials if your interested. > > BTW, regarding bugs: > > Bugs are reported on leaf-user or in our SF project bug tracker. Then > > corrected in cvs, and noted in a changlog of each release. You can > > monitor all steps of this process if you want to. > > Okay. That conflicts with what Jacques said -- he said to use leaf-devel > rather than leaf-user. But you both said to use the bug tracker, so as > that's the most targeted path for bug reports, that's what I'll use in the > future. You probably should update the Bering install and user's guides to > say to use that, rather than saying to email you guys directly. What Jacques says for Bering bug reporting is correct. What I said, indicates my preference. There are no mandates here. You need to read our development model. It may clarify things for you. Evolution as a project development model http://www.mail-archive.com/leaf-devel%40lists.sourceforge.net/msg04541.html -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
