Basie Blog

Here’s my grading scheme for the tagging ‘team’. As you can probably tell, it borrows from the IRC and diff teams’ schemes.

20% – Participation

Whole lotta stuff falls under here. Attending IRC meetings and maintaining contact with the team on the blog and mailing list. Giving helpful feedback while not degrading the signal-to-noise ratio. Also giving feedback on UCOSP blog posts (if this is supposed to be a Basie-only grading scheme, move 5% to something else, like documentation). Keep contact with other team members friendly and constructive (Tony’s comment would be funny if it wasn’t so true).

30% – Functionality

Make sure that my contributions cover all basic use cases. All features I add beyond the bare minimum should be justified and fulfil what I anticipate the user needing. Submitted code should follow Basie’s best practices, and be easy to read. Ideally, it should also be easy to extend.

15% – Testing Coverage

All working code should be accompanied by test cases. Try to cover as much of the code as possible. Most of the time, test cases should be terse and easy to understand (although testing for complicated edge cases is inevitable). I should not focus on testing Django or django-tagging, except in cases where I’ve changed the default behaviour.

10% – Documentation Coverage

At the code level, all nonintuitive sections of code should be thoroughly commented (and if a section of my code raises a question during review, it was obviously not intuitive). Even if the code is clear, comments should be provided whenever a design decision was made. On a higher level, make sure that documentation of the design process exists, like on this blog or on a wiki. A short description of the tagging application should be provided with the code, for later developers who want a quick summary without delving into the code.

15% – ‘Enabler’

Keeping active on ReviewBoard: reviewing the patches I’ve been assigned promptly and giving critical feedback if anything’s wrong or missing.

(There’s a lot of overlap between this category and ‘Participation’.)

10% – ‘Final Presentation’

Not quite sure what to call this. Contributions to the screencast would fall under here. Another idea I had earlier was getting feedback from other UCOSP students on the UI aspect of tagging. If I have enough substantial approved and committed a week or two before the code freeze, I’ll give this a shot to see what suggestions I can harvest.