Nathan Torkington wrote:
>
> I like the idea. Is there a threaded discussion package for mod_perl?
>
mwForum does a nice job, and runs under Apache::Registry. It allows
both the usual threaded messaging and file uploads/downloads, so it's a
natural for associating files and comments.
I use it
>>OK, you probably don't want it to be another mailing list
>>then. But a web
>>bbs that allows you to post replies to code.
kind of ... I would like to see someplace to post _working_ code (complete
or snippets) with an explanation of what you are trying to accomplish, and
with any issues/spec
Let's create a "Mod_perl League" - it gives us
at least one line on the first page of LWN.net
OK, you probably don't want it to be another mailing list then. But a web
bbs that allows you to post replies to code.
So you still post your issue here and entice people to go to the URL with
your code (On the root post of a WebBBS). And then allow people who happen
to have the time when you
> "Stas" == Stas Bekman <[EMAIL PROTECTED]> writes:
Stas> Personally I've found that it's much easier to find a few coders that you
Stas> believe that their style is good and learn from their code. In my early
Stas> days I've learned a great deal of idiomatic Perl coding from Randal's
Stas> c
> I like the idea. Is there a threaded discussion package for mod_perl?
Good idea...
I'm working on one, kinda sorta. Right now, it's an Apache::Registry
hack based on crufty old Perl 4 code I wrote back around 5 years ago.
In other words, I won't even let other people look at it. (If anyone
> >>Just don't post your code to the list itself. It's rude to
> >>bloat the mails on the list. Provide a hyperlink to your annotated code.
>
> True, but what happens after you get your answer? You take the code down and
> move on. It would be nice to have a place to post the code where it can
Homsher, Dave V. writes:
> With all of the advocacy talk on the ML right now I've been
> mulling around the idea of having a "peer review" forum where one could post
> code that you are currently working on w/an explanation of what you are
> trying to accomplish and have the community review/give
"Homsher, Dave V." wrote:
>
> >>Just don't post your code to the list itself. It's rude to
> >>bloat the mails on the list. Provide a hyperlink to your annotated code.
>
> True, but what happens after you get your answer? You take the code down and
> move on. It would be nice to have a place to
>>Just don't post your code to the list itself. It's rude to
>>bloat the mails on the list. Provide a hyperlink to your annotated code.
True, but what happens after you get your answer? You take the code down and
move on. It would be nice to have a place to post the code where it can be
organize
You're describing what open source is about. People do this all the time
here on this mailing list and others. If you have some mod_perl code you
are trying to produce, put it up and write an email asking for comments.
You may not get many people reading (most people are quite busy at any
give
11 matches
Mail list logo
