Mike Noyes <[EMAIL PROTECTED]> writes: > > "The person making the announcement needs to decide the target audience" > > _is_ more vague than "security advisories should be posted to > > leaf-announce". > > You keep returning to security advisories. I'm talking about > announcements. In my mind they are distinct and different things.
As I made clear, I think in most people's minds, a security announcement is a type of announcement. If they aren't in yours, then you're using some weird semantics and people could get confused about the leaf-announce policy, which was my only point. > > 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. 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. > > That would be more likely if the policy as to what kinds of things should be > > posted there (e.g. security advisories and new version announcements) were > > short, clear, and concise. > > The announce list was created shortly after our project was founded. Its > stated purpose hasn't changed. Our project members haven't used it. What > do you want me to do about it? 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. > > It absolutely _is_ relevant to leaf-user. People need to know what types of > > things (e.g. security advisories) they can still expect to receive once > > their immediate problem is fixed and they've unsubscribed to leaf-user but > > stayed subscribed to leaf-announce. > > I believe this is a project administration topic, and it belongs on > leaf-devel. Well, at least the final result of the discussion deserves to be known by the leaf-user subscribers, but since I had the final post on that list before you redirected it off, and that post pointed out your semantic oddity, I won't insist we make another post on it. > In summary: we agree that the leaf-announce list is underutilized. I've > tried in the past to get our members to use it. I wasn't successful. > What suggestions do you have to remedy the situation? Just telling them > to use it isn't sufficient. At least it wasn't in the past. 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. One thing you said is that in the past you re-posted things to leaf-announce _for_ people. That's not a good way to get people to post there, since they're more likely to just come to depend on you moving things over when appropriate. Better to ask people to re-post things themselves -- the conscious effort they'll have to expend posting it twice is more likely to lead to them to just post to the right list in the first place next time. -- 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
