ecrin-github / ecrin-github/rms-portal
set up ticketing system for crr
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
@Gerd-ECRIN suggested the use of a ticketting system for a better management of repository related requests.
see below quotation.
a quick search finds at least 2 projects that seems suitable:
https://www.opensupports.com/features/
https://osticket.com/
to trial.
> 1. Having a single point of contact. Using [crr@ecrin.org](mailto:crr@ecrin.org) for incoming and outgoing emails so that the communication isn't split into many personal accounts. As you know emails will be forwarded and so the single point of contact will be sure washed-out. People from outside will write to a person which has to forward to the person in charge.
> 2. All communication will be traceable. What means if there will be questions or disagreements between partners in future and maybe the person in charge has changed the dialogs will be still readable for others. Internal it helps to keep up the responsibility. If a new mail comes up, everyone from the team can see, that the person in charge has answered or not and remind.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.