SugarForge 2.0?

bsoremsugar —  June 8, 2009 — 8 Comments

I’ve been thinking a lot lately on how you (the developer community) and SugarCRM can work closer together.  We’ve come up with a few ideas that we’re working on here at Sugar.

For starters, I want to revamp SugarForge.  There are some features that I want and they do not currently exist.  My inspiration has come from sites I have been using lately – GitHub, BitBucket, and LaunchPad. I have also been playing with Trac a lot.  What all of these have in common is excellent source control and wikis. I also particularly like the project management & issue tracking available from Trac.

I don’t think its possible (or even wise) to replace SugarForge with any of the above mentioned developer collaboration services.  However, I do think we have some options.  These are the few that I have identified:

Is there any software collaboration suites that you think would be perfect for SugarForge 2.0?  Right now I’m leaning towards gForge because it’s PHP and SugarForge is already gForge based.  It looks like they’ve done some major updates since we initially started SugarForge.

If you have any other ideas that will help SugarCRM collaborate with you better PLEASE let me know. You can often find me hanging out in the IRC #sugarcrm channel (nick: roder).  That’s irc.freenode.net in channel #sugarcrm.

8 responses to SugarForge 2.0?

  1. 

    I think gForge is the way to go Matt.

  2. 

    I think gForge is the way to go Matt.

  3. 

    Great idea. Just posting here trying to make sure that you consider moving the Bugs to a new system as well. I’m sure you’re proud of SugarCRM, and rightly so. But I cannot search the Bugs list in order to find out duplicates before I submit a Bug, there is lack of communication, and a detachment from the Bug trackers from all other SF projects. These are just a few issues. My guess is that Sugar’s own Bug Tracker was never designed with a project as large as Sugar Suit in mind. Kind of ironic, really.

  4. 

    Great idea. Just posting here trying to make sure that you consider moving the Bugs to a new system as well. I’m sure you’re proud of SugarCRM, and rightly so. But I cannot search the Bugs list in order to find out duplicates before I submit a Bug, there is lack of communication, and a detachment from the Bug trackers from all other SF projects. These are just a few issues. My guess is that Sugar’s own Bug Tracker was never designed with a project as large as Sugar Suit in mind. Kind of ironic, really.

  5. 

    A reminder: Launchpad’s source will become open source in July: https://dev.launchpad.net/OpenSourcing.

  6. 
    Kevin Roberts June 22, 2009 at 1:50 pm

    Your links are mixed up. The gForge link goes to Trac, and the Trac link goes to gForge.

  7. 
    Kevin Roberts June 22, 2009 at 5:50 am

    Your links are mixed up. The gForge link goes to Trac, and the Trac link goes to gForge.

  8. 

    A reminder: Launchpad's source will become open source in July: https://dev.launchpad.net/OpenSourcing.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s