Re: [perldoc2-developers] General Questions

[Joergen W. L. <joe...@gm...>]

Robert 'phaylon' Sedlacek schrieb:

> CPAN :) The web frameworks manage their own dependencies pretty well. I
> mean we should discuss _which_ XML module we use, _which_ database access,
> and so on. To keep the dependencies as simple and as communicated as
> possible. This should ease deployment too.

I'd prefer an "out of the box" approach as much as possible unless we 
have a really good reason not to.

>>> [stability issues]
>>>
>>> That's rather a deployment and development issue imho. We should
>>> certainly do testruns before deploying/updating the main site. Things
>>> like PAR could also help us with this, as it captures a whole environment
>>> (optionally even including core modules).

>> Or one step further - and you have something like apachefriends.org's
>> XAMPP project.
> 
> Also a possibility. Although I see the "other projects" and "whole
> different languages" target groups more fit to this way of distribution.

That would oppose the "simple" principle, though. After all the 
application itself does not really have to be "distributed", it's the 
services it offers - and they are distributed over HTTP, etc.

[hosting on sourceforge]

> Question is which perl, what kind of webspace, how much influence on the
> perl environment, etc.

perl 5.8.3
Apache 1.3.xx?
...

Well... not very much info.

>> BTW - There's plenty of space on my server... :o)
> 
> Which might be a much better fit. Sidenote: Of course I mean the
> translation platform itself, not the hosting of the finally translated
> files. 

Oh - really? :o)

Let's hope the translated files eventually reside on peoples harddrives 
or under xx.perldoc.perl.org.

> For that I'd think a sort of export (e.g. into the projects SVN, so
> everyone, including the $lang.perldoc.perl.org space can easily stay up to
> date) would be a much better fit for that.

That also should be part of the "workflow" page... more work... oh my!

So far....

Joergen