Notes:

2) Translations in plugins.cordova.io - README gets uploaded in npm JSON payload, so nice to put it there - Still, only EN gets uploaded… Demo at http://stage.plugins.cordova.ioEasiest path for translations is to have README.md manually link to its translations Can we internationalize the entire site? [Yes, but not v1] Can we include a browser compatibility matrix? [Yes, it's intended] Action: Steve to release some notes about the status; possibly a blog post

What do we want to do with platform-specific plugins? AI: We need to have another list conversation about what 'core' means, and what is 'core'. - e.g. 'core' is only when there is enough people to maintain it

- Coho does things! but we agree that we want a turn key release process. google/adobe to really send some love into this tool to make lives easier. Google working on this now. Adobe folk will look into after new plugins.cordova.io is live.

- Releasing: we do it a lot. Synchronization of platforms seems to slow us. Moving away from dedicated Release Manager role to rotating. Current thinking is decoupling platform releases. (So iOS could ship independent of Android, for example.) Andrew to kick up a thread for further discussion of the impacts.

- Statusbar/Keyboard: adding to core? Some think 'core' means >3 platforms. Some think it might mean its too important for us to ignore. Also perhaps some are so important they need to be a part of a platform. Needs discussion / Tommy will kick up this thread.

- Plugins should not be doing asset injection for user space concerns. Example: somebody creates a Cordova plugin for jQuery. That would not be cool.

- Hooks for plugins. We like it. Platform pre/post build. Plugman install/uninstall/build/prepare. We likely need a plugin registry policy and possibly Maven has already been down this path at Apache.