The wiki is slowly getting deprecated. Replace all wiki links with their
respective replacements.
Only the translation project information still only resides on the wiki.
Based on feedback by @mcatanzaro on #gnome-design, the current issue templates may discourage filing issue templates when the bug is already fixed in main, even if it's affecting the supported stable versions.
What we want to know is whether it's happening in main or not.
Also, in order to use consistent language across the template text, converge on "latest development version".
First build glib with introspection disabled, in order to build gobject-introspection, which then can be used to rebuild glib with introspection enabled, as per fe32c3f5c5
Similar to the last commit, we are using fedora:latest which doesn't
know about a new dependency for libadwait (appstream). Install it
manually after the dnf builddep.
The pages job currently fails as the gnome-autoar dependency has been
bumped without updating the image. However, the image is based on
fedora:latest, which is still Fedora 37. So it doesn't include the latest
gnome-autoar release anyways. Let's build the gnome-autoar master to
fix the pipeline.
As part of 42c195897c9e7cf9c80b01446466b4f535a354b2 uncrustify was being
built from source to address a bug that is now fixed in the current release
0.75.
Add a default template that will be displayed by default when opening a
new issue. This encourages usage of the template selection, that users
not familiar with reporting issues might otherwise miss.
Users familiar with reporting issues will have the option to clear the
text and file an issue from scratch.
The existing Feature issue template is tailored for contributors who
understand the process, have insight on benefits and drawbacks.
In practice, that's a minority of the people how use the template.
For everybody else, the template appears to encourage submission of
features requests without previous community discussion. This often
results in poor quality issue descriptions which lack actual use
cases and naïvely assert there are no drawbacks. Poor quality issues
end up being closed, which sends negative vibes, feeding frustration
and unproductive behaviors.
Aiming to avoid the negativity trap and promote community engagement,
point people in the direction of Discourse and the place to discuss
ideas.
Also, add a new Shortcomings template to get more useful information
on the underlying problems motivating the feature request.
The fedora job was there before the flatpak job. But now we relies on
flatpak job and the fedora job doesn't really give much benefits. It is
rather waste of runners and maintainers time. Let's remove it.
There are various problems with the rawhide image currently and I don't
know how to workaround them. Let's use fedora:latest (temporarily) to fix
our pipeline.
The fedora rawhide CI job fails currently as the image doesn't contain
libhandy package, which is new Nautilus dependency. Let's add the package
to fix the CI job.
The pipeline currently fails with Fedora rawhide, because g-ir-scanner fails
with failures like: "ldd: error: you do not have read permission for
`/builds/GNOME/nautilus/_build/tmp-introspectgwhh729q/Nautilus-3.0'".
This obviously affects more projects:, e.g. GNOME/grilo!62. Let's use
Fedora latest for now as a workaround.
The fedora rawhide job fails currently as the image doesn't contain
Tracker 3 packages. Let's temporarily install the packages from
ssssam/tracker3 copr repository as they are not available yet in
rawhide repositories.
Issue templates are exposed to all users as a way to help them communicate their issues more effectively.
Epics were meant to be written by the project's contributors, so having a template for Epics serves only as a distraction.
Fedora and style check jobs install dependencies on each run. This
causes that the pipelines take a long time. Let's use a custom docker
image to not block runners for such a long time and to get the pipeline
results faster. This commit also adds a new job to generate the docker
image for us.
The process of copying an URL to open in the browser, then saving it
with the propper name, and then figuring out how to install it is
cumbersome and hard to explain in short instructions.
So, just provide a terminal command that does the job.
Also, move this section to the top, so that the person filing the issue
is invited to test the Nightly before they invest time writing the
steps to reproduce.
Closes https://gitlab.gnome.org/GNOME/nautilus/issues/621
