Question | Answer |
---|---|
Who are current developers (and NREN/Organisation)? | Mijo Đerek, Miroslav Milinovic (SRCE) |
Can the previous developers be contacted? | no previous developers |
Where is the code repository? | in internal SRCE repository (git); plan to move to GEANT git |
Where is documentation? | Code of Conduct Monitoring Tool |
Which language/libraries/database are used? | PHP, PERL, MySQL, Apache (HTML, CSS) |
What code maintenance is needed? | none |
Which new features are needed? | add support for CoCo v.2. |
Was the IPR check for the tool done? | no |
Where is the development roadmap? | no immediate dev. plans (pending CoCo v.2.) |
Which project management tool is used? | none |
What is the response of the code security audit? | never audited (by GEANT) |
What are the biggest gaps in terms of development? | none |
Who is operating tool? | SRCE (https://monitor.edugain.org/coco) |
What is the operational contact? | miro@srce.hr, mijo@srce.hr |
Where is the service hosted? | monitor.eduroam,.org (monitor.edugain.org) |
What is the deployment model (manual, ansible, docker, etc)? | manual |
Where is the deployment and operations documentation? | git / comments in code |
How is tool usage monitored. Are the statistics publicly available? | no usage stats available; no outside monitoring (logs kept; overall website monitoring by SRCE in place) |
How is tool monitored, who is alerted? | overall website monitoring by SRCE in place; developers are alerted |
How is service backup (if needed)? | SRCE backup & archiving |
Is tool processing personal data, is GDPR resolved (ok if you don’t know the answer) | no |
What are the biggest gaps in terms of operations? | none that we are aware of |