I'd like to suggest a sightly different tact. Instead of writing
Guidelines, how about writing "How to get involved" (maybe we already
have one). Specifically, I'm thinking about a section on best
practices for working on an issue including assignment, patch
submission, and the related email to the dev list.
I have a dislike for stuff labeled "Guidelines"
-dain
On Jan 18, 2007, at 11:52 AM, Jeremy Whitlock wrote:
Hi All,
I was wondering if we had patch submission guide lines? If we
do not,
can we put some together. Now that I'm getting more involved in
OpenEJB
(finally) I would like to make it easier on developers to be able to
identify patch requests on the mailing list. I know we have Jira
to house
the issues and the patch contents but usually you get an email
asking for
someone to review/apply a patch and since there is no particular
format for
the request, it is hard to make sure you don't miss a request. I'm
not sure
we need a real process but maybe just a suggested email subject
line that
jumps out to us developers so we don't overlook a patch review/
application
request. Thoughts?
Take care,
Jeremy
