www.xfce.org/projects/ points for Xfburn to the page www.xfce.org/projects/xfburn/ and this one contains the following *invalid* links: http://svn.xfce.org/index.cgi/xfce/browse/xfburn/trunk http://svn.xfce.org/svn/xfce-goodies/xfburn/ The correct links are: http://svn.xfce.org/index.cgi/xfce-goodies/browse/xfburn/trunk http://svn.xfce.org/svn/goodies/xfburn/ The absence of the correct links *might* have been one of the causes for which Xfburn is *missing* from the repositories of: Debian, Fedora (the XFCE spin is using Brasero, and http://sundaram.fedorapeople.org/spins/livecd-fedora-8-xfce.ks contains the question "# where is xfburn?" before including brasero), CentOS Extras (who provides XFCE for CentOS), Slackware (rlworkman.net, slacky.eu, slackbuilds.org, slackbuilds.net, linuxpackages.net, develia.org), and from the XFCE-based distros: Wolvix, Vector, Zenwalk, GoblinX. Note that Ubuntu's repos contain Xfburn, but Xubuntu is using GnomeBaker instead. Please note that http://changelogs.ubuntu.com/changelogs/pool/universe/x/xfburn/xfburn_0.2.0-0ubuntu4/xfburn.copyright contains a note stating that they have downloaded the upstream tarball (back in 2006) from the author's site, http://foo-projects.org/~pollux/xfce-snapshots/, but right now there is no such project out there! The correct URLs should be fixed, or else nobody will use Xfburn anymore! (And it works great for me.)
Please refrain from making assumptions as to why someone else might not have xfburn in their repo, or at least don't call names. I have my reasons, and it has nothing to do with inability to actually search for something if a link is broken.
Robby, please refrain from assuming that mentioning a repository in a certain context is against its author. Given that you're a famous Slackware guy, I assume you're smart enough to understand that I have listed all the popular Slackware repositories *only* to prove that there is *no* Xfburn binary package from *no* Slackware repository. I have also phrased it "The absence of the correct links *might* have been one of the causes for which" etc., and I have listed several distros. The "relative invisibility" of Xfburn *might* suggest that the project is neglected, discontinued, not even valued by people at XFCE, etc. Have anyone ever wondered *why* is Xfburn practically unused in the real world? Instead of assuming that I have pointed to you specifically (again, "the absence ... *might* ... *one* of the causes", and I listed several distros, and your repo was specified only in a list of ALL the Slack repos widely known), you could rather cool down and abandon the aggresive attitude. Or tell me (as I have had a quarrel on GNOME's bugzilla recently): what's wrong with you, people? Should everyone who is reporting a bug expect a kick in his ass? Thank you then. I didn't know that open source developers are so self-sufficient that they don't tolerate human interaction that is not specifically praising them.
We recently migrated to a new SVN web viewer, so all the links pointing to it need to be updated -- this isn't done yet, obviously. The reason xfburn isn't used in the 'real world' is because it's incomplete, unmaintained (until the last couple weeks), and has no actual releases. beranger5ca@yahoo.ca: There's no reason to be defensive or call names. We appreciate feedback, but try to be a bit more gentle in your criticisms. We all do this in our -- VERY limited -- spare time, and it's very unmotivating when people approach us as you have done (and your blog posts aren't particularly friendly, either, btw). To be blunt: don't be a dick to us, and we won't be a dick to you. Now, since I've wasted a bunch of time replying to your bug posts, I don't really have time to actually look into the broken URLs, so I'll have to do that later.
> "We appreciate feedback, but try to be a bit > more gentle in your criticisms." My original text that opened this bug report was correct and "gentle enough" by the standards of many other projects where I reported bugs in the past (Fedora, CentOS, Ubuntu, Parsix, StartCom AS, Wolvix, etc). Some people from GNOME and from Zenwalk could not handle correctly bug reports without reacting the same way I see it's the norm on XFCE. Now I know why I WILL NEVER REPORT ANY BUG TO XFCE ANYMORE. My blog is has nothing to do with that.
(In reply to comment #4) > Now I know why I WILL NEVER REPORT ANY BUG TO > XFCE ANYMORE. Hooray! I won't have to worry about my blood pressure anymore. > My blog is has nothing to do with that. Sure it does. How you represent yourself on your blog -- or anywhere else, really -- is an important measure of your character and how people should expect to have to deal with you.
> "Sure it does. How you represent yourself on your blog -- > or anywhere else, really -- is an important measure of your > character and how people should expect to have to deal with you." There is a serious lack of judgment in this phrase. When someone reports that a light is red instead of being green, facts are (or good odds are) that a light is red instead of being green -- and this has nothing to do with the reporter being Bush, Putin, Jack the Ripper or Hu Jintao.
(In reply to comment #6) > > "Sure it does. How you represent yourself on your blog -- > > or anywhere else, really -- is an important measure of your > > character and how people should expect to have to deal with you." > > There is a serious lack of judgment in this phrase. When someone reports that a > light is red instead of being green, facts are (or good odds are) that a light > is red instead of being green -- and this has nothing to do with the reporter > being Bush, Putin, Jack the Ripper or Hu Jintao. Straw man. No one's calling you any of those things, and frankly your argument just doesn't have anything to do with what I'm saying. If you comment on your blog (or in any other 'public' space) in a certain manner, with a certain tone and certain style, then I'm going to have to expect that writing is representative of your character and how you deal with people, and I'm going to keep that in mind when dealing with you in other venues. Without knowing someone in person, that's the only information I have to go on. Anyhow, this discussion is getting a bit OT for a bug tracker, I think. I had a few minutes, so I fixed the incorrect URLs (note that it might take some time for the fixed files to get updated on the xfce.org mirrors).