Skip to content

Instantly share code, notes, and snippets.

@mkaito

mkaito/memoricide-codefest.md

Forked from manpages/memoricide-codefest.md
Created August 25, 2012 16:16
Show Gist options
  • Save mkaito/3467475 to your computer and use it in GitHub Desktop.
Save mkaito/3467475 to your computer and use it in GitHub Desktop.
Download ZIP
Memoricide /codefest/ workflow
Raw
memoricide-codefest.md

Workflow for memoricide /codefest/ project

  • Our work flow is based on features and projects. Each project has a maintainer, usually, the same person as the project author. The maintainer accepts new features and is makes decissions about feature APIs.

  • A feature request is assigned to a programmer.

  • He or she negotiates the JSON API with the project maintainer. For pretotypes[1], JSON is transfered over HTTP or HTTPS.

  • Our programmers write a module in their favourite language, implements chosen API.

  • The feature is deployed on one or more servers. After testing, the project maintainer may decide to accept the feature, so that it can be used from other features via "Feature Discovery".

  • Separately, the frontend guy™ for the project integrates the additional feature in the project's representation layer. Designers must pay attention to the fact that pretotypes aren't that reliable, and thus if a feature is unavaliable, the design must respond properly.

  • Then the design may get accepted in a similar fashion, and is deployed at frontend nodes.

Questions? Suggestions? Criticism?

[1] — Pretotype concept originating from the following talk http://youtu.be/X1jWe5rOu3g

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment