Requesting assertive statement on the status of compton

ikeydoherty commented 7 years ago

I'm currently getting it in the ear regarding compton, which is being conditionally blocked from Solus inclusion for the following reasons:

No recent git tags
Last git tag is 3 years old and cannot be incorporated into Solus
Sparse git history
Conflicting statements of project future

Can someone please clarify if this project is entering twilight, or just maintenance twilight? And preferably a tag incorporated to include the 80+ changes since 2013, if this project is still suitable for use.

Obviously I'm ok with either outcome - but I need to know upfront if I can realistically look at including this, or if it's going to become a security burden over time.

Cheers in advance.

ikeydoherty commented 7 years ago

Downstream report https://dev.solus-project.com/T1530

richardgv commented 7 years ago

Can someone please clarify if this project is entering twilight, or just maintenance twilight?

Would you mind explaining what "twilight" or "maintenance twilight" indicates? I failed to find definitions for the terms.

The state of compton, from my understanding:

It has received no proper maintenance since mid-2014, and it will probably not receive proper maintenance in the future.
The code base in master branch mostly works. We have a lot of open bugs, but I estimate not many indicate bugs in the core functionality of compton itself: Many of them could simply be resolved through proper configuration. (Unfortunately, the configuration of compton is quite confusing, if you are not willing to stick to small modifications to the default configurations.)

And preferably a tag incorporated to include the 80+ changes since 2013, if this project is still suitable for use.

I think it is better to go through the open bugs first. Well, if the process ever finishes...

... if it's going to become a security burden over time.

Actually I never realized security would be a problem for a X compositor.I never payed attention to security in the development, so it cannot be guaranteed even if compton is maintained. I have not noticed a bug report about security, though.

ikeydoherty commented 7 years ago

"twilight" - completely done "maintenance twilight" - occasional merge of a PR and new releases, but no active feature work

I think it is better to go through the open bugs first. Well, if the process ever finishes...

Which kinda means no tag will ever come about.

Actually I never realized security would be a problem for a X compositor.

X is by nature insecure, so the potential exists. Which requires monitoring by those integrating into a distro.

Re: bugs in core vs configuration, that is somewhat reassuring, thank you.

kn00tcn commented 7 years ago

is budgie using whatever gnome built? we need to have standalone vsync/gl compositors since mate & xfce (& probably others) are terrible at it

i can confirm i caused a few bugs when tweaking so it's not always compton's fault

ikeydoherty commented 7 years ago

@kn00tcn atm budgie uses mutter

chjj / compton

Requesting assertive statement on the status of compton #398