Bluefin discussions moving to GitHub

Hi ya’ll, Bluefin will be moving to GitHub discussions in the future for discussions: I’ve set up a placeholder section: ublue-os/bluefin · Discussions · GitHub

The Bluefin announcements will also be moving to the blog: Blog | Bluefin - URL is not final.

I’ll leave this section open for the next few weeks then I’ll be marking it read-only once we’ve moved the announcements into the blog for archival reasons, etc. I’ll make sure to update the terminal MOTD before it goes live, thanks!

What is the reason? Discource is IMHO much better way to discuss.

Target audience and focus mostly, it’s easier for our AI tools to index one source of truth in GitHub than spread out over a bunch of places.

I agree with you. It is more convenient and easier to follow everything here

Ok. That makes sense, but I am still a bit sad about it. I enjoy coming to the universal-blue.discourse.group and reading about all the different flavors and general discussion in one place.This feels like a fragmentation of the ublue community. Guess that’s evolution in action. :wink:

Should one assume that this move to GitHub discussion for Bluefin portends the eventual moves of Bazzite and Aurora to their respective GitHub discussions?

Hey @j0rge ,

Afaik it’s possible to create GH Discussions at the org level. So why not open it at the org level so that all flavors are basically sections just like it’s here on Discourse? I can relate the decision behind but imo it creates a disperancy since all other flavors are left here.

THANK YOU! I’ll see you over there.

I am going to miss the New and Unread features though.

EDIT: I haven’t used an RSS reader since the Psion / Palm Pilot days.

It looks like Brave has something built-in.

But what do you guys recommend? No clear winning flatpak in Bazaar.

can you provide an rss feed for the announcements?

I see the discrepancy being the idea of “flavors” in the first place. One big forum/discord isn’t working out well from a scalability perspective since the audiences are different.

People are already posting things like “the ublue family of distros” in places and coming here with mismanaged expectations. Over the past few weeks this place has turned into a “linux distro forum” with the same culture that I sought refuge from in the first place.

But it’s also a scalability issue, we’re also spinning out of the Discord since it’s about to cross 20k people and it’s just not scalable for us. Nothing changes on the backend, it’s all still ublue, nothing really changes from that perspective.

(Yes there will be a nice URL to remember for the RSS feed, I just need to do the dns this weekend).

I’ve been a linux user for about a decade (just realized lol), but this is the first “linux” forum I ever chose to join. Thats because this is not a typical linux project. I dont really mind that much what my aurorae looks like, KNOME all the way. Theming is not what brought me here.

What brought me here was the process. Automagical and reliable generation of system images that, if they ever get borked, get borked in the cloud and not on my PC. Building a sustainable linux ecosystem that just works for the 96% of computer users (not linux users), and creates impact beyond this project. Cleaning up traps that give new users issues, even if linux veterans have developed a Stockholm syndrome over the years. And if I ever really, really disagree with a decision or other I can leverage this framework and make my own image. Having something I can install on my mom’s PC and sleep well, knowing it’s going to work. Not.maintaining.distros.

And so the decision to move makes sense imo.

  1. GitHub for technical/dev conversations + dosu, AI likely leading to documentation generation, deepwiki, etc - saving lots of time and giving everyone a better experience
  2. Blog for bigger announcements for people to subscribe to and follow, without necessarily a forum built around it. Could be a blessing for users who are interested in updates but not necessarily the conversations
  3. Some clear separation between images might help so that maintainers arent seen as accountable for stuff that, well, isnt their stuff

Thanks for doing your thing and please keep doing your thing. \m/

Great idea.

Please delete my account then, I prefer to do that when I don’t use a service, and it seems users can’t do that on Discourse.

See you on Github!

I think I understand the subtext now, and agree.
See you all over there.

GitHub Discussions does make sense for development discussions. Makes it easier to have one confirmed location to follow over the spread of Discord, Discourse, and Discussions.

Will announcements from the blog be mirrored here? Since I don’t see an email subscription option on the blog.

Also, the Ask Bluefin page is pretty cool. How well does it work, given how absolutely wild some issues can be? Though, it uses Devin? I guess they have a generous free tier to make it possible to use with the project?

Kinda reminds me of this XKCD…:face_in_clouds::

GitHub Discussions isn’t anything new, though. I think it’s just underused compared to this forum because GitHub isn’t really known to be a user forum.

But people adapts - I’ve already seen a bunch of new threads/discussions there. I think the only thing missing is if the AI can automatically answer some of it, because I’ve seen that a few questions are standard “could be answered by an AI”.

An answer on this would be nice. I know for sure that I won’t visit github (other than a donation) and surely won’t use a RSS.

Atleast Aurora has no plans to move to GH discussions anytime soon (we haven’t even discussed about it).

Experience of using discourse much better for me than Github Discussions. Using Github discussions makes me sad, it’s looks more like MVP rather than discourse. I surely know that if Github should be choosen, i’ll be disconnected from this community over bad github discussions UX. I came here by searching discourse of Universal Blue, because Discourse is some kind of Standard for FOSS.

Really? To me it seems the vast majority of post here are essentially GH issues or pre-issue asks for support. The people who can and want to provide support are mostly on Discord and GitHub so removing this third channel makes sense to me. Are there other, non-support conversations that you will miss?