[geeklog-devel] Wiki docs

[Vincent Furia]

While its probably a bit more subjective than measuring code, I think
the same idea can work here.  We can identify the holes in the wiki,
and then offer bounties to fill them.  Like Oliver said, we can grade
on number or words; but we should also evaluate the product based on
correct grammar (at least understandable), spelling, sufficient screen
shots etc.

-Vinny

On 7/11/07, Oliver Spiesshofer <oliver at spiesshofer.com> wrote:
> I guess the number of words is the trigger here. We simply pay by word,
> and simply say that the text has to increase the understanding of the
> user/developer about the functions described.
>
> Oliver
>
> Dirk Haun wrote:
> > Vincent Furia wrote:
> >
> >
> >> Offer (small?) bounties for significant contributions?
> >>
> >
> > How would you decide when a contribution is worth something?
> >
> > bye, Dirk
> >
> >
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>