----- 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@xxxxxxxxxxxxxxxxx> > -- > websites mailing list > websites@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/websites -- websites mailing list websites@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/websites
