Sounds good. I was referring to the Scope section of the Tools charter which I assume constrains it’s projects. But since we’re the second incarnation of the CDT, I’m not sure what the original scope was. If there was one, and only John
D may know for sure, we’ve been stretching it for years
At any rate, I’m happy to work with Wayne and get something written down when he’s back.
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Mike Milinkovich
Sent: Monday, October 29, 2018 10:11 PM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Blog on the New CDT
I guess I was unclear. I wasn’t asking about the top-level project charter. TLPs have charters. Projects have proposals. Both are supposed to have clear scope statements. If CDT’s has been lost in the mists of time,
maybe we should do a new one since the mission is changing.
Wayne is out this week, but hopefully he can provide some guidance when he returns.
Good question. I don’t think we have a charter. That would likely have us fall under the Tools Project charter which is here:
It does state “for the Eclipse Platform”. I’m open to guidance on how to proceed, either vote in a new charter for CDT that overrides that, or move CDT to a top level project that enables us.
Mind you, is Theia an Eclipse Platform (or is it? Still fuzzy on that). It’s clearly one of the targets of our efforts. I can imagine other IDE projects becoming interested in that. I wonder if we need a more Tools
level wide approach to this.
I have a pure process question. Eclipse projects are required to work within the scope statement from their project proposal. CDT pre-dates the Eclipse Foundation. Does anyone know what the scope statement actually says?