gistfile1.txt

------
Marek

Only:
c# binding, intellisense, editor, debugger, project management, unit test, semantic highlighting

throw out:
version control, all options, refactorings, all stuff expect the stuff above, most/all pads
------

Grendel

throw out:
Toolbars, ClassBrowser, Document Outline, Log pad, ChangeLog integration

------
Alan

throw out:
Moonlight, prj2make-sharp (project)

------
Mike

throw out:
+ Toolbars

+ Pads:
 - Class browser pad (assembly browser should fill that role)
 - Todo list pad (useless)
 - Help pad (useless - online doc/monodoc)
 - Internal log pad (that's what we have log files for)
 - Document outline (breadcrumb does that)
 - test result pad - 'error list pad' can fill that role - expect if we're going to plan auto layout, then
we could do a special unit test layout, but I would keep it simple.
 - version control pad (output pad can fill that role)

+ global policy dialog - should be integrated in the options (and already is, policies should be redesigned)
+ changelog addin/commit style panel
+ makefile integration (I mean that, it's buggy like hell, generation can continue, but atm it can be used as project format for example)
+ Much version control gui (esp. the stuff that's not working stable with git - branches gui ?)
+ Addin manager - can't the update manager do that keeping things up to date ?
+ 'web' items in the help menu - that what google is for
+ ASP.NET stuff - nice to have, but hard to maintain
+ Code metrics 
+ docking system - rather do it like x-code and have 'modes' for debugging/gui design/unit test.
The feature people really want from that is side by side documents - and we can't do it.
+ regex toolkit (even if I like that one)
+ vb.net binding (we don't really support vb.net atm. - we should focus on things we can bring to a certain usability level,
that's atm only c#)
+ C binding for the same reason
+ Deployment - I'm even not really sure what that is good for in MD
+ 

All projects in extras - for example:
PythonBinding, ValaBinding, PyBinding, JavaBinding, LuaBinding, MonoDevelop.CodeAnalysis, MonoDevelop.Database,
MonoDevelop.Profiling, BooBinding

keep:

gettext addin and stetic (need both to develop md)
ilasm binding (not really hard to maintain and a good example for a minimal backend binding)