Discussions about KDE are source of endless fun.
Answering a question about openSUSE support for KDE3 to guy claiming that it will end soon, if it is not already stopped, I caught myself thinking that support will last for a quite long period.
KDE4 will be probably at version 4.4 when support for openSUSE 11.1 stops, and right now at version 4.2 it is already in a good shape for Joe the Plumber.
The whole pile of rants on opensuse@opensuse.org mail list is actually written by people that would like to run bleeding edge system that is stable. Wash me, but don't make me wet.
They complain because openSUSE 11.2 will not have KDE3, and claim time and again that is catastrophe, like support will end when 11.2 is released. Well, the KDE3 support in openSUSE will last till December 2010, just the same as for openSUSE 11.1. It is standard openSUSE practice to support each release for 2 years.
You know, we are serious distro.
Monday, April 20, 2009
Tuesday, April 7, 2009
openSUSE wiki as knowledge base: Initial
One of problems with wiki, as knowledge base, is that someone has to hang on it and categorize submissions, old and new, but it is not one man, nor a layman show.
The Mediawiki articles and file submissions are just linear list of titles.
It is up to the people that use wiki to sort their knowledge there.
The tools that Mediawiki provides are search, few listings found in special pages, name spaces, categories, and of course ability to create articles that will link other articles and serve as indexes.
I tried few times to sort the knowledge on openSUSE wiki and failed, it is just much more work and skills than any single wiki editor can provide. Attempt to create framework for future expansions without defining properties of objects stored in a wiki database was waste of time.
So this time I'll start drafting a plan from prerequisites to define object properties.
I can see few basic objects:
Let me take images as example. They can be sorted by:
Each of ways to sort image is one of its properties and would require category, so that reader can browse trough categories to the particular image, or better to say description article. When you add other objects and their properties then list is huge.
The other problem is that list of image properties is not complete, there is many more that only professionals in the field know, and just the same is valid for any other wiki object. Without participation of people that are professionals in the field there will be no successful organization of openSUSE wiki as knowledge base.
What is wiki
The Mediawiki articles and file submissions are just linear list of titles.
It is up to the people that use wiki to sort their knowledge there.
The tools that Mediawiki provides are search, few listings found in special pages, name spaces, categories, and of course ability to create articles that will link other articles and serve as indexes.
Sorting openSUSE wiki
I tried few times to sort the knowledge on openSUSE wiki and failed, it is just much more work and skills than any single wiki editor can provide. Attempt to create framework for future expansions without defining properties of objects stored in a wiki database was waste of time.
So this time I'll start drafting a plan from prerequisites to define object properties.
I can see few basic objects:
- articles (html documents)
- uploaded files (images, pdf and some open document formats)
- generated reports (special pages)
Let me take images as example. They can be sorted by:
- function: Wallpaper, Icon, Splash, Emoticon, ...
- application: Evolution Art, Thunderbird Art, Firefox Art, ...
- desktop: KDE Art, GNOME Art, Xfce Art, ...
- source by creator: openSUSE Art, User Art, Upstream Art, ...
- creation tehnique: photography, scan of hand drawing, image creation program
- quality: excellent, good, bad
- completeness: mockup, draft, sketch, release candidate, final
- color format: RGB, CMY, indexed, gray
- color depth:32, 24, 16, 8, 2
- color name: red, blue, green, ...
- size: large, medium, small, ...
Each of ways to sort image is one of its properties and would require category, so that reader can browse trough categories to the particular image, or better to say description article. When you add other objects and their properties then list is huge.
The other problem is that list of image properties is not complete, there is many more that only professionals in the field know, and just the same is valid for any other wiki object. Without participation of people that are professionals in the field there will be no successful organization of openSUSE wiki as knowledge base.
Monday, April 6, 2009
People of openSUSE
First interview is published.
It was with a bit of squeaking, but for the apprentice editor it was good. I can't be strict to myself, it wouldn't be fair, who's going to defend me. There is still missing 'a' in some places, missed 'an' that should be 'a', but in general it was good.
There are more in preparation, so following weeks wont be boring.
The thin point is preparation that needs more work on organization, but from the first one I learned few things that are useful to have before start, like HTML editor that has ability to show page layout, but it is not smarter then human in front of the screen, ie. doesn't change HTML code to bring it in "compliance". I have to check again Quanta+ and Bluefish, or something else if some kind soul has advice for an apprentice.
It was with a bit of squeaking, but for the apprentice editor it was good. I can't be strict to myself, it wouldn't be fair, who's going to defend me. There is still missing 'a' in some places, missed 'an' that should be 'a', but in general it was good.
There are more in preparation, so following weeks wont be boring.
The thin point is preparation that needs more work on organization, but from the first one I learned few things that are useful to have before start, like HTML editor that has ability to show page layout, but it is not smarter then human in front of the screen, ie. doesn't change HTML code to bring it in "compliance". I have to check again Quanta+ and Bluefish, or something else if some kind soul has advice for an apprentice.
Subscribe to:
Posts (Atom)