BeWelcome Berlin summer camp outcomes: Difference between revisions
[[Trustroots Wiki]] is an independent wiki with information for people who are actively exchanging hospitality.
Jump to navigationJump to search
| Line 2: | Line 2: | ||
Documenting results of our Finow meeting (http://www.bewelcome.org/wiki/Berlin_summer_camp) | Documenting results of our Finow meeting (http://www.bewelcome.org/wiki/Berlin_summer_camp) | ||
==Meinhard's notes== | ==Meinhard's notes== | ||
===Random=== | |||
* have mailing list running again by Monday | * have mailing list running again by Monday | ||
* use parts of SCRUM development method | * use parts of SCRUM development method | ||
| Line 10: | Line 11: | ||
* use coding standards and "code sniffer" | * use coding standards and "code sniffer" | ||
* tools clean-up work page: http://piratenpad.de/8W0q9Poqv7 | * tools clean-up work page: http://piratenpad.de/8W0q9Poqv7 | ||
* feature brainstorm: http://piratenpad.de/jBwd50aWk5 | |||
===Task division=== | ===Task division=== | ||
* guaka: migration and general help | * guaka: migration and general help | ||
Revision as of 15:39, 14 August 2011
- This page is written in the context of BeWelcome.
Documenting results of our Finow meeting (http://www.bewelcome.org/wiki/Berlin_summer_camp)
Meinhard's notes
Random
- have mailing list running again by Monday
- use parts of SCRUM development method
- start migration with profiles
- consider using drupal.org issue system for bugs and tasks
- try to put logic into modules that can be reused by other projects
- we should have tasks that newbies can take care of (compare with http://kernelnewbies.org/)
- use coding standards and "code sniffer"
- tools clean-up work page: http://piratenpad.de/8W0q9Poqv7
- feature brainstorm: http://piratenpad.de/jBwd50aWk5
Task division
- guaka: migration and general help
- matthias: theming
- crumbking: theming
- meinhard: project management, migration, sys admin
- bikepunk: finish the FAQs update task force
Better deployment process for rox
- copy current master branch to new "abandoned" branch
- copy current production branch to master branch
- remove alpha branch
- new process:
- develop locally (possibly with local branches)
- push to master
- code review (at least one person, announce to mailing list and wait for response)
- pull master branch to test web server (lamb)
- test the test site
- if ok: merge master into production
- pull production branch on live web server (deer)
- test the live site
