GPL only dictacts you must release source code your *change*, and this is again *only* if you charge for the given product.
If the product is free then you don't have to release the source.
If you are adding new parts those are entirely your property to do with as you will.
Should be interesting to say the least to see this feature implimented in a browser, and i would suggest editing up BlueIDE rather than making your own from scratch.
CVS is a good idea, question stands... are there many users which would actually use it?
See i've been over that very question a good number of times over the past month, and ways have been devised which would actually be more benificial to users.
A system which actually would help keep teams developing as a whole no matter where they are rather than individuals who are just editing up and uploading source others have.
I mean when you think about it, alot of professional solutions are a good idea in theory... but when given to the uninitiated and people who can't normally work in a team will just become fancy unused features.
If on the other hand you work around the premise that your dealing with people who are not putting in 8hrs a day and who are not trained or just used to working with others, then adapting things to fit that given premise. You can come up with features that are not only useful but will be regularly used in order to keep projects going.
I don't want to say to much really, cause partly 'competition' and partly i'm a lil afraid of what darkgirl would do to me :-|
but you can be sure this isn't some sort of novel feature cooked up just to make an IDE unique from the pack, there are alot of features and effects which although feature in other dev enviornments ... are not designed around the user, but more just to be a feature.
So what i'm trying to say is, your not trying to make your IDE popular through an untested brash feature.
If you truely want to make something which will be used because of a feature then sit down and think about just how it would need to be setup and used.
CVS is great, if you can understand (or have) a server with which to setup your CVSROOT directory. This however is a pain in the ass because you have to still do it manually with CVS.
The Standard user doesn't know what Shell is, let alone how to use it and set everything up.
Same goes for a computer networking source... i mean it's fine and dandy saying 'well people will be given passworded access.' but what exactly will they be accessing and how?
you do something like this wrong and it'll be completely counter productive, you need to setup guidelines and boundries within the program itself and figure out how you'd want it to react and work.
