Mailing List Archive

Perrin Harkins wrote:
> On Mon, 2004-08-09 at 14:59, Stas Bekman wrote:
>
>>That's the whole point. In order to make things simple, it shouldn't
>>require commit access or anything list that. We could even use a
>>simplified version of slashdot, so people can submit stories, people can
>>comment on them, making it much more efficient and not creating any
>>bottlenecks.
>
>
> Yes, we could set up a blog for news. It seems a bit redundant to have
> comments when we already have the mailing list(s), so I would skip
> that. We also can't put things on the site without an approval process,
> so it would need users and permissions. If we are able to host web apps
> on perl.apache.org and someone out there feels like playing with some
> simple blog software (Blosxom? Bryar?), that would be fine with me.

Just throwing ideas, really. If the overhead of managing news is too
big, it will be too easy to stop doing that. So I'm just wondering
what's the simplest approach for more people being able to contibute w/o
as little overhead as possible.

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe@perl.apache.org
For additional commands, e-mail: advocacy-help@perl.apache.org

* Perrin Harkins (perrin@elem.com) wrote:
> Glancing at the YAML docs, it looks like putting "----" between those
> would make them parseable as records, so maybe we'll use that after all.

YAML is _very_ buggy.

http://rt.cpan.org/NoAuth/Bugs.html?Dist=YAML

Also from the YAML POD...

WARNING: This is *ALPHA* code.

BIGGER WARNING: This is *TRIAL1* of the YAML 1.0 specification. The
YAML syntax may change before it is finalized. Based on past
experience, it probably will change. The authors of this spec have
worked for over a year putting together YAML 1.0, and we have
flipped it on it's syntactical head almost every week. We're a
fickle lot, we are. So use this at your own risk!!!

Why not just keep it simple, and put text files in a directory and name
them (so you can easily determine order via sort glob)

$year-$month-$day-$hh$mm-filename_safe_headline

and then in the file, make almost e-mail-like

Author: Philippe M. Chiasson <gozer@
Title: How mod_perl saved my life!
Reference: http://www.cnn.com/mod_perl_saved_my_life.html
Date: 2004-08-09
Story Image: http://gozer.ectoplasm.org/me.gif
Category: Success Stories
<-- blank line
the abstract goes here... la la la
---------
the rest of the story goes here la la la

I've just had a bad go with YAML a couple of times. Thought it was the
best thing since sliced bread, until I dumped something to YAML
and couldn't load it :(

BTW, got my darn e-mail fixed... stupid default debian exim install was
rewriting my envelope From and my Sender: header to my user account
instead of the address in my "From:" header.

-- Jeff Bisbee / mod_perl-advocacy@jbisbee.com / jbisbee.com

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe@perl.apache.org
For additional commands, e-mail: advocacy-help@perl.apache.org

Perrin Harkins wrote:

>Sure, with some small tweaks (add a date, remove separate story, remove
>reference, change author icon to story image). See http://php.net/ for
>an idea of what I'm going for.
>
>
Have you looked at blosxom? At first glance, it seems to have everything
you're looking for.
http://www.blosxom.com/

Kenny

---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe@perl.apache.org
For additional commands, e-mail: advocacy-help@perl.apache.org

Jeff Bisbee wrote:
> * Perrin Harkins (perrin@elem.com) wrote:
>
>>Glancing at the YAML docs, it looks like putting "----" between those
>>would make them parseable as records, so maybe we'll use that after all.
>
>
> YAML is _very_ buggy.
>
> http://rt.cpan.org/NoAuth/Bugs.html?Dist=YAML
>
> Also from the YAML POD...
>
> WARNING: This is *ALPHA* code.
>
> BIGGER WARNING: This is *TRIAL1* of the YAML 1.0 specification. The
> YAML syntax may change before it is finalized. Based on past
> experience, it probably will change. The authors of this spec have
> worked for over a year putting together YAML 1.0, and we have
> flipped it on it's syntactical head almost every week. We're a
> fickle lot, we are. So use this at your own risk!!!
>
> Why not just keep it simple, and put text files in a directory and name
> them (so you can easily determine order via sort glob)
>
> $year-$month-$day-$hh$mm-filename_safe_headline
>
> and then in the file, make almost e-mail-like
>
> Author: Philippe M. Chiasson <gozer@
> Title: How mod_perl saved my life!
> Reference: http://www.cnn.com/mod_perl_saved_my_life.html
> Date: 2004-08-09
> Story Image: http://gozer.ectoplasm.org/me.gif
> Category: Success Stories
> <-- blank line
> the abstract goes here... la la la
> ---------
> the rest of the story goes here la la la
>
> I've just had a bad go with YAML a couple of times. Thought it was the
> best thing since sliced bread, until I dumped something to YAML
> and couldn't load it :(

Well, as far as I am concerned, the actual format that's choosen will mostly
be important to the person that decided to implement the news system (perrin).

So I guess as long as it's simple and it's a simple format enough for Joe Anybody,
I think we should let perrin decide.

Perrin, any thought on this ? Maybe it's just a matter of arbitrarly picking the
simplest format we can think of YAML/Email and starting to implement something.
Reserving the option of moving to a different format later on down the road if
it becomes an issue ?

> BTW, got my darn e-mail fixed... stupid default debian exim install was
> rewriting my envelope From and my Sender: header to my user account
> instead of the address in my "From:" header.

Congrats!

> -- Jeff Bisbee / mod_perl-advocacy@jbisbee.com / jbisbee.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: advocacy-unsubscribe@perl.apache.org
> For additional commands, e-mail: advocacy-help@perl.apache.org
>
>

--
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5

On Aug 9, 2004, at 2:44 PM, Kenny Gatdula wrote:

> Have you looked at blosxom? At first glance, it seems to have
> everything you're looking for.
> http://www.blosxom.com/

FWIW, the forthcoming Blosxom 3.0 will run under mod_perl. I'll help
Rael to make sure of it.

Regards,

David