[ home | blog home | recent activity | guestbook | plugins i'm using (19) ]
You've just finished the most fantastic plugin ever and you want to give it to everyone! Woah Nelly--before you distribute it, think of these things!!!
First off, you should make sure you have some kind of license statement in the plugin. What can users do with the plugin? Can they modify and redistribute it? Do they have to pay for usage? Blah blah blah (feel free to steal my license statement).
Second, you should have a copyright notice in the plugin header so people know who owns it.
Third, in order for people to know which version they have and thereby recognize when there is a new version and such, you should have the following items:
Then you should include instructions on how to set up the plugin (any config.py parameters that need to be set, any flavour files that need to be created, other data files that need to exist, ...), how to use the plugin (what variables it might expose to templates, urls that it does things with, ...), and whatever other documentation the user would want to know.
Doing all of this will help the user know what they've downloaded, how to use it, what it does do, what it doesn't do, how to figure out when a new version is out, and what rights they have.
For examples, look at the headers of all my plugins in my plugin index.
changelog
I reserve the right to remove comments that are anonymous, flames, spammy, inappropriate and/or rude. Sometimes I'll reply in email directly--so make sure your email address is correct. New comments get placed in a "draft" status and will NOT show up on the site until I explicitly approve it. Sometimes that happens within 24 hours.
If you can't for some reason post a comment, send me an email: willg at bluesock dot org.
All contents Copyright 1996 to 2010 Will Guaraldi Kahn-Greene.
This work is licensed under a
Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.