Hi all,

I'd like to spin up a lemmy instance with some changes I'd like to make this upcoming weekend, and I'd like to self host a ci/cd pipeline for it.

At work, we use Jenkins tied to Jira.

Our procedure is as follows:

1. We feature branch, build/deploy to dev (manual), self/peer verify.
2. Merge to master, build/deploy to dev (triggered by jira), QA tests
3. Promote to stage (deploy artifact from previous build, triggered by Jira), QA tests
4. Promote to prod, and pray we didn't miss any edge cases lol

I'm not married to Jenkins and I'd be open to other options, if there's something you've tried that you think is better, I'd love to hear it!

Would be nice to have auto triggers that are tied to kanban stories, but not necessary.

Looking to migrate off of spotify. I will miss it for suggesting new songs and keeping up with new releases. What do you use to stay up to date, but off of paid services?

I've had three glasses of wine after a long day at work, and I've began thinking about the slow shift towards federalization/decentralization.

I find myself concerned about the question of incentives. What motivates the owners and maintainers of federated services to continue their efforts over the years? Donations alone are unlikely to cover the costs of servers, let alone the time required for code/infra maintenance, along with community moderation.

It is evident that most successful open source projects have found alternative avenues to sustain Incentivisation. One common approach is offering enterprise packages or services, which generate revenue to support ongoing development and maintenance. Additionally, some projects find support as subsets of larger corporations, such as Canonical, HashiCorp, Apache, MongoDB, k8s, Chromium, Android, Red Hat, and many more.

I am sure that many of us have witnessed many donation-based or entirely free and open-source (FOSS) projects lose traction over time. In my observations, this can be attributed to core maintainers losing interest or facing limitations in dedicating themselves to the project in the long run. The absence of financial incentives can make it challenging to sustain motivation, as maintaining and developing projects require significant time and expertise, and a genuine interest in the product.

What can be done to address these problems? Is it something like decentralized autonomous organizations (DAOs)?

DAOs provide token-based incentives, allowing contributors to earn tokens representing ownership or value in the project. These tokens can be exchanged or redeemed for various benefits within the decentralized ecosystem. By aligning the interests of contributors with the success of the project, DAOs offer a sustainable incentive structure, while maintaining their decentralized nature.

Although incentives pose a valid concern for a decentralized future, it is important to acknowledge that sustainable models exist. Through the exploration of alternative mechanisms such as DAOs and hybrid models, we can create incentive structures that attract and retain contributors over the long term. I strongly believe that for decentralized projects to thrive and maintain momentum, it is crucial for them to embrace alternative models that effectively retain talented individuals. As these projects continue to innovate and adapt, exploring diverse incentive structures becomes essential to ensure their long-term success.

Thoughts?

I'm getting close to my 4gb RPI 4b's mem limit ~80% and would like to migrate from it to a low power SFF thin client. What are some good options?