The survey has been going on for more than one week now and the trends are only enforcing themselves. Let's summarize it:
First, the audience represents many non-commiters (2/3) though the commiters are still quite represented. That's quite consistent with what I was expecting, the survey was published on the planet, some newsgroups and through twitter and as such targeting commiter or adopters following quite closely what's happening in Eclipse Modeling.
Concerning the package size, we're right now at 250MB, it looks like it's mostly ok but being a bit smaller would still be nice.
As the package is an SDK we could probably drop most of the dupplicated javadoc in the plugins.
This one is interesting, it's something we're hearing and hearing again at each Eclipse conference, users do want more documentation, moreover best practices are hard to reveal through the wiki, newsgroup and online help jungle.
There is probably something to do here but, hey, there is an EMF Book already, an Eclipse Modeling one and everybody can contribute on the wiki, so why isn't this urgent need covered yet ?
It might be because:
- People are not even aware of these books or books are old fashioned now : all content should be on the web !
- It's so hard to understand what each project is providing that one really needs some Modeling Guide.
- As a user you always want doc even if you won't ever read it, it just gives you the confidence that the technology is not going to vanish in a glimpse.
- [ ] <----- any opinion expressed through the comments
It's even more disturbing when ...
yes, most people would be willing to give time to make this happen. We might need to do something here, maybe crowdsourcing the doc would do the trick... What is pretty sure is I wouldn't like it if Eclipse Modeling commiters spent half of their time documenting : we should make it easier for the adopters to contribute back.
And yes, writting doc and books takes a huge amount of time !
I asked another related question in the survey about "examples". In fact examples are way easier to provide and in my opinion are more valuable in most cases. And when you look at it, each project is already building its own examples, but these examples cannot be composed in some way. Just like Toast is a best practices application for OSGi, we would need a modeling one.
At its beginning the Amalgam project was providing some; yet since these examples were not part of their target Eclipse project (EMF examples in EMF, ATL examples in ATL) they were not maintained correctly. As a result they are not reflecting the "state of the art" of Eclipse Modeling anymore... Maybe for the next release !
I'm done for the strong trendes, others questions like "Having on the shelf design and generation tools" or "Domain focused UI instead of component focused one" were quite uncertain.
A few more ideas or questions have been given through this survey,
It will take another blog post to describe those.
Thanks again for your feedback !