= 27d567bc2d48d9f40e9ccc20ea370b15)
Vladimir_Nesov comments on Open Thread: April 2009 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (127)
There should be a mailing list. Any open source project must have one, even if the issue tracker is supposed to take care of most of the day-to-day working exchange. You should ask the project owners if there's one already, and if there isn't, set one up, for example, using google groups. The introductory pages should also link to the mailing list.
mailing list created: http://groups.google.com/group/lesswrong-dev
I started working on some bugs, and the lack of a mailing list makes things a bit complicated.
I'll add it to the wiki if it gets used; it might be better if the project owners created one instead.
Could you change the settings to make it more open by default? You can always change it back if you hit problems.
You're right - changed.
Indeed, it'll be useful only if people in the know join it. I believe the archives should be public, and probably joining should be automatic, but the first post moderated.
An LW post is a mailing list, in a way. I'd say go ahead and put up the post for now. Mailing list can be added later.
Only in a way. It's as easy to set up a mailing list as it is to create a post, but the post is a short-term solution, so I don't see any advantages in doing that.
The stronger our reply notifications are, the more like a mailing list it becomes. If we could subscribe to posts, for example, then a post would be just like a mailing list, but with easy threading and archival.
Posts don't have named threads. Google groups and gmail provide threading and archival. Gmail allows to set up custom filters. Group admins can manage membership.
All that is good, but we can get there later. I don't know if there are more than three of us yet. Once there are more than six people who want to discuss the software, we can look at better mechanisms.
I have added links to the mailing list in the README in the code (which GitHub shows) and also on the 'Home' wiki page.