On Sat, Nov 21, 2009 at 10:51:58AM -0800, Nathan Kurz wrote:
> HowToContribute is generally very clear --- much clearer than most
> such pages. Linked style guide is great.
>
> I got a little lost when it got to the "Create a JIRA Issue Stage".
> Not lost to the point of actually being stymied, but if playing the
> canary I might have given up there.
>
> 1) Explain what JIRA is, and why one might want to use it.
> 2) Explain what an Issue is, and why this awkward term is used.
> 3) Mention that one needs to create an account, and that the 'Create
> New Issue' link does not appear until you are signed in, and that no
> amount of searching will help you find it until you have done this.
Nate, your fresh perspective was *very* helpful, thank you!
It's impossible for me to perform this sort of audit myself. I have the hours
available to do the heavy lifting writing code, but the curse of knowledge
blocks me from editing my own material effectively.
I think editorial review is a very good use of limited resources. In the
near-to-medium term, if you and Peter can focus on taking notes and
identifying sections which aren't transparent or optimal while performing
limited coding tasks, we can maximize our collective coding efficiency.
This also fits well with the big picture. I hope that Lucy can set a high
standard for user-friendly API design and simplicity. We're all familiar with
how well usability testing works for web pages. Let's make usability testing
of our APIs and code base standard operating procedure for this project.
Marvin Humphrey
