Rajko M. wrote:
On Monday 25 January 2010 09:14:01 Rupert Horstk�tter wrote:
+1, but .. doesn't that will become a showstopper at some point in time? I mean, at some point in time we WILL release this to the public and everything needs to work for both logged-in and logged-out users.
That problem will be solved. My favorites supect is iChain, as there is another problem with current login process that curbs use of standard wiki tools to fight spammers, but that is another story.
Rush is not good.
Just check the: http://en.opensuse.org/Transition_guidelines
- Should we use categorytree instead of navbar templates ?
My answer is that as long as we don't know properties of that tool, we can't answer the question. My experiment with Category tree was just basic setup to see is it working at all.
- Categorization - whole paragraph shows confusion:
- we have no control over categories, anyone can add some
- we can define only basic category tree layout
For both we can't predict what will be needed, or push articles in certain category, just to have it categorized. Categories are like keywords, there will be as many as it is needed.
All we can do is to remove duplicates that use synonyms, and change too specialized, or obscure category names to more common, easier to find.
Templates (Just as normal articles, or categories) There will be as many as it is needed. All we can do is to prevent layout charade of templates that do the same with different layout, which is already done, bring existing templates in line with general usability rules for web pages that are free available on http://useit.com and keep new creations in line with that.
Structure Not close to be known. Discussion about namespaces is not done. I promised the list, but the work doesn't go very fast. There is a lot to see around, find some software that can help sorting out current fond of articles.
My opinion on namespaces is that is better to have few more and allow users to use targeted search as it is presented in http://en.opensuse.org/SDB:SDB then to have to little and start cramming stuff in available namespaces as it is now.
Search (InputBox) is not the only extension that can be limited to certain namespace, so we gain better flexibility applying extensions that one project needs and the other not.
Bedside existing, I would add: KDE GNOME YaST Artwork News ....
The problem to find articles with default search in Main namespace can be solved:
- with portal pages, that will contain list of articles that user can browse and search for particular namespace.
- instructions to user how to enable search in user preferences
- site map
sorry for so much negativity from apparently a single source, but i have some experience in such things and it seems to me that what has happened here is a transition schedule was crafted without really knowing either the full task at hand, all the decisions needing to be made, or the number/capability of hands to do the work.. consequently i see in the above posting (and some others delivered with my [european schedule] morning coffee a whole host of still unanswered questions, uncoordinated and approved courses of actions and those pesky little details that can derail the train from engine to caboose.. yet, "we" (and i use that term very loosly) continue to discuss the details of which way we wanna go while the train is passing (maybe never to pass by again) track switches and grade crossings with names like "this bug is a showstopper" and "run scripts to run nukePage.php" or the hands off "This article has been reviewed!" i'm probably wrong (and this may tread on the toes of good folks who should be encouraged to "press on" rather than what is about to come) but, it seems to me that this transition requires the concentrated effort of a number of disciplines like [but not limited to these three]: 1) technical wizards/hackers to *force* the wiki program itself to 'serve' us, rather than the other way around; 2) process/project planners, coordinators, managers, leaders, yes even mentors to formulate and execute the complicated plan needed to *force* the _whole_ train to the destination; 3) writers, editors, word warriors, quality assurance checkers and etcetera to *force* the prose on board at destination to convey the 'correct technical info' with as little chance of being misunderstood by (various levels of english & technical proficiency) _*USERS*_ as possible.. from what i've seen (and i'm fully aware i may be completely wrong--having actually seen very little of the process, and having seen NONE of the goings on prior to about mid-December) it *seems* to me that the Discipline One folks drove the train at near full speed in the general direction of the destination until the other disciplines were needed to actually do the work, and then held an IRC "mentoring session" to kick off the coasting in, smooth ride to Nirvana....with the arrival expected to be (when?) about now.. yet, "we" arrive at 'now' without having the *executable* plan of where we wanna be fully mature.. [and now, morning coffee finished, i waddle off to forums.opensuse to try to help yet another first time poster/troll with his/her "how do i change the background?? i logged into KDE as root and STILL it won't let me...SuSe SuX!....Waaaaaaa...i'm going back to Vista!!] peace (remember i wrote it all not to step on toes, but instead trying to be a little helpful), DenverD -- To unsubscribe, e-mail: email@example.com For additional commands, e-mail: firstname.lastname@example.org