## Sections description:

### Groups

The group section defines which groups have to be imported and how this has to be done.

```yaml
groups:
    <grp-name>:
        backend: phabricator | epfl | ...
        username: <user login>
        import-scheme:
            type: project | sub-project | ignore
            user-import-strategy: additive | synchronize
            project: <project name>
            name: <import name>
```

For groups you have to define from which backend you have to get them. They will be transferred as project in phabricator. The way they are imported can be configured through the **import-scheme**.

The two main ways to import groups are for now as projects or as sub-projects. This is defined by the **type** key. In both case the name of the (sub-)project to create can be defined by the **name** entry.
In the case of sub-projects, the parent project name has to be given with the key **project**.

Names could use placeholders that will be replaced, for know only __{original_name}__ can be used. This will be replaced by the original name of the group.

The **user-import-strategy** defines how members are treated, in **additive** mode, users to import are only added to the pre-existing projects. In synchronize mode if pre-existing users are not in the group that is imported, they will be removed. If this is not specified, **additive** will be used.