Tomorrow, we will be having our next weekly hangout at 10:00 AM ET until 11:00 AM ET.
Anyone is welcome to join at this link: https://bit.ly/slicer-googlemeet-hosted-by-kitware
Agenda:
Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.
Thanks
Sam and Ebrahim
I have a conflicting meeting tomorrow. I may join late if people are still around when the other ends.
Notes from the meeting:
It is hosted on digitalocean VM, not at Kitware, unlike most other hosted services. For example download.slicer.org is netflify. We should move slicer.org to a netlify page; digitalocean vm is not very accessible and for changes it is pulling from a repo anyway.
The slicer.org domain expires in 2027 so we should probably pin down who owns and manages it.
Next project week meeting will be in Boston so that will be a good chance to address some of this slicer.org stuff – get it to netlify and potentially hosted at Kitware.
We can also bring into project week the challenging project of moving factoies to github actions. Paid runners are one option, but it depends on how much this costs. A lower cost but higher maintenance middle-ground is self-hosted runners at Kitware that maintainers can access (perhaps in a “DMZ”).
Should copy-pasted AI generated content be distinguished somehow with a disclaimer?
Maybe some kind of discourse plugin that pops up a suggestion to insert a standard AI generated content disclaimer. This would increase the chances that people at least tag it as AI-generated sometimes.
Maybe a template that includes “Human written / AI-assisted / AI generated” to encourage people to label their post. → posted a question about this on the Discourse’s forum.