Sounds good to me. Also, I know that there is reluctance to have comments and snippets embedded in the API docs. But what about having a separate site, which allows snippets and comments for each item in the api? Each page could then be linked to from the API docs.
Tom Boutell wrote: > While we're on the project of support, I've asked in the past about > turning the Symfony developer site into an OpenID provider. > > This would have major benefits - the Symfony trac site itself wouldn't > require a separate login (it currently shares an account database but > you still have to log in twice), and third party sites could be > created to support Symfony plugins without the need for a completely > different set of user accounts. We'd love to do that for > pkContextCMSPlugin, for instance. Due to the nature of OpenID no one > would be required to share their Symfony password with a third-party > site. > > The Symfony site could use this to become an OpenID provider (among > other implementations): > > http://openidenabled.com/php-openid/ > > And the Symfony trac could allow authentication via that provider using this: > > http://trac.sandbox.lt/auth/wiki/AuthOpenIdPlugin > > Third party tracs could do the same with big benefits for the community. > > OpenID would really open up the floodgates to wider community development. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
