Hello Everyone! I feel like we made good progress so far and the existing actions are being used but I think we have a few things to discuss that are about the process/administrative side of things. Some people discussed some of these in either slack or gh issues but I wanted to give it some focused attention on this ML:
1. Versioning and releasing actions What is the process? Normal asf release? Something simpler? This also touches on the next point 2. mono-repo vs one repo per action I am going to list the arguments pro and contra use of monorepo in random order, please feel free to add some if I missed anything. + Community building is easier + One place to watch - versioning/tagging harder (though thanks to Pavan dependabot now supports tags for actions in monorepos!) - larger download needed for CI (there is no way to do a sparse checkout for actions), this will be a bigger problem over time - no way to watch just one action, might deter regular contributions - one repo per action allows publication to the marketplace and is the intended architecture - long names for `uses: apache/instastructure-actions/stash/restore@stash/v1` vs `apache/stash-action@v1` 3. repo name, as shown above the current name is quite lengthy and especially if we would stick with the monorepo. From my understanding of Github Enterprise it should be possible to create a new org under the Apache Enterprise Github that basically acts as a namespace but uses the same runner contingent, settings etc. [1]. I feel like that would be the best of both worlds with an `apache-actions` org -> `uses apache-actions/stash@v1`. Contributors can watch the repo they are interested in without noise but it's still easy to get an overview of all actions through the org -> Community. I don't know if this is feasible at all and will of course defer to INFRA :) Best Jacob [1] https://docs.github.com/en/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#creating-a-new-organization --------------------------------------------------------------------- To unsubscribe, e-mail: ghactions-unsubscr...@infra.apache.org For additional commands, e-mail: ghactions-h...@infra.apache.org
