Next Previous Contents

7. Good communication practice

Your software won't do the world much good if nobody but you knows it exists. Also, developing a visible presence for the project on the Internet will assist you in recruiting users and co-developers. Here are the standard ways to do that.

7.1 Announce to c.o.l.a

Announce new releases to comp.os.linux.announce. Besides being widely read itself, this group is a major feeder for web-based what's-new sites like Freshmeat.

7.2 Announce to a relevant topic newsgroup

Find USENET topics group directly relevant to your application, and announce there as well. Post only where the function of the code is relevant, and exercise restraint.

If (for example) you are releasing a program written in Perl that queries IMAP servers, you should certainly post to comp.mail.imap. But you should probably not post to comp.lang.perl unless the program is also an instructive example of cutting-edge Perl techniques.

Your announcement should include the URL of a project website.

7.3 Have a website

If you intend try to build any substantial user or developer community around your project, it should have a website. Standard things to have on the website include:

Some project sites even have URLs for anonymous access to the master source tree.

7.4 Host project mailing lists

It's standard practice to have a private development list through which project collaborators can communicate and exchange patches. You may also want to have an announcements list for people who want to be kept informed of the project's process

7.5 Release to major archives

For the last several years, the Metalab archive has been the most important interchange location for Linux software.

Other important locations include:


Next Previous Contents