Russell Sharp wrote:
> ...
> Fltk2 should be set up with its own newsgroup and everyone subscribed to
> general should be subscribed to fltk2. This would let people filter the
> messages better but still keep track of dev.
As I mentioned before, *if* we were to create another group, I'd go
for a 1.x group.
> As far as the website goes, the real problem is that there are errors
> and incomplete references in the documentation. You could give out svn
> accounts with access only to the docs. Is this already available? That
> would allow regular users to contribute and only require the devs to
> review it every other week or so.
It is technically possible, but unnecessary. Read-only access is
sufficient to make changes and submit them as diffs, e.g.:
svn co http://svn.easysw.com/public/fltk/fltk/trunk/documentation
fltk-docs
cd fltk-docs
... make changes ...
svn diff >mychanges.patch
The resulting patch can be posted to the bug page.
All of the documentation can be commented as well, and all posts
get sent to the document owner (or webmaster, for documents that
are from the source repo).
In short, what appears to be missing is for people to actually
mention the specific errors/problems they are seeing.
> In my experience, a wiki is better as it has namespaces and several
> other features that makes doc generation very efficient. However, it's
> been voiced that some don't like the wiki and it takes a lil more effort
> to convert it into an offline format. You should give it serious
> consideration.
Wiki's suffer from a variety of problems, including security issues,
"edit wars", and so forth. It takes a dedicated admin to monitor a
wiki, and quite frankly we don't have the resources for that.
Also, there is something to be said for documentation that is
centrally managed - you can't depend on Wikipedia for accuracy,
for example, but you *should* be able to depend on the FLTK
documentation.
That said, the existing article/faq/how-to database is already very
wiki-like - the only missing piece is support for multiple editors,
which I actually have implemented for another of my OSS sites. Add
some front-end enhancements to make the documents more accessible
and I think we'll be able to offer both dynamic, user-created
content and the more static developer-created content on the same
site.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Publishing Software http://www.easysw.com
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
