AJ Ferrigno said the following on 03/31/2011 08:49 AM: > Peter, I think you just pulled me off the fence - I want to help out, > however small my contribution may be right now. > > I am now looking at the website for some more information on how to > contribute, can someone point me in that direction? We probably need to write up a better contribution page. It's scattered all over Trac at the moment. > I am not finding much in the way of a standard method or anything. I see > where I can > download from the repository, should I just go ahead and commit some > of my fixes to a branch in that repository? Unless it is a huge new feature, we tend not to commit to branches and prefer the trunk. The REST / endpoint stuff was done in a branch first because it did touch a lot of stuff.
I'll get you a committer account setup right now. You should be getting an email soon. This works for both SVN and Trac logins. > Where do I go to discuss what I did/want to do? We discuss all development on the Mach-II BER Developers Google Group. Please join this group. https://groups.google.com/forum/?pli=1#!forum/mach-ii-developers This group is public and is open to anybody interested. It's a much smaller group then this one which is good because we sometimes get into long discussions about stuff. > Should I instead submit my feature as a feature request in Trac and go from > there? The process is like this new features / suggestions / change of behavior: 1. Idea / suggestion is bought up on our Dev Google Group 2. Discussion and idiot check questions. 3. Decision usually via consensus. I usually act as the benevolent dictator when a consensus cannot be made. 4. Ticket filed / assigned to a contributor 5. Work is done 6a. For newer contributors, I usually suggest SVN patch files so a team member can easily review changes and commit to the trunk 6b. For more seasoned M2 contributors, we commit to the trunk. Kurt always looks over my work. The commit emails and diffs are like candy to him ;-) 8. Final thoughts to the Dev Google Group For bugs: 1. Ticket is filed 2. Big bugs (change of behavior, wacky things, etc.) should be brought up on the list since not all team members watch Trac closely 3. Discussion on dev or on ticket 5. Same as above We pretty much run as a meritocracy. Our number one priority is backwards compatibility (BC). So that's why at the beginning we have a team member review changes. Any more questions? .Peter P.s. Regarding code formating / style, just follow the rest of the framework. As you can see, we're cfscript less for cross engine compatibility. Also, we comment a lot just so it's easier to follow what's going on. -- Peter J. Farrell [email protected] [email protected] http://blog.maestropublishing.com Identi.ca / Twitter: @maestrofjp -- To post to this group, send email to [email protected] For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
