Thanks for the comments, and I appreciate the feedback. If anyone does an follow-up analyzing JIRA data for attachments (although I don’t see how this is possible), I’d appreciate the information.

Best
Peter

…unless SS agreed separate licences with each owner of the patch.

This of course means that going forward, no new patches from the community can be accepted either.

It does seem that there will now be a need for a community maintained version and it will be interesting to see how active the Spring community really is willing to be.

I don’t think that just analyzing committer-names is useful at all ?
I mean noone other than springsource employees have commit rights, have they ?

I think to get a real impression about the open-source commitment would be to analyze how many people opened jira issues and how many of them
- ‘just’ reported a bug and left all the work to spring employees.
(but nevertheless found a bug, that the springsource employees didn’t)
- took part in a good discussion leading to a good improvement of the spring-framework by a springsource employee
(but nevertheless spent their time and enthusiams to improve the framework)
- provided a patch in the jira issue, which a spring employee then commited under his name.

I’m afraid such numbers can’t be calculated, maybe just the gut feeling of springsource employess can lead to some insight.

Your numbers alone don’t give any useful insight to me. It’s like looking at committer names of our own company-CVS and wondering, why no name of any customer appears there.