└── README.md


/README.md:
--------------------------------------------------------------------------------
 1 | # Beercoding
 2 | 
 3 | ## Español
 4 | Beercoding es un ejercicio de programación en equipo y un buen pretexto para convivir y beber socialmente con otros desarrolladores.
 5 | 
 6 | ### Setup
 7 | * Debe reunirse un grupo de desarrolladores para trabajar en un proyecto común. Se recomienda un pet-project.
 8 | * __No olvidar que debe haber suficiente cerveza.__
 9 | * Se recomienda utilizar Git + Github para control de versiones. Se recomienda utilizar esta guía para el flujo contribuciones al repositorio original: [https://help.github.com/articles/fork-a-repo](https://help.github.com/articles/fork-a-repo)
10 | * Existe un repositorio remoto. Al menos un desarrollador debe ser administrador del repositorio. Se recomienda que preferentemente sean dos personas los administradores.
11 | * Se trazan los objetivos de features a desarrollar.
12 | * Cada desarrollador elige un feature en el qué trabajar o de ser posible se forman equipos para trabajar features.
13 | 
14 | ### Reglas del juego
15 | * Por cada commit propio, se bebe un trago.
16 | * Por cada commit empujado a su propio fork (o el de su equipo) del repositorio remoto se bebe un trago.
17 | * Al completar un feature o mini-features, y abrir un pull request, se bebe un trago.
18 | * El(los) administrador(es) del repositorio original deben estar pendientes y proporcionar feedback inmediato sobre los pull requests.
19 | * El(los) administrador(es), por cada pull request recibido (aprobado o no), beben un trago.
20 | * __Si se aprueba y se hace merge del pull request, todos beben un trago.__
21 | 
22 | ### Opcional
23 | * Se recomienda instalar lolcommit [https://github.com/mroth/lolcommits](https://github.com/mroth/lolcommits).
24 | 
25 | ## English
26 | Beercoding is a social programming exercise, where a group of developers work, drink beer and have fun together.
27 | 
28 | ### Setup
29 | * A group of developers work together in a common project. A pet-project is an excellent choice for this exercise.
30 | * __Don't forget to always have beer available.__
31 | * Git + Github is recommended for version control. Following this guide to manage contributions to the original repo is advised: [https://help.github.com/articles/fork-a-repo](https://help.github.com/articles/fork-a-repo)
32 | * A remote repo should be setup. At least one developer should act as the repo's admin. Preferently, two developers should act as admins.
33 | * The team should discuss and agree on features to build.
34 | * Every developer or a team, should pick a feature to work on.
35 | 
36 | ### Game Rules
37 | * If you make a local commit, you take a sip from your drink.
38 | * If you push commits to the remote repo, you take a sip.
39 | * If you or your team finish a feature or mini-feature (as long as it's functional), and open a pull request to the upstream repo, you or your team take a sip.
40 | * The original repo admin(s) must be aware of pull requests and provide immediate feeback on them.
41 | * Everytime a pull request is opened (approved or not), the original repo admin(s) should take a sip from their drink.
42 | * __If a pull request is approved and merged into master, everybody should take a sip from their drink!__
43 | 
44 | ### Optional
45 | * Recommended to install lolcommit [https://github.com/mroth/lolcommits](https://github.com/mroth/lolcommits).
46 | 


--------------------------------------------------------------------------------