jbucata: The situation is a bit ironic. I don't believe that IBM, Intel, et al, are process-ignorant. It is more that they aren't always very adept at following processes in place for free software projects. I've heard occasionally that this can happen when the company doesn't allow access to the cvs server (making it much harder to participate fully). So education may have to happen in IS more than engineering; I don't know.
For Eclipse (which is largely run by IBM) I've found that the processes do exist, but they aren't disseminated very well. So, for instance, Eclipse nightly builds include automated tests, but figuring out how to run those tests for yourself is not trivial. My impression is that inside IBM, the releng groups runs the tests and nobody sees much need for anybody else to know how to run them. This is a bit contrary to how things are usually done in the "free world".
Yesterday, after a lot of bug fixing and also a couple of questionable hacks, I managed to get Eclipse to start up using gij. This is pretty exciting! There's still a huge amount of work to be done, though, and for the time being I can only do it in my spare time. I expect progress to be slow.
My long term goal for Eclipse is to make it very useful for free software development. Right now we have an integrated development environment on the client side, and then another one (think sourceforge) on the server side. So the next step is to more fully integrate across that boundary. Some ideas along those lines:
- Let the project inform Eclipse about its processes. For instance, easy automation of patch submission, bug tracking, etc. Likewise, things like standard build commands, testing, could be set up automatically on a per-project basis.
- Perhaps if you have a project open in Eclipse it could automatically register you as "online" for instant messaging through the server. Closing the project would deregister you.
- The project could tell Eclipse about its coding standard, and Eclipse could adjust its editors automatically.
- The project could list its dependencies and Eclipse could automatically check them out (or otherwise ensure they are installed).
Lilo and Stitch. I enjoyed it, though not as much as Monsters Inc. Parts were a bit cheesy for my taste.