12-19-2011 07:03 PM
I'm going to post a number of messages on the general topic of the Community Wiki. I'll start with a few messages on general categories that I believe make sense to include in the Community Wiki. Any and all feedback is very wellcome.
12-19-2011 07:08 PM
One page per Open Source Component at GitHub.
Information in the page would include:
* Name
* GitHub repo
* Contact/Owner of port
* Configuration / Build instructions
* License
* Upstream community
* Other links (Wikipedia)
* Notable use cases
Plus links to BB-10/PlayBook-specific information on how to use it, like gotcha's, blog posts, screencasts, discussion forums, etc.
Thoughts? Additional information?
12-19-2011 07:16 PM
In a per-geography (granularity to be decided - and most likely to be adjusted), to track things like
* User-Groups
* MeetUps
* Regular events happening in this geography
* ???
What else should be listed?
12-19-2011 07:22 PM
I'm specially interested in feedback in this category. I think this category is useful now, given that some documentation is not yet fully fleshed-out; I'm less clear whether of its usefulness later.
Each command (or collection of commands?) would have an entry. Structure may be similar to that of a unix MAN page?
Entry would include a description of the command, maybe some examples, maybe longer description of some flag usage. If there is official documentation for the command, then the page can point to it.
12-19-2011 07:51 PM
A developer community has many "sub"communities. This category will provide entry pages for each of these. Regardless of whether they are "open source" communities, or "for-profit" groups; if they have a presence in the community and want to engage the BB10/PB/BBOS community, they can have a page here, although we will want to provide enough guideance so that the pages do not become advertisements.
Examples of subcommunities would be (not exhaustive - just listing to help in conversations):
* Apache Cordova (nee PhoneGap) - Cross-Platform HTML5 platform
* Sencha (Touch, etc) - Cross-Platform HTML5 library
* Other commercial vendors with strong PlayBook products and a community around them
* Adobe (Toolings for PlayBook/HTML5/...)
* Marmalade (cross-platform native library)
* Unity, Unreal (highly portable game engines)
Commercial/for-profit partners are a key part of the community and can get entries in the Wiki. I think the meta-principle should be: if <FOO> helps create a larger ecosystem of developers for the platform, <FOO> belongs here.
Maybe my only concern is avoiding dilution of efforts; so I may focus initially more on certain areas to make sure they are covered, but the nice thing about a community effort is that others can focus elsewhere...
01-04-2012 02:40 PM
Another is a plain FAQ. Need to align with the official Knowledge Base, etc, but a Wiki can move pretty quickly.
See for example the Q from absmall on devmode -