To quickly summarize:
1) Dave Bauer identifies the "lack of anyone doing anything about [open]
bugs" and the lack of "process or resources to deal with the bugs" as a
problem.
2) Tom Jackson identifies that there's little in-community support for
would-be contributors to get their changes merged into the codebase.
3) Tom Jackson identifies that there is "a lack of documentation of all
kinds".
Lets do a little wishful dreaming for a moment and brainstorm actionable
ways to try and address these deficiencies. Let me try to seed this
with a few questions:
How can we find resources to deal with bugs, support contributors and
write documentation? What would it take to get existing contributors to
contribute more? How can we recruit new contributors?
Would adequate funding aid in adressing these issues? In best-effort
accuracy round number estimates, what kind of funding levels would we
need to reach to achieve what kind of results?
If training were provided, could we transform more passive community
members into more active contributors and supporters? What kind of
training would be necessary? What subjects would need to be covered in
order to enable what kind of contributions?
...
Feel free to add more questions as appropriate, but especially answers
that have clear actions associated with them. I'll try to do my best to
collate the various actions and present them in a concise list. Then,
maybe we can try to find ways to make those things happen.
--
Dossy Shiobara | [email protected] | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[email protected]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
