>I’m sitting here with a blizzard going on outside, stuck on a problem with a XSL Content Assist, and reading about all the e4 chaos. Personally, I think having e4 is a good thing, and I don’t think anybody or any blog I’ve read has disagreed with that. What I do see happening is that there still is difference between a corporate mentality and an open source agile mentality.
I’m one of the biggest proponents for visibility. One of my on going fights at work is to try to make us more open, to bare it all. There is resistance to this for many reasons, and most arguements are trying to explain why. Sorry the damage is done, let’s move on and not make the same mistake again. Regardless of good intentions, the eclipse platform needed at least a bug report open to track these changes. There is now an e4 wiki page, but nothing I believe before the announcement.
Unfortunately, this particular project came in under the radar. Compare that with the XSL Tooling project (I’m biased as a committer here so take this with a grain of salt.). Bug 89469 was started in 2005, it was entered by a community member wanting to contribute code, it sat idle for a long time, until Chris poked some embers, and finally the XSL Tooling project came to life. The whole process has been in the open.
One thing that e4 has shown, and I hope that all projects take it to heart. If you are going to be doing something, let the community know that you are thinking about doing something. At least open a bug report on any changes you are working on. The more open the process, the better they will feel that the wool isn’t being pulled over their eyes.