Skip to content

Instantly share code, notes, and snippets.

@joshuamckenty

joshuamckenty/COUNTING.rst

Last active December 21, 2015 03:29
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save joshuamckenty/6242935 to your computer and use it in GitHub Desktop.
Save joshuamckenty/6242935 to your computer and use it in GitHub Desktop.
Download ZIP
COUNTING.RST Our community (being OpenStack) is guided primarily by aspirational standards, rather than expository regulations. We have HACKING.rst for coding style. This is a proposed COUNTING.rst to talk about how we measure ourselves. It's based on conversations I had with Stefano Maffuli and others, after the launch of Stackalytics.com and s…
Raw
COUNTING.rst

COUNTING.RST

Open Source projects and communities, like most things, are full of humans. Humans have egos.

WE FOCUS ON the CARROT, and not the STICK
  • COUNT things in a way to PRAISE many, without CONDEMNING some.
0. Count all the things
  • Don't report on just coding
    • Report on bugs filed
    • Report on reviews
    • Report on meetups hosted
    • Report on email threads contributed to
    • Report on speeches given
    • Report on deployments achieved
  • Count all the repos (http://git.openstack.org/cgit)
1. Don't count LOC except as a last resort
  • Count number of modules
  • Count number of tests
  • Count change to cyclomatic complexity
  1. Count within a module, not across modules
  2. Count within a language, not across languages
  3. Count company absolutes, if you have to, but favor counting deltas
    • Increase in contributors (by percentage)
    • Increase in rate of contributions (by percentage)
  4. Count WITH, not VERSUS
  5. Favor INCLUDING more things in the counting

Projects that count with these principles in mind could be referred to as "Open Count Software" or something.

@zehicle
Copy link

zehicle commented Aug 30, 2013

I like the specifics and the framework of this. Thinking about the cultural aspects, I think you may be tipped more towards tracking & reporting (which are "softer") than counting. I like the tracking deltas > tracking absolutes.

It's true, what's measured gets results. I'd add what results you want to get in these counters because I think that would add valuable perspective.

(note: Victor Lowther is reading over my shoulder and thinks that you need to provide a link for cyclomatic complexity)

@dlenwell
Copy link

http://en.wikipedia.org/wiki/Cyclomatic_complexity

@fifieldt
Copy link

More "all things" that may need different counting methods: Documentation, Translation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment