Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 371118 - LTS Maintenance committer agreement and processes
Summary: LTS Maintenance committer agreement and processes
Status: RESOLVED FIXED
Alias: None
Product: Working Groups
Classification: Eclipse Foundation
Component: LTS (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: LTS Infrastructure Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-09 13:25 EST by Andrea Ross CLA
Modified: 2015-05-01 14:27 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Ross CLA 2012-02-09 13:25:32 EST 
This ticket is for tracking discussion and work related to maintenance committers. This includes:
1) How are they appointed?
2) The agreement they need to sign.
3) How do they resign?
4) How are they removed?
5) What kinds of auditing will we have?
Comment 1 Denis Roy CLA 2014-05-27 09:01:30 EDT 
Moving to the Working Groups section.
Comment 2 Denis Roy CLA 2015-05-01 14:27:27 EDT 
Coincidentlally, we had a request for this just this week.

As I understand it, LTS is reserved for EF member companies, and they may select who can become an LTS committer.  None of this needs to follow the meritocratic process of the EDP.

Requests come to webmaster@eclipse.org.  LTS committer must have an Eclipse Foundation account.  Internally, we have a process to track these individuals as well as their relationship to the member company. We've also documented the process in our internal Knowledge Base (#265).


> 3) How do they resign?
> 4) How are they removed?
> 5) What kinds of auditing will we have?

I believe it is entirely up to the member company to manage their appointed committers, and to inform us of which action to take (add, remove, etc).

I'm closing this as fixed since we've documented a process.