February 2010 - openSUSE Wiki - openSUSE Mailing Lists

[opensuse-wiki] Report: templates documentation and other bits
by Petr Uzel 03 Mar '10

03 Mar '10

Hi, I've spent some time working on documenting the templates in wiki.o.o as suggested in [1], so here is small report and some random thoughts: 1. Every template (except a few - more on this below) in wiki.o.o instance now has its /doc subpage with information about how to use the template (code), general description, where to use it/not to use it and in some cases there is also list of related templates. The documentation could definitely not perfect, but IMHO it is a good start to having general policy that every template should be documented. 2. It seems nobody has objections against making it policy that every $template has to be documented in $template/doc, so I'll mention it in [2] (this is yet to be done if nobody raises objections). 3. The exceptions for which I did not make /doc subpage, as mentioned in point 1, are: Template:App \ Template:Appg | Template:Appk +-> I don't understand what are these good for Template:Appj / Template:Meeting - marked as 'template to rethink', looks useless to me Template:Infobox software, Template:Information: these two templates look very similar, I don't get the difference. Are both really needed? 4. TOCRight template: do we really need this? In en.o.o, only a few pages use this template and IMHO it doesn't look very nice. 5. The templates related to portals were taken from wikipedia, where these templates are also perfectly documented. IMO it would be useless to copy their documentation to wiki.o.o, so I've basically just linked the documentation to our wiki. 6. There are several navigation bar templates in the wiki. I think these templates might be placed into something like [[Category:NavBars]], so it would be easier to find proper Navbar when creating new article. Wikipedia uses something similar. What do you think? 7. I've fixed capitalization of categories, so all the categories now follow the naming conventions. 8. ATM, the documentation of a template is displayed below the template content, which is fine for small templates like AI [3], but isn't so fine for bigger templates like Article boilerplate [4]. If the user opens [4], the documentation should be better visible. I see two options, none of them ideal: a) put the documentation above the template content b) make the template content <includeonly>, so only the documentation would be visible, but then it couldn't be used as an example of recommended article layout. Any ideas? 9. Template:{Torrent, Video} These two templates were implemented using titled-click-external template, which a) isn't in wiki.o.o b) is deprecated according to Wikipedia So I've reworked Video and Torrent templates using [[image:Video.png|22px|link={{{1}}}]] syntax. It should work the same way as before except that it now adds another icon representing external link [5]. I don't know how to get rid of this icon (does it mind actually??), so if ((this is not desired && can not be fixed) || (there are some other drawbacks I didn't notice)), then please revert these two templates back. [1] http://lists.opensuse.org/opensuse-wiki/2010-02/msg00055.html [2] http://wiki.opensuse.org/Help:Template [3] http://wiki.opensuse.org/Template:AI [4] http://wiki.opensuse.org/Template:Article [5] http://wiki.opensuse.org/User:Puzel/Test Petr -- Petr Uzel, openSUSE Boosters Team IRC: ptr_uzl @ freenode

5 14

[opensuse-wiki] bento theme on wikistage
by Thomas Schmidt 02 Mar '10

02 Mar '10

Hi, I added the current state of the bento theme[1] to our wiki staging server [2]. It can be set in Preferences->Skins. There are some issues to solve, I think we need a much wider content area. Greetings [1] http://gitorious.org/opensuse/webdesign/trees/master/design_concept/theme_o… [2] http://wikistage.opensuse.org/Test?useskin=bento -- Thomas Schmidt (tschmidt [at] suse.de) SUSE Linux Products GmbH :: Research & Development :: Tools "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

9 10

[opensuse-wiki] Login problem
by Shayon Mukherjee 26 Feb '10

26 Feb '10

Hello, For the past around 1-2 weeks i have been trying hard to login to the wiki but no result.I get again redirected to the same old login page.I have tried browser caching but same. Any other suggestions ? :) S. -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

3 6

Re: [opensuse-wiki] Testing FlaggedRevs Wiki QA
by Rupert Horstkötter 26 Feb '10

26 Feb '10

All, thanks for moving forward here. JFYI, I pinged Kim again at the forums in order to get input about forums' bot capabilities. To my very own knowledge, it's the autoposting bot that ships with vBulletin by default. You're right that the re-opening of existing threads may be an issue here. I hope it's capable in doing so in order to have a structured thread-list (I see this as an urgent requirement .. maybe you talented people can hack this together if not supported by default?) I'm OK with Rajko's idea to create a subforum for the QA also in production to separate the QA from other threads, makes sense .. or move non-QA discussions to a subforum. As of namespaces: Please follow Rajko here as I lack the appropriate knowledge to be honest. I mean, what we want the QA for is "distro", i.e. end-user documentation and iirc we decided to have just that in Main Namespace, separated from Help, Meetings, Project Docs etc (we certainly don't need QA for those). Only docs interesting for our customer (distro doc, app tutorials etc.) should be covered by QA. Isn't that Main namespace, Rajko? Best, R 2010/2/25 Rajko M. <rmatov101(a)charter.net>: > Sorry, I posted only to the list again. > Repost to all, without ML. > > On Wednesday 24 February 2010 14:36:07 Thomas Schmidt wrote: >> On 02/24/2010 05:16 AM, Rajko M. wrote: > ... >> > I mentioned in another post that FlaggedRevs have own output of pages >> > that need review, and that gives only Main space RSS/Atom by default. >> > Pages that never received any attention will be covered with output of >> > another special page "new pages", that also has Main as default output to >> > RSS/Atom. >> > >> > Those 2 outputs will cover all of the pages that need review. >> > I guess that Tom can combine them in a single stream from Hermes. >> >> That might be possible, but I think it's easier to read those 2 feeds >> with the rss->forum bot. Aren't the new pages of the Main namespace >> included in the 'pages need review' feed? > > No. > That was the reason to look for another Special page that has missing pages in > the first report. > > The other idea is to keep both reports separated, as old articles that have > change are not as urgent as new articles that can be literally anything. > Little mark at the top right that article is not reviewed is some help, but > article is anyway presented to the wiki visitor. > > Below is link to both special pages for Kim. I used reply to mail list for the > first post with this links, so it can be found in archives, but this way is > easier: > First is http://wiki.opensuse.org/Special:OldReviewedPages > Second is http://wiki.opensuse.org/Special:NewPages >> > >> >> Which software is this autoposting bot, do you have a url? > > Kim? > -- 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

3 3

[opensuse-wiki] Honoring openSUSE Wiki Reviewing Contributions
by Rupert Horstkötter 26 Feb '10

26 Feb '10

All, JFYI, this announcement [1] just has been pushed to openSUSE News. Please support this initiative by rating, digging, tweeting and supporting the community with comments (if questions arise), i.e. make noise about it as much as you can! Sascha, please cover the news prominently within "in this week" for the next OWN #112 Thanks in advance, R [1] http://news.opensuse.org/2010/02/22/honoring-opensuse-wiki-reviewing-contri… -- 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

3 4

[opensuse-wiki] suse 11.2
by chad 26 Feb '10

26 Feb '10

Hi I downloaded the kde version and I'm visually impaired. How do you run orca I tried alt-f2 then typed orca and nothing. Also I tried the gnome live cd and not sure how do set it up. This is my first time. thanks -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 1

Re: [opensuse-wiki] Re: Honoring openSUSE Wiki Reviewing Contributions
by Rupert Horstkötter 25 Feb '10

25 Feb '10

Shayon, Petr, > Tweet : http://twitter.com/opensuse/status/9473218053 > > I did it , from my side too :) . > > Yes: > http://twitter.com/ptr_uzl/status/9474028212 > http://twitter.com/ptr_uzl/status/9626366448 > awesome, thanks! R -- 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

1 0

[opensuse-wiki] Content elements usability: templates (in particular shell)
by Rajko M. 25 Feb '10

25 Feb '10

It is white text on black background and it breaks text flow, like many other templates that are intended to be inserted in text. I would like to propose use of templates inserted in text very sparingly. Pages broken with templates that contain images, bold and large text, colored background, plethora of lines, where user has to hunt next appearance of meaningful text are all but nice to read, and we have a lot pages in demand that suffer from this. Our problem with the current wiki is not only "hard to find" articles, but articles that with all information in article is hard to read. See this http://en.opensuse.org/KDE/Repositories and this http://en.opensuse.org/Talk:KDE/Repositories (note that this is older version of main article) or this http://en.opensuse.org/GNOME/Repositories Which is easier to read and find information that user needs? One with 20 templates breaking text flow, or one without. And KDE/Repositories is not alone. -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

3 4

[opensuse-wiki] Testing FlaggedRevs Wiki QA
by Rupert Horstkötter 24 Feb '10

24 Feb '10

Team, while this isn't particularly urgent currently, I'd like to bring this to the teams attention (especially Rajko, Remy, Jon, Henne). At some point in time we need to get going with starting the FlaggedRevs QA Wiki forum testing. I already had a phone call with Henne last week and we had the idea to create a testing namespace at wiki.o.o, fill it with some test content, create a test-subforum of the openSUSE wiki forum and let FlaggedRevs output some test-RSS feed in order to grab it with the Forums RSS posting bot. As this whole thing is an integral part of the overall usability concept, I'd like to ask about commitment of people to help here. At least the mentioned team members (Rajko as FlaggedRevs champion, Henne as wiki.o.o-master and Remy/Jon as Wiki forum Mods) would be required. May we sync for getting started with this please? Additional things we need take care about in advance? ETA? I'll go along with whatever availability you may have to get started and I'll certainly take care of forums admin involvement to configure the posting bot (Kim is in CC:). Testcase: 1. Create a draft rev 2. Hope for good FlaggedRevs RSS/Posting Bot interoperability 3. Flag the draft as sighted 4. create new draft rev besides the sighted one 5. Investigate behaviour of Posting bot (does he create a new thread/re-opens the existing one/config abilities we have here) Thanks a lot, R -- 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

5 12

[opensuse-wiki] Links on logout page from wiki.o.o point to en.o.o
by Rajko M. 24 Feb '10

24 Feb '10

Links on logout page from wiki.o.o point to en.o.o 1) ----------------------------------------------------- Thanks for using openSUSE! To get to the Login page _click_ _here_ or the login button above. * "click here" is link to: http://en.opensuse.org/ICSLogin/?%22http://en.opensuse.org/... * there is no login button above 2) ----------------------------------------------------- Logo points to en.o.o (the OpenSUSE.php ??) -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 2