CMS Made Simple Forums

Dear CORE developers,

I might like to begin contributing to the CMSMS project by working on a particular core security feature/enhancement that I would like to see implemented -- the "feature" was first requested in the forums back in 2005, but to my knowledge is not yet available. What is the best way to go about doing this if one is not on the official dev team?  Are there documented procedures for this?  I couldn't find any on the forge. I presume there is at least some informal procedure for accepting code (in patch format?) that has been adequately tested by the developer (and a reviewer?) prior to submission.

While I have ~30 years of professional software engineering experience, I haven't "published" a great deal of code for open source projects.  I've been working with CMSMS for a little over a year in my spare time. But, I might have a few pertinent questions for the dev team as I progress.

Thanks,
Fred P.

Fred,

in the forge you can submit patches to trackers. For questions for logic, etc... there is the #cms channel at freenode.net. Most of the time, the devs are there.

Questions can be asked there as well, as in the forum. When you have a proposed fix for a tracker, just put the modification in the tracker and it will be seen.

Ronny

calguy1000 wrote: http://forum.cmsmadesimple.org/index.php/topic,2712.0.html

Doh!  I see.  It was on the "Modules/Add-Ons" board.  :-[

Thanks for the topic pointer.  I'll give it a careful read.

Cheers,
Fred P.

Hi Ronny!

RonnyK wrote: ...For questions for logic, etc... there is the #cms channel at freenode.net. Most of the time, the devs are there.

Thanks for the freenode.net channel info.  I'll check it out. 

RonnyK wrote: Questions can be asked there as well, as in the forum. When you have a proposed fix for a tracker, just put the modification in the tracker and it will be seen.

Sounds straightforward.  I've got a bit more reading to do on this and then I might try submitting a small unrelated patch, just go through the process once before moving on to bigger things.

Thanks again,
Fred P.