DSL Ideas and Suggestions :: Open up the wiki (DSL docs badly needed)
Quote
It is oouser.tar.gz, not ootar.gz
That's not really a misspelling or a typo. It was written in the early days of UCI, when there were also *.ci extensions that did not include the user.tar.gz file. The file was a separate tar.gz mydsl package. The 'oo' in this case stands for Open Office, because it was the user.tar.gz for the Open Office extension.
That's not to say that this article does not need some work...just explaining the filename =o) With roberts permission I can make that a bit more clear, and also the bit about the cloop limit (maybe specify which versions of DSL have what number of cloops, if i can recall)
EDIT: here are a couple of suggestions about things I can't change myself:
Category:MyDSL should be a subcategory of Documentation.
The main page should be modified to list "Documentation" as a main link rather than its current status of being what appears to be a static header. I know it's not static, but it appears that way. Tables of contents have always been set up, and with good reason, with main categories being most prominent and subcategories being recognizable as subcategories. Take the numerous How-to pages available for example. They are uniform, with a main category as a prominent clickable link and its subcategories slightly less prominent. In this way there is no question that going to the "Documentation" link will also show each Documentation subcategory below. If the Wiki main page is to keep its current layout, then every Documentation subcategory should be listed in the box labeled "Documentation" so the reader does not have to go in circles to find what he's looking for.
EDIT2: I found the message concerning what not to put in the wiki to be a little extreme, and I don't plan to follow it more than loosely. Including general linux information in the DSL wiki is vital for a new user, particularly when the distribution itself has no room for the general linux docs that are commonly found in other distros.I knew about .ci extensions, though when I started writing extensions, at about DSL 1.5, they no longer worked. I never saw oouser.tar.gz, though. Then again, I keep track of my finances with firefox and leafpad.
Thanks for the history lesson, mikshaw. Did you notice how if oouser.tar.gz was replaced with user.tar.gz, that that sentence would still make sense? It would still be an equally valid and appropriate point about ucis being read-only.yes, it would be applicable to today's uci package. I would also like to expand on the use of the user.tar.gz file (how it is essentially a second mydsl extension) and the shell wrapper.I've begun adding articles that I believe will be very useful to the new user. There is a new subcategory in Documentation which will list as many configuration files as I feel compelled to write about, I will be adding more to the Apps category, including brief descriptions of DSL applications (at least those that I know something about), and I will add a new category for "DSL_Tools", which will explain the tools that were written specifically for DSL.
That's all I have planned for now.I just wanted to voice my agreement with the original post. I edit wikipedia all the time, and the day I started playing with DSL, I looked at the wiki and thought, I can make some contributions here. But then I found I couldn't.
Opening the DSL wiki up to anyone to edit might not be the answer ... dealing with spam and vandalism is the biggest frustration I have with wikipedia, and they have tons of folks devoting all their time and effort to combatting it, which I'm sure is a job no one wants to take on with the DSL wiki. My recommendation would be put some contact info on the wiki about how to get an account created, and tone down the threatening language in the "how to use this wiki" page. I do believe it would be best to set enough obstacles to creating an account to discourage the spammers and vandals, but at least make sure the well-intentioned folks aren't driven away along with them.Next Page...
original here.