Gerald Pfeifer | 1 Aug 2005 01:00

Re: [docs] Add link to gfortran wiki for binaries

On Sun, 31 Jul 2005, Daniel Berlin wrote:
> So, uh, fix it.
> It probably took your 3x longer to write this message than it would have
> to double click on the page and edit it.

You fail to see the educational value of (patch) reviews.

Gerald

Daniel Berlin | 1 Aug 2005 01:25

Re: [docs] Add link to gfortran wiki for binaries

On Mon, 2005-08-01 at 01:00 +0200, Gerald Pfeifer wrote:
> On Sun, 31 Jul 2005, Daniel Berlin wrote:
> > So, uh, fix it.
> > It probably took your 3x longer to write this message than it would have
> > to double click on the page and edit it.
> 
> You fail to see the educational value of (patch) reviews.

You just don't get it.
The idea is not to force the developers to work inside the box you want
them to work on, it is to collaborate and use tools that enable
developers to work inside the box *they* want to work in, while still
producing something *everyone* can use.

We are supposed to be encouraging developers and contributors.
Constantly putting roadblocks in their way does *not* do this. 
Do you really think the reason our docs aren't good is because we don't
have enough process?
Or that we don't mandate enough contribution to them?

If you can't see this isn't the real root cause of the problem, there is
simply no point in continuing this discussion, and i'll go my way and
stop contributing to docs except as i'm required to as part of patches,
and happily stop maintaining tools like the wiki that everyone but you
seems to find useful.

Daniel Berlin | 1 Aug 2005 01:18

Re: [docs] Add link to gfortran wiki for binaries

On Mon, 2005-08-01 at 01:00 +0200, Gerald Pfeifer wrote:
> On Sun, 31 Jul 2005, Daniel Berlin wrote:
> > So, uh, fix it.
> > It probably took your 3x longer to write this message than it would have
> > to double click on the page and edit it.
> 
> You fail to see the educational value of (patch) reviews.

For most documentation?
Yes. 
All having patch review for most documentation does is make it so we
don't have up-to-date or useful docs.

Repeat after me:  Documentation is not code.

You fail to see the value of collaborative development for
documentation, while strangely, other projects have embraced it and have
*much* better documentation than we do.

> 
> Gerald


Gmane