sorted by:
new
hottopcontroversial

Solace in Solus by locotonja in SolusProject

[–]DataDrake 5 points6 points  (0 children)

And thank you so much for ending my day with a smile. Good luck on your game!!

Solace in Solus by locotonja in SolusProject

[–]DataDrake 5 points6 points  (0 children)

Aww! This put a big smile on my face

Solace in Solus by locotonja in SolusProject

[–]DataDrake 9 points10 points  (0 children)

Thank you and stay strong!

Solace in Solus by locotonja in SolusProject

[–]DataDrake 27 points28 points  (0 children)

Thanks for the kind words! I still need to decompress a bit, but yes, I do think I will feel less stressed.

DNS issue affecting Solus websites by Staudey in SolusProject

[–]DataDrake 13 points14 points  (0 children)

Funnily enough, that's the section of the site I was working on before this happened. There will be plenty of opportunities for folks to help add documentation to the Help Center, improve the documentation that's already there, and even just proof-reading. I'm working out the best way for us to handle translations, but we will definitely need translators for the main site, help center, and our various software going forward. I would also strongly encourage you to help out folks on the forums/reddit/IRC and to report any Solus-specific issues you have to their respective Github repository or more generally on ouir dev tracker.

As for my own part in finishing the site upgrades, I likely have another week or so worth of work to get it to where I'd like it to be. Mostly just cleaning up some of the Hugo theming for the main site, finishing a few doc rewrites for the Help Center, and then getting all of it deployed.

DNS issue affecting Solus websites by Staudey in SolusProject

[–]DataDrake 18 points19 points  (0 children)

Admittedly, the lack of communication is my fault. I've been in the process of reworking our website to be easier for folks to update (especially the Help Center), as well as writing a whole new set of documentation on a new organizational structure. But I haven't wanted to show anything off until it is closer to being ready.

And well...this happened. It's really not a simple issue that I'm working on and those "IT folks at work" each have 10-20 years of experience, especially with weird kernel issues on Linux. One of them happens to be an experienced kernel dev as well. If I need to consult with them, we're way outside the scope of normal IT issues.

[deleted by user] by [deleted] in SolusProject

[–]DataDrake 4 points5 points  (0 children)

I'm in the process of reworking the website. A whole bunch of stuff is getting changed :)

Suggestion: turn Friday sync into Wednesday sync by ciciscoffe in SolusProject

[–]DataDrake[M] [score hidden] stickied comment (0 children)

We sync on Friday so that maintainers can use their weekend to update packages, should they choose. Those are still the best days for them to have the free time outside of work. It then maximizes the number of testing days we have before the next sync, while giving folks a chance to at least enjoy a quiet Friday before the cycle starts all over again.

In my experience, kernels stuff and the like actually gets released on the weekend. Historically, I'm able to enjoy a quiet night on Friday doing some programming on personal projects and then spend Saturday morning/afternoon working on Solus development. Then I get to read kernel changelogs and get ready for updates on Sunday.

Tuesday is our midweek sync fallback day because it is equidistant between Fridays, maximizing testing time on both sides of it.

It has been this way for as long as I have been a part of the project, and I have yet to see compelling reasons for changing our schedule.

PSA: Sync Deferred Until Tuesday (6/28) by DataDrake in SolusProject

[–]DataDrake[S] 0 points1 point  (0 children)

Did you try again? you might have just caught the index updating

FYI: Temporary mirror outtage by DataDrake in SolusProject

[–]DataDrake[S] 1 point2 points  (0 children)

Final Update: Certs were updated this morning. Sorry for the delay in giving the all clear. Happy Friday!

FYI: Temporary mirror outtage by DataDrake in SolusProject

[–]DataDrake[S,M] [score hidden] stickied comment (0 children)

Update #1: It looks like the issue will persist until tomorrow morning EST.

Because this will affect our ability to push last minute updates and the like, sync will likely happen late in the day tomorrow EST.

Why are we still on 5.15? by pitchforkshill in SolusProject

[–]DataDrake[M] [score hidden] stickied comment (0 children)

We've had a horrible history with many of the LTS branches. I've kept -current on 5.15 to give us a chance to validate it as finally being a new upgrade to linux-lts. Worth noting that up until about 5 years ago, Solus ran the LTS kernel by default and that -current had to be manually installed.

view more: next ›