by Dave McAllister

Created

July 14, 2010

OpenatAdobe-gfx.png
Today, Adobe in partnership with SourceForge announced the opening of Open@Adobe, the first instantiation of SourceForge’s new developer platform. Open@Adobe is a site aggregating Adobe’s openness programs, which includes source code hosting, such as the Adobe® Flex framework, and contributions from Adobe to standards organizations, as well as specifications.

It has been clear for some time that we needed to become more aligned with development principles is seen in open source projects. We’ve always followed a open process model, with exposure to our bug bases, open discussion forums, roadmaps for products, and early access through Adobe Labs. However, our current repository was not meeting the desire to allow our projects to evolve in multiple directions simultaneously.

We spent a lot of time looking at various solutions. One thing became clear, that to be involved in open source meant being open to as many people as possible. For Adobe, open means being involved in many aspects of technology, standards, specifications, community, content and source. Our solution needed to include all of these elements.

So, in short, we did want the ability to do more than just code. We wanted some distinctive features and the ability to make sure we could also tie back to our own environment, since our open efforts are core technologies and important to our own products. SourceForge gave us the ability to support all of the things we needed and the flexibility to replace things we wanted to. SourceForge and the new development forge gives us the ability to connect our developer community to a global community. It gives us the chance to recognize projects built on Adobe open technologies as well as the technologies we have released.

We also like the fact that SF is still one of the largest forges around. Making our open source products and technologies available on SourceForge gives us the opportunity to tap the creative and innovative energies of one of the world’s largest open source communities. SourceForge currently hosts over 250,000 open source projects and powers open source project development around the world. We believe that by moving our projects to SourceForge will expand access to our open technologies; technologies that are core to Adobe’s own product offerings.

Obviously, this effort has been underway for a while and will continue as we move from our own repository to the new Open@Adobe repository on SourceForge. Our projects aren’t going away nor are we walking away from our projects. If anything, you will see more opportunity to be involved in Adobe’s open source efforts as well as our work in standards and our belief that community empowers technology.

COMMENTS

  • By Daniel Gasienica - 5:31 AM on July 15, 2010  

    I’m a bit disappointed: GitHub with its distributed Git version control system is so much more suited for enabling outside developers to experiment and contribute to Adobe open source efforts without the centralized repository (SVN) access hassle.Considering that companies like Facebook (http://github.com/facebook), Twitter (http://github.com/twitter) and Palm (http://github.com/palm) to just name a few, are already represented there, I’m a bit disappointed by Adobe’s step.–Daniel

  • By Kyle - 7:04 PM on July 15, 2010  

    Hey Dave,Congrats on the move to SF! I’m glad to see the new SF out and in the wild.I’m sorry you thought GitHub wouldn’t be responsive enough to Adobe’s needs. If you guys ever feel like chatting, feel free to get in contact with me (kyle@github.com) and we’d be happy to see if there’s any way we can work together in the future.

  • By Matthew Fabb - 7:26 AM on July 16, 2010  

    I see a number of links from sourceforge to opensource.adobe.com and was wondering if opensource.adobe.com would exist as a secondary portal to certain projects, or if the plan is to eventually migrate everything to SourceForge? Thanks.

  • By Dave McAllister - 8:17 AM on July 16, 2010  

    We plan to move all of the projects over time. Partly this is due to some new features that will be added in coming updates to the forge, and partially because we can’t disrupt our own product engineering teams. Since so much of our open source technology is also core to our products, we have to plan carefully when we can move things.So, over time, the links back to opensource.adobe will diminish, as the projects move to the Adobe neighborhood on Sourceforge.

  • By Mark Ramm - 8:18 AM on July 16, 2010  

    Daniel,It’s probably worth noting that the new sourceforge.net tools that Adobe is using does include git support as an option. But I expect the fact that we also support subversion (which many adobe projects already use) is valuable to Adobe right now. We plan to announce Mercurial support too, so projects will not have to give up the VCS that works for them in order to use the new sourceforge tools. This is important for large organizations that have different needs on different projects, and I expect that it will be valuable to many people.Github’s tight integration with git is also valuable to many people, and I think they do a great job. But it’s pretty clear to me that they aren’t the right tool for *every* job.

  • By Dave McAllister - 8:19 AM on July 16, 2010  

    If there is one truth in open source it’s that “no matter what you do, someone will disagree”. We see this with license choices all the time. The advantage is that there is really no one true way. We did look at github, and yes many groups have chosen that as their site. We talked with Google Code as well, and their solution also works for multiple groups (like Eclipse).The bottom line is that sourceforge gave us a chance to have some of our requirements “built in”; things that make it possible to align external and internal efforts. Remember that we use these technologies in our own products as well and we need to make sure both the open community voice and the engineering teams (when they are building related products) can stay align. Sourceforge was responsive, worked with us (including multiple development teams inside of Adobe around the world). The others possibly/probably would have worked as hard, but sourceforge demonstrated commitment early and honestly, we like what we got.The site will continue to evolve. And we welcome constructive feedback.

  • By Steve Ardire - 6:40 AM on August 10, 2010  

    Hi Dave – nice to see Open@Adobe.

    Discover & Play with Demo of Open Semantic Framework http://demo.citizen-dan.org/ that shows ontology driven information management using Adobe® Flex framework.

    Citizen Dan Goes Live as first Open Semantic Framework instance http://goo.gl/LU0h