LGPL/GPL user-space projects in the AOSP
- There was an email debate about (L)GPL-licensed code in the core Android
  project, that should really have taken place on a public mailing list.
  The CTT will write up the results of this debate and post a clearly-worded
  policy.
- conclusion: license choice is: Apache2, BSD/MIT
  - some components are (L)GPL, but those are rare exceptions
  - exceptions: webcore, bluez
- Make it more clear what pieces are part of the core platform
  - Core pieces: mentioned in the default manifest
    - Included in default build
    - Guaranteed to be tested, supported, backwards-compatible
    - Should only be licensed under Apache2, BSD/MIT
  - Platform/arch support: glue necessary to target the platform
    to a particular piece of hardware
    - L/GPL is a little more acceptable here, since these pieces
      aren't part of the core platform.
  - Other projects
    - shouldn't be hosted on kernel.org, but we make it easy to
      create a manifest that pulls pieces from elsewhere
    - In the future, we would like to provide hosting for experimental
      projects

Gerrit2 switch-over
- make transition next monday morning (26 Jan 09)
  - warning email has been sent
  - warning banners already up on review.source.android.com.
- mostly ready, just a couple of features necessary
  - notify people about new/unclaimed changes via email
  - inter-diff patch support isn't ready yet, but will be before
    we switch
- so far, very fast and very stable
- replication is set up (postgres replication isn't great)
  - we'll also back up to other machines outside of the primary datacenter
  - failure recovery could take an hour to a day
  - some changes/comments could be lost
  - A better recovery scheme is a goal for the future

JIRA switch-over
- Looking for more resources to handle the migration.

public wiki
- Looking for more resources to handle the setup and maintainence

* Talked about possibilities for monitoring and maintaining the open-source Gerrit2 and Jira instances.  Made a decision about where to host them within the Google network.

* Some more progress has been made on setting up a wiki to host documents by open-source contributors.

* Talked about the benefits of setting up a public registry of application-defined intents and permissions, as well as a database describing the capabilities of various shipping Android devices going forward.

* When Jira is ready to go, we will migrate the existing bugs from code.google.com.

* Gerrit2 is coming along, and will soon be ready for beta testing.  Once it's ready, the Gerrit1 instance will be taken down and its data will be migrated to the Gerrit2 instance.

* We need to produce and maintain a document describing the steps for officially adding a new git project to the AOSP.

* Talked about copyright headers.  We continue to prefer that files are attributed to "The Android Open Source Project" rather than a particular individual/company.

Core Technical Team Meeting 2008-12-16

Agenda:

External bug database
Further code contributions from Android Open Source Project
Community wiki
Other business

External bug database

 * Bug database chosen, need to go through security audit for handling security-related bugs.
 * Will host locally to help maintain security.
 * Discussions for naming of components will happen on Core Technical Team list.

Further code contributions from Android Open Source Project

 * The Android Open Source Project has a new branch to offer.  Need to make roadmap for how this branch will be merged into the mainline, protecting current contributions.
 * We need to automatically generate documentation as part of this.

Community wiki:

 * Core Technical Team will work with partners to get base of conversations happening on the wiki and mailing lists.
 * Will create netbook working group mailing list and section of the wiki.

Other business:

 * Would be nice to have some sort of "Android Developer Days" to help share technical knowledge.

Next meeting: 2009-01-06