Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Renaming Iceweasel to Firefox

bugs.debian.org

Post reply on HN
Print view View original

31–40 of 155 posts

Re: Renaming Iceweasel to Firefox

#31

Post by b34r »

astrodust wrote: post #14
shmerl wrote: post #3

Related: https://bugzilla.mozilla.org/show_bug.cgi?id=555935 Also, Debian is really lacking some more modern bug management / issue tracking system. It might be useful to provide e-mail interface for it, but I fail to see why it also can't be managed from some site at the same time instead of limiting it to read only view.

Although GitHub Issues has a lot of issues, for the singular reason that you can opt-in and opt-out of notifications on particular subjects I find it vastly more useful than most bug trackers. Is there a good open-source GitHub alternative that implements this feature?

Gitlab?

Re: Renaming Iceweasel to Firefox

#32

Post by tonyarkles »

DHowett wrote: post #25

It's interesting that the Paul brings up the trademark license clause regarding for-pay distribution. If you are using the Mozilla Mark(s) for the unaltered binaries you are distributing, you may not charge for that product. While it restricts a freedom that Debian is unlikely to exercise, it's still a restriction. Presumably, that makes the trademark license indigestible to the Debian foundation?

Ahhhhhh, I've always wondered about clauses like that with the distribution of software compilations. For example, I can buy a Debian boxed set from here: http://www.jbox.ca/product-category/computers-tablets/softwa... or any of the other distributors: https://www.debian.org/CD/vendors/. I think a clause like that would prevent them from selling those.

Re: Renaming Iceweasel to Firefox

#33

Post by perlgeek »

astrodust wrote: post #14
shmerl wrote: post #3

Related: https://bugzilla.mozilla.org/show_bug.cgi?id=555935 Also, Debian is really lacking some more modern bug management / issue tracking system. It might be useful to provide e-mail interface for it, but I fail to see why it also can't be managed from some site at the same time instead of limiting it to read only view.

Although GitHub Issues has a lot of issues, for the singular reason that you can opt-in and opt-out of notifications on particular subjects I find it vastly more useful than most bug trackers. Is there a good open-source GitHub alternative that implements this feature?

OTRS and RT allow you to watch a ticket. Thus you can chose to be notified for changes to a ticket (opt-in).

I know of no particular opt-out feature, though at least for OTRS it would be rather easy to write an add-on that makes you watch all new tickets in a particular queue, of which you could opt-out by stopping to watch a ticket.

Re: Renaming Iceweasel to Firefox

#34

Post by nitrogen »

oliwarner wrote: post #28

Congratulations HN, OP, we DDoSed the debian bug tracker. Please be considerate when linking to webapps. If there's a static or cached version available, please post that. In this case Debian's tracker mirrors everything to publicly mirrored mail servers (which are static), ie: https://www.mail-archive.com/debian-bugs-dist@lists.debian.o...

Or write faster apps? Caching pages for logged-out users is part of web site performance 101.

Re: Renaming Iceweasel to Firefox

#35

Post by chrisan »

oliwarner wrote: post #28

Congratulations HN, OP, we DDoSed the debian bug tracker. Please be considerate when linking to webapps. If there's a static or cached version available, please post that. In this case Debian's tracker mirrors everything to publicly mirrored mail servers (which are static), ie: https://www.mail-archive.com/debian-bugs-dist@lists.debian.o...

I'm not familiar with whatever bug tracker they use, but shouldn't this be the default such that a user doesn't have to make this mental note?

Re: Renaming Iceweasel to Firefox

#36

Post by windsurfer »

nitrogen wrote: post #34
oliwarner wrote: post #28

Congratulations HN, OP, we DDoSed the debian bug tracker. Please be considerate when linking to webapps. If there's a static or cached version available, please post that. In this case Debian's tracker mirrors everything to publicly mirrored mail servers (which are static), ie: https://www.mail-archive.com/debian-bugs-dist@lists.debian.o...

Or write faster apps? Caching pages for logged-out users is part of web site performance 101.

Debbugs works great for being last updated 12 years ago. It's main interface is email, after all, so the web interface is read-only. I think the real issue here is the hardware it's running on.

Re: Renaming Iceweasel to Firefox

#37

Post by mwcampbell »

windsurfer wrote: post #36
nitrogen wrote: post #34

Earlier quoted context omitted.

Or write faster apps? Caching pages for logged-out users is part of web site performance 101.

Debbugs works great for being last updated 12 years ago. It's main interface is email, after all, so the web interface is read-only. I think the real issue here is the hardware it's running on.

Forking a new process to run a Perl CGI script for every request is going to be far from optimal on any hardware.

Re: Renaming Iceweasel to Firefox

#38

Post by icebraining »

twunde wrote: post #15
Touche wrote: post #2

> On the contrary, Debian having a longer release cycle (about every two years), release cycles don't align. Then change your release cycle. Seriously, it's not that hard. Say that browsers are different and get released frequently. Create a firefox-lts package that is updated at the beginning of your Debian release cycle -- and never again. Let the firefox package be the firefox package, updated as frequently as ups…

If you don't like the 2 year release cycle, use Ubuntu, which is Debian-based. Debian maintains such long release cycles because the tolerance for bugs and incompatibilities are smaller than other linux distros. For long-lived applications or applications that have long planning periods Debian is ideal. NASA uses Debian, because their projects are measured in years, have low tolerances for bugs, and are developed to…

Debian has both: I use Stable on my servers and Unstable/Sid (which is a rolling-release distro) on my laptop.

Re: Renaming Iceweasel to Firefox

#39

Post by oliwarner »

chrisan wrote: post #35
oliwarner wrote: post #28

Congratulations HN, OP, we DDoSed the debian bug tracker. Please be considerate when linking to webapps. If there's a static or cached version available, please post that. In this case Debian's tracker mirrors everything to publicly mirrored mail servers (which are static), ie: https://www.mail-archive.com/debian-bugs-dist@lists.debian.o...

I'm not familiar with whatever bug tracker they use, but shouldn't this be the default such that a user doesn't have to make this mental note?

Perhaps I'm being unfair —because I know how the sausage is made— but if it looks like it's generated by Perl (clunky late-90s design, obvious interactive parts, filter, logins, etc) it probably scales like a squirrel carrying watermelons. (One at a time is okay.)

Debian should definitely do more to stop this from happening but this isn't the first time a HN link to a clunky old webapp has taken it down.

Re: Renaming Iceweasel to Firefox

#40

Post by mayhew »

[deleted] wrote: post #18
twunde wrote: post #15

Earlier quoted context omitted.

If you don't like the 2 year release cycle, use Ubuntu, which is Debian-based. Debian maintains such long release cycles because the tolerance for bugs and incompatibilities are smaller than other linux distros. For long-lived applications or applications that have long planning periods Debian is ideal. NASA uses Debian, because their projects are measured in years, have low tolerances for bugs, and are developed to…

[deleted]

Ubuntu releases come every 6 months with a LTS every 2 years.

The non-LTS releases are of pretty questionable quality and are only supported for 9 months, which makes them pretty awful for server use.

Debian releases and Ubuntu LTS releases are about equal. New releases come every ~2 years and with Debian's new LTS policy, both are supported for 5 years in total. So you could say for server usage they have similar release cycles.

Post reply on HN