| # |
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. |
| # |
Apr 29th 2010, 19:29 |
savant |
a version 1 we can iterate on |
| # |
Apr 29th 2010, 19:29 |
savant |
I have a plan of attack though |
| # |
Apr 29th 2010, 19:29 |
savant |
trying to figure out what would be a good workflow for all of that |
| # |
Apr 29th 2010, 19:28 |
Predominant |
Comments / suggestions / hate mail? |
| # |
Apr 29th 2010, 19:28 |
savant |
yes |
| # |
Apr 29th 2010, 19:28 |
Predominant |
savant: You have seen / read the bakery document, yes? |
| # |
Apr 28th 2010, 21:01 |
nurvzy |
wb |
| # |
Apr 28th 2010, 20:39 |
nurvzy |
Ya, its a biggin. |
| # |
Apr 28th 2010, 20:39 |
Predominant |
Displaying it all in one page takes a while.. still going for me |
| # |
Apr 28th 2010, 20:39 |
nurvzy |
Ya, that would be nice, |
| # |
Apr 28th 2010, 20:38 |
Predominant |
Would be cool to cache / generate that output into a PDF or something |
| # |
Apr 28th 2010, 20:38 |
Predominant |
Thats one solution, yeah |
| # |
Apr 28th 2010, 20:37 |
nurvzy |
can't you display the book as a single page then just "save as website" via a browser? |