Skip to content

Instantly share code, notes, and snippets.

@manpages

manpages/memoricide-codefest.md

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

Work flow for memoricide /codefest/ project

Glossary (Definitions)

¡TODO!

Work flow description

  • 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 decisions 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 front-end-guy™ for the project integrates the additional feature in the representation layer of a project. Designers must pay attention to the fact that pretotypes aren't that reliable, and thus if a feature is unavailable, the representation must respond properly.

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

Questions? Suggestions? Criticism?

Post those here in the comment section or at #xmpp/spaceships MUC.

[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