Hello,
I am currently working in the german wiki. But since I'm translating some
articles I'm also concerned with some english articles. I have two
questions:
1. Concerning this article:
http://en.opensuse.org/Kernel_and_proprietary_drivers
This article is pure fiction. Thus it is less informative. In my opinion
this article should be deleted or it should be made more informative (less
fiction, more facts). What do you think ?
2. In the german wiki are some articles which don't exist in the english
wiki (e.g. http://de.opensuse.org/Hibiscus). May or should I create this
article in the english wiki now (for sure I will translate it and adapt it
to the new "quality assurance" / "transition guidelines") ?
Regards,
icediver
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Hello Mates,
atm we're reworking our Sites like you. But we have an short Question.
Under the KDE/* Hierarchy we have an Mix of KDE3 and KDE4. So one of our
reviewer asked for an idea. He has proposed to delete KDE3 Content (it
isn't supportet yet) and make an KDE4 only Content with an KDE3 Entry in
the History.
What do you mean?
--
Sincerely yours
Sascha Manns
openSUSE Community & Support Agent
openSUSE Marketing Team
Blog: http://saigkill.wordpress.com
Web: http://www.open-slx.de (openSUSE Box Support German)
Web: http://www.open-slx.com (openSUSE Box Support English)
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Jim,
2010/3/5 Jim Henderson <jhenderson(a)novell.com>:
> Makes sense, Rupert - the weeks are going so fast lately that I don't know what day it is any more. :-)
>
> I might propose that we plan on taking this on after BrainShare, unless one of the other admins has availability to help with this before then. I think that would give us some time to plan things out in advance as well, and that would be a good approach to take.
>
Doing the actual testing after Brainshare sounds good to me! That
provides the opportunity to further think about options we have (I see
Rajko contributed a rather comprehensive approach in the meantime, I
still need to go through) and you (as forums representative) are less
busy and able to allocate more time to these efforts. At first glance
it's important to me to bring all involved parties on the table for
gathering input and that's what we managed already. So far, the
implementation of the Wiki QA gained too less attention and this
needed to be fixed.
That said, I continously gather input on a sheet of paper, try to get
this shaped and I'll also sign responsive to schedule an IRC meeting
after Brainshare and think about the testing procedure.
Thanks,
R
> Jim
>
>>>> On 3/5/2010 at 06:24, in message
> <26d1a5471003050524x33d00dadj95be39b8abb5721c(a)mail.gmail.com>, Rupert
> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>> Jim,
>>
>> I doubt this "meeting" will happen this weekend already as we had too
>> less time to sync all interested parties. I'd like to have some more
>> time in advance to think about what needs to be done in particular
>> (step-by-step), i.e. a process we can go through and then come up with
>> an invitation to key people, i.e. (try to) schedule a date/time that
>> fits for everyone. Thanks for your general availability notice though.
>>
>> Best,
>> R
>>
>> 2010/3/4 Jim Henderson <jhenderson(a)novell.com>:
>>> Glad to help out, Rupert; I could possibly make myself available for a
>> couple hours on the weekend - I'm fairly busy getting ready for BrainShare
>> during the week. I've got some things to do around the house this weekend as
>> well but will probably want/need to take a break from that at some point.
>>>
>>> What we could do is start by just testing against a web forum only and not
>> connect it to an NNTP group. There are some wiki users, though (DenverD
>> comes to mind) who access using NNTP primarily so they might complain about
>> that. But we could start by sandboxing in a test group and see how that
>> goes, too. Some newsreaders thread by subject (or can be configured to do
>> so) so that may be a minor issue, especially as it would likely affect a
>> minority of users.
>>>
>>> Jim
>>>
>>>>>> On 3/4/2010 at 07:43, in message
>>> <26d1a5471003040643h1c14d9d8g37342520c8f9eb22(a)mail.gmail.com>, Rupert
>>> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>>>> Jim,
>>>>
>>>> 2010/3/3 Jim Henderson <jhenderson(a)novell.com>:
>>>>> Something to keep in mind on this is if there is a corresponding NNTP group
>>>> for this forum, the auto-merge should take place (ideally) before the new RSS
>>>> feed message is posted - otherwise you'll end up with message inconsistencies
>>>> (as they'll be threaded on the web side and not on the NNTP side).
>>>>>
>>>> Very important feedback and something I neglected so far, thanks. That
>>>> means (unfortuntely) that we'll be unable to hack the merging of
>>>> threads after posting and thus we obviously need to go along with it
>>>> (for now). Or do we have other ideas on the table?
>>>>
>>>> All,
>>>>
>>>> we now have (more or less) a precise overview of the capabilities of
>>>> the vbulletin side and thus I'd like to get started testing. We'd need
>>>> at least involvement from Tom, Rajko, one or more forums admins,
>>>> Remy/Jon. When can we get started with this? Any remaining blockers?
>>>> What about scheduling some realtime meeting on IRC while testing this?
>>>>
>>>> Please provide any feedback and general availability of involved
>>>> parties. I myself will go along with whatever date/time (be it during
>>>> the week or at a weekend)
>>>>
>>>> Thanks a lot in advance,
>>>> R
>>>>
>>>> PS: Remy, sorry, but monkey business seems to be needed here. Seems we
>>>> should recruit at least one other Forums mod for the wiki forum.
>>>>
>>>>> Jim
>>>>>
>>>>>>>> On 3/3/2010 at 00:33, in message
>>>>> <26d1a5471003022333s61a19d11pf60fb0728bf80cae(a)mail.gmail.com>, Rupert
>>>>> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>>>>>> Jim,
>>>>>>
>>>>>> 2010/2/26 Jim Henderson <jhenderson(a)novell.com>:
>>>>>>> Looking in the admin interface, it looks pretty straightforward to set up a
>>>>>> feed; it's not a custom bot, but part of the admin functionality in
>>>>>> vBulletin. We'd need to create a forum for the feed to feed into and the
>>>> URL
>>>>>> to the XML doc that provides the RSS feed.
>>>>>>>
>>>>>>> We could test this in the sandbox and then reset it for a public feed view.
>>>>>>>
>>>>>> Actually that's exactly what I'm planning to do as soon as we thought
>>>>>> the "hack-possibilities" to auto-merge the thread whole through.
>>>>>> Grabbing the feed and posting doesn't seem to be an issue, providing
>>>>>> RSS with Hermes is fine as well. Remaining and most important now is
>>>>>> to investigate the re-opening/merging of subsequent threads related to
>>>>>> one single article "foobar"
>>>>>>
>>>>>> All,
>>>>>>
>>>>>> vBulletin doc is at http://www.vbulletin.com/docs/html/
>>>>>>
>>>>>> Best,
>>>>>> R
>>>>>>
>>>>>>> Jim
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jim Henderson
>>>>>>> Program Manager, Novell Testing
>>>>>>> Novell, Inc.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>> On 2/26/2010 at 05:48, in message
>>>>>>> <26d1a5471002260448o5b6afa85r76f3e24021a7436b(a)mail.gmail.com>, Rupert
>>>>>>> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>>>>>>>> All,
>>>>>>>>
>>>>>>>> 2010/2/25 Thomas Schmidt <tom(a)opensuse.org>:
>>>>>>>>>
>>>>>>>>> According to http://www.vbulletin.com/ this is a
>>>>>>>>> commercial product, I cannot even download the documentation...
>>>>>>>>> So we need the technical forums admin to do that.
>>>>>>>>>
>>>>>>>> I just got notice from Kim that he's rather unavailable these days due
>>>>>>>> to too much on the plate atm. That said, I'll ask him about the
>>>>>>>> forumsbot configuration capabilities in a private conversation and
>>>>>>>> forward the answers to you. Also I try to get the vBulletin
>>>>>>>> documentation we need from him. Furthermore I herewith CC: the rest of
>>>>>>>> the admin team in order to ask for their involvement. Please keep the
>>>>>>>> CC: as is. I'm sorry for the inconvenience.
>>>>>>>>
>>>>>>>> Forums admins,
>>>>>>>>
>>>>>>>> we need some help/input regarding the FlaggedRevs Wiki QA, i.e. the
>>>>>>>> configuration capabilities of the RSS forumsbot. Kim is rather busy
>>>>>>>> these days, so I'm wondering if you, Carl, John, Jim would be able to
>>>>>>>> jump in as an interim replacement?
>>>>>>>>
>>>>>>>> In order to sync up with the current discussion, please read this thread [1]
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> R
>>>>>>>>
>>>>>>>> [1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00069.html
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
--
Rupert Horstkötter, open-slx gmbh
openSUSE Board Member
openSUSE Community Assistant
http://en.opensuse.org/User:Rhorstkoetter
Email: rhorstkoetter(a)opensuse.org
Jabber: ruperthorstkoetter(a)googlemail.com
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Hi,
I transferred the openFATE pages to the new wiki, and
briefly discussed with henne where to put them.
They are now at http://wiki.opensuse.org/openSUSE:Tools/Openfate/...
which means we use the colon only after the configured namespaces,
openSUSE in this case. Is this the correct way we want to do this?
Greetings
--
Thomas Schmidt (tom [at] opensuse.org)
openSUSE Boosters Team
"Don't Panic", Douglas Adams (1952 - 11.05.2001)
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
On Friday 05 March 2010 12:07:42 Jim Henderson wrote:
> Makes sense, Rupert - the weeks are going so fast lately that I don't know
> what day it is any more. :-)
>
> I might propose that we plan on taking this on after BrainShare, unless one
> of the other admins has availability to help with this before then. I
> think that would give us some time to plan things out in advance as well,
> and that would be a good approach to take.
>
> Jim
The time is all that we need :)
Taking that forum software has some documentation at
http://www.vbulletin.com/docs/
* Appendix 3: Technical Documents
* Appendix 4: Developer Tools
** Data Managers
I guess that Thomas can use above if necessary.
I would also propose to think about exact workflow as no script can be written
if we don't have very detailed picture how process will work.
Current idea will bring changes to forums as a post.
How that post looks? In Akregator it is like:
Statistics
Date:Yesterday 21:49
Author:Coolo
← Older revision Revision as of 03:49, 6 March 2010
Line 106: Line 106:
|2944925 |2944925
|2573036 |2573036
-|2607367+ +|2607367
|- |-
and so on for a whole page, and at the end of changes I can see link "Complete
Story" to
http://en.opensuse.org/index.php?title=Statistics&diff=125390&oldid=prev
That link is included in the feed file, so the forum post will have link to
change, and new post for each change.
Taking how much manual work is to aggregate forums posts per wiki page (edit
first post to add new changes and remove posts that duplicate links in first
post) that will at the end produce the same result that one can see directly
on the wiki as:
http://en.opensuse.org/index.php?title=Statistics&action=history
We should see how to save forum operator time for normal forum administrative
tasks instead of using it to create list that already exists.
Here is one possible solution.
-------------------------------------------------------------------
(1) On wiki page creation, create thread with initial post that will contain:
* link to wiki page
* link to history of that page and
* short information how to use it.
After thread creation create wiki discussion page (talk page) with:
* link to thread in forums and
* link to discussion subpage where editing proposals can be published.
Semi protect discussion page.
Problem is that some users will attempt to edit discussion page to add comment
there, so we need warning that will explain why discussion pages in Main name
space are protected and where to post the comment, or editing proposal.
Appropriate template is probably the best option.
Add link to wiki page and link to the forum thread to announcement article
that will contain:
* links to the 10 most recent created pages in Main namespace and links to
corresponding forum threads
* link to Special:NewPages for detailed list of all new pages, plus few words
what the Special:NewPages list is and how it can be used.
(2) On wiki page change, update another announcement list that will contain:
* links to the 10 most recent pages that are changed (listed in
Special:RecentChanges for Main namespace) and
* link to Special:RecentChanges for detailed list of all page changes with few
words what is that page about and how it can be used
We can add more lists, but I would prefer one general announcement post that
will give overview of tools that one can find and use directly on the wiki.
This solves few problems.
1) Where to find forum thread when wiki visitor, or article author, is looking
at the wiki page and want to give or see feedback. The link is in a place that
anyone that wants to comment on wiki article will look for, the Discussion
page of the article which is linked on the top of each wiki page as Discussion
:)
2) Number of forum threads will be large, but it will be easy to find
information that one want to see, or place to post the comment.
3) People reading forum have digest of changes in announcement articles and in
the same place link to more details that are published on the wiki, so there
is no need for large and unreadable forum article.
4) Those that hit forum thread about some article directly can see in the
first post all they need to read article, its history and give comment on
article or its changes.
-------------------------------------------------------------------
I would like that you check procedure and comment is this viable solution.
The only problem that I can see could be that announcement article can't be
edited after creation. That will limit announcement to few links to wiki
special pages and instructions how to use them.
--
Regards Rajko,
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Jim,
2010/3/3 Jim Henderson <jhenderson(a)novell.com>:
> Something to keep in mind on this is if there is a corresponding NNTP group for this forum, the auto-merge should take place (ideally) before the new RSS feed message is posted - otherwise you'll end up with message inconsistencies (as they'll be threaded on the web side and not on the NNTP side).
>
Very important feedback and something I neglected so far, thanks. That
means (unfortuntely) that we'll be unable to hack the merging of
threads after posting and thus we obviously need to go along with it
(for now). Or do we have other ideas on the table?
All,
we now have (more or less) a precise overview of the capabilities of
the vbulletin side and thus I'd like to get started testing. We'd need
at least involvement from Tom, Rajko, one or more forums admins,
Remy/Jon. When can we get started with this? Any remaining blockers?
What about scheduling some realtime meeting on IRC while testing this?
Please provide any feedback and general availability of involved
parties. I myself will go along with whatever date/time (be it during
the week or at a weekend)
Thanks a lot in advance,
R
PS: Remy, sorry, but monkey business seems to be needed here. Seems we
should recruit at least one other Forums mod for the wiki forum.
> Jim
>
>>>> On 3/3/2010 at 00:33, in message
> <26d1a5471003022333s61a19d11pf60fb0728bf80cae(a)mail.gmail.com>, Rupert
> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>> Jim,
>>
>> 2010/2/26 Jim Henderson <jhenderson(a)novell.com>:
>>> Looking in the admin interface, it looks pretty straightforward to set up a
>> feed; it's not a custom bot, but part of the admin functionality in
>> vBulletin. We'd need to create a forum for the feed to feed into and the URL
>> to the XML doc that provides the RSS feed.
>>>
>>> We could test this in the sandbox and then reset it for a public feed view.
>>>
>> Actually that's exactly what I'm planning to do as soon as we thought
>> the "hack-possibilities" to auto-merge the thread whole through.
>> Grabbing the feed and posting doesn't seem to be an issue, providing
>> RSS with Hermes is fine as well. Remaining and most important now is
>> to investigate the re-opening/merging of subsequent threads related to
>> one single article "foobar"
>>
>> All,
>>
>> vBulletin doc is at http://www.vbulletin.com/docs/html/
>>
>> Best,
>> R
>>
>>> Jim
>>>
>>>
>>> --
>>> Jim Henderson
>>> Program Manager, Novell Testing
>>> Novell, Inc.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>>>> On 2/26/2010 at 05:48, in message
>>> <26d1a5471002260448o5b6afa85r76f3e24021a7436b(a)mail.gmail.com>, Rupert
>>> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>>>> All,
>>>>
>>>> 2010/2/25 Thomas Schmidt <tom(a)opensuse.org>:
>>>>>
>>>>> According to http://www.vbulletin.com/ this is a
>>>>> commercial product, I cannot even download the documentation...
>>>>> So we need the technical forums admin to do that.
>>>>>
>>>> I just got notice from Kim that he's rather unavailable these days due
>>>> to too much on the plate atm. That said, I'll ask him about the
>>>> forumsbot configuration capabilities in a private conversation and
>>>> forward the answers to you. Also I try to get the vBulletin
>>>> documentation we need from him. Furthermore I herewith CC: the rest of
>>>> the admin team in order to ask for their involvement. Please keep the
>>>> CC: as is. I'm sorry for the inconvenience.
>>>>
>>>> Forums admins,
>>>>
>>>> we need some help/input regarding the FlaggedRevs Wiki QA, i.e. the
>>>> configuration capabilities of the RSS forumsbot. Kim is rather busy
>>>> these days, so I'm wondering if you, Carl, John, Jim would be able to
>>>> jump in as an interim replacement?
>>>>
>>>> In order to sync up with the current discussion, please read this thread [1]
>>>>
>>>> Thanks,
>>>> R
>>>>
>>>> [1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00069.html
>>>
>>>
>>
>
>
--
Rupert Horstkötter, open-slx gmbh
openSUSE Board Member
openSUSE Community Assistant
http://en.opensuse.org/User:Rhorstkoetter
Email: rhorstkoetter(a)opensuse.org
Jabber: ruperthorstkoetter(a)googlemail.com
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Jim,
I doubt this "meeting" will happen this weekend already as we had too
less time to sync all interested parties. I'd like to have some more
time in advance to think about what needs to be done in particular
(step-by-step), i.e. a process we can go through and then come up with
an invitation to key people, i.e. (try to) schedule a date/time that
fits for everyone. Thanks for your general availability notice though.
Best,
R
2010/3/4 Jim Henderson <jhenderson(a)novell.com>:
> Glad to help out, Rupert; I could possibly make myself available for a couple hours on the weekend - I'm fairly busy getting ready for BrainShare during the week. I've got some things to do around the house this weekend as well but will probably want/need to take a break from that at some point.
>
> What we could do is start by just testing against a web forum only and not connect it to an NNTP group. There are some wiki users, though (DenverD comes to mind) who access using NNTP primarily so they might complain about that. But we could start by sandboxing in a test group and see how that goes, too. Some newsreaders thread by subject (or can be configured to do so) so that may be a minor issue, especially as it would likely affect a minority of users.
>
> Jim
>
>>>> On 3/4/2010 at 07:43, in message
> <26d1a5471003040643h1c14d9d8g37342520c8f9eb22(a)mail.gmail.com>, Rupert
> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>> Jim,
>>
>> 2010/3/3 Jim Henderson <jhenderson(a)novell.com>:
>>> Something to keep in mind on this is if there is a corresponding NNTP group
>> for this forum, the auto-merge should take place (ideally) before the new RSS
>> feed message is posted - otherwise you'll end up with message inconsistencies
>> (as they'll be threaded on the web side and not on the NNTP side).
>>>
>> Very important feedback and something I neglected so far, thanks. That
>> means (unfortuntely) that we'll be unable to hack the merging of
>> threads after posting and thus we obviously need to go along with it
>> (for now). Or do we have other ideas on the table?
>>
>> All,
>>
>> we now have (more or less) a precise overview of the capabilities of
>> the vbulletin side and thus I'd like to get started testing. We'd need
>> at least involvement from Tom, Rajko, one or more forums admins,
>> Remy/Jon. When can we get started with this? Any remaining blockers?
>> What about scheduling some realtime meeting on IRC while testing this?
>>
>> Please provide any feedback and general availability of involved
>> parties. I myself will go along with whatever date/time (be it during
>> the week or at a weekend)
>>
>> Thanks a lot in advance,
>> R
>>
>> PS: Remy, sorry, but monkey business seems to be needed here. Seems we
>> should recruit at least one other Forums mod for the wiki forum.
>>
>>> Jim
>>>
>>>>>> On 3/3/2010 at 00:33, in message
>>> <26d1a5471003022333s61a19d11pf60fb0728bf80cae(a)mail.gmail.com>, Rupert
>>> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>>>> Jim,
>>>>
>>>> 2010/2/26 Jim Henderson <jhenderson(a)novell.com>:
>>>>> Looking in the admin interface, it looks pretty straightforward to set up a
>>>> feed; it's not a custom bot, but part of the admin functionality in
>>>> vBulletin. We'd need to create a forum for the feed to feed into and the
>> URL
>>>> to the XML doc that provides the RSS feed.
>>>>>
>>>>> We could test this in the sandbox and then reset it for a public feed view.
>>>>>
>>>> Actually that's exactly what I'm planning to do as soon as we thought
>>>> the "hack-possibilities" to auto-merge the thread whole through.
>>>> Grabbing the feed and posting doesn't seem to be an issue, providing
>>>> RSS with Hermes is fine as well. Remaining and most important now is
>>>> to investigate the re-opening/merging of subsequent threads related to
>>>> one single article "foobar"
>>>>
>>>> All,
>>>>
>>>> vBulletin doc is at http://www.vbulletin.com/docs/html/
>>>>
>>>> Best,
>>>> R
>>>>
>>>>> Jim
>>>>>
>>>>>
>>>>> --
>>>>> Jim Henderson
>>>>> Program Manager, Novell Testing
>>>>> Novell, Inc.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>> On 2/26/2010 at 05:48, in message
>>>>> <26d1a5471002260448o5b6afa85r76f3e24021a7436b(a)mail.gmail.com>, Rupert
>>>>> Horstkötter<rhorstkoetter(a)opensuse.org> wrote:
>>>>>> All,
>>>>>>
>>>>>> 2010/2/25 Thomas Schmidt <tom(a)opensuse.org>:
>>>>>>>
>>>>>>> According to http://www.vbulletin.com/ this is a
>>>>>>> commercial product, I cannot even download the documentation...
>>>>>>> So we need the technical forums admin to do that.
>>>>>>>
>>>>>> I just got notice from Kim that he's rather unavailable these days due
>>>>>> to too much on the plate atm. That said, I'll ask him about the
>>>>>> forumsbot configuration capabilities in a private conversation and
>>>>>> forward the answers to you. Also I try to get the vBulletin
>>>>>> documentation we need from him. Furthermore I herewith CC: the rest of
>>>>>> the admin team in order to ask for their involvement. Please keep the
>>>>>> CC: as is. I'm sorry for the inconvenience.
>>>>>>
>>>>>> Forums admins,
>>>>>>
>>>>>> we need some help/input regarding the FlaggedRevs Wiki QA, i.e. the
>>>>>> configuration capabilities of the RSS forumsbot. Kim is rather busy
>>>>>> these days, so I'm wondering if you, Carl, John, Jim would be able to
>>>>>> jump in as an interim replacement?
>>>>>>
>>>>>> In order to sync up with the current discussion, please read this thread [1]
>>>>>>
>>>>>> Thanks,
>>>>>> R
>>>>>>
>>>>>> [1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00069.html
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
--
Rupert Horstkötter, open-slx gmbh
openSUSE Board Member
openSUSE Community Assistant
http://en.opensuse.org/User:Rhorstkoetter
Email: rhorstkoetter(a)opensuse.org
Jabber: ruperthorstkoetter(a)googlemail.com
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Hi, yesterday I extended the inputbox plugin
on wiki.o.o to have the ability to generate
bugzilla search forms. So we can include a little search
box on some pages where it is appropriate.
Examples: http://wiki.opensuse.org/User:Digitaltomm/Bugzillasearch
Greetings
--
Thomas Schmidt (tom [at] opensuse.org)
openSUSE Boosters Team
"Don't Panic", Douglas Adams (1952 - 11.05.2001)
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Looking how to document http://wiki.opensuse.org/Template:Article
I looked on its functionality again and it seems that we have to rethink
current layout and the way we want to present information to visitors.
Currently actual content (6.) that wiki visitor is looking for is moved way
below the first loaded screen. The order of page content is"
1. Discover it - solved in Bento theme
2. Navigation bar
3. Introduction to article
4. Knowledge section
4.1. Tested on
4.2. Recommended
4.3. Related
4.4. Used programs
5. TOC (table of contents) - it is too wide on the majority of pages
6. Actual article
I have to scroll down even on 1920x1080 screen, and scrolling down in order to
see text can become very fast annoying if it is present on every page.
Not to mention my experience with one web page that should have lists of Linux
compatible hardware. It has every page top section common to all articles,
occupying whole browser page and a bit more.
First I thought that top of the page is whole page and presents index to
actual article (table), and after some clicking around, jumping from page to
page, looking for actual hardware list, came on idea to check what is below,
and surprise, there was a table. Some tables were only few rows, making whole
page design funny looking.
You can imagine what is my opinion about importance to present actual article
text on the very first page load. All tools, indexes, cross links, tables of
content should flow next to the article text, but never push it way below
article title.
First and the simplest idea is to compact navigation bar, intro and knowledge
bar. The Related column of knowledge bar in this context is redundant as
related articles should be listed in navigational bar. Navigational bar should
be squeezed as much as possible. TOC should be separate column with fixed
size, but not over whole screen, leaving enough room for intro and actual
article beginning.
Next idea would be to use a method similar to wiki.o.o portals, or template
and its documentation, where the main page consists of one or more transcluded
pages. This gives possibility to create few views of the same article with
very little additional effort. In other words to create modules and then use
them in the few articles, or as stand alone units.
How to split article:
1) very short intro in article purpose (problem and offered solution) that can
be published (transcluded) in a different content indexes and portals
2) longer intro (Knowledge) that will list mandatory skills and tools to
accomplish task (prerequisites)
3) actual procedure or discussion
4) conclusion; what we accomplished and where to proceed
5) article reference index;list of related topics internal and external
This proposal has to be tested with articles about few topics in real setup on
a new wiki.
I'm looking for the people that like idea and want to help me with comments,
ideas, creation of proposals.
--
Regards Rajko,
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
