That shouldn't be an option since Yuren and Alexandre will be continue providing support to the module as co-owners, but not day-to-day engineering.
On Thu, Oct 2, 2014 at 4:56 PM, Gervase Markham <[email protected]> wrote: > On 02/10/14 05:29, Tim Chien wrote: >> This is the reality. I don't really know how our module ownership can >> reflect the reality while sticking with the rules. Please advice. >> Thanks. > > Hi Tim, > > I would say that you don't want to have someone listed as an owner who > is not currently involved in the code. Sometimes people who have > knowledge of a code area but very little time to work on it are made > peers, sort of "emeritus", so you could do that. > > The owner should be the person involved with the code who has the best > knowledge of it and who makes the decisions about what goes in, what > stays out, how design is done and so on. The person with whom the buck > stops. If there isn't really such a person yet, it's OK for a module to > have no owner. That's just reflecting reality. > > Gerv > -- Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox OS, Mozilla Corp. (Taiwan) _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
