The Perforce Ecosystem
Jeffrey Bates
Director, Cloud & Ecosystem

James Creasy
Product Tech Research Manager
Where Did We Come From?
FROM MAILING LISTS TO FORUMS



  Mailing List
     •  Up for a decade
     •  “Hands off” by employees
     •  Mostly used by admins

  Forums
     •  Increased participation
     •  Internal experts can be “hands on”
     •  Searchable
     •  Persistent Data Storage
Where Are We Going?
USING SOCIAL MEDIA LESSONS


 •  Integrating Social Media & Other Data Streams

 •  Recognition of Top Users: Who’s Here?

 •  Expansion of Forums to Nurture Community

 •  Elements of the Ecosystem
APP JUNCTION


 •  Building on Existing Tools
      •  Public Depot
      •  Download Site
      •  Other Sources

 •  Centralized Location For Perforce Tools

 •  Community Built Tools (Internal & External)

 •  Community Supported

 •  Connecting Developers and Users
DOC BRANCH


 •  Multi-Faceted Informational Resource
      •  Knowledge Base
      •  Wikis
      •  Blogs
      •  Social Media
      •  User Contributed Material
 •  Launching With Internal-sourced Materials
 •  Brings Together Silos of Material
 •  Want/Need Feedback On What Is Useful
 •  Perforcepedia – leads to User Contributed Material
WHY BUILD THIS?

 •  Field of Dreams is Wrong
 •  Version Everything Means Bringing Together:
      •  Admins
      •  Developers
      •  Non Technical Users
 •  The Virtual Community
 •  Best Practices – “How Do YOU Get Stuff Done”
 •  Social Media/Coding/Practices
 •  “Open” Methodologies
 •  Part of A Culture of Contribution
Creating a Culture of Contribution
WIDEN THE NET
GATHER COMMUNITY, 753 B.C.




       Roman Forum Pic
GATHER COMMUNITY, 19th CENTURY




           Meeting house pic
GATHER COMMUNITY, 2011




          Jeff’s Forum pic
POTENTIAL CHAOS OF IDEAS
FUNNEL UP
CREATING A CULTURE OF CONTRIBUTION




        Widen the Net

        Gather Community

        Funnel Up
Tomorrow’s talk on JavaScript API

              with

 Fred Malouf and James Creasy
Thank You!

Perforce Development Ecosystem and Community Portal

  • 1.
    The Perforce Ecosystem JeffreyBates Director, Cloud & Ecosystem James Creasy Product Tech Research Manager
  • 2.
    Where Did WeCome From?
  • 3.
    FROM MAILING LISTSTO FORUMS Mailing List •  Up for a decade •  “Hands off” by employees •  Mostly used by admins Forums •  Increased participation •  Internal experts can be “hands on” •  Searchable •  Persistent Data Storage
  • 4.
  • 5.
    USING SOCIAL MEDIALESSONS •  Integrating Social Media & Other Data Streams •  Recognition of Top Users: Who’s Here? •  Expansion of Forums to Nurture Community •  Elements of the Ecosystem
  • 7.
    APP JUNCTION • Building on Existing Tools •  Public Depot •  Download Site •  Other Sources •  Centralized Location For Perforce Tools •  Community Built Tools (Internal & External) •  Community Supported •  Connecting Developers and Users
  • 8.
    DOC BRANCH • Multi-Faceted Informational Resource •  Knowledge Base •  Wikis •  Blogs •  Social Media •  User Contributed Material •  Launching With Internal-sourced Materials •  Brings Together Silos of Material •  Want/Need Feedback On What Is Useful •  Perforcepedia – leads to User Contributed Material
  • 9.
    WHY BUILD THIS? •  Field of Dreams is Wrong •  Version Everything Means Bringing Together: •  Admins •  Developers •  Non Technical Users •  The Virtual Community •  Best Practices – “How Do YOU Get Stuff Done” •  Social Media/Coding/Practices •  “Open” Methodologies •  Part of A Culture of Contribution
  • 10.
    Creating a Cultureof Contribution
  • 11.
  • 13.
    GATHER COMMUNITY, 753B.C. Roman Forum Pic
  • 14.
    GATHER COMMUNITY, 19thCENTURY Meeting house pic
  • 15.
    GATHER COMMUNITY, 2011 Jeff’s Forum pic
  • 16.
  • 17.
  • 18.
    CREATING A CULTUREOF CONTRIBUTION Widen the Net Gather Community Funnel Up
  • 19.
    Tomorrow’s talk onJavaScript API with Fred Malouf and James Creasy
  • 20.