Hi All, Don't focus on my wording but more along the lines of what I'm trying to do and that is to make the patch submission process easier. All I am looking for is a consensus on whether an email format would make identifying patch requests easier.
Take care, Jeremy P.S. - I agree with the stance of not liking guidelines but that wasn't my intention of the email. On 1/18/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Jan 18, 2007, at 2:54 PM, Dain Sundstrom wrote: > 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" I know what you mean. If someone printed their diff onto paper and snail-mailed me their patch, I'd still take it and say thank you :) Course I would let them know there are easier ways that might help them out and save them time. A document in that spirit would be great. -David > -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 >
