Welcome to the SugarCRM Developer Wiki. This wiki will detail working with GitHub to contribute changes back to SugarCRM.
If you want to begin to participate in the SugarCRM community development process, you’ll need to set up your development environment and then you can provide a code contribution to SugarCRM thru Github. If you are new to git and Github, you can also go thru the Git Crash Course to help you get started.
We do monthly webinars, normally on the 3rd Wednesday of each month, where we talk about what’s going on with SugarCRM and with the community. We also record each month’s sessions for viewing afterwards.
Topic: Sugar Community Monthly Webinar Meeting
Date: The 3rd Wednesday of every 1 months, from Wednesday, July 20, 2011 to no end date
Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)
Meeting Number: 802 664 337
Meeting Password: (This meeting does not require a password.)
To start the online meeting
1. Go to https://sugarcrm.webex.com/sugarcrm/j.php?ED=152787562&UID=492952802&RT=MiMxMQ%3D%3D
2. If you are not logged in, log in to your account.
Audio conference information
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll number (US/Canada): 1-650-429-3300
Global call-in numbers: https://sugarcrm.webex.com/sugarcrm/globalcallin.php?serviceType=MC&ED=152787562&tollFree=0
Access code:802 664 337
Hot off the heels of Sugar 6.2 comes Sugar 6.3, codenamed “Cotton Candy”, that will include several projects coming from the very successful SugarCon Code Sprint back in April, as well as many fixes coming from our community. In this session, Jennifer will detail and demo some of the new features coming in the version, and answer any questions you may have about them.
We have a partner developer program as well that opens up access to our commercial source code repository, as well as early information on upcoming releases and full development team access. If you are interested, feel free to contact email@example.com for more information.
Last edited by jmertic,