| [technology-pmc] Re: Egit proposal |
|
Shawn, Robin, Phillippe, This is very cool - I'm really looking forward to eGit. However, I would like to have a bit of a revised proposal. Specifically, two things: (1) the "Scope" section is the key in a proposal: the scope defines what the project is about and what it is not about. Your scope section paragraph 1, sentences 1, 2, and -1 are good, but after that the paragraph isn't really about the scope of the eGit project. They are good words, just not "scope" words. Scope paragraph 2 seems to imply that the scope of the eGit project includes the Platform Team component. I think you meant to say that the eGit team intends to become committers on the Platform Team component (because you want to contribute and create extensions for DVCS), but that's not really part of the scope of the eGit project, per se. It's a nice thing to say in your proposal, but again it's just not "scope". Scope paragraph 3 is also not about the scope of the eGit project directly. It's important to do that and to talk about that in the proposal, but it's not "scope". The scope section should also be clear about whether eGit is about git or about DVCS in general: that's an important scope distinction. (2) Eclipse is about "extensible frameworks and exemplary tools" although most users just see us as "free tools" - but we're not - we're about "extensible frameworks". Thus the scope should explain how the eGit project is going to create frameworks for building git tools (and then an example of how to do that, i.e., the exemplary tools). Cheers, Bjorn Anne Jacko wrote: Mike and Bjorn (cc Tech PMC, Shawn, Robin, Philippe) -- |
