= For the next meeting

- Roles in salsa: which roles should we assign and why?

Decided: all people asking for access get Developer (thus write access to everything).
DDs are Masters by default, DMs are Masters only after they worked on Qt/KDE packages for several months, until then Developers.

- Repo layout:
  - I (Lisandro) would like to have a clear text so anyone knows where each project should live.

Agreed:

- qt: everything from qt.io
- kde: frameworks/plasma/apps
- 3rdparty: non-Qt stuff that needs to be packaged because it is used by something packaged (and not already in Debian)
- extras: everything else

Remember to update https://salsa.debian.org/salsa/AliothRewriter/blob/master/definitions/qt-kde-team.conf after we merge extras.
Agreed: update Vcs URLs manually, not automatically

  - Should we move repos around? (except cornercases, like non published packages?)
- Should we store upstream sources in the repos?
  
Keeping only debian/ means:
  Pros:
  - Smaller disk/¿bandwith? footprint.
  - No dependency on external "magic" tools like gbp.
  - No need to check if the applied patches are against the real source code or
    an accidentaly modified one.
  - Very easy cleaning up: git clean -xdff (pure git, no need of external tools).
  - [Qt specific] source from git needs pre processing via scripts (syncqt).
  
  Cons:
  - Source needs to be kept around while developing.
  - A maintainer starting to work with the package needs to run either uscan
    (Debian revision 1) or dget (other Debian revisions).

- Documentation: we really need to coordinate a place/method to have this done.