launchpad development|
Size: 202
Comment:
|
Size: 1199
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| = Go go Banana Slugs! = | https://launchpad.net/~yellow/+mugshots |
| Line 5: | Line 5: |
| == Subscriptions == | Slogan for public consumption: '''''Go go Golden Horde!''''' |
| Line 7: | Line 7: |
| Brad and Benji are working on [[LEP/BetterBugSubscriptionsAndNotifications]], specifics are at [[yellow/Subscriptions]]. | Slogan when we feel tired: '''''Go go [[http://en.wikipedia.org/wiki/File:Banana_slug_closeup.jpg|Yellow Banana Slugs]]!''''' Current project is [[LEP/ParallelTesting]] . == Notes from weekly review call == === Resolutions === * Next "new to us" project (like charms) when we do not know enough to write tests initially, we want to try this process: * Prototype (no tests, as a rule) * Squad discussion: lessons learned, design decisions * Begin coding, TDD. * We will read all ~yellow reviews when in feature development. * We are interested in using Go for our next project, if appropriate. * Short term goal: charm is ready for review next Tuesday, Feb 14. We would like to provide feedback to the juju team about our experience, and we are willing to take time to do so. Gary is reaching out to hazmat and SpamapS to see how it would be best to do this. === Tabled === * How will we share smaller design decisions that we learn during the day? The daily call is good but not good enough. IRC? micro-blogging? |
Yellow Squad Wiki Home
https://launchpad.net/~yellow/+mugshots
Slogan for public consumption: Go go Golden Horde!
Slogan when we feel tired: Go go Yellow Banana Slugs!
Current project is LEP/ParallelTesting .
Notes from weekly review call
Resolutions
- Next "new to us" project (like charms) when we do not know enough to write tests initially, we want to try this process:
- Prototype (no tests, as a rule)
- Squad discussion: lessons learned, design decisions
- Begin coding, TDD.
- We will read all ~yellow reviews when in feature development.
- We are interested in using Go for our next project, if appropriate.
- Short term goal: charm is ready for review next Tuesday, Feb 14. We would like to provide feedback to the juju team about our experience, and we are willing to take time to do so. Gary is reaching out to hazmat and SpamapS to see how it would be best to do this.
Tabled
- How will we share smaller design decisions that we learn during the day? The daily call is good but not good enough. IRC? micro-blogging?
