in reply to TPF RFC

Since my blog comment wasn't approved, I posted my TPF recommendations on my own blog. Basically it comes down to three things (for starters):

  1. Community Events Calendar: something like the right sidebar on PHP.net's homepage but for YAPCs, PM meetings, Hackathons and one-offs like the Pittsburgh Perl Workshop. A dynamic events calendar on the perl.org and pm.org homepages can easily show people what's happening in the community.
  2. Use Perl-based software on TPF sites: the Planet Perl, Planet Perl Six and Planet Parrot sites say "powered by python" and/or "powered by planetplanet" (planetplanet is python-based sofware). It would be nice if those sites migrated to Plagger so they would be Perl-based.
  3. Better communication: I get the feeling TPF doesn't communicate with the community very well. It may be better if they communicated more like an open source project, e.g. (a) talk about future plans, (b) respond to emails, (c) have unmoderated comments on the blog and (d) have a public IRC channel (is there one?).

Just my 2 cents.

Replies are listed 'Best First'.
Re^2: All TPF blog entries get approved (was: TPF RFC)
by Ovid (Cardinal) on Aug 29, 2006 at 15:00 UTC

    All TPF blog entries which are not spam are approved. The only ones we reject are obvious spam entries. I try to go through and make clean up the spam periodically, but if it's a legitimate response, it's approved whether I (or anyone else) likes it or not.

    The only thing I can think of is that the entry was marked as "junk" by accident. If so, I apologize. I'll talk with Robert and Ask and see if there is a better way of handling this. In any event, thank you for your feedback. We really appreciate it!

    Cheers,
    Ovid

    New address of my CGI Course.

[reply]

In Section Perl News