Mitchell asked for a list of outstanding module creation requests. There
have only been 2 posted to mozilla.governance which do not seem to have
been resolved.
Gerv
Build/Puppet
------------
(Proposed by Dustin Mitchell on 2012-06-22)
Release Engineering and Release Operations are building a new puppet
implementation to manage release engineering systems. We would like to
make this distinct from the "Build and Release Tools" module, since the
code, review process, and experience required are substantially
different from that module.
Name: PuppetAgain
Description: Puppet configuration for release engineering systems
Owner: Dustin J. Mitchell
Peers: Justin Wood
Source Dir(s): http://hg.mozilla.org/build/puppet
Bugzilla Component(s): mozilla.org::Release Engineering: Machine
Management, mozilla.org::Server Operations: Release Engineering
Discussion Group: #build
Content HTTP Headers
--------------------
(Proposed by Gervase Markham on 2012-06-20)
This is a proposal for a new Core module:
Name: Content HTTP Headers
Description: HTTP headers related to content, e.g. User-Agent,
Content-Type, Accept. (Transport-related headers are the
responsibility of the Necko module owner.)
Owner: Gervase Markham
Peer(s):
Source Dir(s): None
Bugzilla Component(s): Core/Networking: HTTP
URL: https://developer.mozilla.org/en/Gecko_user_agent_string_reference
Discussion Group: mozilla.dev.platform
Discussion around the User Agent string, particularly, requires
balancing of a large number of perspectives from across the organization
- compatibility, developer relations, standards compliance, privacy -
and so does not easily fall into the remit of any one existing module.
It would be useful to officially allocate decision-making ability in
this area.
