yunity heartbeat 2016-10-30

Created by Janina Abels
Last updated: Oct 31, 2016 by Philip Engelbutzeder
4 min read

The yunity heartbeat - what has each team done, what are they doing and what do they need help with.

Foodsharing.de Development.

Done

The foodsharing.de development is reopened! To keep track of what is going on in that regard visit the new foodsharing devblog.
For direct answers to pressing questions like 'What?! Why?! How?!" read this blog entry written by Matthias Larisch. Also taken from that blog post are these already completed achievements:

  • Having a development environment that is checked out, setup and running with 3 commands (using docker/docker compose)
  • Integration of Codeception for Acceptance, API and Unit tests
  • Local execution of all tests
  • Automated execution of tests in a CI system (Gitlab CI) for every push
  • Acceptance tests for a very little selection of pages, more to come
  • Open issue tracker to include the community in bug reporting and feature discussion
  • Having one contributor working on feature development
  • Having three contributors working on fixing (security) issues and refactoring the code

Some days later Matthias Larisch was motivated to move the wiki, Mumble and the media database on a new server to fix some security issues present before. More about this can be read in this blog post.

In Progress

Most of the time is now spent to make contribution as easy as possible. That will include refactoring, means touching almost every single line of code in the code base (approx. 50000 of them are there). We made the decision to slowly move in some core components of symfony and hopefully end up with a workable, fully tested code base that can be deployed from a continuous integration system automatically when a core contributor approves the changes. Having the platform open sourced is a strong wish from most contributors as it fits the vision of sharing.

Matthias Larisch, foodsharing devblog


Foodsaving Tool.

Done

Created an open chatroom, linked in the README of the GitHub repository, bridged it to the Slack channel

Included more functionality & code structure:

  • Picker for groups in navigation bar
  • Added translation support, language picker in navigation bar
  • Unified templates for main pages (e.g. group, store) and splash pages (login, signup)
  • Signup & login page in directive-free style, using ng-click
  • Convention for partials (components which are using inside pages) - they now start with an underscore (_)

In Progress

Started discussing features on a product level - look at the current questions here and contribute your ideas! (E.g. should users be required to enter first/last name, do we need a feature for trial pickups, how do we prevent abuse of powers)

Planning the foodsaving tool. Started collecting user requirements in a written way - currently only Taiwan, more hopefully coming soon.

Looking for a logo! Need to answer the basic questions: "What is the message we want to communicate? Which emotion do we want to effect?"
Proposals:

 

Post your ideas in GitHub or in Slack in #foodsaving-tool-plan!


Foodsaving worldwide.

Done

Finally we held a syscon about how to name the FSINT sections on the wiki and on Slack, which resulted in: Foodsaving worldwide! (Hence the shortened title of this paragraph... (wink))

Tilmann put the graphics and drafts for logos on the wiki to make them accessible and editable for anybody interested.

In Progress

Challenges/help needed

  • more feedback and co-creation wanted with regards to the material to get started!
  • summary of the Russian foodsharing projects visible on vk.com is still missing


IT-Service.

Done

  • setting up channels in matrix (via riot chat) incl. incoming and outgoing webhooks. (from matrix you can chat towards slack and other way around) (Tilmann, Kaiser Mikato) 
  • rocket.chat and slack integration (Paul Free)

In Progress

Challenges/help needed

  • rocket.chat import freezing while doing so 


Structure.

Done

In Progress

Challenges/help needed

  • what does yunity actually signify to its contributors individually?
  • how can we be open to everybody and still protect an atmosphere of trust if we encounter destructive and unreasonable behaviors?


WuppHouse.

Done

In Progress

  • analyzing Mietshäusersyndikat principle and formal paper (Bodhi Neiser)

Challenges/help needed

  • finding the right building
  • finding the right legal setup
  • developing a clear concept of how to live together in a WuppHouse


Translation.

Done

In Progress

  • foodsharing devblog translation via gitlab (everybody can just work on an issue... (smile))
  • translation of the first strings of the foodsaving tool via transifex (Tilmann, Janina Abels)

Challenges/help needed

  • French translation of the foodsharing devblog issued on gitlab


Public Relations.

Done

Challenges/help needed

  • do we want to paper print? (by Katia)


Community Relations.

In Progress


Future WuppDays.

In Progress

  • looking for a WuppSpace in Austria, close to Vienna (Chrisi)


To the extent possible under law, the yunity wiki contributors have waived all copyright and related or neighboring rights to the content of the yunity wiki. More information...

You have an account but can't edit or create pages? Write us in the open chatroom or in our yunity Slack!