Maybe we need a "detailed announce" list, where I can send stable build
updates and so on to?

On Thu, May 22, 2003 at 10:52:34AM -0700, Todd Walton wrote:
> On Thu, 22 May 2003, panamerica334 at gmx.net wrote:
> 
> > why aren't these cc'd to the annouce list?
> 
> In the past, it's only been version number increases that have been posted 
> to the announce list.  I can't speak for the actual reason for this, but 
> it makes sense to me.
> 
> I've often received "announcements" from various places.  I hadn't done 
> anything with those places in a long time, but I couldn't complain about 
> the email, since I *had* signed up to receive announcements.  In the 
> process, I was reminded about this thing that I had once been interested 
> in and had dropped, thinking it needed more time to develop, or that I 
> wasn't quite ready for it.  Being reminded of it, I went to check it out 
> again.  I've never been in this situation with Freenet, but there may be 
> those who are.
> 
> They check out Freenet, sign up for the announcements, find that they 
> don't like Freenet for whatever reason, and give up.  A month later, they 
> get an announcement about a new release with all these nifty new 
> improvements, and they maybe consider trying again.  If they don't, they 
> just delete the email, and end up going through the same thing again a 
> month later.  If they were getting an email from this project they weren't 
> interested in every week, then simply unsubscribing from the list would 
> become an attractive option.
> 
> At least, that's the way I'd react.  I like announcment lists that allow 
> me to use them that way.
> 
> -todd
> _______________________________________________
> devl mailing list
> devl at freenetproject.org
> http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20030522/76a4fcc9/attachment.pgp>

Reply via email to