Collect all properties files and labels.json within at least two github-Repos: to.science.resources and orca.resources

[aquast]

Create a repo for to.science.resources (for frl for instance) and a separate repo for orca

[peterreimer]

Shouldn't we have a single to.science.resources repo with branches for each to.science-instance? Or one repo per instance with matching names like

• to.science.resources.frl
• to.science.resources.orca
• to.science.resources.edoweb

[aquast]

Good question. What would you prefer?

My first thought was to create a single repository for each customer, which may facilitate usage of the respectively repository and prevents us from chaos within a one for all repository.

Do we have a tool for an "Abstimmung"?

[peterreimer]

we have https://wolke.hbz-nrw.de/index.php/apps/forms/
have it never used, though.

[aquast]

Can you than provide us with a form, please ;-)

[peterreimer]

Vote now!
https://wolke.hbz-nrw.de/index.php/apps/forms/WXLFPcioS6DBMwm7

[aquast]

Zwei Umfragen?

[hadoud]

Meine Umfrage habe ich gelöscht.

[aquast]

Refinement:

• files with *.properties and *.json should come in new directory "resources"
• Only these files should be taken into new git repo.
• One repo for each customer: frl, edoweb, orca.
• Start with orca: repo name = orca.resources
• Tag repo with dwi and orca

[aquast]

@peterreimer : please make it so

[peterreimer]

your were faster than me.

[aquast]

jep, I do need this ;-)

[peterreimer]

Voting results