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

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

23 Feb '10

Sascha, 2010/2/22 Sascha Manns <Sascha.Manns(a)open-slx.de>: > Am Montag, 22. Februar 2010 13:09:59 wrote Rupert Horstkötter: >> 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 > Done. Now it is the first Announcement there. > BTW: Good Job Rupert. > Thanks for taking care! Best, R > -- > Sincerly yours > > Sascha Manns > OpenSUSE Community & Support Agent > open-slx GmbH > > -- 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] wiki.o.o news 02/15
by Henne Vogelsang 21 Feb '10

21 Feb '10

Hi, After i moved everything from the openSUSE namespace into the Help namespace which was very straightforward i started to wade through the Template namespace. I must say i get frustrated with the cruft that is already in this instance by today. There were a lot of "standard" Templates that did not follow our own Template guidelines. CamelCase naming, strange content and most of them had no documentation at all. I fixed all the case and content issues and with documentation i got as far as the letter B. I used the wikipedia way of documenting templates. Every template has a subpage /doc which provides the documentation. You include it on the Template page in a 'noinclude' block so it does not get included when you include the Template. It's easier as it sounds ;) Just look at the first Template we have: AI http://wiki.opensuse.org/Template:AI This way explaining a Template on a some page is as easy as {{AI|000001}} {{AI/doc}} So if you want to help you can go through the Templates[1] and create documentation where its missing. Thats it for today. Henne [1] http://bit.ly/bilRR5 -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

5 8

Re: [opensuse-wiki] Wiki Outage on Saturday
by Matthew Ehle 20 Feb '10

20 Feb '10

Thank you for bringing this to my attention. The problem was that the wiki was not getting the configured values from the database and so pulled the default values for the sidebar into memcached. A restart of memcached fixed the problem right away. Please let me know if anything else comes to your attention. Matthew Ehle Application Services mehle(a)novell.com 1-2722 >>> "Rajko M." 02/20/10 1:01 PM >>> On Friday 19 February 2010 18:00:03 Matthew Ehle wrote: >... I will be verifying > that they work once the cable work is done and the database servers are > back up. Matthew, The left sidebar is in default MediaWiki status, with empty SEARCH, TOOLBOX, LANGUAGES. "Navigation" is default too: Main Page Community portal Current events Recent changes Random page Help The content of http://en.opensuse.org/MediaWiki:Sidebar doesn't show at all, and it should be listed in "Navigation". -- Regards Rajko, -- 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] Wiki Outage on Saturday
by Matthew Ehle 20 Feb '10

20 Feb '10

The datacenter will be moving some fiber cables on Saturday, from 9 to 10 AM (EST). During that time, the database servers for all the openSUSE wikis and blogs will be intermittently unavailable. I will be verifying that they work once the cable work is done and the database servers are back up. Thank you, Matthew Ehle Web Engineer Application Development & Maintenance Affiliated Computer Services, Inc A Xerox Company Office Phone: (801) 861-2722 mehle(a)novell.com

3 2

[opensuse-wiki] New user guidelines
by Jon Rocker 19 Feb '10

19 Feb '10

A user by the name of dvhenry recently discovered what happens when you run rm -rf *. http://forums.opensuse.org/opensuse-wiki-discussions/433257-suggest-warning… Another user, fiertel91 also discovered what happens when you run that command. http://forums.opensuse.org/install-boot-login/433148-everything-erased-thro… In the first case, the code was removed, in the second case, the code was allowed to stay. I understand the New user safety. http://en.opensuse.org/openSUSE:Wiki_Style_Guidelines#New_user_safety In the second case, I discussed it with Frank and henne on IRC and we decided that removal of the code did not make sense since the article is about what not to do as root. But in the first case, I can't make out the purpose of that article. It's short, but the grammar is bad. The title says its about how that root can run certain programs, yet it used to reference rm -rf *. At any rate, I feel we need to come to a single mind, a commonality about what is acceptable, regarding scenarios like this. It doesn't make much sense to allow it in one article and not in another. -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 2

[opensuse-wiki] wiki.o.o change notifications
by Thomas Schmidt 19 Feb '10

19 Feb '10

The implementation of the mediawiki hermes extension is ready [1] and online on wikistage.o.o and wiki.o.o This makes it possible now to configure custom notifications and feeds on hermes.opensuse.org. I already created an rss feed for all changes on wiki.o.o: https://hermes.opensuse.org/feeds/59596.rdf I think it would be useful to create notifications and feeds for the different namespaces for example, or for the proofreaders. Please let me know if you need help in setting up notifications. To enable the standard mediawiki notifications we have a bug pending (#325753) Greetings [1] https://svn.berlios.de/svnroot/repos/opensuse/trunk/infrastructure/wiki.o.o… -- 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

2 1

[opensuse-wiki] Guidelines, Revision control, Template in new instance
by Rémy Marquis 19 Feb '10

19 Feb '10

Some stuff about the new wiki instance: *Updating guidelines. For some reason, the wiki guidelines that were in the new instance weren't the last version available on en.o.o. I changed them to the last version and merged the changes done on wiki.o.o. The Guidelines articles in en.o.o are now tagged as "Transfered in the new wiki". Please make further changes directly in wiki.o.o if you need to improve the Guidelines (and ensure that the last version of en.o.o articles is in wiki.o.o before starting to edit). ---- *Revision control draft I prepared http://wiki.opensuse.org/Help:Page_validation as a first draft, loosely based on Second Life wiki [1] (the deepest explanation I found on Flaggrev). This page is linked from the main wiki guideline page, and all pages that are under revision control. What should be done here: - proper introduction/presentation of flaggrev control. I remember that Rupert asked for a deeper explanation about our QA process. This should be written here :) - Reworking user groups. I'm not sure how Reviewer/Editor groups will be used in our new instance, it is a bit different from the SecondLife wiki. Administrators: Can flag as "Quality" (Reviewer in SecondLife wiki) Reviewer: Can flag as "Sighted" (Editor in SL wiki) Editor: ? (only Frank in this group at the moment) Am I right on this? ---- *Revision control and help namespace. Actually, flaggrev seems enabled on main, Portal, Template namespaces. I believe it would be good to enable it for the Help namespace too. ---- *Articles tags Template simplification [2] Actually, we have the following tags template in wiki.o.o : - Expand - Cleanup - Obsolete - Merge - Delete The following aren't in wiki.o.o yet, and I'm wondering if we should get rid of them: - Needs review (obsolete with flaggrev QA process) - Section cleanup (almost similar to Cleanup) - Outdated (similar to Obsolete, and (almost) never used correctly in en.o.o ) - SpeedDelete (similar to Delete + obsolete with the "sighted" feature of flaggrev QA process) - Move to SDB (no idea if this one is still required) ---- *What I am planning to do next (if I find time... ) - Transfering/reviewing pages that should be in Help (should be almost done now) and Template namespace - Working on the three Portals already available (Shayon works [3] will be useful there) - Defining a proper list of predefined Categories to be used in the new wiki, as defined by [4] Regards, R. [1] http://wiki.secondlife.com/wiki/Flagged_Revs_Configuration [2] http://en.opensuse.org/openSUSE:Wiki_Tag_Guidelines#Article_tags [3] http://en.opensuse.org/User:Wwarlock/Test1 and http://en.opensuse.org/User:Wwarlock/Test2 [4] http://en.opensuse.org/Transition_Guidelines#Step_0_:_Preparation -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

3 2

Re: [opensuse-wiki] wiki.opensuse.org preferences pages
by Matthew Ehle 18 Feb '10

18 Feb '10

Done. Matthew Ehle Application Services mehle(a)novell.com 1-2722 >>> Thomas Schmidt 02/18/10 4:59 AM >>> On 18.02.2010 04:26, Rajko M. wrote: > On Wednesday 17 February 2010 10:46:58 Thomas Schmidt wrote: >> Hi, I just stumbled over the wiki preferences pages and found some issues: >> >> - E-Mail: >> Should we make this field read-only and sync the adress from ichain >> automatically upon login? > > To that sounds fine. > Prevents pranks, ie. give someones email instead of yours and laugh when guy > starts to get emails that he can't decipher what they are. > >> - 'Change password': I think we should redirect >> this link to the Novell/openSUSE account page. > > Sure. > MediaWiki change password has no use with openSUSE. Ok, I committed these changes to svn. Matthew: Could you please deploy wiki.o.o? Thanks, 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

1 0

[opensuse-wiki] wiki.opensuse.org preferences pages
by Thomas Schmidt 18 Feb '10

18 Feb '10

Hi, I just stumbled over the wiki preferences pages and found some issues: - E-Mail: Should we make this field read-only and sync the adress from ichain automatically upon login? - 'Change password': I think we should redirect this link to the Novell/openSUSE account page. - Skin Tab: I think that one should be removed. Are you ok with me doing these changes? Greetings -- 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

3 2

[opensuse-wiki] HCL
by Jon Rocker 18 Feb '10

18 Feb '10

One of the forum members was perusing the HCL and noticed that on a particular one, he didn't mention which one, that he had to scroll quite a ways to the right. The thread is here http://forums.opensuse.org/opensuse-wiki-discussions/433160-hcl-progress.ht… I did go through each one, but I don't remember which one I had to scroll a bit to the right. Also, my resolution is not near as high as his. Mine is 1024x768. I mention some possibilities in the thread, and wonder what you all think. -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 1

[opensuse-wiki] Template "Infobox Software" is garbled in Internet Explorer
by Rajko M. 17 Feb '10

17 Feb '10

Using Firefox or Konqueror, it looks good, but in Internet Explorer the image keeps position and it is right aligned, but frame elements are shifted left, closer to the TOC, each in its own position so the frame looks like couple of disjoint lines and corners. Besides that, template does not show versions, only {{{VersionXYZ}}}. See in Internet Explorer: http://en.opensuse.org/Amarok Does anyone check his web design in other major browsers? Do we create designs that will work for browsers used in Linux alone? I know that I didn't check before this case, but it seems that is bad idea. The browser market is still largely Internet Explorer turf, and having template like Infobox Software, that should be on every software description page, broken, is guarantee that a lot of the visitors will laugh, and completely understand claims that Linux is designed by bunch of amateurs. -- 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

Re: [opensuse-wiki] Navigation bar (NavBar) doesn't solve all navigation problems
by Rémy Marquis 17 Feb '10

17 Feb '10

Hi, I'm forwarding this answer on the -wiki ML as one could add some ideas/suggestions. On Tue, Feb 9, 2010 at 5:28 AM, Rajko M. <rmatov101(a)charter.net> wrote: [...] > I use HCL as example as it is really large group in need of at least 2 levels > of navigational bars, in our local parlance NavBar as Template:NavBar. > > http://en.opensuse.org/HCL/Laptops > is example of double navigational bar. > > Both navigational bars are stand alone templates: > http://en.opensuse.org/Template:HCL > http://en.opensuse.org/Template:NavLaptops > > The rest of templates that have similar layout, like one used on > http://en.opensuse.org/Documentation > are created using http://en.opensuse.org/Template:NavBar . > > Two templates at the top are not really elegant solution, but currently we > don't have better idea how to add subtopic. The best solution I can find is this proposal (if we define that "Board" content is a subgroup of "Community" wiki pages) : http://en.opensuse.org/Community http://en.opensuse.org/Board As you can see, I've added a link to the more global "Community" page directly in the "Board" navbar. Advantage is that we don't clutter the user with (too) many links, but only the link of the "parent page" (in this case, "Community"). Imho, a double navbar is just too "overkill". Add too many navigation links and the user is lost again. The disadvantage (or advantage too) is that we need to define a very clear "tree-structure" on the new wiki, i.e. : Community Portal \__ Board \__ Members \__ Ambassadors \__ Teams \__ How to Participate \__ Artwork \__ subtopic Documentation Portal \__ Installation \__ Package Management (end user) doc \__ HOWTOs \__ Developer Portal \__ Packaging \__ OBS ... > > > I short conversation with Remy on IRC we came to conclusion that we have to > experiment on the new wiki, as creating solutions on old wiki that are missing > abilities of extensions and parser hooks leads nowhere. > > I still have no idea how to organize tests as it was mentioned in topic 'New > "Need consent" tag in transition table' we have some articles that we can't > handle as we don't have any written or spoken policy about that. > > Even worse, we never listed wiki content by type, and besides end user > documentation we have quite a few other types, like developer documents, > teamwork related articles, meetings, team pages, plans, etc, etc. Yeah, we really have to separate content by "user case". See above. > > My time is currently even more restricted as company needs more hours and the > current weather doesn't cooperate, so if all will wait on me it will stretch > quite a bit. I guess that Remy and you are not in a better position. > > -- > Regards Rajko, -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

4 5

[opensuse-wiki] Get going wit the new instance
by Henne Vogelsang 16 Feb '10

16 Feb '10

Hey, i would like to get going with the structure. Judging from the recent messages in this list we're dancing around it and don't really go forward. IMHO we're taking the wrong approach in trying to think everything through before doing anything. I think we need to take the ship out of the harbor and roll with the waves :) So I want to start tomorrow 11:00 CET with the new structure on wiki.o.o. For that i will get rid of the test content that i there today, take reviewed content from http://en.opensuse.org/Transition_list_table and general structure pages and start. I will let you know daily where i am and what you can do to help me. Rajko you would have to limit your testing to a specific area, sorry. I propose /Rajko or do you need something else like a namespace or something? Please let me know. Any objections? Speak now or forever hold your peace! :) Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

5 9

[opensuse-wiki] SDB <keyword> tag
by Andras Dosztal 16 Feb '10

16 Feb '10

Hi, I just found out recently that the <keyword> tags in SDB articles are not interpreted. Example: http://en.opensuse.org/SDB:Repair_MBR_after_grub_install Is it replaced with something else or a bug? Regards, Andras -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 2

[opensuse-wiki] wiki.o.o news 02/14
by Henne Vogelsang 14 Feb '10

14 Feb '10

Hi, i tried to work on the Portals but got carried away by the mess with is already now in the new instance. So i decided to to clean up. I started with the File namespace[1] where i unified (now using nearly only oxygen icons) and categorized the content. TODO: Document all the icons. What is it that we want to express with those by default? This is important so people actually use them for their content. There is no need to have 16 oneway signs or 4 different graphical representations for help. The Guidelines need to be extended for this topic too. I then went on to the Template namespace[2] where i decided which are usefull (to get going!) and which are not. Here we suffer from the same fact. People duplicated templates. I guess we need to put more work into the guidelines, especially for newly added content. The only "creative" thing i did was re-using the Portal boxes to make a userpage template. http://wiki.opensuse.org/Template:Userpage The next namespace to "clean" would be openSUSE:. From what i can see we can move nearly all content to Help:. I will look into that tomorrow. Thats it for now. Henne [1] http://bit.ly/dkKLcw [2] http://bit.ly/bilRR5 -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- 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] Image OxygenRpmPackage.png
by Rajko M. 13 Feb '10

13 Feb '10

IMHO, I don't see connection between current icon for rpm packages: http://en.opensuse.org/File:OxygenRpmPackage.png and package management. Can someone help me to understand. The old version was more then clear, package with label RPM, but this one is generic Oxygen icon. Do we have to replace all icons with Oxygen in the name with this one? -- Regards Rajko, -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 1

[opensuse-wiki] wiki.o.o news 02/13
by Henne Vogelsang 13 Feb '10

13 Feb '10

Hi, yesterday evening Matthew purged the main namespace so today i started to move content. I started with reducing the content of the Main_Page[1]. It now only points to the 3 things we have in this wiki. Information about the distribution, the project and the wiki itself. The introductions point to portals about the subjects. And thats the second thing i worked on. The Portal template[2] and Help[3] about it. What can you do to help? Of course the Portals and especially the intros could use some love. For the distribution and the project it was relatively easy to find cool sentences to glue together because we have a lot of content about those topics in the old instance. For the wiki itself it was not so easy. So go to that page[4] and fill it please. I'm also sure that we can make the design of the frontpage easier for the eye, less text'ish for instance. I will continue to work on the Portals and then go from there starting with the Help namespace because its the most important for now. Thats it for today... Henne [1] http://wiki.opensuse.org/Main_Page [2] http://wiki.opensuse.org/Template:Portal [3] http://wiki.opensuse.org/Help:Portal [4] http://wiki.opensuse.org/Portal:Wiki/Intro -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

1 0

Wiki forum is live! (was: Re: [opensuse-wiki] New "Need consent" tag in transition table)
by Rupert Horstkötter 11 Feb '10

11 Feb '10

Team, 2010/2/8 Rupert Horstkötter <rhorstkoetter(a)opensuse.org>: > 2010/2/8 Rajko M. <rmatov101(a)charter.net>: >> I was missing such forum few times since wiki cleanup action begun. >> I'm sure that 90% of forum guys are annoyed with IRC and mail lists for some >> reason, so I vote for it and as soon as possible. >> > I just took care about that one at the team area at forums.o.o .. > should be a matter of days and we should have the wiki forum up and > running. > Done! The Wiki forum is live at http://forums.opensuse.org/opensuse-wiki-discussions/ I posted a quick welcome (will be stickied) at http://forums.opensuse.org/opensuse-wiki-discussions/432668-welcome-wiki-fo… to explain its final and its interims purpose. Have fun! Lemme know if you need anything, 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

3 4

[opensuse-wiki] Team Pages
by Rupert Horstkötter 11 Feb '10

11 Feb '10

Team, gnokii thought about informations that should be provided on team pages and I'd like to forward this to you in order to get more feedback before I'll reach out to the Teams asking for implementation/adoption. I CC: interested parties to make sure they're aware. So, what we'd like to achieve? Team pages are an integral part of reaching out to potential contributors and GOOD team pages encourage contributors to get involved in the Project/specific Team. Here is what gnokii prepared so far --- What information should be on team pages 1. what does the team do, tasks etc. * include the sources in the wiki 2. how is it organized -> the way to work in this team!!! 3. members of the team * important some teams sort the members after novell and community thats not good! * some teams like the boosters give all contact informations for each member there, thats not necessary. Better link to the userpage and hold each information there. 4. contact data for the team like IRC and mailing lists mor isnt necessary on the wiki pages. I would like to have point 4 on the side like the "team template" now is. And the team template on the end of the side is better. Over the contact data Iwould put a graphic that represent the team, or this I need the dimensions for it. Look after art team page, there is the graphic same size like the "team template" has. So it looks good. On one page I saw a nationality flag behind the member, thats a good idea, for connecting I would me pick a member in my language its easier --- So far for specific Team Pages .. It's all about providing the right, and ONLY the sufficient info in an accessible and common way across ALL team pages we have and integrate them under one umbrella (see below). The other thing is our "Inter-team page", i.e. listing the teams. Currently we have http://en.opensuse.org/Teams and http://en.opensuse.org/openSUSE:Teams is what we'd like to have instead. Thanks henne! So, after all, this is a two step process: 1. Implementing/adjusting team pages 2. Listing teams at http://en.opensuse.org/openSUSE:Teams Any suggestions? Additional ideas? Best, 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

4 6

[opensuse-wiki] SoftwareInfoBox
by Sascha 'saigkill' Manns 10 Feb '10

10 Feb '10

Hello Mates, we've started the same Process like you: Reviewing of the Wiki. But i have Question. In the Amarok Article we have the "Knowledge" Macro and an selfmade SoftwareInfoBox. Both in one Article are not recommended, Should we use in this case just the Knowldege Macro? -- 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

2 1

[opensuse-wiki] New "Need consent" tag in transition table
by Rajko M. 08 Feb '10

08 Feb '10

Some types of article is not defined how to handle, some are questionable and what one community member will delete, the other will preserve as community history. Some articles are transient content, like: http://en.opensuse.org/openSUSE_Launch_Party_Locations Ditto, to speed up reviews I added that tag so that reviewer can go on while we can discuss how to handle specific type of article. This will raise questions: Where to discuss such problems? Is opensuse-project is good place, or we should go broader. Use Forums and opensuse(a)opensuse.org ?? In what namespace belongs historic material? In what namespace, or even another server to put transient content that is obsolete after the event? Where to document procedure? Is explanation of tag in tables sufficient? -- Regards Rajko, openSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 3

[opensuse-wiki] wiki.o.o test of new functions
by Rajko M. 08 Feb '10

08 Feb '10

We imported pretty large body of articles from old wiki that will allow us to test wiki. Further imports will be done only if we really need article or group. What is left to upload are images that are missing so that we can really test complete page layout. Right now we have bug that prevents creation of thumbnails so we have time to upload images. The number of new features is quite large comparing to old wiki version 1.5, so we will have quite a job to test them. You can see list of features here: http://wiki.opensuse.org/Special:Version **************** First to test was CategoryTree http://www.mediawiki.org/wiki/Extension:CategoryTree It enables editors to create list of categories and articles in categories that are available on every page on the wiki. This will allow us to have groups of articles with common navigation menu that is updated as soon as article is added to common category. Unlike current method of creating navbar (navigation bar) templates for each group of articles and updating that navbar every time new article is added, with <categorytree> tag all that wiki maintainers have to do is to ensure that new articles have proper [[Category:<nameit>]] link included at the end of article. I started to create categories from YaST related articles, then used ready to go tag from mediwiki.org to test the wiki tag <categorytree>. Some samples for preview are here: http://wiki.opensuse.org/YaST http://wiki.opensuse.org/Category:YaST and live wiki that is using that tag is here: http://www.mediawiki.org/wiki/Extension:CategoryTree The "plus" widget that you can see in the mediwiki.org CategoryTree is missing in our wiki, which makes use of mode=pages problematic in: <categorytree mode=pages style="float:right; clear:right; margin-left:1ex; border:1px solid gray; padding:0.7ex; background- color:white;">YaST</categorytree> You can see on the page http://wiki.opensuse.org/YaST that there is no distinction between listed category and article in that category. **************** The next in the list is Flagged Revisions. http://www.mediawiki.org/wiki/Extension:FlaggedRevs It is extension with a lot of options. I checked the basics. The editor/reviewer tools at the bottom of the page appear in Main and Template namespace. We are missing icons (images) for tag that is present on every page, before words/strings Unreviewed or Current revision, as well as bars in detailed view that can see user that is not logged in a wiki. The "plus" widget that is used to switch from detailed view of article status to simple is missing too. **************** The rest of extensions is not tested on a new wiki, but we know that: InputBox http://www.mediawiki.org/wiki/Extension:InputBox works in a simple example on http://en.opensuse.org/SDB:SDB that is the same version. There is more options in InputBox to test and see where this extension can be useful. **************** Next extension to test is DynamicPageList which is described on http://www.mediawiki.org/wiki/Extension:Intersection From description, it can be useful to create list of articles that belong to few categories without need to create new category and add tags to all articles. **************** Conclusion: Sorting articles in categories and subcategories is very important in order to use new tools. It shifts majority of efforts on one time categorization of existing fond in the old wiki, and then export to new one category by category. New software allows us to name category and it will automatically create list of articles that are listed there, so it will be easier track transfer. The files (images etc) is right now the most labor intensive. We have to see is it possible to categorize them and transfer as category, if not them we have to run quite a few downloads from old wiki and uploads to the new one. -- Regards Rajko, openSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

5 7

[opensuse-wiki] Template Sablon:PointHere used in Weekly news
by Rajko M. 08 Feb '10

08 Feb '10

Template Sablon:PointHere http://en.opensuse.org/Template:Sablon:PointHere used in Weekly news will be very soon removed. Please use previously existing PointHere : http://en.opensuse.org/Template:PointHere All pages that used Sablon:PointHere template, including page templates, are converted to PointHere so the only problem can be copy of this templates stored on your computer. If you see on your page multiple messages: "Template Sablon:PointHere is duplicate of template PointHere and it will be deleted eventually. Please use Template:PointHere instead. In wiki text it looks like {{PointHere}} All other Weekly News pages are already converted, including page templates, and only Weekly News templates outside this wiki en.opensuse.org, for instance on your computer, can require Sablon:PointHere." then you are trying to use Sablon:PointHere. -- Regards Rajko, openSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- 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] Navigation bar (NavBar) doesn't solve all navigation problems
by Rajko M. 04 Feb '10

04 Feb '10

NavBar is meant for single group of articles where group should be maximum to 7 articles ( http://useit.com ). Problem is when there is subtopic that needs own navbar. What we can do? 1. Add another navigational bar for that subgroup, like it is used in HCL, and have 2 navigational bars on top of the article 2. Look for another solution like category tree on side that will list category, subcategories and articles there? The second solution will require some articles to be transferred or to play with current YaST group with more articles from that group transferred on a new wiki. -- Regards Rajko, openSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- 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] The most annoying bugs 11.3 dev on wiki
by Rastislav Krupanský 03 Feb '10

03 Feb '10

Hi. If i´d like to add some annoying bugs on wiki to prevent repeated/unnecessary reporting bugs, how is the procedure? This article is under review. The contents are currently being evaluated and edited by User:Jonathan_R. Others should not make any changes. Or can i add the most annoying bugs in M1 myself? Thanks. -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

5 9