Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion Thunderbird's future role
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Brendan Eich  
View profile  
 More options Apr 5 2007, 4:02 pm
Newsgroups: mozilla.dev.platform
From: Brendan Eich <bren...@mozilla.org>
Date: Thu, 05 Apr 2007 13:02:56 -0700
Local: Thurs, Apr 5 2007 4:02 pm
Subject: Re: Thunderbird's future role

Simon Paquet wrote:
> bren...@mozilla.org wrote on 02. Apr 2007:

> [Brendan, I also sent you a (slightly different) mail about this.]

I'll reply here.

> Please try to see it from my side. You are announcing a major
> reorganization/rewrite/whatever of the mozilla backend platform and are
> also announcing, that this will be done only on Firefox and XULRunner.

I think you are misstating the Mozilla 2 plan. We do not propose to
rewrite all front ends for a new back end. We don't propose to change
every, or even necessarily most, APIs (but we may change all C++-only
APIs -- we need that freedom).

Other than Firefox, which has special status along with XULRunner,
front-end porting to Mozilla 2 is a job for each front-end project to
work on. I do not have Camino commit access, and I don't want it. So
there never was and never will be a free lunch here.

Hosting Camino (let's use it instead of Thunderbird) in the Mozilla 2
repository is not the issue, either. Hosting != tinderbox build coverage
!= API design feedback != API porting division of labor.

I keep repeating that we must focus on the Mozilla 2 goals (JS2 via
Tamarin+SpiderMonkey, automated refactoring and deCOMtamination,
embedding, layout and graphics competitiveness) to the exclusion of API
compatibility where we justify breaking it.

I also keep saying that we will fail if we require ourselves to keep all
cvs.m.o-hosted apps working all the time during the bulk of the back end
rework for Mozilla 2.

This point is important. I don't think you've responded to it head-on.
Feelings and fears or accusations against "MoCo" don't make sense until
you confront the insuperable practical problem of doing Mozilla 2 while
keeping all the hosted XUL apps, or even more than two of them, working.

> You are also announcing that you are changing the tree rules to a
> significant extent.

Yes, but this is for the new tree, based on the premise I keep repeating
-- we are not deciding *next year's* tree rules, but we are strongly
suggesting that new VCSes and better embedding APIs make way for other
hosting arrangements, no matter the tree rules.

So we are trying to get started without having to solve the tree rule
problem in 2008, or even 2009. You seem to want us to keep the current
tree rules (Firefox, SeaMonkey, Thunderbird) for the new Mozilla 2 repo
from day 1. I repeat again that's suicide.

> Does it really surprise you, that some people outside of the MoCo
> inner circle

What MoCo inner circle?

The Mozilla 2 work has been doing via blogs and wiki.mozilla.org.
Nothing is being done "in secret".

I think you are out of line using such inflammatory language. But apart
from *my* feelings, that language is demonstrably fact-free.

> seem to see bad implications coming from this. Robert
> voiced some concerns in the discussion and I know from discussions
> with Calendar developers, that I'm not the only one having doubts.

Robert seems to be doing fine in his posts, and you have a reply from
Karsten that doubts some of your assertions. Let's stop trying to rally
others and name-drop as if we are in a political campaign, please. This
is m.d.platform, and I'm very concerned about practicalities of Mozilla
2 development concurrent with 1.9. That's the problem to solve.

Turning this into a "I doubt MoCo 'cares' for other XUL apps than
Firefox" is both:

1. irresponsible -- sayrer's right, we have to favor Firefox, "we" being
the whole community, but especially MoCo (as distinct from MoFo); and

2. categorically confused -- emotional when the topic here is technical:
how to do Mozilla 2 so that all XUL apps have a better future, without
serializing with 1.9 or taking on impossible workload in keeping to the
current tree rules every day we develop Mozilla 2 in the new repo.

> The comments from the Calendar devs that I spoke with generally went
> into the direction of "MoCo did not, does not and never will care
> about us, it cares and will always care only about Firefox".

Stop looking for "care" and consider the point sayrer made.

Free lunches are a bad idea in general. As I wrote, with a good plan for
Thunderbird, I hope and expect that Mozilla Foundation (again I'm on the
board) will support a separately focused effort for Thunderbird that is
independent of the Firefox and XULRunner effort except to the extent
that the common platform needs shared work -- which is best done via
Mozilla 2's rearchitecture of the code and APIs.

> I know that this is again a feelings-based statement, but I think you
> should be aware of the feelings of the community outside of the Firefox
> ecosystem. What you make of this, is of course your choice.

Feelings are inarguable, so all I can do is try to appeal to your
reason, your technical judgment.

> Please also consider, that in blog posts like
> http://www.allpeers.com/blog/2007/03/22/the-future-of-applications/ or
> http://blog.mozbox.org/post/2007/03/21/ApolloDecolle (translation at
> http://www.allpeers.com/blog/2007/04/01/apollo-takes-off/) other people
> voiced their concerns, which, although not identical with mine, seem to
> go in a similar direction IMO.

You are mixing up VCS hosting of XUL apps currently hosted on cvs.m.o
with tree rules, and with XUL as a platform (which does not necessarily
depend on either hosting or tree rules). Again this seems like vague
connect-the-dots political campaigning.

All I can say is that XUL as a platform cannot be the focus ahead of
Firefox, or we are doomed.

And I'll add (again) that the best hope for XUL as a platform, apart
from uplifting pieces of XUL along with other stuff (such as offline app
support) into the web standards, is Mozilla 2.

>> Firefox >> Thunderbird. This isn't a "MoCo" thing, it's a fact that's
>> obvious based on active user counts, buzz, effect on the competition,
>> effect on the web, etc. etc.

>> This does *not* mean that only Firefox matters, or that other XUL apps
>> must be broken all the time. But without a Mozilla 2 that focuses on
>> APIs and embedding, where "focuses" means "does not have to keep all
>> current API clients hosted in cvs.m.o working at all times, or even
>> for a long stretch up front", then everyone will face rising costs,
>> conflicts over bad APIs, and build system divergence.

> I fully understand. But please also understand, that from my point of
> view, there is a big difference when you or Ben are saying, "We will
> not fix breakages in community projects like Calendar or Seamonkey"
> to "We will not fix breakages in our 2nd product Thunderbird".

Not in the Mozilla 2 repo we set up this year. Not now.

If Thunderbird ports to XULRunner and gets going on Mozilla 2 in due
course, great. We can revisit the tree rules then, as bz and I already
agreed. We do not need to co-host, however -- that's a non-requirement.

> So why I absolutely support your assertion that the Thunderbird
> community must grow beyond MoCo. I think that without an up-front
> effort from MoCo or its paid developers to grow the mail-related
> community, this will be very hard to do.

Then we disagree (we've been over this already). MoCo won't be spending
more on closed-source-like dev/build/qa than it already has. The Mozilla
Foundation is actively investigating a better plan.

> You actually did that with Firefox in a very successful way, by
> creating spreadfirefox.com, hiring people to improve the ease of
> extension development, etc.

Firefox was already a rocket unlike any other XUL app well before MoFo
(there was no MoCo then) had more than ten full time employees. Please
don't revise history.

> In addition Firefox people have shown significant effort to communicate
> with the community in a very open and direct way. The huge number of
> blogs dedicated to the various parts of Firefox development from MoCo
> exployees is a good indicator for that.

Yes, Firefox >> Thunderbird. I don't know how else to put this. If you
are arguing for subsidized blogs, they won't help; that's not the good
plan Thunderbird needs.

> I don't see this from mailnews people at all. I know that mscott was
> posting in the mozillazine forums (I don't know if that's still the
> case) and he and bienvenu are both on IRC I believe, but that's
> basically it.

They are the only paid Thunderbird developers. Adding more inside MoCo
is a terrible idea and I've said why several times.

> I don't know the reason of this. Are mscott and bienvenu not interested
> in communicationg with the community (I can't imagine that)? Is their
> workload so high?

Why don't you ask them?

> Are they required to serve other master (e.g.
> commercial customers of MoCo with customized Thunderbird builds) as well?

No, there's no paying commercial customer pulling Thunderbird developer
focus. We've passed up relatively-small-money-at-high-cost opportunities
here.

> I can only say, judging from my experience in the Calendar camp and in
> dealing with folks from Seamonkey, that active communication is *the*
> major key in growing and keeping in touch with the community and that
> both Calendar and Seamonkey seem to do a pretty good job with it
> (judging from the feedback we're getting).

I agree, of course.

>> You might argue that "MoCo" should throw *more* money at Thunderbird.

> As I said above, I think that to actually grow the mail-related
> community it would need at least a temporary up-front investment.

Not from MoCo, not at the expense of Firefox and Mozilla 2.

Management 101: an organization does at most one thing well. The Mozilla
community does many things well, some better than others. And some
things, say Firefox, are inherently stronger products than others. All
of this says any Thunderbird subsidy ("up-front investment") will be
separate from MoCo, and as a MF board member I will insist on this.

> You
> could do that by either employing more people or by freeing mscott
> and bienvenu from others duties, so they can more actively approach
> the community.

They're not constrained from community involvement now. It's wrong to
insinuate otherwise.

>> That would inevitably mean less focus and fewer people working on
>> Firefox and the core Gecko/XULRunner code.

> Not necessarily, as I mentioned above.

No, necessarily. No free lunch. You can't add people to make things
happen without consequence. See Fred Brooks.

Money is not the issue. Hiring is one issue. Management bandwidth is
another. Build infrastructure is yet another. Organization focus is yet
another, and it's a vague term, but obvious to anyone who has worked at
a startup that grew into a big company. I could write about it at length
and define it concretely, but I'm out of time here.

>> Yet it would also make Thunderbird even less of an open source
>> project with significant patch inflow from various committers,

> This can be a possible outcome, if it's done in the wrong fashion. If
> you do it right, the opposite can (and will) happen.

This is the challenge for the Mozilla Foundation, I agree.

What this has to do with the initial import into hg for Mozilla 2, I
have no idea at this point. I'll leave it to others to continue the new
thread you started with this message (which google groups seems not to
have linked properly, for some reason).

>> Don't take this to mean that money is the issue. As a board member of
>> Mozilla Foundation, I'm happy to spend on Thunderbird *if* there's a
>> plan and signs of a community that will develop it to the degree that
>> it needs to be developed, and in different-in-kind ways, all while
>> keeping its build system from diverging. Money alone won't provide
>> these things, and money spent badly would actually harm Thunderbird.

> I fully agree. How can this be solved? Who can/should develop a plan
> to further validate MoFo's money spending regarding Thunderbird? It
> seems to me, that you are frustrated with the current state of
> Thunderbird. What can be done to change that? What can you do?

I'm focusing on Mozilla 2. That's necessary and overriding. Thunderbird
will have to fly free. If it does not reach a promised land, even with a
good plan and some investment, I will be sad. But I will not jeopardize
Firefox and the platform, which depend on Mozilla 2, by spending more
time on it than my MF board duties require.

So again, apart from my board duties you won't hear from me on this
thread. And I'm not going to speak for the Mozilla Foundation board, or
preempt them in any way. All the above is my opinion, which I've shared
before. I've given my reasoning. I hope it's both sound and valid, and
that it can overcome raw feelings and help others, so that we can all
improve the situation.

/be


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google