Agenda

Points for discussion:

• Present Philips project overview.

• Applicants;

• Sort existing application into various categories.

• Change application form to have rigid category selection (i.e. drop-down menu) to make further sorting much easier → AP for a Dev.

• Documentation;

• Create/store development diagrams (i.e. application process flow, data model, etc).

• Research existing platforms (i.e. number of users, public API?, etc)

• Identify existing problems (i.e. disagreement between food-sharers) and potential problems (i.e. Freecycle split in the UK because users felt they were dominated by American founders)

• Project structure;

• Identify capabilities of existing contributors (i.e. those of us at WuppDays)

• General, high-level planning. Work on an appropriate model and 'publish'

• Create a WuppDays 'bucket-list'

• AOB

Minutes 

Present: Philip B, Camille C, Doug W, Raphael F, Martin S

Apologies: None

Location: Malo

[Meeting begins 11:15]

PB: Project overview sprung from attempt to create a one­-page project summary – in order to create a summary, a full documentation was required first. Overview goes into detail in all areas of the project (e.g. purpose, targets, execution, etc.)

• • DW: So anyone can read this document and either understand what they need to, or know where to look?

  • PB: Exactly.

  • RF: Suggests changing 'server' to 'partners'.

  • DW: Do you want to work on your own for a little more before the document becomes collaborative?

  • PB: Yes, a few more days before it becomes collaborative.

  • DW: May require migration to Google docs.

  • [applause of PB achievement]

DW: Sorting of existing applicants is underway.

• • RF: Adrean is currently sorting translators, design, etc.

  • DW: We should define fields (on form) to speed up application flow.

  • All: Teams we should have: Development split into the 5 sub­groups, Design, Translation, Marketing/Communication, Legal, Accomodation (offers and research), Project Management, Regional facilitator

DW: Started researching the existing platforms, should collaborate effort with user needs.

• • RF: Good to focus on the mapping platforms, as there are less data usage problems.

  • MS: Including cargo bikes in Berlin, Freifunk, etc.

CC: Describes high-­level planning.

• • MS: Will it overlap with the development team? They’ve done a lot of planning and we don’t want to re­do work.

  • RF: We should all use Trello [all need to sign up]

DW: Should we make a WuppDays ‘bucket-list of tasks?’

• • MS: Just use Trello with red-­tags. Dev have to use Waffle for GitHub integration.

  • RF: Better for everyone else to use Trello, but may need an introduction as it can be misused

  • MS: Have a README column at start of each Trello (glossary, links, how­-to-­use, etc)

RF: Proposes regional managers.

• • DW: What for?

  • RF: When going around to different countries and presenting the project. (marketing/PR/etc) Wrt project launches, it’s worth focussing on FoodSaving.

DW: Is it ok to publish minutes/accounts online?

• • RF: Yes, and should be done.

[Meeting ends 12:35]