Date
Attendees
Goals - Technical Meeting
1st Friday of Month will be webinar open to anyone with the link (will be on the Clowder main website).
Other 3 weeks will be technical meeting for developers to discuss code, planning, etc.
- Will start inviting more people - and we can send link to people on individual basis for invitation
- CSSI - we now have some funding to pay for hardening of Clowder outside of work done by project specific work
Discussion items
| Item | Who | Notes |
|---|---|---|
| Codebase is outdated/libraries | Luigi Marini |
Note: updating Scala/Play was very difficult - we need to do this so we don't have to do such major version updates Luigi has a wiki page where he is tracking what needs updated - this needs reformatted Identify a bunch of things we don't use anymore - remove them - legacy code that has not been used since the project that placed it in there Testing Suite are recommended - but current one is very old and tests are configured strangely in order to be able to run them If anyone has ideas on best practices for refactoring and updating tests - please speak up |
| Documentation | We do have Sphinx documentation that is getting built - it is rough - but it is there This is the best way to keep going - but it needs revitalized Everyone should pitch in Swagger and Sphinx should be part of PR for new features - and should be enforced There is a branch for the Sphinx Documentation Collaborators can write this and contribute and you can include it with the PR - that way you are not solely responsible for docs Contributors are not only coders - they contribute design, documentation, - they are mentioned as contributor! There is a contributing.md - is this the current contributor guide? can it be changed to be more strict on requirements on writing tests and docs? | |
| CSSI Meeting at PEARC - Promoting | 1 Day registration available - rent a mini-van and drive up - need to know who wants to go Rough planning doc: https://docs.google.com/document/d/16eFM5tOGfZq6gKX09CDnvIHo6PZ89V_wQET8wyD2_IQ/edit?usp=sharing Building an on-going open source community Need to stay active on mailing lists, slack, etc. - office hours on slack Slack add on: https://tettra.co/ Advertise - video - talk about it Any video that is posted to U of I site must be close captioned Planning to use Zoom - which will support 100 people - to record PEARC as well as the Once a Month meetings | |
| Contributor Process | Do we need to refine? update Docs? Whether code should reside in both git and opensource still |