Budgie/Solus Road Map

WetGeek

DataDrake I'm optimistic that Josh and co will give us a good option with EFL

Not being familiar with EFL, out of curiosity I researched it. I found 6 or 7 different meanings, starting with "English Football League," but nothing to do with software development. What am I missing?

Staudey

WetGeek "Enlightenment Foundation Libraries" https://www.enlightenment.org/about

WetGeek

Staudey "Enlightenment Foundation Libraries"

Damn! That's impressive. I'm using Terminology now in place of Konsole, and it's left me wondering about just one thing. When I launched it for the first time, I set 120 as the scaling factor, but I guessed wrong and as a result the characters on my FHD screen are really hard to work with. I've been unable to find any way to adjust that now. I suppose I should look for a config file.

Ah ... I just found out by accident that Ctrl+Up/Down changes the font size. I was trying to figure out command history. I'll be happy if my new font size sticks.

I can't wait until I'm able to try out Rage on my media machine.

WetGeek

WetGeek I was trying to figure out command history

Just to be clear, command history works the same way as it always has ... with Up and Down keys. I'm not sure why I was trying to find a way to use the mouse scroll wheel for that, but I realized my mistake right away.

By the way, after using Terminology for a bit, I've discovered some of its rough edges, but so far nothing that would affect my using it, just minor annoyances. Still, I'm keeping Konsole close at hand, in case I ever DO find a showstopper in Terminology.

rrfss

You guys are awesome, thank you for the info. I think my only other question is what should I do? It's not very clear what issues/tasks are appropriate to work on. Learning how to package has been suggested, but in the dev tracker they're all awaiting triage. The stuff in the GitHub (like the software center) looked stagnant and I wasn't sure if it was appropriate to fork and play with.

Harvey

rrfss

If you want to get involved in packaging there is an accepted for inclusion list here: https://dev.getsol.us/project/view/4/

But that is not all of them, tasks for accepted requests are not left open forever and usually get closed 30+ days after being accepted if no one has stepped up to maintain it. That does not mean they are no longer eligible for inclusion, they are just closed to avoid clutter. You can see them all here, be sure to read the task for the package you are interested in, it should say something along the lines of:

This has sat in accepted for inclusion for over 30 days. Clearly, there is a lack of demand for the inclusion of this software, nobody has stepped up to provide a completed patch, maintain it, and properly integrate it. Closing as a result. Feel free to reopen but only when someone offers a patch via our proper patch submission methods and volunteers to be maintainer.

Some things anyone should consider before becoming a package maintainer.

Package maintainers should use the application they wish maintain, avoid adding/maintaining things purely because someone requested it. Just like you should not request things purely because they exist and are not in the repository.
Are you going to use Solus long term? Example are you a distro hopper? We have had this before and it resulted in the maintainer saying were unable to update the package when it was needed because they switched to another distro for a month as part of a challenge (whatever that means). Solus users should not have to go without updates for a month because of this. They were of course replaced.
If a new maintainer is needed for whatever reason a request is put out. If no one is found in a reasonable amount of time the package is removed from the repository.

« Previous Page