Difference between revisions of "Platform Developer Communication"
(New page: 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...) |
m (a bit of clean up) |
||
| Line 1: | Line 1: | ||
| − | Developers stay in touch via a number of mechanisms | + | Developers stay in touch via a number of mechanisms |
| − | + | ||
| − | + | === Mailing List === | |
| − | + | ||
| + | The [http://groups.google.com/group/platformtalk Developer List] is open for all to join and our [http://groups.google.com/group/platformtalk/topics archives] are public. 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 === | ||
| + | |||
| + | Our IRC channel is #sirikata on irc.freenode.net and we keep open([http://sirikata.com/irc/logs/freenode/ logs]). This is used for real time discussion with developers - quick questions, detailed questions about code, etc. If you have never used IRC then the [http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia article on IRC] gives a good overview | ||
| + | |||
| + | === Bugs === | ||
| + | |||
| + | We don't have an issue tracker in place yet, so please send to the [http://groups.google.com/group/platformtalk developer list] for now. | ||
| + | |||
| + | === Events === | ||
| + | |||
| + | Upcoming meeting in meat space will be announced on the [[Events|events]] page and past meetings will be documented there as well | ||
Revision as of 19:13, 24 June 2009
Developers stay in touch via a number of mechanisms
Mailing List
The Developer List is open for all to join and our archives are public. 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 community mailing list or art related topics go to the artist mailing list.
IRC
Our IRC channel is #sirikata on irc.freenode.net and we keep open(logs). This is used for real time discussion with developers - quick questions, detailed questions about code, etc. If you have never used IRC then the Wikipedia article on IRC gives a good overview
Bugs
We don't have an issue tracker in place yet, so please send to the developer list for now.
Events
Upcoming meeting in meat space will be announced on the events page and past meetings will be documented there as well