LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"Mittelbach, Frank" <[log in to unmask]>
Wed, 3 Jul 2002 08:57:57 +0100
text/plain (64 lines)
let me clarify that statement a bit. i fully agree that larger projects
would benefit from something like sourceforge (the kernel would, for
example, and so would something like fontinst, koma and a small number of
others). but i was only trying to point out that this is not the case with
the majority of the lppl related software.


-----Ursprüngliche Nachricht-----
Von: Lars Hellström [mailto:[log in to unmask]]
Gesendet: Mittwoch, 3. Juli 2002 00:50
An: [log in to unmask]
Betreff: Re: Suggested changes to LPPL

>as an aside: which life is made unnecessarily complicated? I'm not aware of
>single software project under LPPL which would really gain anything from
>living on something like Sourceforge. I'm not saying that it wouldn't be
>if LPPL is approved, on the contrary, but i don't see Sourceforge and the
>as a real practical argument.

I beg to disagree; any software project large enough would certainly
benefit from living on _something_ like SourceForge. I agree most projects
governed by the LPPL only have one developer and these would probably not
benefit from it, but as soon as the project becomes larger than what one
developer can effectively maintain you do get a problem. Experience has
shown that a centralised server somewhere that holds _the_ current version
of the project and which all developers can access over the internet
removes much of this problem. Presumably provides
something of the sort for the LaTeX project, but setting up a completely
new site seems to me as a bit of overkill for reasonably sized projects. It
ought to be more effective to use one of the generic services that are
currently available.

CTAN, for one thing, does not suffice as a development server. As its name
indicates, it's an archive. Putting things on it requires communicating
with and the manual intervention of the archive administrators, which means
you hardly ever upload anything you plan to continue working on tomorrow,
and that takes away much of the usefulness of the central development
server. Maybe CTAN can be complemented by a "development hotel" such as
SourceForge, but at least to me that sounds like more work than getting the
LPPL approved.

In case you want a concrete example of a project then I've got that as
well: fontinst. I have on occation considered suggesting setting up a
fontinst project at SF, but the fact that the LPPL isn't approved has
stopped from pursuing that possibility. (IMHO it is a major problem for
fontinst that there isn't such a central server, because it really has
become too large for any of the persons involved to maintain on one's own.
The only components I've ever effectively maintained is the DTXs from which
fontinst.sty is generated. The latin alphabet MTXs and ETXs would probably
be far better maintained by Walter Schmidt, since he is anyway their top
user due to PSNFSS. The cyrillic alphabet MTXs and ETXs should be part of
the fontinst distribution, but the author of those is Vladimir Volovich,
which means he is the logical maintainer. And so on. But I digress.) In
view of the recent discussion on why the LPPL is different from the GPL one
could of course draw the conclusion that fontinst should not (unlike most
LaTeX packages) be LPPLed, but I would prefer that it stayed under the
LPPL, if possible.

Lars Hellström