Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 529499

Summary: Please answer this Question on Github
Product: Community Reporter: Christian Dietrich <christian.dietrich.opensource>
Component: BugzillaAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Christian Dietrich CLA 2018-01-08 03:20:06 EST 
Please answer this Question on Github:
https://github.com/eclipse/xtext/issues/1159
Comment 1 Eclipse Webmaster CLA 2018-01-08 15:39:15 EST 
Done.

-M.
Comment 2 Christian Dietrich CLA 2018-01-08 15:45:22 EST 
Ok thanks. But the answer dös not help with our Problem. What can we do
Comment 3 Eclipse Webmaster CLA 2018-01-08 15:55:47 EST 
Either:

1) You need to be elected to the TMF project.

2) You need to have a TMF committer manage the versions and milestones for you

3) Xtext needs to stop being a component of TMF and become a product of it's own.

Frankly I don't recall why Xtext isn't a product already, but I'm sure there's a reason.

-M.
Comment 4 Christian Dietrich CLA 2018-01-08 15:57:04 EST 
WHO are committers and the project Leads of TMF in Sven efftinge is not
Comment 5 Eclipse Webmaster CLA 2018-01-08 16:29:33 EST 
Sven is one of the PLs on TMF, and the list he provided is the list of active TMF committers.  It's also clear that there is some overlap of committers between TMF and Xtext which explains why some Xtext committers can update bugzilla and others can't.

-M.