-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> True. But since these are new projects we need a forum to announce new
> releases.
Then plucker-announce is the place to send that, or plucker-list,
but having a third-party project that uses Plucker using the lists dedicated
to Plucker's users and development of Plucker itself, is probably straining
towards being off-topic.
This "problem" must exist for the other 50,000 projects on
SourceForge as well, and they don't seem to have an issue with announcing it
either. SourceForge has all of those facilities for a reason, so I'm told.
> Now I can post news to freshmeat and sf.net but I doubt anyone would pick
> it up amidst all the other non-Plucker announcements.
That is the result of so many projects in one place, unfortunatey.
> plucker-dev and plucker-list are just about the only really active Plucker
> forums.
And still unrelated to any third-party development and bugtracking.
There are probably a dozen projects actively using Plucker, or some
sort of Plucker components (Fling-It, Agenda Reader, etc.) and they don't
use the Plucker mailing lists to report their bugs or track releases and
usability issues.
> As for plucker-announce: for all intents and purposes it lies dead in the
> water. There are about twenty posts between March 2001 and September 2002.
> (Notice that Viewer 1.2 wasn't even announced there.) I didn't even bother
> subscribing.
It's also moderated (thankfully), for a reason. If you have a tool
that you'd like to annouce there, it gets posted when Mark approves it. If
people aren't subscribed, perhaps they don't care to know about new
releases.
As with PlkrData, an email to [EMAIL PROTECTED] (which gets sent to
me anyway) will get your release put on the Plucker website (thanks Tony).
The website gets much more visibility than the plucker-announce mailing
list, to be sure.
> I've put a notice in my signature stating that issues with JPluck should
> be reported to me directly. I think that should satisfy your concern.
> Meanwhile, I'll keep posting announcements.
I'm not saying that your work, or the project isn't valuable, it
definately is (though for me, it serves no purpose, all of my Plucker work
is done with perl now anyway), but that continuing the discussion about how
Java bits and pieces won't load properly, etc. probably would be considered
"off-topic" here, since those relate to your tool, and the use of your tool,
not to the use or development of Plucker itself.
If, however, your tool used the Python or Jython parser/distiller,
that would be a different story entirely, since as the python code used by
Plucker matures, your code will be affected by inheritence. Does that make
more sense?
As an example, PIL, the graphics tool used by Plucker, which exists
on SourceForge also, doesn't have bugs reported here either (nor do issues
with Python, also on SourceForge), and anyone here with issues using PIL,
would report them there also.
> I'm willing to move JPluck to plkr.org, if that makes me less
> "third-party". Let me know if that is possible.
Moving it to plkr.org would still make it third-party, since it is
not part of Plucker itself, much like Abiword is not part of Microsoft Word,
even though they can both edit and deal with the same files.
I'm ok with people talking about JPluck here (and believe me, I'm
only one person, certainly not the majority vote), but continuing to discuss
JPluck usability issues in the Plucker lists, where those issues are
probably unrelated to Plucker's use or development, is probably off-topic.
If you want me to provide services/etc. for you on SourceFubar, I'd
be glad to, but I think SourceForge has more bandwidth and manpower to
provide what you need than I can at the moment. Let me know, though, if you
change your mind.
Keep up the great work. One of these days I'll give JPluck (and
PlkrData) a try. I've been dedicated to trying to find a paying job (been
out of work now for over 400 days) and releasing all the Plucker perl stuff
I've been working on over the last year.
d.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+BM64kRQERnB1rkoRAsa5AJ0RXIJUvVvBruABaYbNrWfC8c3lKgCg0aLo
WhH7FBn7rP9H08aFRBeKzGA=
=4g6n
-----END PGP SIGNATURE-----
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
