[Members] Voting criteria

Nolan Eakins sneakin at semanticgap.com
Tue May 10 22:33:23 CDT 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bart van Bragt wrote:

| Nolan Eakins wrote:
|
|> I guess trying out the
|> programs would give us something to do.
|
| Eehm. It's not like the average JSF member is bored and has lots and
| lots of spare time. IMO there are more productive things that the
| JSF could do than create even more open-source projects, what would
| the added value of being an 'official JSF project' be anyway?

I'm not suggesting creating new projects as should be apparent in
previous posts in this thread. I'm suggesting that we or a program's
author(s) nominate their program to be a "JSF Official Project". What
would be the added value...

| IMO doing more marketing would be much, much, much more productive.
| There are already lots and lots of people programming cool things
| for Jabber. If we want to increase the number of projects further we
| should work on more basic stuff like making sure that people know
| what Jabber is, creating up to date documentation (FAQs, HOW-TOs,
| etc), making press releases, creating exposure for Jabber in the
| online and offline media, etc, etc, etc.

...marketing is the added value! We'll be able to focus our efforts on
PR, documentation, etc. on the official JSF projects. It's rather
pointless to market only a protocol and its extensions. There needs to
be something to market, and a process should be in place to choose
what to market.

| There has been a lot of talk about these things and also about
| new/better server/client lists, certification programs, etc, but
| almost nothing is followed through (yes, I know, jabbercentral.org
| isn't up an running yet either). IMO it would be nice to focus on
| these things first. IMO having a decent/usable certification program
| would be more valuable than yet another random opensource tool that
| does something with Jabber but now created by/through the JSF. If we
| really want to do something with software we should host a bounty
| system (that also has been talked about a few times but which also
| wasn't followed through).

Of the ideas discussed on this list and not followed through, this
would be the easiest to implement. No harder than the current member
application process. Slap up a web form, populate a DB, let memberbot
call out the votes, and then let the project make some noise on j.org.
In theory the program should already have bit of a community to make
that noise.

It could then lead into a certification system too as some bored
member or random person starts going through the protocol suites and
checks off some check boxes (another web form?).

As far as a bounty system, is there a FOSS implementation to set one up?

- - Nolan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCgX0ChuPszQVSPEARAjneAJoDPrVlrFDKT63d7J01WMl378NP4wCggh9B
Ks6wmAqXto2RtplezITslKw=
=S3tz
-----END PGP SIGNATURE-----



More information about the Members mailing list