| # |
Apr 29th 2010, 21:20 |
PhpNut |
Predominant the things we discussed on the phone the other day about oAuth for all cake related sites using cakephp.org/*/developername |
| # |
Apr 29th 2010, 21:19 |
Predominant |
Release schedule |
| # |
Apr 29th 2010, 21:19 |
PhpNut |
ok |
| # |
Apr 29th 2010, 21:19 |
Predominant |
PhpNut: Need to talk to you about that at some point too |
| # |
Apr 29th 2010, 21:17 |
savant |
okay |
| # |
Apr 29th 2010, 21:17 |
PhpNut |
then openID soon after |
| # |
Apr 29th 2010, 21:17 |
PhpNut |
not really, we are going to release the oAuth client and server in a about a week |
| # |
Apr 29th 2010, 21:16 |
savant |
anything I can do to speed that up? |
| # |
Apr 29th 2010, 21:16 |
PhpNut |
savant: it is not released yet |
| # |
Apr 29th 2010, 21:13 |
savant |
so if I started working on this, where could I get the source to the openid stuff that would be used (eg the cakeqs stuff) |
| # |
Apr 29th 2010, 19:54 |
savant |
and that way you could have an index of all the cakephp developers |
| # |
Apr 29th 2010, 19:54 |
savant |
and there could be verification methods for each (upload a file to your ftp, enter your github api key) etc |
| # |
Apr 29th 2010, 19:53 |
savant |
and their twitter, their blog etc |
| # |
Apr 29th 2010, 19:53 |
savant |
like that way we could automatically tie in a user's profile with their github account |
| # |
Apr 29th 2010, 19:53 |
savant |
and providing the user data in an api would be great as well |
| # |
Apr 29th 2010, 19:53 |
savant |
signing in with it would be magical |
| # |
Apr 29th 2010, 19:53 |
savant |
OpenId sounds great |
| # |
Apr 29th 2010, 19:40 |
savant |
yeah |
| # |
Apr 29th 2010, 19:40 |
Predominant |
Thats my opinion |
| # |
Apr 29th 2010, 19:40 |
Predominant |
I think we'd like to retain the data locally |
| # |
Apr 29th 2010, 19:38 |
savant |
like IntenseDebate or Disqus |
| # |
Apr 29th 2010, 19:38 |
savant |
and we could also consider outside sources for commenting |
| # |
Apr 29th 2010, 19:37 |
savant |
there is also defensio |
| # |
Apr 29th 2010, 19:37 |
savant |
Akismet works for spam protection |
| # |
Apr 29th 2010, 19:34 |
savant |
and it's not readily apparent for users to contribute in this way |
| # |
Apr 29th 2010, 19:34 |
savant |
right |
| # |
Apr 29th 2010, 19:34 |
Predom[mac] |
At this stage, getting multiple eyes is the problem. |
| # |
Apr 29th 2010, 19:34 |
Predom[mac] |
Okay. |
| # |
Apr 29th 2010, 19:34 |
savant |
that way we can have multiple eyes on an article |
| # |
Apr 29th 2010, 19:33 |
savant |
then a workflow whereby two moderators (or more) would categorize and approve an article |
| # |
Apr 29th 2010, 19:33 |
savant |
so we can focus on the admin interface |
| # |
Apr 29th 2010, 19:33 |
savant |
disable commenting and adding new articles |
| # |
Apr 29th 2010, 19:32 |
savant |
simple enough |
| # |
Apr 29th 2010, 19:32 |
savant |
the general idea is to setup a barebones app that simply displays all the articles with their comments |
| # |
Apr 29th 2010, 19:31 |
Predom[mac] |
Fair enough |
| # |
Apr 29th 2010, 19:31 |
savant |
been a busy week with finals and such |
| # |
Apr 29th 2010, 19:30 |
savant |
I need to write it all down first :) |
| # |
Apr 29th 2010, 19:30 |
savant |
yeah |
| # |
Apr 29th 2010, 19:30 |
Predom[mac] |
Wouldn't want to see it in a situation like previously, where one person held all the information |
| # |
Apr 29th 2010, 19:30 |
Predom[mac] |
Its important that everyone can access information regarding plans for features and development |
| # |
Apr 29th 2010, 19:30 |
Predom[mac] |
Well, be sure to share your plan of attack. |