The team has done a lot since we set sail on A New Voyage. Letβs talk about what we have been up to and what we have planned for the future in our State of Solus: August 2023 post!
New Blog Post: State of Solus - August 2023
- Edited
"Thanks everyone! We look forward to continuing on this journey together, and we hope youβll join us for the adventure."
I'm so there
- Edited
That's an impressive to-do list for the beginning of fourth-quarter. That's not too many weeks away.
- Edited
Have I already written how great you people are ??
@davidjharder Were alternatives to Github discussed ? Less features (?) but also less Microsoft sponsored ?
Or it is currently an obvious choice and you always keep a way of walking away in case of need ?
(I'm in the mindset that I don't always want to use what most people are using... this is what led me to discover Solus. But I can understand it when the features in place are what a team needs to make progress
οΈ )
I find it great that you are working on a way of onboarding - and offboarding - people easily : too much experiences IRL lately when groups were protective of their "baby" and not letting any help in, even when it was highly needed.
"Frustratingly slow Python db queries"
-> Is this a Python or query issue ? (it's never the database ! ^^)Just the fact that this monthly blog post is published is already a great step forward compared to the beginning of the year.
Keep going Solus Crew ! The horizon is the limit
I'm really happy to be able to read all this, I'm very happy that it's going on so well. I wish you the best of luck on your journey and I am grateful that you continue to do so.
Sorry google translator.
[deleted]
Were alternatives to Github discussed ? Less features (?) but also less Microsoft sponsored ?
Or it is currently an obvious choice and you always keep a way of walking away in case of need ?
I'm pretty sure they've considered the alternatives, but prioritized the best workflow. Like any choice made, it can be re-evaluated later if needed.
MichelDwo We don't care if it's "Microsoft sponsored". We're not anti-Microsoft. GitHub saves us from having to self-host GitLab (costs money), pay for hosting it (costs money), pay GitLab (costs even more) or be shooting ourselves in the foot with free-tier limitations (not feasible at an OS scale, I mean alone we have 3x the top-level group users already), etc.
That isn't even touching on GitHub free CI / CD action runners, GitHub Pages, hub & gh CLI tools, experience with graphql and REST GitHub APIs for tooling, discoverability of it being the largest platform for code sharing, useful organizational capabilities such as repo and org wide workboards in both task and KANBAN style that actually exceed Phabricator workboard capabilities, IDE integrations, and more.
I could spend about an hour writing out the pros of just rolling GitHub for our org even without having to pay anything. I could have an endless list of cons of us having to self-host something like GitLab, meanwhile the only arguments I've heard against GitHub is "not open source" and "owned by Microsoft", and we are far too pragmatic to care about either.
And now, everything is said: pragmatism, Joshua Strobl already made him his master word before leaving Solus in 2022.
On his return to the helm in April 2023, he did not change his logic and it is a very good thing: define a line of conduct, organize the resulting priorities and stick to it without deviating from it, in order to avoid falling into dead ends that could become sources of problems. .
It is this state of mind that has been able to federate around him the whole team of developers who does not spare their efforts to offer its users, a quality distribution, with the appreciable support of Ikey Doherty, its founder, which will create profitable synergies between Solus and Serpent OS. Without forgetting the community of users very attached to its distribution, which can intervene to make suggestions or offer improvements to the existing.
What is exciting is this medium-long term vision that drives this community today.
Long life to Solus and that the ominous birds predicted its imminent disappearance during the major breakdown of this beginning of the year recognize that they were wrong.
Cheers!
- Edited
penny-farthing Trust me when I say I am by no means having folks "federate" around me, so let's try to dispel that idea I'm very hands off on day-to-day operations of Solus, as my focus is on Buddies of Budgie. Don't get me wrong, really love all the work being done on Solus, but it shouldn't be attributed to me. There is a seriously badass team working on all parts of Solus now that actually have the authority and trust to take ownership of issues, make decisions and take action. That simply was not the case with the old leadership structure.
I would say that team communication is really great as well and while it's taken a bit for the team structure to more organically form and self-organize, things are really chugging along now. As a very relevant example with this blog post, @davidjharder took the lead on it with us in Comms Team collaborating on the blog post. David made sure it was up on the blog, we figured out a way of communicating it out to people, and the only thing I did as part of the process (beyond the collaboration) is the Mastodon and X posts. Remember when I used to always be the one posting on social? Check Solus accounts now and you'll see a very different and much healthier story!
The old leadership style basically would've meant: I write blog. I post blog. I talk about blog. I much prefer the new approach / ways and in the upcoming weeks when I'm furloughed, I'm going to be writing tooling to make it so even more team members are able to work asynchronously and be unblocked more frequently (e.g. post-sync ISO communication, OpenCollective export + import for mailing lists).
@ermo, @ikey and myself never would've gotten involved if there wasn't going to be new forms of leadership and ability for folks to take ownership of parts of Solus. We didn't want the Solus of old, the team that you see nowadays (and even returnees!) didn't want it, and the community wanted change too. Lots of Solus leadership ideas have been inspired by lessons learned and applied in BoB and Serpent.
So no, no rallying behind me
OK, thank you for your feedback, I now have a better understanding of the new Solus way of working.
With exciting prospects, thanks again to the whole team.
JoshStrobl Remember when I used to always be the one posting on
socialeverywhere?
fify