README

This website is the new documentation website for the carsharing platform cooperatively developed by The Mobility Factory.

Some (older) documentation can also be found here: https://docs.themobilityfactory.coop/

Gitlab guide

Gitlab is used by TMF to manage everything that has to do with the carsharing platform. Getting support, reporting bugs and describing new feature ideas and member needs, is all managed through Gitlab.

The platform has been used internally for years by the team. In order to stream line processes and avoid and information spread across different tools the team started re-organizing its tools landscape in favor of Gitlab.

This page acts as a guide on how to use Gitlab as a TMF member representative for members that makes use of the carsharing platform. You can request access to our Gitlab by contacting us.

By default logging into Gitlab 5 projects are visible:

Support & help

If you need support or help with anything related to the platform you can contact TMF directly on the known support email. You don't necessary need access to Gitlab to interact with TMF support.

If you prefer to follow up on support issues through a user interface instead of email you can open support issues directly in the Helpdesk project. If you prefer to use email you can continue to send support questions to the support email.

Support issues created via email will not show up when you login on Gitlab at the moment. If you want to follow up on the status of your support issues you should create them via the Gitlab user interface.

Member Needs

The Member Needs project bundles issues that describe a need, use case or user story that exist at one or more TMF members.

You can browse around the issues in this project to see what needs other TMF members have, provide your point of view in the comment section and share your cooperative ideas. Doing this help finding synergies between TMF members. Based on the issues in this project the TMF team decides on what needs to be developed next.

Guidelines for opening the issue

• choose a good, comprehensive title that also others can understand, without adding too much detail in the title

• provide context in the issue description

• focus on the need and or goal that you want to accomplish, instead of on the solution

Examples of what should not be in this project

What should not be in this project	What to do instead
user X has problem Y when using the app	contact support@ or open a bug report
this button does not work	open a bug report
I want a button here in the app that does Z	don't focus on the solution (the button), but what is the need you try to fulfill. Describe the need in an issue in this project

Visibility of issues

By default all of the issues in this project are visible by other members. On a regular basis TMF will groom the issues in this project, connect relevant issues to each other.

Bug reporting

There are 2 projects to collect issues that describe bugs and incident on the platform depending on where the bug occurs.

You can read more about directly reporting bugs here.

Cooperative docs

The cooperative docs project contains the contents documentation on The Mobility Factory as a platform cooperative. You can find here legal information, statutes, policies and the general service agreement.