On Thu, 06 Jan 2022 09:44:27 -0600 Katherine Cox-Buday <[email protected]> wrote: Hi Katherine,
> I hope we can take the reasons people make these channels and bring > them back to Guix proper to make contributing here just as easy. Contributing to Guix upstream is definitely high priority for the guixrus channel and the whereiseverone community. For example, as a small community we are planning to organize a monthly channel cleanup day in which we look at all the packages in guixrus and determine which packages should be sent upstream and which packages still need more work. This style of iteration can serve as an additional and more intimate layer of onboarding for newer users because we review patches on https://lists.sr.ht/~whereiseveryone/guixrus as well as discuss package issues on #whereiseveryone (libera.chat) in a short feedback loop. In the process of doing the above we also explain the upstream contribution process to newcomers. My hope is that higher-quality packages by first-time Guixers will become more commonplace in upstream issue trackers. We are also experimenting with using builds.sr.ht to run the guix lint checker, and more when submitting patches to guixrus/upstream thanks to dhruvin: https://builds.sr.ht/~dhruvin/job/665098 https://builds.sr.ht/~dhruvin/job/665205 We are developing a package search[1] in the context of the guixrus channel web site: https://paste.sr.ht/~dhruvin/0828f7b1df2ffa7b7b31c50e07ef043d94caeea0 guixrus had 83 packages that day. If interested in the library that was used to generate the json paste output see this repo: https://git.sr.ht/~dhruvin/doug A top priority goal of the whereiseveryone community is to encourage new Guixers to contribute to Guix (upstream as well as whereiseveryone community projects). We want to facilitate, develop, and discuss that process, as well as experiment with fun ideas and tools for Guix. It's ambitious, I know. We'll take it one S-expression at a time. happy hacking, https://sr.ht/~whereiseveryone/
