ToDo List about addictive-community

[brunnopleffken]

Man, there's so much more to do. Some of the pending suggestions:

• Oldest important task: software update and database migrations (#64);
• Not that old: extensions/plugins (#90);
• #114 is about subforums (like IPB does);
• #120 adds Nginx support;
• #58 suggests a micro-blog inside Addictive Community.

Basically, we need at least a safe update system (upload and replace files) and database migration like Ruby on Rails does (in case of database changes between versions), then we'd be ready to go to the final stable v1.0!

[xQuByte]

I've updated the list. I will add new things. You can do it too.

What about the blog? If you can add what you have done so far. I can finish blog because updating system is too much for me. ;)

[brunnopleffken]

@xQuByte About the micro-blog feature: I already have an ArticlesController here and some HTML layouts (but not commited, of course). I'll make things less raw and commit so you can check it out and proceed.

Do you have Nginx? @R-J posted a configuration file, we need to do some tests before it goes to 'master'.

Indeed, the auto-update system is tough. I have to make sure everything will work seamlessly. Upgrading from both 1.1.0 to 1.1.1 (minor v.) should behave the same way as upgrading from 1.0.3 to 1.1.1 (major v.), the only difference is the number of DB migrations.

--
And BTW, I wish to move the 'addictive-community' repository to an organization. Because Addictive Community belongs to the dev community, it's not my private project anymore. I'll see how to migrate from my user to an organization without any troubles.

[xQuByte]

@brunnopleffken I don't have Nginx.

Waiting for micro-blog commit. Update system is something new (to much?) for me. I think i can't help too much with it.

Moving addictive to organization is good idea! New organization name was AddictiveHub i think ;)

[brunnopleffken]

Articles/blogging is coming soon!