labwc / labwc

A Wayland window-stacking compositor

Home Page:https://labwc.github.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

When reporting problems with labwc - guideline

droc12345 opened this issue · comments

It would be helpful to know a few things about the system having problems, specifically version numbers
labwc,
wlroots,
mesa,
libinput,
wayland and wayland-protocols

Along with a good description of the problem, and maybe how to reproduce it.

Any other thoughts from others?

It might be nice to have something like this pinned in the issue area,
it helps to know some of these things when diagnosing potential problems.

We should probably make a few templates for issues, with specific forms for feature requests, bug reports and the like. If submissions don't fit one of those templates, we can encourage users to open up a discussion topic instead of an issue.

We could add an issue template I think.

However, personally I am not a big fan of having a list to fill out because in most cases that information doesn't actually help us diagnose the issue and it just causes unnecessary work for people reporting bugs / requesting features.

Agree with Consolatis.

Last time we discussed this we concluded that the volume of "poorly worded" issues was low and that those probably wouldn't improve much by enforcing a template (might be more verbose, but not helpfully so).

My preference is to not have a template, but recognise that I no longer triage most issues, so am open to adding one if you want.

Just try to redirect users to "Discussions" for questions helps a lot IMO.

I'm not sure how I feel about templates, etc.
I was envisioning a voluntary thing, not a bucket list that everyone must follow.

This was just an attempt to get some info that might help determine where an issue might lie.
Is mesa too old, is it a problematic version, etc?
Does that version of wlroots have a known flaw?

I know with linux versions like arch, they are pretty cutting edge on their packages, but others like debian
have much older versions.

Anyway up to y'all, it was just a thought I had.

Maybe a compromise would be a very short and informal template that only conatins

  • Usage question? Use discussions instead.
  • Please state your labwc and wlroots versions.

The mesa version isn't really that important however (I can't remember a single issue that ended up being caused by an old version of mesa). Same for libinput, wayland or wayland-protocols (wlroots has version requirements for those).

Might be nice to know which version of xwayland they're running when reporting X problems.