On 04.04.2011 21:20, Brian K. White wrote:
On 3/22/2011 4:14 PM, Brian K. White wrote:
On 3/22/2011 7:53 AM, Henne Vogelsang wrote:
Hey,
On 03/22/2011 12:46 PM, Jiri Slaby wrote:
could you remove robots.txt from old-en.opensuse.org?
There are valuable data in the wiki and as the wiki wasn't ported to the new one in a reasonable time, it should definitely be indexed by search engines.
Otherwise people repeatedly fail to find the info and we have to point them to that manually.
How about you tell us what you are missing instead? :)
Henne
That approach has already failed too badly.
The brokenness is the rule not the exception.
Sure go ahead and fix one more broken link. It's better than leaving it broken. But who cares any more?
Exhibit #26341
I want to get the jbig-kit library package added to Factory. I have created a package that adheres to all general and SUSE guidelines as well as I can understand them and builds and packages cleanly on all current suse versions, and have gotten it added to the graphics repo with myself as the maintainer of it.
So far so good but now comes the part that I know might involve people whos time I do not want to waste. Rather than just emailing people more or less at random and making them tell me what to do and wasting a bunch of peoples time before I piece together the procedure, I want to read whatever docs are available first.
Ok I start at the build service home page. It has a link to a wiki page about the build service... http://en.opensuse.org//openSUSE:Build_Service
Which mostly talks about the build service itself, not what I'm looking for, but does include a link named "Packagers" which sounds promising...
http://en.opensuse.org/Portal:Packaging
Which looks like the beginning of exactly what I want, and links to
http://lizards.opensuse.org/2010/03/23/how-to-add-new-packages-to-the-opensu...
Which says to send an email using this link...
http://en.opensuse.org/Factory/Packaging#Adding_a_package_to_Factory
Which no longer exists.
Of course I can find other avenues to the info I need. That is why you will hardly get a teeny tiny fraction of the reports of the breakage and why you can't say "just report what's broken!", nor say "no reports == no problem!". It took far longer to write this email than it took to look around and find out what I needed by other means. Even if I had merely clicked the "report problem" link provided in the 404 page, and merely pasted the broken link and left out all the ranting, that's still more than most people are going to bother with.
The point is the wiki failed to deliver.
Worse than that, it started off looking like it was going to deliver and then broke in the middle.
Worse than that, the evidence is plain to the user that an article once existed, but the curators of this content allowed purely internal links wholly under their own control, in reference material, in _current_ reference material, to break. That not only fails to deliver the info, it advertises that the info store is unreliable. It means regardless what you find or fail to find, you can't really trust it. You can't know that what you do find is current or correct, and you can't know that what you don't find doesn't exist.
I think the reference material should exist in the wiki, not in blogs, so I will move this article to the wiki. Are there more blog articles that can be considered as reference? By the way, the blog article now links the correct page. Greetings
How is it possible that people have to explain why broken links are bad? I really don't understand the "cry me a river" remark. It boggles the mind.
-- 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@opensuse.org For additional commands, e-mail: opensuse-wiki+help@opensuse.org