Mike Noyes <[EMAIL PROTECTED]> writes: > Dan, > My "semantics" are not weird. > > Google search results. > "Security Announcement" 25,600 > "Security Advisory" 117,000
I wouldn't dispute that "security advisory" is a more common phrase than "security announcement" (in fact I'm surprised it's only ~4X more common), but I don't see what that's supposed to prove. Bottom-line, I'm sure most people consider a "security advisory" / "security announcement" / whatever-you-want-to-call-it a type of announcement. > > > > Who said anything about forcing?? I just think that should be the > > > > official _policy_. > > > > > > Isn't that the same thing? > > > > No, because unless you're going to travel to the homes or workplaces of each > > potential leaf-announce poster, grab ahold of their hands, and make them > > type things against their will, you *can't* force anyone. > > Yes you can. It's called moderating a list. Moderation allows you to *stop* people from posting things that *aren't* inappropriate, but it doesn't give you the power to *force* people to post things that *are* appropriate, and the latter is what we're talking about. We're talking about people _not_ using leaf-announce when they should, not using it for inappropriate things. > > However, an official policy can be helpful in people's decision-making > > process as to what types of things should definitely be posted to > > leaf-announce, if they're going to be posted anywhere. > > A policy generated without consensus of our project members is of little > use. They need to find our announce list useful on it's own merits. Who said anything about doing something against the consensus of the project members? I'm really not proposing anything radical or controversial -- I'm just saying that at a minimum, when you're going to post information about a security hole or an updated package that fixes a security hole, you should make the announcement to leaf-announce. I can't imagine that's something people wouldn't be able to come to a consensus on. > > Nothing more than we've done by drawing attention to the list by discussing > > it over the past couple of days. Your post did have one semantic oddity > > that might have continued to dissuade people from using it, but we've now > > sorted that out. > > My "semantic oddity" statement "and/or" stands. > http://www.mail-archive.com/leaf-devel@lists.sourceforge.net/msg05368.html The semantic oddity was considering a security advisory to not be a type of announcement. The "and/or" stands because, as you say, that sentence was implicitly excluding anything security-related when it talked about "announcements". > I'll post something to leaf-user when this thread concludes. Lord let that be soon... ;^> > > People forget. If they don't use a list regularly, they can forget it > > exists. It's not surprising that people don't remember your admonitions in > > the past to use leaf-announce. However, if you (or someone, for instance > > me, recently -- anyone who takes an interest) continues to remind people > > about it by asking that they re-post certain things on leaf-announce so that > > people only subscribed to that list will have the benefit of the > > information, then eventually the list will get to be used often enough that > > people _will_ be consciously aware of it, and the decision to post there > > will be natural. > > I don't believe nagging our project members is beneficial to our > project. Politely asking someone to re-post something on the appropriate list does not equate to "nagging" in my mind. And as I said, if leaf-announce use can just be jump-started, it's hopeful that once people are receiving pseudo-regular posts on it, they'll be consciously aware of the list and people won't need to be reminded to use it very often. -- Dan Harkless [EMAIL PROTECTED] http://harkless.org/dan/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
