Sharing code in private branches between teams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
William Grant |
Bug Description
We need to be able to share and reference code between teams internally within our company. All our code, open sourced or otherwise, should be accessible by default to any member of the company.
The user story goes like this:
As an employee of our company I can access, branch and submit fixes to any code that the company owns by default once I am a member of the company's launchpad private team, but should not be receiving any email as a result of this access by default. This is so that it is easy to share my code with other teams in the company and improve it through their feedback and scrutiny and I can learn from looking at the code generated in other teams within the company.
As this has been under discussion previously there are some existing bugs relating to possible solutions and workarounds for this:
Barry contributed this list: (Thank you!)
https:/
This one almost definitely addresses my recent attempts to join ~canonical to ~private-
https:/
Probably not related
https:/
The uber-issue
https:/
Similar "constraint not satisfied" error
Changed in launchpad-registry: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: feature |
Changed in launchpad-code: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: canonical-losa-lp |
tags: | added: disclosure |
tags: | added: sharing |
Changed in launchpad: | |
status: | In Progress → Fix Released |
This issue was discussed at the 2009-09 team leads meeting. This is very hard, it is not a registry problem, it is a launchpad problem. This requires a rethink of launchpad ACL. It was suggested that the Launchpad architect do a spike solution during the 3,1 to evaluate problems. If the problems seem solvable, ACLs could be a focus of the 3.2 series.
If this issue is just about code, this bug should be move to launchpad code where a non-comprehensive solution can be found.