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

Comments

[(Anonymous)]

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

I'd suggest looking at archives in other languages as well. Animexx did some interesting things in its day (fanart, doujinshi, cosplay and fanfic, all on one site, for one), for example.

[dlh]

For the code of conduct, can I suggest "Helping with the project doesn't mean committing to a full-time job?" The level of commitment the OTW required in its early days - and still requires - made it impossible for people to pitch in with small but vital tasks and advice, and led to abusive working conditions for many of those who did commit. We should envision this project as something that's going to be driven primarily by people who have an evening or a Saturday afternoon free and can help.

More people making smaller contributions means more need of good project management, but if we don't have that we're going to crash and burn anyway.

[curiouskitten]

+ all the ones

Good project management is going to be key and so is discipline. Agreeing the scope and what the goals are before any code is written will make it far easier.

Intense modulisation will protect both the project from failure if one module's approach fails and allows sections to be split down rather than being a full-time job for any one.

Code of conduct suggestion

[dlh]

Based on what I'm seeing on FFA, we need something to the effect of, "This is not an anti-AO3 project. The point is not to destroy, annoy, spite, or replace AO3. If you have an axe to grind with AO3 or the OTW, take it up with them. Don't bring it here.

The point of the project is to build an easy-to-startup, robust, scalable, fandom-focused archive, incorporating lessons learned from previous archive projects."

If there are people here just hoping for drama, those people need to be discouraged.

Re: Code of conduct suggestion

[(Anonymous)]

We could just ignore it and redirect conversation to the technical conversation. If no one bites the bait, then there shouldn't be drama.

Re: Code of conduct suggestion

[quivo]

Good call, I saw some of the same shit on FFA last night before I sacked it in. Have added an AO3 disclaimer to the profile, will most def include in the code of conduct somewhere.

[(Anonymous)]

I'm a backend person who's interested in the technical conversation/being like the engineers in Star Trek yelling about "I'll give ya all I can, captain, but the stress on the warp drive!!" I think I'll lurking for the most part, but just wanted to say I'm excited and curious about the discussion!

[(Anonymous)]

I'd advise coming up with an MVP yourself instead of polling meme. Meme will ask for the stars, because everyone has their pet feature that MUST BE IN RIGHT NOW. Then the project has no direction, gets bogged down in minutiae, and ever gets off the ground.

There's a reason the tech world keeps harping on MVPs. It's because it's easy to add more, but hard to cut stuff.

I'd suggest first concentrating on building something where users can upload text content and that text content can be read later. The absolute bare minimum. No tags, no comments, no block lists, nothing but the ability to upload and the ability to read. But it's up to you. Just...don't poll meme.

[quivo]

I'd advise coming up with an MVP yourself instead of polling meme. Meme will ask for the stars, because everyone has their pet feature that MUST BE IN RIGHT NOW. Then the project has no direction, gets bogged down in minutiae, and ever gets off the ground.

Thank you for raising this point. We've slowed a bit re noting down the first big batch of desired features and so forth, and I was starting to feel a bit overwhelmed/at sea re where to start, but thinking of it from the standpoint of "what *must* it have" helps a lot. And yeah, uploading text + displaying it is basically as bottom line as it gets :D

I'm going to have a think about what other barebones thing should make the cut, bat it around with the other contributors, and make a decision tomorrow.

[(Anonymous)]

Yeah, and it goes along with "don't be afraid to redo old decisions". If something you picked to help you quickly get to MVP starts holding you back, change it!

I'd say that's AO3's big problem, right there. A lot could be improved by a culture of being willing to revisit old decisions. Every popular website started off small with a ton of bad decisions. The only question is if you learn from that and start making good ones.