|
Wiki simply means, "what I know is...". If you know something, and you have something valuable to add to the official documentation, what is so wrong with having to request access? That said, there's nothing stopping anyone from setting up their own site with a wiki focused on e-17, and if something valuable is posted there that should be in the official docs, someone who does have access can simply post it to the official documentation. At least at this point, though, there are a lot of changes going on, and if you allow just anyone to post it requries more work from the e team's end beceause someone would have to moderate that wiki. For example, if I am running a 3 month old build of e, and I try to do something that consitently causes e to crash, I might just be tempted to put on that wiki that e won't work with app xxxx. That would be wrong though, because I'm way out of date, but that would mislead other users to believe something about e based on what is found on the official e website. Besides, the mailing lists and various forums and blogs out there suffice for now. Eventually when e17 is more complete, a wiki might be in order, but right now in it's ever changing state, I think it would be a bad idea. Just my two cents. // Michael radar wrote: quoting the twiki reference manual:An Important Control Consideration |
_______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
