Hard to find links to nightly builds from mozilla.org or mozilla.com
Smaug
Currently it is way too difficult to find links to nightly builds.
There used to be a link to http://www.mozilla.org/developer/
in www.mozilla.org, but I can't find that anymore.
http://www.mozilla.org/developer/ contains links to
nightly builds.
A link to nightly.m.o/c would be ok too, I think.
I wonder what was the reason to change mozilla.org so that it is
harder to find such a pretty critical information.
Also, I think even mozilla.com should somewhere
provide links to nightly builds.
https://bugzilla.mozilla.org/show_bug.cgi?id=540022
br,
-Olli
Mike Shaver
around, probably, but I don't think it's a governance topic.
Mike
> _______________________________________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/governance
>
Robert Kaiser
> we should just sprinkle some links to http://nightly.mozilla.org
> around, probably, but I don't think it's a governance topic.
Oh, "mozilla.org" nightlies are just the Firefox ones? Interesting...
Robert Kaiser
Asa Dotzler
I'm guessing what you meant to say was "who do I speak to or where do I
file a bug to get additional builds added to this page"?
That's precisely what I asked when I found this page and it didn't
contain what I was looking for.
https://bugzilla.mozilla.org/show_bug.cgi?id=524881
Or am I misunderstanding your comment?
- A
Robert Kaiser
> I'm guessing what you meant to say was "who do I speak to or where do I
> file a bug to get additional builds added to this page"?
>
> That's precisely what I asked when I found this page and it didn't
> contain what I was looking for.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=524881
>
> Or am I misunderstanding your comment?
Ah, thanks, good to know. Having a pan-project link for nightlies would
be cool.
I case anyone didn't catch it, my comment was meant to be humorous /
tongue-in-cheek, I might not have gotten that across well enough ;-)
Robert Kaiser
Robert Kaiser
> I case anyone didn't catch it, my comment was meant to be humorous /
> tongue-in-cheek, I might not have gotten that across well enough ;-)
My bad. I'll take that back. People who think that Firefox should kill
everything else in the Mozilla project seem to be heading this effort,
so no excuses, I'll actually turn back and lose my humor on this.
It's not fun when your work, life and project is being trampled upon by
your fellow "colleague" (or so I though that we all in Mozilla were some
kind of colleagues).
Robert Kaiser
sayrer
>
> It's not fun when your work, life and project is being trampled upon by
> your fellow "colleague" (or so I though that we all in Mozilla were some
> kind of colleagues).
Oh come on, tell us how you really feel.
No one asked me anything about this site I made or what its goals are,
fwiw. I just got a (misguided) patch in the bug and bunch of flack.
Thanks "community".
- Rob
John J. Barton
I've had trouble finding the nightly builds for a long time. I
appreciate your effort to solve this problem.
jjb
Asa Dotzler
> Robert Kaiser wrote:
>> I case anyone didn't catch it, my comment was meant to be humorous /
>> tongue-in-cheek, I might not have gotten that across well enough ;-)
>
> My bad. I'll take that back. People who think that Firefox should kill
> everything else in the Mozilla project seem to be heading this effort,
> so no excuses, I'll actually turn back and lose my humor on this.
Why the assumption of bad motives here? I don't know anyone (I mean
that) working on any Mozilla project that believes "that Firefox should
kill everything else in the Mozilla project" and I don't think you do
either.
Attributing bad motives to someone trying to solve their own problem,
even at the exclusion of solving your problem, is not, I think, how we
ought to communicate in this community.
A community member here had a problem he wanted to solve. He wanted
people to be able to easily find and acquire Firefox nightly builds so
that more people would test Firefox nightly builds.
His solution may not solve your problem of wanting people to find and
use SeaMonkey builds (or solve my problem of wanting people to find and
use Fennec nightly builds) but that does not mean that he wants to kill
SeaMonkey or Fennec and it seems quite rude to make that claim.
> It's not fun when your work, life and project is being trampled upon by
> your fellow "colleague" (or so I though that we all in Mozilla were some
> kind of colleagues).
No one has trampled on you or your work here. Not helping you with your
particular problem is not the same as trampling on you. I don't get why
you want to make yourself a victim here by attributing bad motives to
one of your colleagues.
As I read this, you're the one treating your fellow Mozillians poorly here.
- A
Ken Saunders
The Firefox Should Kill Everything Else in the Mozilla Project Project
http://www.86allbutFx.org
Project lead Smaug
(jk Smaug)
"Can't we all just get along?"
I know that this isn't bugzilla, but mozilla.com/en-US/mobile doesn't
even provide a proper format for the desktop version.
"Download Firefox for mobile to your desktop"
firefox.install is the downloaded file
That issue had been discussed on irc but I'd rather not call anyone
out on it (that wouldn't be cool).
I'm mentioning it to you because of your interest in Fennec.
I just use pub/mozilla.org/mobile and while it isn't the prettiest way
to get Fennec, perhaps "Download Firefox for mobile to your desktop"
should be linked to that.
Ken
timeless
> "Download Firefox for mobile to your desktop"
> firefox.install is the downloaded file
> That issue had been discussed on irc but I'd rather not call anyone
> out on it (that wouldn't be cool).
> I'm mentioning it to you because of your interest in Fennec.
> I just use pub/mozilla.org/mobile and while it isn't the prettiest way
> to get Fennec, perhaps "Download Firefox for mobile to your desktop"
> should be linked to that.
I've spent time trying to find the mobile binaries on ftp.mozlla.org
and i've failed miserably. I try roughly once every two months. And I
last tried a couple of hours ago in response to asa's plea in this
thread.
I can't actually provide a better scrape.py for mobile because I
really can't figure out where the latest thing is. I found a latest
directory in /firefox/ but it has ~30 or so files w/ random names and
versions, as a script, that's impossible to manage. As a human, I gave
up.
You're complaining that you can't get the win32 mobile firefox binary
(what used to be fennec.exe), right? Yeah, I can't see that, and this
will cause me pain as I try to tell bugs.maemo.org reporters to test
w/ Mobile Firefox on their Windows computer. However do note that I
have the same problems w/ scrape.py in the area of trying to figure
out what might be the latest version.
Robert Kaiser
Well, it was your reaction that prompted that admittedly overdone
reaction by me (sorry for being over the top a few hours back).
It would be much more helpful by giving an idea of how to solve the
basic problem the patch wanted to work on (making other products'
nightlies available just as easily and give people a way to find them
easily) than to straight turn it down and say "throw it where nobody
finds it" (or do you really think a Thunderbird tester will know that a
link titled "more stuff" could give him what he is looking for, as you
suggested in the bug?). Basically, this sounded to timeless and me me,
who was approached with rather strange wording by him ("your stupid
nightly.mozilla thing"), like you would have said "go away stick your
sh*t elsewhere". I realize you didn't say that, but at that time, this
is how at least I read it at first glance.
We now have put this off in a followup bug and I hope we'll reach a
constructive approach there. And thanks for thinking about starting such
a site at the first place.
Robert Kaiser
Mike Beltzner
> When you intentionally piss off non-Firefox Mozilla projects in the
> mozilla.org namespace, that is what you deserve and what you should be
> expecting.
How do you figure it was intentional to "piss off" anyone? I'm continually alarmed by the anger and bile that's being delivered by leaders of non-Firefox Mozilla projects in this forum. We have well established mechanisms for discussing things and for working together to make changes for the better, and it seems to me that you have elected instead to harbour feelings of resentment and then lash out later.
Doesn't feel like a responsible or effective way to make positive changes, really.
cheers,
mike
Robert Kaiser
> Why the assumption of bad motives here? I don't know anyone (I mean
> that) working on any Mozilla project that believes "that Firefox should
> kill everything else in the Mozilla project" and I don't think you do
> either.
It looks like a few things lead to each other respectively, and made me
probably interpret sayrer's comment differently than he meant it. I hope
in the followup bug we're going more constructively and make this site a
win for everyone involved.
Still, even if you know nobody with that attitude, I repeatedly heard
from people in non-Firefox parts of the community (not just the
SeaMonkey project) that a numbers of statements repeatedly make them
feel like that would be the mindset.
And, of course, as any other project in our community is easily shadowed
by the mindboggling number of users that Firefox brings to the tablet,
it's clear that it's just too easy to get into that mindset in
non-Firefox areas and also to get to seemingly ignore everything else
from a Firefox developer's POV.
I'm sometimes torn by the admiration and love for the tremendous success
of Firefox and the wish that it wasn't so much of a different world to
what we are working in.
Robert Kaiser
Mike Beltzner
> And, of course, as any other project in our community is easily shadowed by the mindboggling number of users that Firefox brings to the tablet, it's clear that it's just too easy to get into that mindset in non-Firefox areas and also to get to seemingly ignore everything else from a Firefox developer's POV.
I don't know a single developer with a Gecko or Firefox focus who ignores other community projects. We sometimes do not prioritize resources in ways that some people may like, but that's not the same thing as ignoring other projects; they are very much present and considered in the decision making process. Further, we often make choices which have real costs in terms of our flexibility and opportunity in order to preserve compatibility and to assist other Mozilla based projects. Especially when those projects take the time to make their requests known!
cheers,
mike
Robert Kaiser
> On 2010-01-17, at 5:41 PM, Robert Kaiser wrote:
>
>> And, of course, as any other project in our community is easily shadowed by the mindboggling number of users that Firefox brings to the tablet, it's clear that it's just too easy to get into that mindset in non-Firefox areas and also to get to seemingly ignore everything else from a Firefox developer's POV.
>
> I don't know a single developer with a Gecko or Firefox focus who ignores other community projects.
Maybe I didn't make the word "seemingly" clear enough in this sentence.
What I meant there is that it's easy for someone to focus on Firefox
alone for some time while working on something and that makes it seem to
others like he would (possibly intentionally) ignore the others, which
does not mean that it actually is that way, but it may SEEM that way for
an outside watcher.
> Further, we often make choices which have real costs in terms of our flexibility and opportunity in order to preserve compatibility and to assist other Mozilla based projects. Especially when those projects take the time to make their requests known!
I know you do, and the teams as a whole quite often do, and I'm usually
very happy about it. Sometime it takes us quite some time from
unintentionally not being in the focus until we realize something
affects us and we can make a request know though, and then the thought
of "why didn't they just pass a message in the beginning and we could
have reacted earlier" comes to mind - and if you're already under enough
stress (and you probably know that the seemingly "bad" things usually
all happen at the same time and when you're already under stress) the
thought of someone maybe doing this intentionally isn't far away. Of
course, it's complete nonsense in reality and everything is just an
oversight, and you are free to post a patch and get it into the next
stable branch or something, if you just were able to write it up - and
in a number of cases, it's even easy and the developer will happily do
it for you (and I probably should point out the positive examples more
often).
But that all leads quite far away from the actual topic of this thread
right now - we hopefully have things under control in the followup bug
and I tried to help coming up with a possible way to solve this there.
Robert Kaiser
Asa Dotzler
> like you would have said "go away stick your
> sh*t elsewhere". I realize you didn't say that, but at that time, this
> is how at least I read it at first glance.
And I think this is nearly the root of the problem.
You admit that this is not what was said yet you believe it appropriate
in our community to assume the worst and to read it "at first glance"
and respond based on your "at first glance" reading?
That's not the kind of community I'm happy working with and I assume
it's not the kind of community you're happy working with.
So why do you assume the worst and respond after only "read[ing] it at
first glance." ?
When I think about the community I enjoy working with, I read bugzilla
comments and blog posts and newsgroup accounts and give everyone the
benefit of the doubt, not the assumption of evil.
You seem to have taken the opposite approach recently and that bothers
me quite a bit. Why do you not give your colleagues the benefit of the
doubt?
- A
Asa Dotzler
> Mike Beltzner wrote:
>> On 2010-01-17, at 5:41 PM, Robert Kaiser wrote:
>>
>>> And, of course, as any other project in our community is easily
>>> shadowed by the mindboggling number of users that Firefox brings to
>>> the tablet, it's clear that it's just too easy to get into that
>>> mindset in non-Firefox areas and also to get to seemingly ignore
>>> everything else from a Firefox developer's POV.
>>
>> I don't know a single developer with a Gecko or Firefox focus who
>> ignores other community projects.
>
> Maybe I didn't make the word "seemingly" clear enough in this sentence.
> What I meant there is that it's easy for someone to focus on Firefox
> alone for some time while working on something and that makes it seem to
> others like he would (possibly intentionally) ignore the others, which
> does not mean that it actually is that way, but it may SEEM that way for
> an outside watcher.
But you're not an "outside watcher" and you have a responsibility that
comes with your leadership role in the Mozilla community to help dispel
the mis-understandings of the "outside watcher".
It seems to me, in the last couple of days of your commeting around
various Mozilla threads that you're not only not dispelling
misconceptions of those "outside watchers" but that you're adding to them.
Please tell me otherwise. I really do want to have an alternative
explanation here.
>> Further, we often make choices which have real costs in terms of our
>> flexibility and opportunity in order to preserve compatibility and to
>> assist other Mozilla based projects. Especially when those projects
>> take the time to make their requests known!
>
> I know you do, and the teams as a whole quite often do, and I'm usually
> very happy about it. Sometime it takes us quite some time from
> unintentionally not being in the focus until we realize something
> affects us and we can make a request know though, and then the thought
> of "why didn't they just pass a message in the beginning and we could
> have reacted earlier" comes to mind - and if you're already under enough
> stress (and you probably know that the seemingly "bad" things usually
> all happen at the same time and when you're already under stress) the
> thought of someone maybe doing this intentionally isn't far away.
This isn't the kind of community that any of us (you, included, I'm
sure) want to work in. If the thought that others on the project are
trying to harm your interests isn't far away, I'm very sad about the
Mozilla project -- something I've devoted a decade of my life to. Is
that really the case, that you easily gravitate to the thought that
others in the Mozilla project are intentionally trying to hurt your efforts?
- A
Robert Kaiser
> On 1/17/2010 2:32 PM, Robert Kaiser wrote:
>> like you would have said "go away stick your
>> sh*t elsewhere". I realize you didn't say that, but at that time, this
>> is how at least I read it at first glance.
>
> And I think this is nearly the root of the problem.
>
> You admit that this is not what was said yet you believe it appropriate
> in our community to assume the worst and to read it "at first glance"
> and respond based on your "at first glance" reading?
Now I am the bad guy because sayrer told timeless to "go away" just in
nicer words, and timeless did seem to understand it that way as he
obviously was angry when he contacted me?
And I even saw others reading those words the same way as me even though
I admit they can be read differently and might just have been meant
differently. Thanks for punishing me for trying to calm things down here.
> So why do you assume the worst and respond after only "read[ing] it at
> first glance." ?
Probably because 1) the amount of information I read daily is
overwhelming but I already trimmed it down and leave out some sources
that would have information I'd need to deal with ideally, and 2)
because I sometimes waste some of my 7-days-a-week working time with
things called "fun" and then try to catch up with work so hard that I
forget to eat and read comments like this in a very hungry state (just
like today, er, yesterday, as I still am here in front of the computer,
half-working, at 3am on a Sunday night).
> When I think about the community I enjoy working with, I read bugzilla
> comments and blog posts and newsgroup accounts and give everyone the
> benefit of the doubt, not the assumption of evil.
>
> You seem to have taken the opposite approach recently and that bothers
> me quite a bit. Why do you not give your colleagues the benefit of the
> doubt?
Erm, what you are writing here against (yes, against) me in this reply
does not sound like the "benefit of the doubt" approach, but I take it
that you understand neither my humor, like you stated elsewhere but also
not my attempts to calm things down. Well, you will not be able to get
rid of me in the project, I've been masochistic enough to already have
endured 10 years of it, I will not let go easily now. ;-)
So, please, try not to state how unoffensive you are with quite
offensive phrasing, or you will prolong the flames that I just thought
we finally can calm down by apologizing for my part of what went wrong
and - perhaps naively - hoping that others would do the same and we
could go back to the actual topic and be constructive, and perhaps even
all (including me, of course) learn a bit more of how to improve our
work together in the project.
Robert Kaiser
Robert Kaiser
> But you're not an "outside watcher" and you have a responsibility that
> comes with your leadership role in the Mozilla community to help dispel
> the mis-understandings of the "outside watcher".
When it comes to things that are mostly decided by Mozilla employees, I
usually actually am an "outside watcher" and often feel like one as many
decisions come to my attention phrased like they would already have been
made, even if I find out later in the discussion that this isn't
actually that much true, as with the roadmap, add-ons system, or profile
manager debates that came into light recently.
That reminds me, do you guys know whom I'd need to ask about possibly
being invited to all-hands weeks or whatever they are called nowadays?
(And e.g. not being able to access current ADU and download data of the
product I'm leading is one more example why I feel as being an "outside
watcher" most of the time.)
> This isn't the kind of community that any of us (you, included, I'm
> sure) want to work in. If the thought that others on the project are
> trying to harm your interests isn't far away, I'm very sad about the
> Mozilla project -- something I've devoted a decade of my life to. Is
> that really the case, that you easily gravitate to the thought that
> others in the Mozilla project are intentionally trying to hurt your
> efforts?
Sometimes, yes, and the last weeks contained a few of those "WTF?"
events where though thought came up in various areas. Being rested from
vacation and holidays - I could put away most of them, realize
statements come from expressing a personal view that not necessarily
reflects a wide view of all things involved and sometimes is even
unfortunately phrased and try to go for constructive ways instead (and,
thankfully, people like beltzner or shaver are often very positive and
reasonable examples of how to get things right and bring out
constructive approaches).
Unfortunately, the most straining debates are those with users that
don't understand some product decisions and with our move from xpfe to
toolkit in SeaMonkey 2 we (and me as a project leader) get a number of
flames from always the same tro... er, people who accuse us of
deliberately ignoring users by making password and form management
really suck and destroying the download progress window with the ugliest
design ever.
And the "WTF?" moments out of the Firefox and Mozilla platform community
then came on top of that.
At the end of a week where I somehow could get much less stuff done than
I wanted, this topic here unfortunately brought me personally over the
top, though I should actually be cheering for "my" Saints advancing to
the championship game and even playing an opponent they haven't lost to
already this season. :)
I agree that the community we work in is not ideal and can be improved.
I don't want to go as far as saying it's not the one we want to work in
as it's still incredibly cool in many ways, and at times very rewarding.
I guess in the last weeks we just had a number of things culminating,
which might be a good point to think about how others in the community
might read our statements and learn to improve how we communicate things
- I for myself already learned to either avoid or very clearly mark
statements that I find humorous / tongue-in-cheek and to restrain myself
harder from writing anything when I get emotional. I hope others will
also take away their own insights from this discussion or incident and
we might even become a slightly nicer community.
Robert Kaiser
Justin Wood (Callek)
> On 1/17/2010 2:32 PM, Robert Kaiser wrote:
>> like you would have said "go away stick your
>> sh*t elsewhere". I realize you didn't say that, but at that time, this
>> is how at least I read it at first glance.
>
> And I think this is nearly the root of the problem.
Asa,
I just have to say, that even after reading this whole discussion and
mostly disagreeing with Robert (in terms of generalities) having just
read the bug comments [after discussion] I was VERY taken aback by the
comments that set him over the top. I would not have expected that, and
if I was the one reading them, before this thread, I likely would have
made similar comments from my own frustration.
I think we *all* need to try and be less dismissive about things we
don't agree with.
When I first heard about nightly.mozilla.org on IRC (I have yet to
actually VISIT that, to be honest) I was ecstatic that the mozilla
community site had a page for [easier] nightly downloads. Up until my
reading of this thread and this bug I had actually thought that was
[already] the case. And would have expected nothing less.
If it was nightly.mozilla.com or nightly.firefox.com or
nightly.mozillamessaging.com etc. I could have expected a much different
initial thought.
Even then, visiting the page and not seeing anything other than Firefox,
without thread or bug would have been a "WTF" moment like KaiRo expressed...
I'm interested in ways we can resolve misconceptions as a community, as
fellow developers, and as -essentially- coworkers here. I don't know
what those ways are, but I hope we can start with understanding where
each other is coming from. You understanding where myself, Robert, and
timeless are coming from. As well as us understanding you.
The first step in resolving conflicts, no matter how tiny, is actually
understanding either: where you are wrong, or why the other person feels
the way they do [even if you disagree].
-
~Justin Wood (Callek)
Justin Wood (Callek)
> That reminds me, do you guys know whom I'd need to ask about possibly
> being invited to all-hands weeks or whatever they are called nowadays?
I would also love to know this answer.
For the firefox 1.5 I think it was release party, I was invited
(recommended by Dria) for my help on devmo at the time.
Unfortunately at that time I was unable to take Mozilla up on the offer
of flying down to join in and meet everyone.
I would love that opportunity again, but its one of those things I don't
know if I'll get again, short of being hired by Mozilla.
-
~Justin Wood (Callek)
Mike Beltzner
> Now I am the bad guy because sayrer told timeless to "go away" just in nicer words, and timeless did seem to understand it that way as he obviously was angry when he contacted me?
Whoa, whoa. Let's be clear. Nobody's a "bad guy," here. I think Asa's trying to figure out why people's assumptions run towards the negative, is all, and asking you fair questions about what made you lean that way.
cheers,
mike
Robert Kaiser
> On 1/17/2010 9:49 PM, Robert Kaiser wrote:
>> That reminds me, do you guys know whom I'd need to ask about possibly
>> being invited to all-hands weeks or whatever they are called nowadays?
>
> I would also love to know this answer.
Justin, the all-hands is a very small employee-only event, if we manage
to get anyone else there, then I doubt it would be anyone else but a
project lead from SeaMonkey or calendar.
For the Summit, I'm trying to get a presence there for us officially,
which might only be a handful of people, but you're certainly on my list.
Robert Kaiser
Simon Paquet
> Justin, the all-hands is a very small employee-only event, if we
> manage to get anyone else there, then I doubt it would be anyone
> else but a project lead from SeaMonkey or calendar.
>
> For the Summit, I'm trying to get a presence there for us officially,
> which might only be a handful of people, but you're certainly on my
> list.
So there will be another summit? The last I heard (in October at the
EU MozCamp in Prague) was that somebody somewhere was thinking about
doing another summit, but nothing was set in stone. Has that evolved
now?
Cya
Simon
PS: I don't know if this is the appropriate newsgroup for this.
Please set a F'up2 if you know of a better place.
--
Thunderbird/Calendar Localisation (L10n) Coordinator
Thunderbird l10n blog: http://thunderbird-l10n.blogspot.com
Calendar website maintainer: http://www.mozilla.org/projects/calendar
Calendar developer blog: http://weblogs.mozillazine.org/calendar
Mike Beltzner
> So there will be another summit? The last I heard (in October at the
> EU MozCamp in Prague) was that somebody somewhere was thinking about
> doing another summit, but nothing was set in stone. Has that evolved
> now?
I believer that there's intent and resources set aside to host another Summit but plans are still only just coming together, so you'll have to be patient for now :)
cheers,
mike
Gervase Markham
> When you intentionally piss off non-Firefox Mozilla projects in the
> mozilla.org namespace, that is what you deserve and what you should be
> expecting.
I think that's unwarranted and unfair. There was no "intention to piss
off", and your .org vs .com us-and-them we're-under-siege mentality is
of no help to anyone.
Nobody deserves flak for making something better. It may not be better
for you yet, but it was better for someone. Sure, let's make it work to
be better for you too.
Gerv
Robert Kaiser
> Nobody deserves flak for making something better.
Right, that was why this controversy started - because a try to make
this new site even better was turned down in a quite rude way.
I hope we got this into more constructive ways now with the followup
bug, though (still would love to hear from sayrer what he thinks about
the proposals there).
Robert Kaiser
Mike Connor
> Gervase Markham wrote:
>> Nobody deserves flak for making something better.
>
> Right, that was why this controversy started - because a try to make
> this new site even better was turned down in a quite rude way.
A poorly executed, ill-placed try, by someone who should know full well
that patches out of scope for a bug, without even talking to the owner
of the site about goals/intent/best way forward, are a pretty
passive-aggressive way of "improving" something. The patch was rejected
because it went against previously-declared intent for the site to
remain simple for the initial user experience.
Filing a _constructive_ bug about adding other projects to
nightly.mozilla.org, especially starting with questions to the effective
module owner for the project about how to do that in line with the goals
for the project, is the right way to do things, and we all know this.
Why that wasn't done is simply beyond my comprehension, as everyone
involved _should_ know better than to pick fights in unrelated bugs.
-- Mike
davidwboswell
thread about how we're telling our story through our websites.
Basically, using a Mozilla domain to talk exclusively about Firefox
can be confusing and can create tension. I wrote up some thoughts
about this in a blog post and was interested to get people's feedback.
http://davidwboswell.wordpress.com/2010/02/02/what-i-learned-from-the-firefox-nightly-builds-site/
David
Tony Mechelynck
> Hi all,
>
> Currently it is way too difficult to find links to nightly builds.
> There used to be a link tohttp://www.mozilla.org/developer/
> inwww.mozilla.org, but I can't find that anymore.http://www.mozilla.org/developer/contains links to
> nightly builds.
> A link to nightly.m.o/c would be ok too, I think.
>
> I wonder what was the reason to change mozilla.org so that it is
> harder to find such a pretty critical information.
> Also, I think even mozilla.com should somewhere
> provide links to nightly builds.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=540022
>
> br,
>
> -Olli
A few notes after reading this whole thread:
1. Finding nightly (or even hourly) builds for any Mozilla products
isn't that hard. Start at (ftp: or) http://ftp.mozilla.org/ and go
down from there by product name, then /nightly/ (or /tinderbox-builds/
for hourlies) then (for nightlies) something starting latest-
depending on the code branch you're interested in, etc. Of course
*more* ways to find a given build are always useful, but they should
be unambiguous. IMHO a name like nightly.mozilla.org ought to give
access to _all_ Mozilla-family products.
2. When reading titles in places (such as the Planet Mozilla newsfeed,
but also elsewhere) which are concerned by the whole Mozilla world, I
often notice that the fact that a given item concerns only Firefox is
not at all obvious from the title. I often get the (true or false)
impression that "Firefox people" are apparently oblivious of the
existence of Thunderbird, SeaMonkey, Sunbird et al. I suppose it is
not intentional, but I believe that Firefox people ought to make a
conscious effort to remind themselves that there are other Mozilla
products, and to display that awareness in what they write. (The same
goes, of course, for "specialists" of all other Mozilla products, but
AFAICT they already mostly seem to display such awareness.) On the Net
just like in the "real" world, displaying awareness of other people's
existence and worth goes a long way towards making life easier.
davidwboswell
> impression that "Firefox people" are apparently oblivious of the
> existence of Thunderbird, SeaMonkey, Sunbird et al. I suppose it is
> not intentional, but I believe that Firefox people ought to make a
> conscious effort to remind themselves that there are other Mozilla
> products, and to display that awareness in what they write.
From my experience, the issue is not that people working on Firefox
are unaware of anything but rather that they are being sensitive to
the community and are trying to be inclusive by referring to Mozilla
even when they are talking about just Firefox. It might be worth
rethinking some of the assumptions behind this if the intention of
recognizing the broader community is coming across as lack of
awareness.
David