Peter J. Holzer writes:
On 2006-11-05 13:09:22 +0100, [EMAIL PROTECTED] wrote:
Peter J. Holzer writes:
>Something else I forgot?
Yeah, that people won't bother doing either of that. =/
Yes, that's problem with all polls.
Yeah, but the way you wanted to do it is, IMHO, a sure way to keep even more
people away from actually taking part... People that don't use wikis nor
feel like mailing stuff will/might push a simple button on a webpage.
Instead of being a "simple" poll regarding what people are using (which
doesn't say that much if people are using a lot of customized plugins)
there'd finally be this ultimate collection of plugins; a very simple way
for new/potential users of qpsmtpd to find out what's possible.
Once that's available it'd be easier to create a sort of package-system,
allowing people to easier install and configure plugins; using qpsmtpd could
grow into more or less a quick webbased configured system.
Start with creating a single page listing _all_ plugins;
That assumes that I know all of them. The most complete list I know of
is the one in the wiki.
Good enough, and then keep adding as people tell you about other plugins...
Using a wiki to add ones plugins isn't exactly user-friendly, so
qpsmtpd-plugins becomes a somewhat closed business (at least when it comes
to sharing ones plugins).
their name, a short description and an URL to where they can be found,
These are already on the wiki. Hence my first idea was to let people
vote there.
It's not exactly the easiest to use solution, the wiki isn't exactly a
beautiful example of UI-design...
Being new to qpsmtpd (I've just started porting my old solutions to it) I
try to ignore what I can do, and try to view the whole process from the
newbie-without-that-many-clues point-of-view (to see where obvious
improvements are needed); and using qpsmtpd is far from as easy as it
could/should be. Much because of the wiki.
Personally I think its much less work to mail a file to some address
(especially if there is a script to do it) than to go through a long
list of plugins and decide for each one whether it is good or not (which
btw is a different question that whether I use it or not).
Calling something a poll and forcing people to mail things is... hmmm...
well... I just don't like it. =)
Let's drop the poll-talk as well as the idea of it being a script, as if
it's something seperate, and move it straight into qpsmtpd as a feature that
people need to switch on (to keep the paranoid people happy)... About once a
month an e-mail goes out with this information: `grep "^[a-z]" plugins | sed
-e "s/ .*//g"`; that ought to be enough to begin with, but then we'd need to
do some version-checking of the plugins to see if it is an "official" plugin
or if someone's written their own plugin with the same name as an "official"
one. We could of course md5sum:ing the active plugins from the start, as the
changes to them should be similar enough that we'd be able to tell what
configurations are mostly used without it revealing any private information.
Just a thought or two about it... and if no one else feels like being on the
receiving-end of these e-mails I could handle that and automagically upload
the data to some webpage (or the wiki).
Personally, I implement what I need. But if any qpsmtpd developer is
feeling bored and looking for ideas to implement, such a page might be
useful. But since its mainly a source of ideas I think a wiki page
"ideas for new plugins" would be sufficient.
Maybe, but personally I think that having a wiki as the main source of
information is holding the project back.
/Tony
