LinuxMCE Forums
General => Users => Topic started by: bongowongo on April 28, 2010, 09:04:35 am
-
Hello fellow users,
Had a problem with linuxmce 0810, and couldn't find a solution quick enough, or were not certain the wiki entry will even work on your newly installed 0810 beta?
Let's make this vow..............that if you used a wiki-page in 0810 succesfully put it in the 0810 category by using [[Category: 0810]] on top of the wikipage.
Example:
http://wiki.linuxmce.org/index.php/ShuttleX50V2
http://wiki.linuxmce.org/index.php/Category:0810
Because we are not into a release yet, you should state which built of the beta you used.
I think it is a good and simple idea, in the end we can purge all articles not 0810.
Please give me some feedback.
P.S.
This also counts for forum topics that are succesfully solved.
If you are not a linux wiz/coder/dev please contribute through the wiki.
-
Dude,
I fully agree and have proposed similar in the past. Sadly.... :-\
Let's hope your suggestion / appeal is more successful ;)
-
I want to see vow's
Do you vow?
-
Of course ;D
-
Could you explain this idea a little more? I would prefer that we not have a million categories if they aren't needed.
I think if there is something 0810 specific, it should be mentioned in the table of contents on that page, and not added to another category. As we move forward dedicating a category to what essentially is a snapshot in time doesn't seem very efficient. Proper tagging and notation should be more than enough to find what your looking for.
golgoj4
-
...
I think it is a good and simple idea, in the end we can purge all articles not 0810.
...
And destroy all of LMCE's history? I don't think so.
-
And destroy all of LinuxMCE's history? I don't think so.
I was not really serious on that :)
-
And destroy all of LinuxMCE's history? I don't think so.
I was not really serious on that :)
But I think it speaks to the larger question at hand. Why tie data to a specific release? Just properly annotate the wiki page to begin with and there will be no need for superfluous categories.
golgoj4
-
I actually suggested this a while back (and created the categories) but to no avail. I also suggested that we add a header to each page (maybe a table) that would act as a version compatability / relevance matrix, again no take up :( (It should be possible to to a mass modification to put an empty matrix at the top ov every page on the wiki, with an "unknown" status for every version. That way, s soon as someone visits a page with knowledge of its relevance, they can simply modify the matrix. This would have the effect of not only making the pages consistent, but also reminding folks to do this.)
One of the most frustrating things about the wiki is that it's hard to know if information is current / relevant. Even the last edited date doesn't neccessarily help! All these ideas are good ones for solving the problem, but only if there is "buy in" from everyone. Even a "Works with 810" logo on pages would be an improvement!
-
I actually suggested this a while back (and created the categories) but to no avail. I also suggested that we add a header to each page (maybe a table) that would act as a version compatability / relevance matrix, again no take up :( (It should be possible to to a mass modification to put an empty matrix at the top ov every page on the wiki, with an "unknown" status for every version. That way, s soon as someone visits a page with knowledge of its relevance, they can simply modify the matrix. This would have the effect of not only making the pages consistent, but also reminding folks to do this.)
One of the most frustrating things about the wiki is that it's hard to know if information is current / relevant. Even the last edited date doesn't neccessarily help! All these ideas are good ones for solving the problem, but only if there is "buy in" from everyone. Even a "Works with 810" logo on pages would be an improvement!
+1
Sounds like a stellar idea to me. I expect this should improve the participation rates quite a bit!
-
Weirdbeard65, work it out and let's make a sticky in the forum so these guidelines are known.
-
Weirdbeard65, work it out and let's make a sticky in the forum so these guidelines are known.
I'd be glad to, however my preferred option (a compatability matrix / grid at the top of each page) would require someone who is a Wiki Admin to do the mass insert (assuming this can be done, of course!)
Anyone else able to offer suggestions or help?
-
I talked to possy on IRC, and he said it cannot be done by mass insert.
-
Oh?
I've done similar on other Wiki's by running a query on the underlying SQL database. Of yourse, you need to be DBA to do that ;)
Otherwise, maybe we can write some sort of curl script to go in and edit all the various pages automatically. Not a good solution, though!
-
Ok well get that password from somebody.
-
We could try ;)
Before we go ahead and do anything, though, what is a good format for the table?
What information would people like to see?
I'm thinking something like:
| |Version | |Status | |Date | |Contributed / tested by | | |
| |710 | |Status Unknown | | | | | | |
| |810 | |Working | |29th April 2010 | |Wiedbeard65 | | |
What do others think?
Also, I reckon we should have a "Works with 810" type logo that we could add to wiki pages etc. Anyone artistic?
-
We could try ;)
Before we go ahead and do anything, though, what is a good format for the table?
What information would people like to see?
I'm thinking something like:
| |Version | |Status | |Date | |Contributed / tested by | | |
| |710 | |Status Unknown | | | | | | |
| |810 | |Working | |29th April 2010 | |Wiedbeard65 | | |
What do others think?
Also, I reckon we should have a "Works with 810" type logo that we could add to wiki pages etc. Anyone artistic?
This looks good! I think that this would greatly improve the quality of the wiki pages at a glance. As far as mass inserts, i've categorized tons of pages by just working my way down a list of articles + copy and paste. It eventually gets done. Now i think there a little to no uncategorized articles, not that I categorized them all but you get the point. In the end this is a community project and I think that this would be a great thing for people like me who cant necessarily contribute to the code-base to add more robust support.
Lets just agree on a standard format and go. :)
golgoj4
-
Works for me :)
I'll try to make a start on it later...
The reason I was suggesting a mass S&R was that it makes sure we've hit all the pages (even the odd ones!!)
-
you guys should try to make this a mediawiki template, so that you can easily insert this with parameters on the relevant pages.
Look at the meta mediawiki for instructions.
-Thom
-
Oh, I agree totally - I'm concerned about getting the information into the existing pages though.
Still, at least once this is done, I'll feel I've contributed something!
-
Looks nice.
Go for it, if you need manpower I am there
-
Oh, I agree totally - I'm concerned about getting the information into the existing pages though.
Still, at least once this is done, I'll feel I've contributed something!
Then how about you get off your lazy ass and actually start editing? Or would that be to much effort if it can't be done with "mass inserts"?
And yeah, that's what the wiki is actually about, giving certain people a warm glowing feeling that they might actually have done something that does not exclusively benefits themselves... :P
-
An honest man speaks the truth, though it may give offence; a vain man, in order that it may.
-- William Hazlitt
-
Then how about you get off your lazy ass and actually start editing? Or would that be to much effort if it can't be done with "mass inserts"?
Zaerc,
I take great offence to this comment. I don't have experience of coding, or that much experience with Linux, but I do have extensive knowledge of networking and SQL. I contribute where I can and wanting to do things efficiently does not make me lazy. One of the powers of SQL is the ability to update information "En masse", this much more efficient than doing it record by record (which is what updating each page would require) as it is faster, ensures no pages are missed by accident, the point I was making when I said I'm concerned about getting the information into the existing pages though.
and ensures consistency.
Unlike some, I don't have a lot of time to throw at the community, I do what I can. Just because you haven't seen me start, is no excuse for your, frankly, insulting comment.
Whether you are telling the truth or not, I definately think your posting falls into the second category of Wombiroller's! and as such if that is all you have to say, you should keep your postings to yourself.
-
Ok all nice, we all have seen eachother's teeth and claws, but how do we go from here?
You say you have the expertise, so what now?
-
you guys should try to make this a mediawiki template, so that you can easily insert this with parameters on the relevant pages.
Look at the meta mediawiki for instructions.
-Thom
Yes, template is the way to go for sure. See the docs here:
http://meta.wikimedia.org/wiki/Help:Template
You can find some pretty ridiculous examples on wikipedia. Just edit a page and look for the template include:
{{ template_name | parameter }}
Then you can go look up the source of the template by editing the template page. Remember to add the Template namespace, like so:
http://en.wikipedia.org/w/index.php?title=Template:Infobox&action=edit
-
I've got a thick skin so I'll jump in.
Coming to this community as someone with programming skills but no multimedia / AV knowledge, my first impression was the wiki sucked. I had trouble finding basic answers like what exactly is LMCE? Where do I find a list of all currently supported alarm systems? What are the pro's and cons of various automation protocols? Etc. The information is somewhat there, just scattered and not well organized.
Now I have not contributed anything, wiki, code, or otherwise (I just bought a house, spare time is an oxymoron). I hit the forums a couple times a day while my code is compiling at work.
If I jump in the wiki and start trying to make stuff easier to find will I be welcomed for helping out or will I get my butt chewed for changing stuff when I'm a clueless newb?
No promises here, I've got all the usual excuses of a full time job plus kid plus I'm studying for my PE certification. But this community has a little "abrasiveness" some times that makes me hesitant to stick my neck out.
David
-
http://forum.linuxmce.org/index.php?topic=10049.0
-
I've got a thick skin so I'll jump in.
Coming to this community as someone with programming skills but no multimedia / AV knowledge, my first impression was the wiki sucked. I had trouble finding basic answers like what exactly is LinuxMCE? Where do I find a list of all currently supported alarm systems? What are the pro's and cons of various automation protocols? Etc. The information is somewhat there, just scattered and not well organized.
Now I have not contributed anything, wiki, code, or otherwise (I just bought a house, spare time is an oxymoron). I hit the forums a couple times a day while my code is compiling at work.
If I jump in the wiki and start trying to make stuff easier to find will I be welcomed for helping out or will I get my butt chewed for changing stuff when I'm a clueless newb?
No promises here, I've got all the usual excuses of a full time job plus kid plus I'm studying for my PE certification. But this community has a little "abrasiveness" some times that makes me hesitant to stick my neck out.
David
I would say jump in, but when you make some more significant change post the link also to forums and if you are doing something wrong you will soon hear about it ;)