Difference between revisions of "Platform Developers"

From Sirikata Wiki
Jump to navigation Jump to search
m (mInor changes to the intro part of the page)
(Further simplified the page)
Line 1: Line 1:
 
The core of Sirikata is a platform for building virtual world applications.  This means that we don't produce any single virtual world and there is no resulting "product."  Sirikata, at its core, is a set of interfaces and protocols for building virtual worlds.  We also implement many of these interfaces, some with multiple variations to support the demands of different applications.  If you're interested in building an application on top of Sirikata, for example a game, by writing scripts for objects and using Sirikata's infrastructure to handle things like user logins, content distribution, and rendering, then you are an ''Application Developer''.
 
The core of Sirikata is a platform for building virtual world applications.  This means that we don't produce any single virtual world and there is no resulting "product."  Sirikata, at its core, is a set of interfaces and protocols for building virtual worlds.  We also implement many of these interfaces, some with multiple variations to support the demands of different applications.  If you're interested in building an application on top of Sirikata, for example a game, by writing scripts for objects and using Sirikata's infrastructure to handle things like user logins, content distribution, and rendering, then you are an ''Application Developer''.
  
If you're interested in helping define these interface and protocols as well as building implementations of them, then you're in the right place.  This page describes how to get in touch with the developers, how the project is setup as well as how to start contributing.
+
If you're interested in helping define these interface and protocols as well as building implementations of them, then you're in the right place.  This page's goal is to guide you through your first steps in getting involved:
 
 
== Communication ==
 
Developers stay in touch via a number of mechanisms:
 
* '''Mailing List''': [http://groups.google.com/group/platformtalk Developer List], [http://groups.google.com/group/platformtalk/topics Archives].  Use for discussion about the platform architecture, protocols, and implementations. Patch sets can also be sent to this list for review and application if you do not have core commit access. We don't specifically separate mailing list traffic for application and platform developers since the overlap is significant and often useful, but we'd prefer to see general inquiries on the [http://groups.google.com/group/open-platform-community community mailing list] or art related topics go to the [http://groups.google.com/group/sirikata-art-list artist mailing list].
 
* '''IRC''': #sirikata on irc.freenode.net ([http://sirikata.com/irc/logs/freenode/ logs]). Used for real time discussion with developers - quick questions, detailed questions about code, etc. ([http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia article on IRC])
 
* '''Bugs''': Nothing yet, send to the [http://groups.google.com/group/platformtalk developer list] for now.
 
 
 
== Working with Sirikata ==
 
Because Sirikata is a large project, getting involved can be a bit daunting. This section's goal is to guide you through your first steps in getting involved:
 
  
 +
# [[Communication]] describes ways developers stay in touch
 
# [[System Architecture|Architecture]] is a great place to learn about the Sirikata system
 
# [[System Architecture|Architecture]] is a great place to learn about the Sirikata system
 
# [[Source Code|Source Code]] helps you understand how to get and build the code
 
# [[Source Code|Source Code]] helps you understand how to get and build the code

Revision as of 17:25, 24 June 2009

The core of Sirikata is a platform for building virtual world applications. This means that we don't produce any single virtual world and there is no resulting "product." Sirikata, at its core, is a set of interfaces and protocols for building virtual worlds. We also implement many of these interfaces, some with multiple variations to support the demands of different applications. If you're interested in building an application on top of Sirikata, for example a game, by writing scripts for objects and using Sirikata's infrastructure to handle things like user logins, content distribution, and rendering, then you are an Application Developer.

If you're interested in helping define these interface and protocols as well as building implementations of them, then you're in the right place. This page's goal is to guide you through your first steps in getting involved:

  1. Communication describes ways developers stay in touch
  2. Architecture is a great place to learn about the Sirikata system
  3. Source Code helps you understand how to get and build the code
  4. Subsystems is a place to understand the directory layout of our repository
  5. How Can I Contribute? Learn about a number of ways to get involved

If you're not sure what you want to help out with yet, this process above should hopefully give you some ideas, and the coding projects projects page or a discussion on the developer list can help you pin down exactly what to work on.