On Fri, 2007-03-16 at 13:26, Martin Hejl wrote:
> Hi Mike,
>
> > Is there a reason I'm the only one that's done anything with the new
> > wiki?
>
> as always, I can speak only for myself - but I'm going to assume that I
> speak for at least a few of the developers who might look at the wiki at
> some point.
>
> While the wiki might be a big help down the road, at least for me, the
> timing of SF opening it up to the projects participating in the beta,
> didn't work terribly well. I had a brief glance, which was enough for me
> to know that I didn't have enough time to really do anything with it.
Martin,
That's all I'm looking for is some feedback. I conclude you're
indicating the UI looks to complex to grasp in a short time.
<snip>
> I was wondering what exactly should go into the wiki
> - and what it was supposed to replace. Replacing the documents
> currently in doc-manager is fine - but to be honest, those are
> outrageously out of date, so simply migrating those would be a waste
> of time. Getting them up to date would be a good idea
I realize they're outdated, and need considerable work. Hopefully
placing them in the wiki will allow more project members to work on
updating them.
Note: not all of our project members are familiar with docbook.
> - but with everything else being in docbook format, it would seem more
> sensible to migrate those docs to docbook in our guides collection
> (unless you're considering we drop the whole docbook approach, since
> SF seems to make building the docs too difficult, and just go with
> the wiki - if that's the case, please say so, since then, working on
> keeping the docbook stuff updated would be time wasted).
I don't plan on dropping DocBook. In my opinion, DocBook is one of the
best options to generate guides for FOSS projects.
> In short, it seemed to me that the wiki was a place for people to
> provide their own content (like the developer pages were a while back) -
> if that's the case, just give people some time to get used to the new
> system. If that's not what you had in mind, you should probably be more
> vocal about what you want the wiki to be.
I expressed that exact thing numerous times on this list. The only
difference is most of my prior references indicated mediawiki. The SF
solution is much easier to manage. It's probably not as feature rich as
mediawiki, but I don't have to try and shoehorn it into the SF shell.
Note: SF even provides a way to dump the content from the wiki
to a tarball.
> I have a chapter for the Bering uClibc users guide that still needs to
> be committed to CVS (regarding creating an access point that supports
> WPA2)- in your opinion, should I (or anybody else who wants to
> contribute to the docs) continue to use docbook, or should I/we drop
> that and port it to the wiki?
As I indicated above, please continue to use docbook for guides.
> To me, the wiki doesn't provide any additional benefit for now - as far
> as I know, everybody who has written docs so far has managed to get
> them published in our guides. If keeping things up to date, and
> getting more people to participate is what the wiki will give us, I'm
> all for it
I hope this is the case. A wiki syntax is much easier to grasp than a
docbook schema/dtd.
> (and by the way, I totally agree with your decision to only
> give leaf developers access to the wiki - I've seen too many projects
> struggle with wiki-spam to make me want to consider opening up to
> everybody)
Agreed.
> I'm just not sure what the general direction of the wiki
> should be at this point.
This is the content I'd like to see in the wiki:
* individual developer content
* smaller howto's
* FAQs
Note: I'm thinking of the wiki as a documentation sandbox, and
the docbook guides as a finished product. I envision a similar
relationship for developer content in the wiki and our project
website.
> As always, just speaking for myself,
Noted.
--
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, sitedocs
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
