Thanks chris thats a fair few things for me to start with. I've read aboutthere being some stubs of code that I need to fill in inorder for people to access information stored on my database, do you have any information on where these stubs are? and the types of functionality i should be providing in them for developers.
On Jun 29, 11:44 am, Chris Chabot <[email protected]> wrote: > Hey Terry, > > It really kind of depends on the amount of resources you have available and > what your goals are, a site like MySpace has other goals then a site with > 50000 visitors does :) > > First of all, please make sure that your OpenSocial implementation is > compliant, that's the first must for any gadget developer, the best way to > test this is by using the 0.8.1 complaince test > fromhttp://code.google.com/p/opensocial-resources/wiki/ComplianceTests > > Next, list your site in wiki.opensocial.org and include all the details you > can in there, for developers that are looking for new containers to support, > that's the place to be :) > > On your site there's a couple of things you can do, but again it depends on > the resources you have available for which of these you can implement or > not, anyhow a wish list for a developer would look something like: > > - A documentation source (wiki, forum, etc), feel free to point to the > opensocial-...@googlegroups list if you can't maintain your own, and > wiki.opensocial.org is a great place to link to for how-to articles and docs > - A developer console where a gadget dev can: > - Add his application and test it (sandbox/not live yet) during > development > - A 'submit for approval' process if you want to do white listing > - An overview of how many installs the app has > - Extra points for showing the installs / removals / profile views / > canvas views in a nice statistics overview (numbers over time, graphs, etc) > - A way for the users of the app to contact the gadget dev for feedback .. > a form that sends an email to the <author> of the gadget is fine really > > For the rest, the best way to get a feel for it is by simply going to other > social networks and see how they did things, you can find a list of them on > the samehttp://wiki.opensocial.orgsite > > Hope that helps! > > -- Chris > > On Mon, Jun 29, 2009 at 1:30 AM, terry <[email protected]> wrote: > > > Hi > > > I've successfully setup a sub domain on my social networking site and > > have shindig running... Now I'm trying to figure out what my next > > steps are. I want to allow developers to develop apps for my site and > > use my site as a container. I'm trying to find some guidance on the > > correct steps I should be going through to make this possible. I'm > > guessing i need to make an API for developers to access the sites > > backend and also create a wiki for developers to find out how to make > > apps but this is a bit vague and some more references would be > > grateful! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
