Apache OpenOffice (AOO) Bugzilla – Issue 1323
Customized issue writing guidelines are not migrated
Last modified: 2003-12-06 14:52:32 UTC
Customized issue writing guidelines are not migrated. The standard bugzilla/issuezilla guidelines are linked on the "Enter Issue" page. The sc-OOo URL for the guidelines is http://inst/issues/bugwritinghelp.html For t-OOo the URL is http://www.openoffice.org/bugs/bug_writing_guidelines.html There was also a customized text about StarOffice with link to Sun Support.
This looks to have been resolved with final migration.
No, the original content for Bugzilla from Eli Goldberg is shown, not the customized content.
I'll look into this. louis if the document in question is the one from tigrisc, I can just do a carefully trimmed transplant. louis
Assigning to Louis.
done. I used the old tigris c document from issues_docs and improved it a little, also adding information about logging in, registering, etc. let me know if more needs to be done. louis
Looks like you took the wrong document as a basis. We had a customized version talking about Spreadsheet instead of a browser. Please use the version from t-OOo not the general Tigris one. You'll see that there is no line asking to send feedback to Eli Goldberg and that there is an mailto: URL at the bottom pointing to Michael.Bemmer.
St: I am confused here, for the one I worked on and posted *was* from the old tigris Ooo version, and *has* Michael Bemmer's mailto at the end. The URL where I posted it to is: http://www.openoffice.org/bugs/bug_writing_guidelines.html. The one I posted, too, has discussion of a "spreadsheet": "Bad: "My spreadsheet crashed when I tried to open a document. I think it contained a chart. My computer uses Windows. I think that this is a really bad problem and you should fix it now. By the way, your icons really suck. Nobody will use your software if you keep those ugly icons. Oh, and my grandmother's has a problem with the word processor. Nothing works right, either. Good luck." " Hope this clears things up. Leaving reopened for you to close. Louis Good: "I crashed each time when I opened the attached spreadsheet document using the 10.13.00 build on a Win NT 4.0 (Service Pack 5) system. I also rebooted into Linux (RedHat 6.2), and reproduced this problem using the 10.13.00 Linux build.
Seems you're commiting to the wrong place. The URL in the Submit Form on sc-OOo is http://www.openoffice.org/issues/bugwritinghelp.html Just try to enter a new issue, choose a component and then look at the link "Enter Issue This page.... See ->Issue writing guidelines<- for help." Follow the link and you'll see....
ah, I see. this is bugwritinghelp (which is specified below): but that is different from the bug_writing_guidelines.html, btw. For what it is worth, I think it is endlessly confusing and madness incarnate to have multiple identitical (or worse, subtly different) documents here and there, referenced from unknown locales. I vote to make these all the same document and link to the same document. For now, will fix. -louis
May be Michael would like to share his opinion about the different documents with us; he is (was) master of documents talking about issue writing guidelines.
Stefan, I can change the document, but I am curious: where does one come across the link that takes one to /issues/bugwritinghelp.html? More generally, I do not have access to /issues/, because it is a directory they think I might break--:(. I can ask people to change things, but I cannot change things on my own. Solution: To rewrite the links in the IZ pages so that they point to static documents * outside* of /issues/, allowing me (and anyone else with my permissions) to change them. I think this is a feasible solution. This would allow us to streamline the documents, and stamp out bogus cloning. Meanwhile, I'll ask for the other page to be replaced by /bug_writing_guidelines.html -louis
You are still lokking for the link to http://www.openoffice.org/issues/bugwritinghelp.html? As said: Just try to enter a new issue, choose a component and then look at the first text line below the bar and above the form "Enter Issue This page.... See ->Issue writing guidelines<- for help." Follow the link and you'll see.... I'm fine with the rewriting, which gives you (and possibly) Michael Bemmer) the ability to change the content. I can't remember whether the 2 files at different locations on t-OOo had different content.
Stefan, I created an issue to resolve this issue immediately; the longer term resolution (moving the static html files out of /issues/) will come next. louis
am closing this; it's now a collabnet issue.
From my point of view "it's an collabnet issue" is no reason to close the issue. It's not solved and at least the short term solution (getting the document to the correct place) should be solved. May be mentioning the pcn issue # and reassinging to kat is a way to track this.
okay. I guess from *my* point of view I still get iz mail... I'll just keep this alive, but then we shoul d downgrade it by the way, I am surprised that the above document has not been fixed. I will up the issue number if it has not been fixed by tomorrow. I meant to close it because th e l arger issue---moving the html files to a place I can fiddle with them--was not directly related to fixing the file above, which I assigned to one of our workers to do. louis louis
I just reminded the engineer in charge of the collabnet analogue of this issue, 5357, that it needs to be cleared. louis
This simple fix has taken on strange proportions. I have reminded the engineers of the files in question; also of the more permanent solution (to move all html files having to do with /issues/ out of that directory). louis
Once again reminded the engineers of the pressing nature of the issue (and of its seeming simplicity). It is issue 5357. -louis
changing QA contact from bugs@ to issues@
this has finally been done. yippee. louis
.