<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div id="smartTemplate4-quoteHeader">
<style type="text/css"> #newHeader { font-size: x-small; } #newHeader b { font-weight:bold; color: #990033; } </style>
<div id="newHeader"> <b>To: </b>"tb-planning"<a class="moz-txt-link-rfc2396E" href="mailto:tb-planning@mozilla.org"><tb-planning@mozilla.org></a>
<br>
<b>From: </b>"Robert Kaiser"<a class="moz-txt-link-rfc2396E" href="mailto:KaiRo@KaiRo.at"><KaiRo@KaiRo.at></a><br>
<b>Sent: </b>Tuesday, 23/10/12 12:45:21 12:45 GMT Daylight Time
{GMT DT} +0100 [Week 43]<br>
<b>Subject:</b>Re: list of TB contributors and governance </div>
</div>
<blockquote cite="mid:50868351.7060809@KaiRo.at" type="cite">Kent
James schrieb:
<br>
<blockquote type="cite">That list is Brendan Eich, Stuart
Parmenter, Dan Mosedale, Robert
<br>
Kaiser, Mike Connor, David Barron, Frank Hecker, and Mitchell
Baker. I
<br>
just don't think that is the best list of people to, for
example, decide
<br>
that a Thunderbird Marketing module is needed, fill that role,
and
<br>
ensure that the module owner is fulfilling their
responsibilities.
<br>
</blockquote>
<br>
We in this group are not really responsible for submodules, e.g.
those under Thunderbird. This group is responsible for organizing
the structure of top-level modules. Consider them the peers of the
module to manage top-level modules. You need some way to grant new
top-level modules, possibly even retire some, have "unowned"
top-level modules be transferred to active owners again, and
resolve potential fights over a top-level module - and that's this
module ownership group. And we mostly only act out of proposals
from current or to-be module owners in this respect.
<br>
Owners and peers of the top-level modules are responsible for
their submodules. I'd expect "Thunderbird Marketing" to probably
be a submodule of Thunderbird, so it's the responsibility of the
Thunderbird owner and peers to decide if a module is needed for
that. </blockquote>
<br>
<blockquote cite="mid:50868351.7060809@KaiRo.at" type="cite">Note
that we traditionally didn't even have an actual module structure
for non-code stuff like marketing, as those might be better
organized in a different way, e.g. by the bodies caring about
shipping products. </blockquote>
that is exactly what Kent and me were trying to say; the module
system does not necessarily cover things like Marketing, overall
product design, monetization and the roadmap for the future. <br>
<br>
There aren't any "modules" for these; but these are precisely the
tasks that I feel JB was describing when he showed the slide from
"Das Boot" (*Community to the bridge*)<br>
<br>
<blockquote cite="mid:50868351.7060809@KaiRo.at" type="cite">That
said, we have added some non-code modules in the last year or two,
but we're still not completely convinced that this would be the
right thing to do for everything. I don't think we have a Firefox
Marketing module, for example, this just falls to the appropriate
team inside the paid staff right now, AFAIK.
<br>
We have the marketing responsibility in some submodule in
SeaMonkey, and the SeaMonkey project never asked the module
ownership group for how to form submodules like that - and doesn't
have to.
<br>
</blockquote>
I believe Thunderbird needs this. And an overall decision process on
product design - who is for, where is it going? And I don't think
that these have to be necessarily filled by programmers.<br>
<br>
Axel<br>
<br>
<br>
<div class="moz-signature">-- <br>
<style type="text/css">
.myName:hover { font-size:13pt; text-shadow: 3px 3px 4px rgba(200,250,200,0.7);}
</style>
<div id="testSignature" style="width: 65%; padding: 0.8em 1.2em;
font:x-small verdana; color: #444; box-shadow: 4px 4px 9px -2px
rgba(0,0,0,0.65); border-radius: 1em; padding: 0.4em 2em;
border: 1px dashed #444; background: rgb(230,240,163);
background: linear-gradient(to bottom, rgba(230,240,163,1)
0%,rgba(210,230,56,1) 50%,rgba(195,216,37,1)
51%,rgba(219,240,67,1) 100%); background:
-moz-linear-gradient(top, rgba(230,240,163,1) 0%,
rgba(210,230,56,1) 50%, rgba(195,216,37,1) 51%,
rgba(219,240,67,1) 100%);">
<b class="myName" style="text-shadow: 1px 1px 2px
#DDD;cursor:pointer;-moz-transition-property:font-size;
-moz-transition-duration: 0.5s;">Axel Grude</b> [T]
<br>
Software Developer
<br>
Thunderbird Add-ons Developer
<span style="color:#666666; font-size:xx-small">(QuickFolders,
quickFilters, QuickPasswords, Zombie Keys, SmartTemplate4)</span>
<br>
AMO Editor </div>
</div>
</body>
</html>