#userops — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #userops, aggregated by home.social.
-
This is a high bar for how to run an open service. I like it!
"""I believe that if we enable contributions to services rather than just the software, we reap the advantages of true open source. That means enabling users to make a change to a running service and experience that change themselves.
"""
You still with me?
Yes, that means opening a pull request against a running service and experiencing that change before it's merged.
[ . . . ] Rapid deployment of changes to services is a powerful capability that's highly sought after. For example, GitHub deploys changes before they're merged. [ . . . ]
opensource.com/article/21/4/op…
Combining SaaS and not just #UserOps but #UserDevOps? Can it be done? It's a very cool idea with important effects. -
Specifically one subthread went into pure monetary cost, specifically hardware or hosting cost. And the thing I want to reply to is the take "but there is nothing free software developers can do about this".
It's not binary, lower cost is not as good as without cost, but it's better than higher cost. If we target lower-cost platforms like old phones, old computers and SoC boards, we widen the funnel of who can use the software.
If we make the #UserOps better, we increase the chance that your friend is hosting the software on some machine, even if you cannot.
If we make a true p2p app that doesn't require a public IP, we greatly increase the number of people who can run it. -
@cj If you don't mind me reawakening this thread, I think this is a great layer to put on top of the lower free software layer. The lower layer provides the foundation of the four freedoms through the license and through community practices.
The next layer of user freedom involves #userops, #userdev and giving greater recognition to contributions outside code, i.e. documentation, evangelism, support and giving users a say in the development of the software in terms of priorities. I think "those who do, decide" is still an inevitable and necessary component, but you can foster a project culture where those who do (and therefore in practice decide) find it in their interest to develop the features user want, need and deserve, and which provide user autonomy. -
One single scene had a team of 15-20 engineers working on it for weeks, just to make a tentacle grab you, flip you on your back and you being able to fire back at it from your back.
Imagine what a AAA budget like that could do for free software solving the problems of distributed applications, deployment, composability and interaction design, ushering in a new era of users doing programming. How do we get the money for that?
#userops #userdev invidio.us/watch?v=BQ3iqq49Ew8… -
Can we still call it #userops? Or is it PeopleOps or ContributorOps now? DevelopmentByOtherMeansOps?
I don't think there's anything degrading in "user" or "consumer", we all create some things and consume or use other things, unless we're subsistence farmers.
If someone suggests another term that describes the role clearly and doesn't carry any stigma, I'm open to it. -
@z428 yeah I'm more interested in learning #devOps / #userOps skills than extending my coding skills in an engineering direction. I think we need far more server farmers than we need engineers. But even doing server farming requires at least a basic knowledge of #Bash, and probably always will. Designing good UI needs coding too (HTML/CSS is code!). Coding has many uses other than back-end software engineering.
@alcinnz