This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH,wwwdocs] redirect users to the gfortran wiki
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: sgk at troutmask dot apl dot washington dot edu
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Wed, 21 Dec 05 23:34:15 EST
- Subject: Re: [PATCH,wwwdocs] redirect users to the gfortran wiki
> However, not requiring any form of copyright assignment/disclaimer/
> whatever means that we will not be able to take any of that and
> integrate it into our regular documentation or main web pages. And
> this does concern me.
A large amount of info on the Fortran home page is out of date due
to its transient nature. For example, we have a wish list of Language
Extensions. Item 9 is completed, item 8 is on its way, and item 3
is being worked. The hoops to jump through to change the status and
then delete the item in a few months is too much when I'd rather be
hunting gfortran bugs. The TODO list is even in worse shape. Many
items have been fixed or implemented.
There are two separate possible purposed for a wiki. One is what you
talk about, which are todo lists and related transient material. I
agree with others that a wiki is the best way to deal with such material
and there's no IPR issue because there's no final product.
However, the other usage is a sort of collaborative documentation, akin to
the way wikipedia works, with the goal of making a final document that
can become part of the official documentation. In *that* case, you need to
be very clear that you track the IPR status of every contribution. If you
don't, you can't distribute the result or even use it as a starting point
for a rewrite, thus making all the work useless.