August 2010 - openSUSE Wiki - openSUSE Mailing Lists

[opensuse-wiki] Wiki Google Custom Search
by Matthew Ehle 08 Nov '10

08 Nov '10

Hello, As Carlos pointed out, I had accidentally hijacked an earlier thread, so I am starting this new one up. Here is the original message: I have implemented Google Custom Search on enstage.opensuse.org, and I am personally very happy with the results. To try it out, you can visit http://enstage.opensuse.org/Portal:GoogleSearch and try searching on anything you want. It is about a thousand times better than what we have, and with the better relevance ranking, namespace searching is no longer an issue. While the current search is advertisement supported, I am nearly positive that we can get ad support removed. It seems that Google is pretty willing to do this for non-profits. What does everyone think? If you don't have access to the staging site, I will be more than happy to send you a screen shot of the search page. If everyone is on board, I will ask Thomas to edit the theme to make it the default search, and we'll send it live. Thanks, Matt By the way, you need access to the staging site to see this (i.e. you need to be on the Novell network). I can provide screen shots if requested.

11 31

[opensuse-wiki] Lucene Search Update
by Matthew Ehle 07 Oct '10

07 Oct '10

Good Day, So here is an update on https://bugzilla.novell.com/show_bug.cgi?id=625677. After contacting the author about the spelling suggestion issue I was having, I finally got it to work. As an added bonus, I have discovered and enabled the related articles feature as well. With these features working, Lucene is definitely a better option than Sphinx now. All the "new" wikis on stage (en, dewiki, and languages) are now using Lucene search. The enstage wiki has the most content of the three, so you can get the best idea of how well it works by going there. However, those of you who are fluent in German should also try dewiki, so that you can see how well the search deals with German stemming and stopwords. The indexing takes 45-50 seconds on stage, so I'm expecting it to take about a minute to index the live English wiki, and probably another 30 seconds for the production dewiki and languages. Once everything is transitioned over to the new wiki structure, total indexing will probably be in the 10 minute range. I plan to put the indexer on a daily cron, so all changes should show up in the search within 24 hours. I am setting up a meeting with the data center to go over an OS upgrade plan so that we can get this going as soon as possible. -Matt

6 13

[opensuse-wiki] Colon in category Title
by Tim Mohlmann 08 Sep '10

08 Sep '10

Hi Guys, I see multiple Category with colon in title. Eg. Category:SDB:Network. I feel this is not correct, but I can't find anything in the Guidelines about it. So what will be the guideline on this? Category should be Category:Network and should become a sub-category of Category:SDB... right? I discussed a few weeks ago on IRC, but I can't remember the outcome off this and I feel it needs to be discussed with more then 1 men ;) (I'm asking this, because there are network related topics, that do not belong to SDB:, so forcing me to create Category:Network) Greatings, Tim -- 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] Preparation progress languages.opensuse.org
by Rajko M. 01 Sep '10

01 Sep '10

I started to create basic structure that will be the same as en.opensuse.org . Not much done this evening. Part of main page and Help:Language_wikis. Created interwiki links for almost all domains, but skipped few that are dead for years, see http://languages.opensuse.org/Help:Language_wikis . There can be more to comment out. Tomorrow will try to reach the point to have Portal:Bulgarian as basic navigation for all other pages in Bulgarian language. Navigation as usually in right side vertical bar, and list of all pages in Category:Bulgarian using CategoryTree. Basic navigation should be: "English title/BG" as redirect to "Translated title in Bulgarian" without any suffix or prefix. Not yet sure that I like / ie. subpages as place for redirects, ie. are there any advantages to use them. There is obligation that translator put all articles at least in [[Category:Bulgarian]] and also [[Category:Bugarski]] (missing cyrilic alphabet, but potential translators will get the point). Each of categories will live in root of all translation categories [[Category:openSUSE project languages]]. One of basic requirements for this to work is that is simple to create translation, which can be achieved with each mandatory page containing InputBox. Number of mandatory pages must be real minimum, so that is easy to update them, and they must be tracked for changes (watch list). -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

4 9

[opensuse-wiki] Connection resets on wiki forum
by Roman Bysh 31 Aug '10

31 Aug '10

Hi all, I'm trying to provide support on the forum. However, my browser's connection keeps getting reset so I cannot log on. :-) Cheers! Roman -- 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] missing page
by Brian K. White 27 Aug '10

27 Aug '10

From opensuse(a)opensuse.org > I'm sure this issue has come up before (found several references in > google, all with URLs that point into oblivion since changes. e.g. > http://en.opensuse.org/VirtualBox_installation) Just logging this since I have time for that much. If some kind soul would put in yet another redirect or copy the page? Or I may get to it myself sometime, just wanted it recorded. -- bkw -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 2

Re: [opensuse-wiki] Sphinx vs. Lucene
by Matthew Ehle 27 Aug '10

27 Aug '10

>> I have installed both Sphinx and Lucene on the staging sites. They >> each have their advantages and disadvantages, so I want to see what >> everyone would like to see go to production. > >I know that sphinx might be tempting right now but i would definitely go >with lucene. Because we can then live off the development and >maintenance of mediawiki instead of doing our own. I also think we >should use the same style as the mediawiki search page because people >are used to it. Yes, I agree that that the search integration bothers me too. If Sphinx had the same quality of plugin as MWSearch, then I would be much more convinced that it is better choice for us. As it is right now, I suppose it's something of a coin toss. One option is to rework the plugin to integrate with the default search functions instead of working around them. This shouldn't be as hard as it sounds. The vast majority of this would be in a single PHP file, and I don't think it would take more than a couple of hours. I could do it myself if I wasn't so swamped by other requests. The default search and both search extensions are hardly ever updated, there wouldn't be much work once this is done. Anyways, it's just a thought. One of my main concerns for Lucene are that the indexing process is very heavy, so I wouldn't want to run it more than once or maybe twice a day, compared to every few minutes for Sphinx. There is a way to do incremental updates, but it involves yet another extension and schema change, and there have been numerous problems reported with it. The other big concern is that I cannot get suggestions to work at all under Lucene. The spelling index gets created, but I cannot get the search daemon to use it. I'm going to try compiling the Java source under the system's JDK and Ant to see if that gets me anywhere. If I can get the suggestion functionality to work, then I will agree that Lucene is absolutely the superior choice (their suggestion functionality beats aspell/pspell hands down).

1 0

[opensuse-wiki] Sphinx vs. Lucene
by Matthew Ehle 27 Aug '10

27 Aug '10

Hello, I have installed both Sphinx and Lucene on the staging sites. They each have their advantages and disadvantages, so I want to see what everyone would like to see go to production. Here is a quick rundown of the advantages of each: Lucene: -Better integration with MediaWiki default search -Displays the custom "No results" message that Henne created if no results are found (Sphinx can probably be hacked to do this without too much trouble) -Slightly better relevance on some queries -Displays word count and timestamp for each result (some hacking can probably get this on Sphinx as well) Sphinx: -More frequent indexing possible (full indexing daily with incremental indexing every few minutes) -Written in C, no Java installation required -Because of the above, it can be moved live without having to wait on an OS upgrade -Spell checking through aspell (Lucene's is supposedly better, but I cannot get it to work at all) -Easier to customize the extension and better documentation Both search options are extremely fast, provide highly relevant results, support wildcard searches, and work well with multiple wikis (including language specific stemming). Needless to say, both are far superior to the default search. I am slightly more in favor of Sphinx right now. This is partly because it is easy to hack the extension, and partly because it could go live tomorrow if we want to. For those of you who can get to the staging site, Lucene is set as the default search, and Sphinx can be found at stage.opensuse.org/Special:SphinxSearch. Feel free to try them out and compare. -Matt -- 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] some help with Portuguese wiki page
by Carlos Ribeiro 26 Aug '10

26 Aug '10

Hello all, Up here in Brazil, we are working together with some guys from Portugal to improve and grow our openSUSE Portuguese language community in quality and numbers and one of our next steps is to make our Portuguese wiki page more aligned with the global wiki page. Then we believe we need no more than 3 users with full rights at http://pt.opensuse.org/MediaWiki:Mainpagerightcolumn to be able to migrate our wiki theme to "bento" for example. Is this possible? Makes sense? Also, As I mentioned we like to migrate our wiki theme to "bento" Any clue who is the best one to give a hand to us? Is there anything we must do before this process happen? best regards thanks CarlosRibeiro -- 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] New Staging Server
by Matthew Ehle 24 Aug '10

24 Aug '10

Hello, In preparation for the 1.16 upgrade and installing the latest Lucene search, the data center has created a new virtual machine with the latest and greatest version of SLES. Over the next few days, I will be setting up this new machine and transferring content, after which we will change the iChain configurations to point to the new stage server. Please make sure to inform me if you are doing anything on the current staging box, as your changes could otherwise be lost. I will inform you when the changes are all done, hopefully sometime next week. -Matt

1 1

[opensuse-wiki] pt.o.o
by Kayo Hamid 18 Aug '10

18 Aug '10

Guys, we are working to translate the new schema to our wiki, but we have some problems - We do not have some extensions like CategoryTree - Missing the Bento theme My big question is: what will happen with pt.o.o? We can continue to translate the pages without future problems? -- Kayo Hamid Fontinhas - kayohf(a)gmail.com openSUSE Member, Ambassadors & Testing Core Team http://en.opensuse.org/User:Kayohf -- 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] Performance Options
by Matthew Ehle 17 Aug '10

17 Aug '10

Hello Everyone, I was looking at some site stats, and right now Google is reporting that the wiki pages are taking an average of between 2.5 and 3.5 seconds to load. This is slower than 50%+ for all sites. I am hoping to cut this down to under 2 seconds, which would put us in the 25% range or better. Here are a couple of options to do that: Localization Caching - There is no conceivable reason to not do this, and it should provide a small speed increase. Enable Gzip - This would help out a little, and there shouldn't be much risk to it. File Caching - This would provide a major boost in speed. This alone could take nearly a second off page loading time. However, this does have a drawback. Taken from the manual page: "The file cache tends to cache aggressively; there is no set expiry date for the cached pages and pages are cached unconditionally even if they contain variables, extensions and other changeable output. Some extensions disable file cache for pages with dynamic content." How badly would this affect us? It would be easy enough to cron up a refresh of this cache if that would help. Combine external files - Perhaps some of the skin designers might want to look at this. Right now, each page requires up to 13 CSS files and 9 Javascript files, a good portion of which are on static.opensuse.org. Combining some of these would make a noticeable difference. Caching Proxy (Squid) - An alternative to file caching and a viable long term option. Would require some big changes and probably not justifiable right now... I can work on the first two, but I would like to hear some input on the last three. In particular, I want to see if the file caching option is viable, since it has the largest potential right now.

4 8

[opensuse-wiki] Templates for languages.o.o
by Matthew Ehle 17 Aug '10

17 Aug '10

Hello, I have exported all the templates from the English wiki. I was wondering if they should all be imported into languages.o.o. I think there's something like 150 of them, so it would likely save on time. Also, I have put an article on planet.opensuse.org about all that has happened with the wikis lately. Considering that we were running on MediaWiki 1.5 just a year ago, we have come a pretty long way! By the way, I will soon be trying out MediaWiki 1.16 on the Novell wikis. Provided that all goes well there, expect an upgrade to the openSUSE wikis within a month or two. This should be MUCH less painful than the jump from 1.5 to 1.15 =)

3 4

Re: [opensuse-wiki] validate email address instructions in German
by Matthew Ehle 16 Aug '10

16 Aug '10

>>>> Thomas Schmidt 08/16/10 3:53 AM >>> >On 13.08.2010 16:26, DenverD wrote: >>while looking at http://en.opensuse.org/openSUSE:Services_help just >> now i saw a new (to me) link saying to edit i need to verify my email >> address...(a feat i thought was done years ago when i received my >> novell/openSUSE ID/password login for the forum..) but i decided to >> play the new game and am directed to: >> >> http://en.opensuse.org/Help:Email_validation >> >> which includes instruction to go to >> https://secure-www.novell.com/selfreg/jsp/protected/validateEmail.jsp >> >> where i am assaulted ;-) with German text that will NOT translate to >> understandable English at google.. >> >> i don't really enjoy these games.. > >I think the Novell account pages switch to a language that is preferred by your browser. >You could check for example on http://www.ericgiguere.com/tools/http-header-viewer.html >if your browser prefers german (accept-language). In addition, there is a cookie that gives localization information, but I have no idea why that would have been set to German for you. You can test that by going to www.novell.com. On the top right of the page, there is some text that indicates country and language. Just select the button to the right ("Change"), and pick your favorite country and language. That will set the cookie to a language you can understand ;)

3 3

[opensuse-wiki] Update selected language wikis to the current state of en.opensuse.org
by Rajko M. 16 Aug '10

16 Aug '10

Bugzilla request: https://bugzilla.novell.com/show_bug.cgi?id=629405 can produce longer discussion, so it would be better to use ML for that *** Having separate wiki.o.o was advantage with en.o.o, as it helped to create new structure without having ballast of backward compatibility on our neck that can spoil efforts and final result will be far from wanted. Our biggest problem after the switch was sudden and large change, which always creates tensions. People have aversion to change. With language wikis is different. They don't have backward compatibility problem, all they have now is problem how to get in sync with en.o.o. What is advantage of just updating? 1. We don't have to think about article histories and attribution to authors, they will be preserved with article move to new location. 2. When splitting articles all we have to do is: 2.1. create new article 2.2. leave message in a very first comment that tells: "This article is based on [[original_article_name]]." The new wiki allows to use syntax [[original_article_name]] which is converted to link to original article, even in comment field. 3. Move is much faster operation then export from one wiki and import to the other, plus all icons and logos are in place and can be replaced as time permits with those that are used in en.o.o. 4. The change will be stretched over the time which will give users a chance to adjust. 5. Search engines will not index temporary wiki. (Any more?) BTW, script (bot) that will browse wikis and update interwiki links is long overdue, so this can be opportunity to find or create one. Disadvantage: 1. A lot of article deletions, which can be handled with some of scripts in a maintenance directory like deleteBatch.php , or some extension that will remove all traces of deleted files like http://www.mediawiki.org/wiki/Nuke . 2. There is need for careful planning, like listing articles in few categories: 1) keep (keep as is, split to, update) 2) obsolete good >> direct to Archive 3) obsolete and low quality >> delete 4) need expert help and probably more. Comments, please :) -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

6 11

[opensuse-wiki] validate email address instructions in German
by DenverD 16 Aug '10

16 Aug '10

while looking at http://en.opensuse.org/openSUSE:Services_help just now i saw a new (to me) link saying to edit i need to verify my email address...(a feat i thought was done years ago when i received my novell/openSUSE ID/password login for the forum..) but i decided to play the new game and am directed to: http://en.opensuse.org/Help:Email_validation which includes instruction to go to https://secure-www.novell.com/selfreg/jsp/protected/validateEmail.jsp where i am assaulted ;-) with German text that will NOT translate to understandable English at google.. </sigh> i don't really enjoy these games.. and, since i guess it might be an iChain thing, i'm not sure if i should report it to an iChain person, the wiki mail list, Henne direct, admin(a)opensuse.org, webmaster(a)opensuse.org, or to the wiki forum.. but, since i don't see this situation described on http://en.opensuse.org/openSUSE:Services_help maybe it should go to Bugzilla as an "Anything else" but, for now i'll hold off on filing a bug.. DenverD cc: Henne cc: webmaster(a)opensuse.org cc: admin(a)opensuse.org -- 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] New language.o.o request
by Matthew Ehle 10 Aug '10

10 Aug '10

>> I agree that we shouldn't have two domains (wiki.o.o and en.o.o) serving >> the same content. Therefore I propose to change wiki.o.o - it should >> just RedirectPermanent to en.o.o/$requested_page. This will also make >> sure that search engines replace wiki.o.o with en.o.o in their results. > >+1 > >Can you add that to the bug report: >https://bugzilla.novell.com/show_bug.cgi?id=629542 I have just set up Apache to redirect wiki.o.o to en.o.o with a 301 status code. >> This also means that you should really create a new subdomain >> (languages.o.o or babel.o.o), even if it is more work ;-) > >+1 It actually really isn't that much work, at least not for me. It's more that I'm very big on the KISS principle, and it's just starting to feel like there are a lot of exceptions creeping in ;-) >languages.o.o is pretty obvious what it is meant and it is already requested >in a bugzilla Fair enough, but remember that Bugzilla requests can always change :P I am kind of partial to babel.o.o myself, but I agree that it is not likely to translate well to other languages or cultures. Too bad, since it seems to be such a good description of what we'll find there! In any case, I'll start the process of getting languages.o.o going tomorrow.

2 1

[opensuse-wiki] missing pages
by Ludwig Nussel 10 Aug '10

10 Aug '10

Hi, I noticed that that following pages are not available in the new wiki. Please migrate them to an appropriate place: http://old-en.opensuse.org/Security http://old-en.opensuse.org/Security_Features http://old-en.opensuse.org/Packaging/Security_Policies http://old-en.opensuse.org/Encrypted_Filesystems http://old-en.opensuse.org/SuSEfirewall2/Service_Definitions_Added_via_Pack… cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] rpmlint docu in wiki
by Ludwig Nussel 10 Aug '10

10 Aug '10

Hi, Is http://en.opensuse.org/openSUSE:Packaging_checks supposed to stay that way? I'm asking because I'd like to have links into the wiki for rpmlint and other build check errors. For example the web ui could link to the wiki when viewing the build log and osc could dump a list of links when viewing the log. Atm a link would look like this: http://en.opensuse.org/openSUSE:Packaging_checks#arch-dependent-file-in-usr… I'm not sure an anchor in the page scales though. It might be better to have one page per error. That also has the advantage that clicking on an error that doesn't exist yet would offer to create the page. All available rpmlint description pages could be listed in an automatically created page like this one: http://en.opensuse.org/Category:Build_Service Opinions? What's needed to make it happen? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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 language.o.o request
by Matthew Ehle 10 Aug '10

10 Aug '10

Hello Everyone, I know there has been some discussion on creating a language.o.o subdomain and using that as a sort of sandbox for multilingual content. Recently, bug 629542 has been submitted for it. Before I do this, may I request that we consider using our current wiki.o.o for this purpose instead of creating languages.o.o? My reasons for this are given in the bug comments, but the short of it is that I want to keep things simple, both from my standpoint and that of the users. Why have two domains serving the same content, while we create an entirely different one for new content? Also, creating a new subdomain takes time, as we need to wait for the DNS entry, iChain configuration, database setup, after which, I will need to muck around with the wiki farm configurations to accommodate a new subdomain that doesn't fit in with the pattern we have been following. Just some food for thought...

3 2

[opensuse-wiki] [[Portal:Wiki]] - News
by pistazienfresser (see profile) 09 Aug '10

09 Aug '10

http://en.opensuse.org/index.php?title=Portal%3AWiki&diff=21663&oldid=20335 http://en.opensuse.org/index.php?title=Portal%3AWiki%2FNews&diff=21659&oldi… I created (recreated???) a news-box to the wiki's own portal and improved (in my opinion) [[Portal:Wiki/News]]. Hope it is to your liking/you are able to change what you like not. Regards pistazienfresser -- - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- 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] Need help with VNC wiki articles
by Tim Mohlmann 09 Aug '10

09 Aug '10

Hello people! I'm sending this to both opensuse and opensuse-wiki list to ask for some help on this. I am moving content from http://en.opensuse.org/SDB:Remote_access_to_openSUSE to http://en.opensuse.org/Portal:Remote_access Putting general information in the latter and creating / updating topic specific articles. I need help from someone who knows about VNC. And I ask for the following: http://en.opensuse.org/VNC Needs to be a general description about (tight?)VNC. http://en.opensuse.org/SDB:VNC_usage Is a copy - paste from the original Remote access article. It is a HOWTO use VNC and needs to be verified and updated. Thanks in advance! Tim http://en.opensuse.org/User:Muhlemmer -- 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] Just a comment on the wiki
by C 09 Aug '10

09 Aug '10

Hey guys.. just wanted to comment on the work on the oS Wiki... it's really shaping up nice. You can see a lot of hard work has gone into bringing it this far... it's got a long ways to go yet :-) As someone who's been on the sidelines a lot just watching... I'm wondering... how can the rest of the community lend a hand with the migration? Moving pages isn't really a task that can be parceled out... or is it? What other tasks are sitting waiting to be done? When was the last "reminder" or status update sent out to the general oS community (was it lost in the general mailing list chaos)? How many out there know about http://en.opensuse.org/Help:Transfer ? An one last question... what about a headline on the openSUSE Weekly? Just trying to think how I and others can contribute... and raise some awareness/help instead of just seeing complaints. C. -- 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] Improvements to templateNavbar
by Rajko M. 09 Aug '10

09 Aug '10

It is compatible with old one, just uses bento like layout: http://en.opensuse.org/Template:Navbar_1 Currently is used for only one page :) http://en.opensuse.org/Special:WhatLinksHere/Template:Navbar_1 If you agree we can replace the old one. -- 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] use of localized wikis
by jdd 09 Aug '10

09 Aug '10

Hello, wiki team :-) As you may know, the localized wikis are no more in par with the english wiki. I plan to create new page (or translate some from the en one), and I would like to know what is the prefered syntax. Until now, it was advised to use the very same name from the english wiki and do a redirect to the localized page. For exemple, if a page "install on usb" was on the en wiki, the french wiki held a page "install on usb" that redirects to "installer sur usb". This allowed the interwiki links to work easier. * till the move these links don't work anymore -lack of "old-" in the link. Could somebody correct this or explain how I can do, at least until the localized wiki have done the move; * How can we do similar things now for new pages? I don't know how to cope with the namespaces, if we don't have them in localized wikis. thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- 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] Boletín 135 de las Noticias Semanales de openSUSE en Español
by Marco ''AlpVonKri'' Flores 08 Aug '10

08 Aug '10

El boletín 135 de las Noticias Semanales de openSUSE en Español está listo para ser traducido. ¡Únete al equipo! +Info http://bit.ly/9uhtmN Saludos. -- Marco "AlpVonKri" Flores Computer Systems Engineer Ing. Sistemas Computacionales http://www.alpvonkri.co.cc alpvonkri(a)alpvonkri.co.cc openSUSE Member ~ Ambassador ~ Weekly News Miembro ~ Embajador ~ Noticias Semanales http://wiki.opensuse.org/User:Alpvonkri alpvonkri(a)opensuse.org -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

1 0

Re: [opensuse-wiki] Fix for Session Data Lost Error
by Matthew Ehle 07 Aug '10

07 Aug '10

>>>> Thomas Schmidt 08/07/10 10:43 AM >>> >On 08/07/2010 05:56 AM, Matthew Ehle wrote: >> Hello Everyone, >> >> I have rolled a fix for Bug 619735 to the production wiki. I have provided details about the problem and solution there, but here's the short of it: >> >> PHP requires session_start() to be called before any session data can be saved. The javascript login only passes login information to iChain and never explicitly calls the MediaWiki login, where the >> session_start() function is called. Thus, when using the javascript login, no session is started, and no session data is saved. Editing a page also calls session_start(), which is why it starts >> working after trying it one time. >> >> I added a session_start() call in the automatic iChain login script, and I have not been able to duplicate the problem on stage since. As this appears to solve the problem, I have moved it out to the >> live wiki. Please test it out and report any issues to me. If I don't hear anything over the weekend, I'll close the bug out on Monday. >> >> In addition to the fix, the latest deployment also contains the code for email validation. It won't do anything until it is provided certain header information by iChain, which should be set up to do >> that on Monday morning. > >Cool, thanks Matthew for finding this nasty bug! No problem! Looks like I was a little hasty in trying to blame this on your login form (I'm assuming that you were involved in its development). It actually works really well, aside from originally sending passwords in plain text ;) Actually, I think a lot of the random login/session problems that have been reported in the forums were because of this long-standing bug. The javascript login only made it more apparent, so it turned out to be quite a good thing!

1 0

[opensuse-wiki] Fix for Session Data Lost Error
by Matthew Ehle 07 Aug '10

07 Aug '10

Hello Everyone, I have rolled a fix for Bug 619735 to the production wiki. I have provided details about the problem and solution there, but here's the short of it: PHP requires session_start() to be called before any session data can be saved. The javascript login only passes login information to iChain and never explicitly calls the MediaWiki login, where the session_start() function is called. Thus, when using the javascript login, no session is started, and no session data is saved. Editing a page also calls session_start(), which is why it starts working after trying it one time. I added a session_start() call in the automatic iChain login script, and I have not been able to duplicate the problem on stage since. As this appears to solve the problem, I have moved it out to the live wiki. Please test it out and report any issues to me. If I don't hear anything over the weekend, I'll close the bug out on Monday. In addition to the fix, the latest deployment also contains the code for email validation. It won't do anything until it is provided certain header information by iChain, which should be set up to do that on Monday morning.

2 1

[opensuse-wiki] Redundant namespaces, in particular openSUSE:
by Brandon Philips 06 Aug '10

06 Aug '10

Hello All and Everyone- Today, I wish to talk about redundancy. In particular things that add no new information and are a simple rearrangement of the understood data. In other words: repetitiveness for no-gain at all. Problem ------- I was trying to point a community member at the Kernel Git page today so they could get involved. But I was baffled to find it gone. Searching a bit I ended up finding it at this URL: http://en.opensuse.org/openSUSE:Kernel_git Two openSUSE's in one URL, what a deal! Without that openSUSE: namespace I might have thought I was going to grab the Ubuntu Kernel Git... As we are breaking URLs all over with this new wiki anyways can we take a moment and consider the URL monsters we are creating here? Just look at it once again: http://en.opensuse.org/openSUSE:Kernel_git There has got to be something better, lets find a solution. :) Solution -------- Lets look at the mission statement of the openSUSE: namespace[1]: "And the openSUSE community's openSUSE: namespace to collaboratively write on documentation for their projects and teams." Possible alternatives: 0. No namespace at all, the openSUSE community exists at openSUSE.org! We have an entire domain to call our own! Why do we need a namespace? 1. devel: ? Oh, but these teams are not necessarily developers 2. teams: ? Erm, no because then it would be teams:Kernel_git which makes no sense 3. community: ? Maybe, but community:Java packaging cookbook looks strange 4. project: ? This is my second choice as nearly all of the links on http://en.opensuse.org/Portal:Project are to the openSUSE: namespace... 1-4 have their problems but at least they are not redundant. Lets discuss what problem this openSUSE: namespace is trying to solve and how we can make sane looking URLs on our new wiki. And lets do it fast so we can avoid breaking URLs again. Cheers, Brandon [1] http://en.opensuse.org/Portal:Wiki/Concept -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

7 32

[opensuse-wiki] "Terms of site" for other languages
by pistazienfresser (see profile) 05 Aug '10

05 Aug '10

http://wiki.opensuse.org/index.php?title=Help:Translation&curid=4820&diff=2… " + |[[Terms of site]] + |Please add the following header translated into your language: <nowiki>{{Info|This is an translation of the [[en:Terms_of_site|openSUSE Terms of site]] into '''LANGUAGE'''. It does not legally state terms for these pages—only the original English text of the Terms of site do that. However, we hope that this translation will help language speakers understand the Terms of site better.}}</nowiki>" As legal terms are not congruent in other languages and nether are the legal systems based on that languages - this is not a task for a person without an education in legal issues. And I doubt that such a person (if not very stupid and so not the best choice to do it at all) will do that without the security of a paid insurance and/or something that assures he/or she is free of liability according to the legal system he/she (and probably also the users and contributors of the wiki in that language) lives in. And maybe someone professional should also examine which terms of that standard form contract would be binding in the legal systems the contributors and the users would probably live in. Regards pistazienfresser -- - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

3 3

Re: [opensuse-wiki] A Couple of Wiki Items
by Matthew Ehle 05 Aug '10

05 Aug '10

>>> "Rajko M." 08/04/10 9:56 PM >>> >On Wednesday 04 August 2010 14:53:24 Matthew Ehle wrote: >> Another alternative is to simply redirect users straight to the email >> validation page. What does everyone think? >That should be the best case. The only problem I would have with that is that there is no explanation given as to why all of a sudden users are being sent to validate their email. I know, the page is pretty self-explanatory, but you know what happens when you assume anything out of the end user ;) >The only problem can be with the forums.o.o users. >Do they validate email when subscribe to forums, or they use some equally >efficient method to prevent creation of fake accounts? Not currently, but soon. I am actually working with the forum admin, and he has a very similar bug open on the openSUSE forums. We are test driving the email validation solution on the wiki, and assuming it works, we will be doing the same thing on the forums.

1 0

Re: [opensuse-wiki] accreditation
by Matthew Ehle 05 Aug '10

05 Aug '10

>>> Henne Vogelsang 08/05/10 4:28 AM >>> >Hey, >On 05.08.2010 11:22, Matthew Ehle wrote: >>>>> C 08/05/10 12:00 AM >>> >> On Thu, Aug 5, 2010 at 06:05, Rajko M. wrote: >>> On Wednesday 04 August 2010 20:21:17 Brian K. White wrote: >>> >>>> I just noticed, perhaps this is petty, but I don't think it's right that >>>> I spent a lot of time writing /LXC (and the init scripts and .spec / rpm >>>> packaging to go with it) and then through no action of my own it loses >>>> all trace of me. >>> >>> The xml file is 3.3 MB, and wiki allows import up to 2 MB. >>> So importing only the last revision was the only way that I know to >> transfer >>> LXC. >>> >>> Maybe Matthew can increase that limit? >> >> I think there's a problem with your XML file if it's that big. An XML >> dump of the entire wiki comes out to about 11 MB, and as detailed as >> that article is, I don't see it being 1/3 of the wiki : ) >> >> I exported the LXC article just now, and it came out to about 25 Kb. > >You did not export the complete history (all revisions) :) *facepalm* That's why I shouldn't send email at 3 A.M. ;) >>>It's a fairly simple tweak to up the Wiki upload limit.... and for >>>what it's worth, I'm 100% behind Brian on this one. One of the key >>>factors in opensource contributions and virtually every single OS >>>license... be it CC, GPL etc. all require accreditation for the >>>contributors (it's not optional).... baffles me why people think it's >>>ok to simply lose all the edit history on the Wiki. :-( That's very >>>much against one of the core requirements and principles of open >>>source contributions. >> >> Yep, it's just a couple entries in the php.ini file. If you guys really >> want, I can up that limit a bit with no problem. >Please up it to 4MB Done.

1 0

[opensuse-wiki] accreditation
by Brian K. White 05 Aug '10

05 Aug '10

I just noticed, perhaps this is petty, but I don't think it's right that I spent a lot of time writing /LXC (and the init scripts and .spec / rpm packaging to go with it) and then through no action of my own it loses all trace of me. It's almost time to do it all again for a new version of lxc which is significantly different from the currently documented 0.6.5 so it's almost the same research and testing and optimization all over again, and this latest discovery just adds to the already existing disinclination to invest in this wiki. In my "copious free time" I guess I'll look in to what it takes to transfer an article with it's history & metadata from the old wiki.. No I don't want my name plastered in the article itself or anything gross like that in overreaction. It's not like that. The normal built in edit history was perfectly acceptable. Exactly the right level of visibility. But, since that's all there was in the way of accreditation for work, it's pretty bad to erase it I think. It makes me rethink the choice not to just write up internal company docs which would be a lot more convenient, would not move, could be filled with internal company-specific stuff, and which would be more useful for me and useless to anyone else. I hear you guys about how bad the old wiki was and how much more sane the new one should eventually be, so I'm no longer disregarding the work and eventual benefit, but I am requesting that you at least pretend to be a little more understanding of just how much and how bad fallout this move caused, or rather how this move was performed. Even if we _are_ just a bunch of whiners and complainers, instead of people with legitimate grievances, does it make a difference? Do you or do you not want contributors? Do you suppose the people who do not care about such things as broken links and lost accreditation are the more quality contributors and the ones who do care about these things and so avoid this wiki are the crappy ones you don't want anyways? -- bkw -- 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] Fwd: [opensuse-project] A proposition regarding wiki.opensuse.org
by pistazienfresser (see profile) 05 Aug '10

05 Aug '10

F.Y.I. -------- Original Message -------- Subject: [opensuse-project] A proposition regarding wiki.opensuse.org Date: Thu, 5 Aug 2010 12:04:54 +0000 From: Ann Price <ann.price(a)topspot-promotions.net> To: <opensuse-project(a)opensuse.org> Hello, Topspot-Promotions, an established advertising company, would like to pay you for placing a small advertisement on wiki.opensuse.org for one of our clients. These days we are using a few methods of advertising to guarantee that the ad we choose will fit the site nicely. After reviewing your website I thought about an advertisement that fits perfectly a few pages on your website. For full details please contact me at ann.price(a)topspot-promotions.net. *If you have other websites which I can review for advertising please send me their URLs as well. Kind Regards, Ann Price Advertising Specialist ann.price(a)topspot-promotions.net To permanently delete yourself from our list, simply reply to this with a blank email and you will never receive any communication from us in the future. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

2 2

Re: [opensuse-wiki] accreditation
by Matthew Ehle 05 Aug '10

05 Aug '10

>>> C 08/05/10 12:00 AM >>> On Thu, Aug 5, 2010 at 06:05, Rajko M. wrote: > On Wednesday 04 August 2010 20:21:17 Brian K. White wrote: > >> I just noticed, perhaps this is petty, but I don't think it's right that >> I spent a lot of time writing /LXC (and the init scripts and .spec / rpm >> packaging to go with it) and then through no action of my own it loses >> all trace of me. > > The xml file is 3.3 MB, and wiki allows import up to 2 MB. > So importing only the last revision was the only way that I know to transfer > LXC. > > Maybe Matthew can increase that limit? I think there's a problem with your XML file if it's that big. An XML dump of the entire wiki comes out to about 11 MB, and as detailed as that article is, I don't see it being 1/3 of the wiki : ) I exported the LXC article just now, and it came out to about 25 Kb. >It's a fairly simple tweak to up the Wiki upload limit.... and for >what it's worth, I'm 100% behind Brian on this one. One of the key >factors in opensource contributions and virtually every single OS >license... be it CC, GPL etc. all require accreditation for the >contributors (it's not optional).... baffles me why people think it's >ok to simply lose all the edit history on the Wiki. :-( That's very >much against one of the core requirements and principles of open >source contributions. Yep, it's just a couple entries in the php.ini file. If you guys really want, I can up that limit a bit with no problem. However, there really should be no reason to do it. As I mentioned above, you would have to be pretty much importing an entire namespace to get above that 2 MB limit. I am also with Brian on this. Do we have any other articles that are in a similar situation? I suggest that we find them and either try to import their history or make a mention of the original contributor(s) in the article itself. The latter is easier and it seems like a nice gesture, but I'm not too sure how to fit it in without breaking the flow of the article itself. Maybe in the info boxes?

2 1

[opensuse-wiki] A Couple of Wiki Items
by Matthew Ehle 05 Aug '10

05 Aug '10

Here are a couple of items that I wanted to update you on from my perspective: Spam- After some research, I found that there is an entitlement give to users who validate their email address at https://secure-www.novell.com/selfreg/jsp/protected/validateEmail.jsp. This is the same entitlement required for Bugzilla users. I am working with our iChain admin to get entitlement information passed to the wiki, and then having our login script check for that entitlement. If the user has the entitlement, then the login will continue as usual. If the user does not have the entitlement, the wiki will stop the login and redirect the user to some other page. Since there are probably a number of legitimate users who have not validated their email address, I thought it would be nice if they were taken to a page explaining the new policy and containing a link to the validate email page listed above. I have asked Thomas Schmidt to design such a page to be put somewhere on www.opensuse.org to accomplish this. However, now that I think about it, a better alternative might be to create a wiki page with the explanation and then redirect users there. Another alternative is to simply redirect users straight to the email validation page. What does everyone think? If we were to create a page on the wiki, what would be the best namespace for it? By the way, the bug information can be found at https://bugzilla.novell.com/show_bug.cgi?id=627446 Search- In addition to http://en.opensuse.org/MediaWiki:GoogleSearch, I have been experimenting with Lucene search, and I have installed it on http://enstage.opensuse.org as a replacement for the default search. So far, it looks really good. Pretty soon, we should be able to have the staging server upgraded, after which I will install the newest version of the Lucene MW search. This version will have much better features. Stay tuned on https://bugzilla.novell.com/show_bug.cgi?id=625677 for updates. That's about it for now. Let me know if there is anything else! -Matt

3 2

[opensuse-wiki] A Wiki Q&A?
by Bryen M. Yunashko 04 Aug '10

04 Aug '10

Is there any possibility of considering holding a Q&A session in the -Project channel to do a live quick how-to of *WHERE* to create pages on the new wiki? I am still quite confused by the way pages are created now that we no longer have a new structure. And others are too. Maybe a nice 1/2 hour session sometime within the next week would be helpful as its a barrier right now for me to do my work and know where things belong properly. I think if even just a few people show up for your wondrous lesson, that would be empowering because it will allow those of us who go to then be able to spread the word to others who have questions. Thanks! Bryen -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

6 10

[opensuse-wiki] Page Nonefound
by Rajko M. 04 Aug '10

04 Aug '10

Does InputBox work in MediaWiki namespace? It seems yes, but I didn't want to change current page before I hear opinions. -- 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] Noarticletext page can be improved
by Rajko M. 04 Aug '10

04 Aug '10

Compare: http://wiki.opensuse.org/MediaWiki:Noarticletext http://en.wikipedia.org/wiki/MediaWiki:Noarticletext Opinions? -- 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] Blocking users
by Rajko M. 03 Aug '10

03 Aug '10

Do we have solved issue with blocking IP when user name is blocked? -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

5 4

Re: [opensuse-wiki] Download help on the download page
by Thomas Schmidt 03 Aug '10

03 Aug '10

On 15.07.2010 12:21, Marcus Rueckert wrote: > On 2010-07-15 12:12:56 +0200, Thomas Schmidt wrote: >> On 14.07.2010 23:25, pistazienfresser wrote: >>> On 14/07/10 22:20, Atri Bhattacharya wrote: >>>> On Thu, 2010-07-15 at 01:38 +0530, Atri Bhattacharya wrote: >>>>> Hi! >>>>> In the main page >>>>> http://software.opensuse.org/112/en >>>>> none of the links work, they have to be modified to point to the correct >>>>> location. >>>>> >>>> >>>> To follow up, there is a link to >>>> http://en.opensuse.org/BitTorrent_and_openSUSE >>>> in the write-up which appears when you click on the little blue "?" just >>>> beside the string "Download Method" for every type of download media, >>>> i.e. for the 4.7GB DVD, Live images and others. This too points to an >>>> empty page, and I have no idea where this should point to either, bcoz >>>> there seems to be no page close to this. >>>> >>>> >>> Hello Atri, hello list, hello "admin", >>> as there was a very little link with "Feedback" and admin(a)opensuse.org >>> behind it on that page "http://software.opensuse.org/112/en" I added >>> this address to the TO section above. >>> >>> And as "software" is none of the 34 namespaces I see on >>> http://wiki.opensuse.org/Special:Search the administrators of the wiki >>> may not the only ones with the ability to fix it. >>> >>> But I think temporally that could be fixed also in the wiki if someone >>> knows where the meant articles are now and creates or recreates a >>> redirect to the meant page/article on the page the link on >>> "http://software.opensuse.org/112/en" or tomorrow >>> "http://software.opensuse.org/113/en" etc. points to... >> >> I removed the link to bittorrent, as the article is not yet transferred and marked as incomplete >> (http://old-en.opensuse.org/BitTorrent_and_openSUSE). >> The other link is fixed: http://en.opensuse.org/SDB:Metalink >> >> Changing strings short before the release has the downside we will have those strings >> in english only for all users until the translations catched up. > > uhm ... we want to push bittorrent usage for this release. > could you please work on migrating this? Ok, I copied it to SDB:BitTorrent_and_openSUSE. Can someone with bittorrent expertise help reviewing this article? 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

9 21

[opensuse-wiki] Bento Login Form Problems
by Matthew Ehle 03 Aug '10

03 Aug '10

Hello, There are two major problems with the bento theme login which will need to be fixed. Until they are, I am recommending that everyone avoid using the javascript login form and instead use the standard login page that is used by the legacy wiki. Issue 1: The login form sends information in plain text over plain HTTP. I have actually fixed this on stage, but perhaps others would like to review it to make sure that passwords aren't being sent in clear text anymore. Assuming that is the case, it can go live when I run the next update. So please try this out in stage (if you are able) and get back to me. If one of you have WireShark installed, that would be perfect. Issue 2: As far as I can tell, this login form is the reason behind Bug 619735. After a lot of testing and troubleshooting in stage, this is the most likely culprit so far. Basically, I can duplicate the problem easily when using the bento login form, but I cannot duplicate at all using the standard login page. It looks like the cookie is not set properly when using this login, although I can't see any apparent reason why that is. Strangely enough, submitting an edit does set the cookie, which is why only the first edit fails. Please test out the fix for the first issue, and see what might be causing the second. Until then, the best workaround is to use the standard login form. Thanks! Matt

3 4

[opensuse-wiki] Main page protected now
by Henne Vogelsang 02 Aug '10

02 Aug '10

Hey, only spammers edited the main page for a long time now. As the bot's seem to have no clue about Flaggedrevs i have protected the page for now. 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 11

[opensuse-wiki] where is the knowledge gone
by Sven Burmeister 02 Aug '10

02 Aug '10

Hello! The web and the KDE Portal refers to http://en.opensuse.org/KDE/Developing/Guide for developing KDE on openSUSE, i.e. tries to attract developers to use openSUSE. Those links now point into emptiness. How come they were not transfered and the work that went into them thus disregarded? Sven -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org

7 11