dividing up the wiki?

Chris Roberts croberts at cintrixhosting.com
Wed Aug 21 16:14:28 UTC 2013


Jaroslav,  I will start to work on drafting up a document on my best
practices for cleaning up the wiki. I will keep you posted on its
progress. It would be awesome to more people on board helping out, and
with a good best practice guide I think more people will be willing to
help wiki garden. - Chris Roberts>>> Jaroslav Reznik
<jreznik at redhat.com> 08/21/13 12:00 PM >>>----- Original Message ----->
I have been going through the wiki as of late and looking at each page>
and making sure any outdated information is corrected of put into an>
archive page. For example on team meeting pages we don't need meeting>
notes from 2008.> > For example here is the docs team meeting page:>
https://fedoraproject.org/wiki/Category:Docs_Project_meetings> > > and
the Archived page:>
https://fedoraproject.org/wiki/Old_Docs_Project_Steering_Committee_meeting_minutes_links>
> Part of my contribution to the Fedora is making the wiki look better,
I> have good experience with this, as its part of my day job in dealing>
with wikis.Wow, awesome to have you working on it. Could you please
document how do you deal with it and we can try to get it widespread, so
maybe morepeople would join you. It's a gigantic task and every hand
would benice I'd say ;-).Jaroslav> - Chris Roberts> > > Chris Roberts>
https://fedoraproject.org/wiki/User:Chrisroberts> > >>> Jaroslav Reznik
<jreznik at redhat.com> 08/21/13 10:52 AM >>>> ----- Original Message
-----> > I've been thinking a little bit about why our collaborative>
documenation,> > and, you know, why it's a painful mess despite all of
the awesome> interested> > people we have. I think that part of it is
that our wiki is> intimidating,> > and I think that's partly because we
use the wiki in different ways> all> > together:> > > >   1. End-user
and developer documentation that isn't as formalized as> that> >      at
https://docs.fedoraproject.org/ but is still very useful.> > > >   2.
Workspace for communication, like the features / changes pages,> the> > 
    font request workflow, or even just the packages wishlist.> > > >  
3. Free-for-all drafts and ideas that may eventually turn into one> of
the> >      above and may go no where, but shouldn't really be mixed in>
because> >      it's not at that level.> > I'd say these are valid use
cases for Wiki - and I'm not saying we can't> do better job to make sure
people understand which of the above sections> > they are. But we have
bigger problems - after years, even these,> previously> valid uses got
too outdated, that it probably does not make sense to> store> them (I
know, wiki & history), or at least not be visible to search (has> anyone
ever tried to use it at all ;-)?.> > So for me, the first step would be
to clean up old mess, make search> available again, review current
information (especially for stuff that's> in the main categories).
Having some way to sort out information would> cherry on top of our wiki
to make users happy :)> > Jaroslav> > > I wonder if there's a way we can
make the distinction more obvious,> and> > steer people appropriately?>
> > > > > > > --> > Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁>
<mattdm at fedoraproject.org>> > --> > websites mailing list> >
websites at lists.fedoraproject.org> >
https://admin.fedoraproject.org/mailman/listinfo/websites> --> websites
mailing list> websites at lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/websites> > > > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/websites/attachments/20130821/0cae3277/attachment.html>


More information about the websites mailing list