[tex-live] linguex in texlive snapshot

[Robin Fairbairns]

Manuel Pégourié-Gonnard <mpg at elzevir.fr> wrote:

> Frank Küster scripsit (17.08.2008 15:44)
> > $ grep -A1 license entries/a/acronym.xml 
> >   <license type='lppl' version='1.17' checked='2006-03-07'
> >   username='frank' file='header'/>
> 
> Oh, I wasn't aware of the "checked" field. Good news that it already exists.

it's not exactly common (it came as a surprise to me, for sure -- a
whole bunch of people who i'd never heard of, checking new versions in
that make no difference to the user-displayed output).

i've done a few myself, but it's ineffably tedious -- as witness the
tiny number of entries thus marked in the several thousand total in the
catalogue.

> >    - I think "lppl" means some "or
> >      later" clause, but I'm not sure, and I'm not sure whether I've indicated
> >      any "exactly version $foo" somehow.
> > 
> >    - Which files are covered (this is important in particular for font
> >      stuff)
> 
> Agreed, and also there should be a way to indicate contradictory statements,
> like "lppl any version" and "you shall not modify" in the same file, as it
> sometimes happens.

which, is being interpreted, "other-nonfree".  i changed a package from
lppl to nosell this morning, since the author had added the proviso that
no part of it should be included in a package for sale.

i can't record that in the present structure.

> >    - author could be contacted at $date by $collaborator under
> >      $e-mail at address.
>
> Or also (unfortunately) "missing author address".
> 
> >    - $collaborator is currently in contact with
>
> With the date of the "currently" :-)
> 
> >    - don't bother to try to get the license changed, this will stay
> >      non-free 
>
> Agreed to.

this lot merely skims the surface of the collaboration issue.

at present, there are two people who write catalogue entries: rainer s
(for the packages he installs) and me (for everything else, and for
packages who never had an entry in the first place).

it's easy for us to collaborate.  if someone else (e.g., karl) finds a
problem, they can mail one of us and we'll put it right.

to widen the collaboration, we need something better supporting the
enterprise, than a subversion server.  (imo)

as the (only) person who does significant quality work on the catalogue,
i've lots of scrappy little notes about what's in progress, what needs
to be done, whatever...  if we set up a collaboration, we need something
to hold scrappy little notes, not well structured statements about
entries.  work in progress, that is.  not necessarily related to a
catalogue entry.

i have no idea how to do such a thing.  but then i've already said i
want no part of setting up collaboration: i merely offer to collaborate
if i'm wanted when the time comes.

robin