To Do.txt

[quivo]

Most important thing to begin with, at least imo, is to decide on a bare-bones feature set that we can all feel mostly happy with. I’m going to leave the brainstorm post running as a grab bag for ideas for at least the next day or so, while also mining through my pinboard and dememe for past thread discussions to pull from.

Otherwise, though, this is what I’ve got planned as tentative first steps for the next few days:

• Features:
  • start a shared document so we can collate the most-requested stuff
  • boil down that document into a list of features
  • put feature list to a quick-and-dirty poll on meme so we can figure out what we can shelve for future releases vs what absolutely needs to be in the first one
• Important community stuff:
  • piece together quick code of conduct so we don’t all go down in flames. At least not right away, right :D?
  • maybe assign a couple more mods for this comm
  • say hi to each other in an awkward post??
  • list what we can all bring to the table
• Archive looks / front end:
  • let’s go look at a bunch of other archives we’ve used in the past, and see what we can steal and what we absolutely shouldn’t
  • figure out what should be in our mockup reel
    • put together two or three different sets
    • decide on most loved set
• Archive name:
  • collect a list of great and obnoxious names. winnow down over time
• Archive stack / back end:
  • list framework options that would best serve our purpose. Think stuff that is easily installed on your bargain-bin VPS
    • laravel, rails, django, node.js maybe, etc etc
    • friendly cage match until one framework is ruled the victor
  • figure out a data structure for fanworks & fanwork metadata that won’t send the db mad when it’s trying to handle a million works
  • figure out what extras will be useful
    • memcached, elasticsearch for fulltext search, S3 for image/file hosting, etc