Determine what features should be included

[jfredett]

Initial thoughts

Probably don't need a full rails app, but it'll be good for hacking, so the over-engineered approach might be good for purposes of pedagogy.

We'll definitely need a blogging-esque system for rapid communication to the community, we'll need project listings w/ changelogs, CI status, contact info for maintainers, etc. Ideally some twitter feeds and similar.

[netbyte]

RSS feed would be cool

[jfredett]

Absolutely -- maybe a combined changelog for each project?

[Naomarik]

What about a user/profile system to keep our roster rather than having it as a repo on github? Could implement omniauth github and allow people to sign in with that. Would alleviate the need for dealing with pull requests.

[jfredett]

As we talked about on IRC. I think this is a good idea long term, but first I think we should go for some simple blog functionality w/ a very basic, self-hosted user model. Then we can look at expanding that model to include Omniauth functionality.

Ideally, I'd like to have integration (like you suggest) with github and other services (at the users discretion) so that every user can have a profile page.

Finally, the user model will eventually need to encompass some permissions so that I can manage who can make posts, post screencasts, and similar.