Beercoding es un ejercicio de programación en equipo y un buen pretexto para convivir y beber socialmente con otros desarrolladores.
- Debe reunirse un grupo de desarrolladores para trabajar en un proyecto común. Se recomienda un pet-project.
- No olvidar que debe haber suficiente cerveza.
- 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
- Existe un repositorio remoto. Al menos un desarrollador debe ser administrador del repositorio. Se recomienda que preferentemente sean dos personas los administradores.
- Se trazan los objetivos de features a desarrollar.
- Cada desarrollador elige un feature en el qué trabajar o de ser posible se forman equipos para trabajar features.
- Por cada commit propio, se bebe un trago.
- Por cada commit empujado a su propio fork (o el de su equipo) del repositorio remoto se bebe un trago.
- Al completar un feature o mini-features, y abrir un pull request, se bebe un trago.
- El(los) administrador(es) del repositorio original deben estar pendientes y proporcionar feedback inmediato sobre los pull requests.
- El(los) administrador(es), por cada pull request recibido (aprobado o no), beben un trago.
- Si se aprueba y se hace merge del pull request, todos beben un trago.
- Se recomienda instalar lolcommit https://github.com/mroth/lolcommits.
Beercoding is a social programming exercise, where a group of developers work, drink beer and have fun together.
- A group of developers work together in a common project. A pet-project is an excellent choice for this exercise.
- Don't forget to always have beer available.
- 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
- A remote repo should be setup. At least one developer should act as the repo's admin. Preferently, two developers should act as admins.
- The team should discuss and agree on features to build.
- Every developer or a team, should pick a feature to work on.
- If you make a local commit, you take a sip from your drink.
- If you push commits to the remote repo, you take a sip.
- 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.
- The original repo admin(s) must be aware of pull requests and provide immediate feeback on them.
- Everytime a pull request is opened (approved or not), the original repo admin(s) should take a sip from their drink.
- If a pull request is approved and merged into master, everybody should take a sip from their drink!
- Recommended to install lolcommit https://github.com/mroth/lolcommits.