Fw: [Aust-NZ] Re: [OSGeo-Discuss] Open Source development metrics

[Bruce.Bannerman at dpi.vic.gov.au]

IMO:


Would someone like to have a go at developing a first cut of some generic 
metrics that we can develop for people to use during performance planning 
sessions?


Jody's suggestions make a good starting point. 


Don't be shy, first in, first served.



Bruce Bannerman





----- Forwarded by Bruce Bannerman/DPI/VICGOV1 on 29/05/2008 10:36 AM 
-----

Bruce.Bannerman at dpi.vic.gov.au 
Sent by: aust-nz-bounces at lists.osgeo.org
29/05/2008 09:42 AM

To
Jody Garnett <jgarnett at refractions.net>
cc
OSGeo Discussions <discuss at lists.osgeo.org>, Aust-NZ OSGeo 
<Aust-NZ at lists.osgeo.org>
Subject
Re: [Aust-NZ] Re: [OSGeo-Discuss] Open Source development metrics







IMO: 


Thank you for the insights Jody. 


You have made some excellent suggestions that we as an OSGeo-AustNZ / 
ANZLIC community can build on. 


Bruce 







Jody Garnett <jgarnett at refractions.net> 
Sent by: aust-nz-bounces at lists.osgeo.org 
29/05/2008 08:15 AM 


To
OSGeo Discussions <discuss at lists.osgeo.org> 
cc
Aust-NZ OSGeo <Aust-NZ at lists.osgeo.org> 
Subject
[Aust-NZ] Re: [OSGeo-Discuss] Open Source development metrics








Bruce.Bannerman at dpi.vic.gov.au wrote:
> However this is probably unrealistic  as to do this the developer will 
> have to have existing credibility within the community and there may 
> be good reasons why the community does not want to have 'product X' 
> included.
So start slow with some metrics reflecting getting involved in the 
community and making contacts.
> Does anyone have any examples that they use or thoughts on the above?
> I do understand that metrics can be abused, may be meaningless and may 
> not be the best way to handle this, however we have to start somewhere.
What a hard question ...

Try for a couple of the metrics you use when evaluating open source 
projects:
- open development; what is their level of involvement on a scale of 
learning, helping, submitting patches, commit access, responsibility, 
responsibility
- documentation and help (assume number of pages written/edited; or 
number of questions answered on the user list)
- quality assurance: number of test cases produced
- number of patches submitted, or number of bugs depending on level of 
involvement... consider putting this on a scale so long standing bugs 
are worth more :-)
- frequency of release (number of releases the employee assisted with 
via either tagging and packaging, testing; announcing etc...)
- etc...

I recommend approaching the specific communities you wish to be involved 
in and asking where help is needed.
> We have a window of opportunity to get some more developers working on 
> OS projects as the Performance Planning cycle re-starts shortly and 
> I'd like to help our developers get some constructive ideas to take 
> into their sessions.
Cheers,
Jody
_______________________________________________
Aust-NZ mailing list
Aust-NZ at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/aust-nz

Notice:
This email and any attachments may contain information that is personal, 
confidential,
legally privileged and/or copyright. No part of it should be reproduced, 
adapted or communicated without the prior written consent of the copyright 
owner. 
It is the responsibility of the recipient to check for and remove viruses.
If you have received this email in error, please notify the sender by 
return email, delete it from your system and destroy any copies. You are 
not authorised to use, communicate or rely on the information contained in 
this email.
Please consider the environment before printing this email.
 
 
 _______________________________________________
Aust-NZ mailing list
Aust-NZ at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/aust-nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/aust-nz/attachments/20080529/65d2e0f6/attachment-0001.html