Fluid and Infusion Discussion

[Justin Obara]

Hi Everyone,

I?m organizing a meeting to discuss Fluid and Infusion. It?s set to take place on Dec 2 at 9am ET. Please join us in the zoom <https://ocadu.zoom.us/j/727986784?pwd=T2VxRXYvenUzbkI4YWozU0x3NEVGQT09> call.

I?d like to discuss the infrastructure that the Fluid Project uses such as JIRA for Infusion?s issue tracking, the wiki, and other logistical pieces. If there is time it would also be good to discuss some higher level questions about Fluid and Infusion.

Thoughts to seed the conversation:

What is the fluid community?
I think we might have a written up another definition of this in one of our Infusion meetings.
Migrate JIRA issues to GitHub issues
I believe only Infusion is left, the rest have been manually migrated
Would be nice to have an automated process for this; however that may be more work to make than would be valuable.
Ned has looked into creating a static site for existing issues as a backup. Some of this work could also be leveraged for the automation; namely the JSON object generated that includes all the issue data.
GitHub?s import tool for this has been deprecated and was removed earlier this year, but could still use the issue api; although the results would be similar to doing it by hand
There are currently 600+ open issues. 
I?ve tried to migrate out non-infusion specific issues
Example of a manually migrated issue <https://github.com/fluid-project/infusion-docs/issues/303>
Could use another pass to clean up issues before migration.
Will probably only migrate open issues.
JIRA would be left as is after migration, but we?d add a banner notification about the migration. 
We could change permissions to make it harder to add new issues too.
Use conventional commit style commit messages
Setup release-please for repos to make it easier to cut releases
Could also setup automation to create npm packages when a release is cut
Would this change necessitate squash merges?
Should we setup Dependabot/renovate for the repos?
This would require us to commit the package-lock file and change how we save dependencies
What to do about the wiki?
It?s gotten slow on the cloud
We should migrate docs to the infusion-docs site
Probably the rest should just stay as is until we can find a viable alternative
The project website <https://fluidproject.org/> and docs site <https://docs.fluidproject.org/infusion/development/> could use a refresh. 
Should they be combined into one site?
If we have an update on what the fluid project/community is that should be updated on the site. Right now it?s Infusion heavy and also IDRC focused. Is that correct?
What is the future/trajectory of Infusion and UIO?

Thanks
Justin


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocadu.ca/pipermail/fluid-work/attachments/20241118/46a828df/attachment.htm>