| 
 Hi Doug, 
  
1. The project dashboard has been totally changed recently, 
without any notice to committers. I liked the old dashboard, and I had put a 
link to it on the dsdp/tm homepage. So my #1 feedback to Bjorn is: if you are 
planning any changes to publicly visible URLs, let committer know what 
you're up to. Don't we want to have open processes? I hate broken links 
like http://www.eclipse.org/projects/dashboard/dashboard_detail.php?project=dsdp.tm that 
used to work fine. 
  
2. Projects should not define the metrics 
themselves if they are publicly visible. The dashboard gets unusable if 
it's not totally clear what's visible. Projects could be enabled to use the DASH 
databases to make their own computations and publish them on their own 
homepages. But the common dashboard should work the same for all projects, or it 
gets totally confusing. 
  
3. I agree that different metrics would be 
useful in different phases of the project, but there should be ONE 
common definition of what is visible. 
  
4. Yes, being explicit about the formulas 
used is important. I don't think that SQL statements are sufficient. There 
should be some plaintext explanation of what's visible on a 
report. 
  
5. Regarding the new metrics: 
5a) dsdp.tm project is missing 
totally. 
5b) I liked the metrics on mailinglist, newsgroup and 
bugzilla activity, I'm missing those. I'm not sure that commits only is a good 
indicator. 
  
I've been using the dashboard before to look which projects 
seem very active ("green light") - in order to get inspired by them and see why 
they are so active, how they are promoting their stuff. For instance, I took the 
GMF project as reference for most of the TM homepage.  
  
So, for me it was useful to have projects compared against 
each other by common metrics. Perhaps it would make sense to think about other 
use cases of the dashboard (for whom do we make this?) 
Cheers, Martin -- Martin Oberhuber - WindRiver, 
Austria +43(662)457915-85
  
   
  
  
  
  Hi 
  folks, 
    
  I want to draw your attention to 
  the Eclipse Project Dashboard (http://www.eclipse.org/projects/dashboard/).  
  This dashboard is under construction, as noted at the top of the page.  
  The intention is to provide an activity gauge for various Eclipse 
  projects. 
    
  I would like to provide some 
  feedback to Bjorn on the usefulness of the information and changes you would 
  like to see on this dashboard.  My comments to Bjorn so far 
  are: 
    
  1.  Don’t apply a “one size 
  fits all” metric for projects; instead allow projects some latitude in 
  defining their own metrics of activity. 
    
  2.  Don’t treat projects in 
  incubation the same as mature projects containing multiple 
  releases. 
    
  3.  Be explicit about the 
  formulas used for “liveliness” and green/yellow/red status so that project 
  leads understand the system. 
    
  For the next PMC meeting, please 
  take a look at this page and the bugzilla entry.  I suspect this will 
  come up in the planning council meeting in Chicago, and I’d like to propose some 
  alternate ideas. 
    
  Thanks, 
  Doug 
      
 |