Upstream Android Build

Registered by Zach Pfeffer on 2011-04-28

This topic will discuss which changes we can upstream.

* What should be upstream to AOSP?
* What should be upstream somewhere else?
* legal aspects..
  * Copyright
  * Agreement with AOSP
  * Can we accept patches from outside of Linaro for Android...

After this session we should know:
 1. if we can take in patches from outside
 2. if we can take code from LEB and push to AOSP (or what action in needed)
 3.

Presentation to get this session started https://docs.google.com/present/edit?id=0AfbNxiGaNujWZGhxMnFocjJfMTNnZjJ2ZmRkNQ&hl=en&authkey=CNPslfcC

Possible Action Items from the discussion:

1. Check with legal to ensure that our contributor agreement allows people to contribute code and binaries and that those contributions can be sent upstream or can otherwise be distributed under some other licensing scheme.

2. Investigate having people submit to AOSP and then pulling the changes from AOSP as a way to possibly make licensing easier.

3. Set up a way to track patches from origin to destination.

4. Write guidlines for Android submissions.

5. Check that we can pull patches from outside.

6. Write guildlines for multihomed patches (that may go to Ubuntu and AOSP).

7. Create legal training.

8. Define working group submission policies.

9. Define landing team submission policies.

-Zach

Session notes: http://summit.ubuntu.com/uds-o/meeting/linaro-android-o-upstreaming/

Blueprint information

Status:
Not started
Approver:
Zach Pfeffer
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items