[yast-devel] Tiny URL for "People were very unhappy because I only wrote..."
Hi, I've just created a new Tiny URL for http://en.opensuse.org/Bug_Reporting_FAQ#
People were very unhappy because I only wrote "see subject" in the Bugzilla bug description - but my subject really explains it all! Isn't it pure nitpicking to insist on bug reporters repeating that in the description field?
It is http://tinyurl.com/24zvkc I wish if it only was something easier to remember! :) And why did I do that? Well, I don't think that the long URL makes anybody happy :) and we use it quite often in bugzilla :) ;) Have a nice day L. -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
On Wed, Mar 05, 2008 at 04:55:09PM +0100, Lukas Ocilka wrote:
Hi,
I've just created a new Tiny URL for http://en.opensuse.org/Bug_Reporting_FAQ#
People were very unhappy because I only wrote "see subject" in the Bugzilla bug description - but my subject really explains it all! Isn't it pure nitpicking to insist on bug reporters repeating that in the description field?
It is http://tinyurl.com/24zvkc I wish if it only was something easier to remember! :)
Use decenturl.com :) ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Guten Abend, Am Mittwoch, 5. März 2008 16:55:09 schrieb Lukas Ocilka:
I've just created a new Tiny URL for http://en.opensuse.org/Bug_Reporting_FAQ#
People were very unhappy because I only wrote "see subject" in the
Bugzilla bug description - but my subject really explains it all! Isn't it pure nitpicking to insist on bug reporters repeating that in the description field?
It is http://tinyurl.com/24zvkc I wish if it only was something easier to remember! :)
And why did I do that? Well, I don't think that the long URL makes anybody happy :) and we use it quite often in bugzilla :) ;)
And thats the wrong approach! Most of the people do not like to "click" on a URL which does not tell what is behind it. Even if you say that this is "http://en.opensuse.org/Bug_Reporting_FAQ#" they will refuse to use it if you give them the tinyurl address. In my opinion it would be the best way to give the full address to "inexperienced" users. Greetings, Marco -- Marco Michna -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Marco Michna napsal(a):
Guten Abend,
Am Mittwoch, 5. März 2008 16:55:09 schrieb Lukas Ocilka:
I've just created a new Tiny URL for http://en.opensuse.org/Bug_Reporting_FAQ#
People were very unhappy because I only wrote "see subject" in the Bugzilla bug description - but my subject really explains it all! Isn't it pure nitpicking to insist on bug reporters repeating that in the description field?
It is http://tinyurl.com/24zvkc I wish if it only was something easier to remember! :)
And why did I do that? Well, I don't think that the long URL makes anybody happy :) and we use it quite often in bugzilla :) ;)
And thats the wrong approach!
It's no worse than this: http://en.opensuse.org/Bug_Reporting_FAQ#People_were_very_unhappy_because_I_...
Most of the people do not like to "click" on a URL which does not tell what is behind it. Even if you say that this is "http://en.opensuse.org/Bug_Reporting_FAQ#" they will refuse to use it if you give them the tinyurl address.
Yes, we should fix wiki to provide some more useful link. Possible?
In my opinion it would be the best way to give the full address to "inexperienced" users.
The full URL makes people angry and if you get bugzilla mail with it, it might be cut on (each) 80 characters. That is not useful for inexperienced users. L.
On Thursday 06 March 2008 10:09, Lukas Ocilka wrote:
Yes, we should fix wiki to provide some more useful link.
I would appreciate that very much. Those links really are too long.
Possible?
I have serious doubts. I don't think we want to develop yet another Wiki
software...
CU
--
Stefan Hundhammer
Stefan Hundhammer napsal(a):
On Thursday 06 March 2008 10:09, Lukas Ocilka wrote:
Yes, we should fix wiki to provide some more useful link.
I would appreciate that very much. Those links really are too long.
Possible?
I have serious doubts. I don't think we want to develop yet another Wiki software...
Well, HTML has a special named anchor. http://www.w3schools.com/html/html_links.asp --- cut --- <a name="tips">Useful Tips Section</a> You should notice that a named anchor is not displayed in a special way. To link directly to the "tips" section, add a # sign and the name of the anchor to the end of a URL, like this: <a href="http://www.w3schools.com/html_links.asp#tips"> Jump to the Useful Tips Section</a> --- cut --- Maybe this way? Any wiki specialist? L.
On Thursday 06 March 2008 05:50:18 am Lukas Ocilka wrote:
Stefan Hundhammer napsal(a):
On Thursday 06 March 2008 10:09, Lukas Ocilka wrote:
Yes, we should fix wiki to provide some more useful link.
I would appreciate that very much. Those links really are too long.
Possible?
I have serious doubts. I don't think we want to develop yet another Wiki software...
Well, HTML has a special named anchor.
http://www.w3schools.com/html/html_links.asp --- cut --- <a name="tips">Useful Tips Section</a> You should notice that a named anchor is not displayed in a special way.
To link directly to the "tips" section, add a # sign and the name of the anchor to the end of a URL, like this: <a href="http://www.w3schools.com/html_links.asp#tips"> Jump to the Useful Tips Section</a> --- cut ---
Maybe this way? Any wiki specialist?
L.
[http://very-long-url#section Some name here] Shows up in text as link 'Some name here' with mark that is external link. First blank after URL is for Mediawiki software sign that URL is done and the rest to the ']' is the name that should appear in a text. That is equivalent of http://"very-long-url#section">Some name here</a> that will be seen as link 'Some name here', though without any mark. BTW, while many HTML tags can be used on wiki page, the above doesn't work. The Mediawiki will write all to page text, make all between quote marks hyperlink, so very long URL will look even uglier. I fixed yesterday one such link. -- Regards, Rajko. See http://en.opensuse.org/Portal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Friday 07 March 2008 01:43, Rajko M. wrote:
[http://very-long-url#section Some name here] Shows up in text as link 'Some name here' with mark that is external link. First blank after URL is for Mediawiki software sign that URL is done and the rest to the ']' is the name that should appear in a text.
Well, yes, but the problem we have is that we often refer to the bug reporting
FAQ in Bugzilla. That's where we have that long link. AFAICS the Wiki names
the anchors according to the section heading, and since those section
headings are the questions, the anchor will be the full question (with
special characters escaped).
Not using the question as the section heading would OTOH make the TOC pretty
useless - we'd have to use something very short which would not be very
descriptive for the respective question.
CU
--
Stefan Hundhammer
On Friday 07 March 2008 04:25:03 am Stefan Hundhammer wrote:
On Friday 07 March 2008 01:43, Rajko M. wrote:
[http://very-long-url#section Some name here] Shows up in text as link 'Some name here' with mark that is external link. First blank after URL is for Mediawiki software sign that URL is done and the rest to the ']' is the name that should appear in a text.
Well, yes, but the problem we have is that we often refer to the bug reporting FAQ in Bugzilla. That's where we have that long link. AFAICS the Wiki names the anchors according to the section heading, and since those section headings are the questions, the anchor will be the full question (with special characters escaped).
Not using the question as the section heading would OTOH make the TOC pretty useless - we'd have to use something very short which would not be very descriptive for the respective question.
CU
Not tested much on openSUSE wiki: http://en.wikipedia.org/wiki/Help:Section#Section_linking I tested in the Sandbox: <span id="123"> = pre test = </span> which works as the link from another wiki page: [[sandbox#123]] or [[sandbox#123|bugfaq 1]] The only problem with complete link with section included is that any change to section title will break the link. Link that points to non existant part after # will bring up the top of article. Which means that no edit to section titles is allowed, even correction of grammar or spelling errors. More flexible method of linking is using IDs, but then if one want to rearange IDs because some sections where inserted it will mess previosly created links. Probably the most flexible way to refere to question is this: http://en.opensuse.org/Bug_Reporting_FAQ see "Why is bug description "see subject" bad idea?" This way if question is changed than it is easy to copy and paste new I looked at the page and it seems that is possible to shorten section titles. Some examples: -------------------------------------------------------------------------- 1.1.5 People got mad at me because I entered "Install SUSE x.y-Beta-z" in Bugzilla's "how to reproduce" field. Why? 1.1.5 Why is "Install openSUSE <version>" usless in "how to reproduce" field? 1.1.5 Why "Install openSUSE <version>" doesn't help as "how to reproduce"? -------------------------------------------------------------------------- 1.1.6 People were very unhappy because I only wrote "see subject" in the Bugzilla bug description - but my subject really explains it all! Isn't it pure nitpicking to insist on bug reporters repeating that in the description field? 1.1.6 Why is bug description "see subject" bad idea? -------------------------------------------------------------------------- 1.2.2 Don't I become the bug owner when I change a bug's status away from NEEDINFO to ASSIGNED (with Accept bug (change status to ASSIGNED) in the Bugzilla bug details page)? 1.2.2 Am I bug owner if I use "Accept bug"? This is not clear anyway. "Accept bug" should change status and owner, or it doesn't work as the expression "Accept bug" suggests. -------------------------------------------------------------------------- 1.2.3 Why is it important that I set a bug status away from NEEDINFO to ASSIGNED? Isn't that the bug owner's responsibility? 1.2.3 Why is important to change a bug status to ASSIGNED after providing information? -------------------------------------------------------------------------- 1.3.1 Should I mark a bug as VERIFIED or CLOSE it when I see that the problem is solved in a new version or with the updates? 1.3.1 What to do if problem is solved in a new program version or after update? [TBD] :-) So, what is going to be delivered? -------------------------------------------------------------------------- etc. -- Regards, Rajko. See http://en.opensuse.org/Portal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (5)
-
Arvin Schnell -
Lukas Ocilka -
Marco Michna -
Rajko M. -
Stefan Hundhammer