Message: previous - next
Month: February 2012

Re: [trinity-devel] Improving community involvement

From: "David C. Rankin" <drankinatty@...>
Date: Wed, 29 Feb 2012 11:58:06 -0600
On 02/28/2012 07:46 PM, Darrell Anderson wrote:
> Lastly, we need people who have some skills to start helping with bugs. Many bugs do not require C++ skills but require makefile, cmake, automake skills, etc. Other bugs require little more than knowing how to use grep and sed once the solution is realized. People don't need commit access, just get the patches submitted. Somebody who is qualified will review the patch.
> Comments? Ideas?
> Darrell

All of the ideas are excellent. Concerning the bugs specifically, is there a way
the current bugzilla could sort or categorize bugs so that they are loosely
grouped by the discipline needed to fix them? For those that don't require an
in-depth level of c++ knowledge, etc., it may help those willing to help wade
through and find something they could handle.

The submit patch, then review/approve is a great safeguard, but the
review/approve still puts a significant demand on the reviewer/approver :)

It would even be a help if those who know/review the current active bugs could
dump a list of "need help with this" to help prioritize which should be attacked

Just my "Comments? Ideas?"

David C. Rankin, J.D.,P.E.