FYI:
When I started doing in patches for C::B, I did not know what was a C::B owned module or maintained by someone else. I looked though the code and here are the ones that looks to be maintained by people outside of the C::B team. I am looking for feedback on wrong info and missing info. Then maybe someone can make a Wiki page with the data.
wxScintilla (was modified for use by Code::Blocks)
sdk/wxscintilla
http://wxcode.sourceforge.net/components/wxscintilla/
Scintilla
sdk/wxscintilla/src/scintilla
http://sourceforge.net/projects/scintilla/
wxFlatNotebook
sdk/wxFlatNotebook
http://sourceforge.net/projects/wxflatnotebook
TinyXml
sdk/tinyxml
http://sourceforge.net/projects/tinyxml
wxPropertyGrid
sdk/propgrid
http://sourceforge.net/projects/wxpropgrid
Squirrel
sdk/scripting
http://sourceforge.net/projects/squirrel
Squirrel SqPlus
sdk/scripting/sqplus
http://wiki.squirrel-lang.org/default.aspx/SquirrelWiki/SqPlus.html
astyle Artistic Style
plugins/astyle
http://sourceforge.net/projects/astyle
wxPdfDocument
plugins/contrib/source_exporter/wxPdfDocument
http://wxcode.sourceforge.net/components/wxpdfdoc/
bzip2
plugins/contrib/devpak_plugin/bzip2
www.bzip.org
Support Functions/Classes
wxBase64
sdk/base64.cpp
http://www.frank-buss.de/wxwindows/winodocs/html/functions.html
Port's of external code that is highly modified for use in Code::Blocks
KeyBinder maintained by CodeBlocks' own Pecan
plugins/contrib/keybinder
is a port of wxKeyBinder from wxCode
http://wxcode.sourceforge.net/components/keybinder/
Tim S
keyBinder originally started as wxCode, but half of it is now tied to CB.
It is maintained by pecan
Has the CB team considered using someting like vendor branch management (http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html) for these packages?