OK, Code is King! But, where should you put your Developer Relations sample programs?
All developers require a Developer Relations Programs to follow the “3 C’s” – Community, Code and Content. To this list of C’s I also add a few of my own: Collaboration, Continuity, Cooperation, Communication, Caring, Celebration, Civility, Consideration, Clarity, Conversation and Curiosity. In surveys, during conversations, in emails and as the most commonly asked webinar question, developers tell us that Code is King! Even though we provide documentation for SDKs, APIs, libraries, frameworks, systems and applications, the ultimate documentation is the source code itself. The Computer History Museum (CHM) collects the source code for great computer software programs and systems. Do you want to download the source code for MacPaint and QuickDraw created by Bill Atkinson? You can download them both and you can read the story behind the software too! I love what CHM is doing to preserve the source code artifacts of our industry’s history. Developers tell Evans Data that source code examples, sample projects and tutorials are some of the top requirements for a successful developer relations program. So, the question is, where should you put your sample programs so that your developer relations program members can find it, download it and use it?
Developer Relations – where to put your sample programs, tutorials and source code?
There are several places that Developer Relations programs put there source code. Some programs keep their code on their own servers (ftp or http access), some put code in public repositories and others put their source on code hosting sites. There are many sites to choose from including: Amazon S3, Microsoft Azure Storage, GitHub, SourceForge, DropBox, Cloud Forge, Box, CodePlex, Google Drive, Assembla, BitBucket, ProjectLocker, and LaunchPad. Most of these sites support the leading source code version control services including Subversion, Git and Mercurial. Some of the hosting sites will also provide additional tools and services like defect tracking, deploy/install, security scanning, and license compliance audits. Several of these sites are popular places to put open source software projects allowing the developer community to collaborate and enhance the sample code. Some of the sites also provide APIs (GitHub Developer for example) for you to automate interactions, search catalogs of entries, access control, and more. Other developer programs place source code on sites to make it simple to distribute and update the code. Most integrated development environments and programmer’s editors support pulling sample code from repositories.
Where do you put your Developer Relations program and products sample code?
Send me an email and tell me where you put your developer relations program code.
David Intersimone “David I”
Vice President of Developer Communities
Evans Data Corporation