Launchpad has statistics, but there's no way to look "back in time" at previous releases that I can find. Are there any ideas for how to do that by looking at the
patches from contributors applied --------------------------------- Miro 1.0 4 Miro 1.1 2 Miro 1.2 1What this table shows is that almost all development is being done by PCF. This table troubles me the most--more about that at the end. On to stats from Bugzilla.... First off, our Bugzilla data before October is probably mediocre, so I'm not really even looking at that. After that, the data has been getting better as more people are helping to triage and annotate bugs. Also, some bugs never make it to Bugzilla. I know that sedatg and some other people mention issues to us on IRC semi-regularly which get fixed, but aren't tied back to Bugzilla bugs. It's probably fair to say these stats are indicative of things but aren't 100% accurate.
Miro 1.2 stats ============== length of cycle: 70 days bugs fixed: 82 total By Operating System: all: 26 gtkx11: 14 osx: 13 win: 29 By Severity: blocker: 1 critical: 12 major: 5 normal: 58 minor: 2 enhancement: 4 By Component: Channels 11 Download 4 Feeds 1 Guides 3 Install 5 Library - New 3 Menu - Shortcut 3 Min - Max 1 Playback 14 Playlists 2 Search 6 Startup 10 Storage 1 System settings 2 User interface 5 main 11 bug reporters: 24 total pcf people: 7 community: 17Miro is benefiting greatly from the community with testing and translations--that's really great and it's helping a ton! However, Miro is not getting much help from the community with code and PCF is pretty much funding all development. This is troubling. Miro is getting bigger over time and the complexity is growing, too. There are a lot of moving pieces in the stack of external components that Miro relies upon. There are two ways for Miro development to scale well:
- more contributors
- additional funding for PCF so that they can fund developers