Re: Moving final mailman lists over to discourse
On Thu, 2022-09-29 at 16:48 +0100, Neil McGovern wrote: > For both, the archives will be preserved, but they won't accept or > distribute any new mail after the end of October. Are there plans to update the https://mail.gnome.org frontpage to link to Discourse, and put redirects in place for https://mail.gnome.org/mailman/listinfo/* URLs? The last section on https://mail.gnome.org has two broken links. Looking at Git repo content under GNOME, there are a lot of outdated mailing list links in DOAP files and documentation pages to update: $:ac\> grep -r --include=*.page "mail.gnome.org" . | wc -l 44 $:ac\> grep -r --include=*.xml "mail.gnome.org" . | wc -l 24 $:ac\> grep -r --include=*.doap "mail.gnome.org" . | wc -l 170 andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-internet-radio-locator 12.1.0
On Wed, 2022-03-02 at 18:51 +0100, Luna Jernberg via desktop-devel-list wrote: > Segfaults for me Please report bugs in the issue tracker of the application and not on a general GNOME development mailing list. Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: File-Roller Settings
Hi Dale, On Wed, 2021-11-17 at 03:37 -0500, Dale Kelley via desktop-devel-list wrote: > "how can the default behavior of file-roller be changed when using the > context menu to extract files from an archive?" As this does not seem to be a development question, could you please bring this up in a support forum such as https://discourse.gnome.org/ ? Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: I am overwhelmed by the sheer number of open source remote desktop software in the world
Hi, On Sun, 2021-07-04 at 16:50 +0800, Turritopsis Dohrnii Teo En Ming via desktop-devel-list wrote: > I am overwhelmed by the sheer number of open source remote desktop > software in the world. How many open source remote desktop software > don't know how to choose! > > Could you recommend some of the best open source remote desktop > software? This mailing list is for discussion of GNOME development only. Please bring up your question in a general user support forum instead. Thanks a lot, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Is libgd still a thing?
https://gitlab.gnome.org/GNOME/libgd/commits/master hasn't seen changes
for 30 months. Emails to both maintainer addresses listed in the DOAP
file ({cosimoc|malureau}@gnome.org) bounced.
Context: Wondering whether to archive; coming from Bugzilla migration.
Thanks,
andre
--
Andre Klapper | ak...@gmx.net
https://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Wrapping up Bugzilla migration
On Sat, 2021-05-22 at 13:43 +0200, Sam Thursfield wrote: > On Wed, May 19, 2021 at 2:49 PM Andre Klapper via desktop-devel-list > wrote: > > I'd prefer adding a heads-up comment[1] and mass-close remaining open > > tickets as a courtesy to reporters, before turning Bugzilla read-only > > and then converting it to static HTML. Happy to help with that. > > That would be my preferred approach for Tracker project, rather than > migrating a set of mostly obsolete issues from 10 years ago. Would you > mind writing a quick guide on how to do it? Basically: I go to https://bugzilla.gnome.org/buglist.cgi?order=bug_id=---=1=NAMEOFYOURPRODUCTHERE , scroll down, click "Check All", change "Status" to "RESOLVED | OBSOLETE", add my own email address to "CC List" (if people have followup questions), copy the boilerplate text below into the "Additional Comments" field, and press "Commit". (I'm also happy to do that for you, if wanted.) Cheers, andre GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/NAMEOFYOURPRODUCTHERE/-/issues/ Thank you for your understanding and your help. -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Wrapping up Bugzilla migration
On Mon, 2021-05-17 at 16:44 +0200, Bartłomiej Piotrowski wrote: > I have been looking at Bugzilla migration requests today and have some > related announcements. > > First of all, if for some reason you are still using Bugzilla, you > should stop and move to GitLab. I hope it's not a surprise to anyone. > > Infrastructure team will be accepting bugs migration requests till the > end of May 2021. After this date, we intend to turn > bugzilla.gnome.org > to static HTML page and decommission its infrastructure. A specific date > will be announced in June. > > I know some of these requests are not resolved for years, but I'm slowly > going through the queue. Please let me know if we should prioritize > specific migrations or if you have any questions. Thanks for looking into this. FYI, the number of open tickets per product can be seen in this table: https://bugzilla.gnome.org/report.cgi?x_axis_field=product_format=report-table=---=table=wrap Right now there are 101 products with ~9700 open tickets left (numbers displayed may be lower if you don't have access to Security tickets). I'd prefer adding a heads-up comment[1] and mass-close remaining open tickets as a courtesy to reporters, before turning Bugzilla read-only and then converting it to static HTML. Happy to help with that. Cheers, andre [1] Example: https://bugzilla.gnome.org/show_bug.cgi?id=617445#c1 -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Nemiver current status
On Tue, 2021-03-30 at 11:54 +0200, Adrien Plazas via desktop-devel-list wrote: > Hi Pavel, > > I suspect Nemiver isn't maintained anymore as it has been archived: > https://gitlab.gnome.org/Archive/nemiver. > > Feel free to report the issue here though, but I doubt someone will > work on it: https://gitlab.gnome.org/Archive/nemiver/-/issues/new. Please don't report it there - as said, the project has been archived. Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: svg scaling drawing or viewport ?
Hi, On Sun, 2020-12-06 at 08:58 +0100, Pro Turm via desktop-devel-list wrote: > how is a svg scaled depending on the set viewport? Is the whole > drawing scaled first, and then only the viewport rendered or only > the viewport is being rendered ? Is trimming the viewport the optimal > strategy of scaling only a portion of the svg? > > Are any known considerations regarding the scaling factor regarding > memory size, performance and the order of the scaling factor itself ? > > What does negative values in a viewport would mean? > > Any documentation suggestions about where to find your answers? How is this related to developing GNOME software? Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Direct Shortcuts to Input Languages
Hi, On Thu, 2020-11-26 at 20:37 +0900, yasu wrote: > (I am not sure if this is the right mailing list for my topic - my > best guess :-)) Best to ask user questions on https://discourse.gnome.org/ instead. This mailing list is meant for development questions. :) > Is it possible to assign a direct keyboard shortcut (say, F1, F2 and > F3 for English, Russian and Japanese) for input method selection? See > the attached screenshot. Not that I know. You can switch between input methods via Super+Space. See "Typing" under https://help.gnome.org/users/gnome-help/stable/keyboard-shortcuts-set.html Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: sorry if this is the wrong place
Hi, On Mon, 2020-09-14 at 22:52 +1000, Francis Grizzly Smit wrote: > I wish to make a feature request for the gnome desktop Please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: [Development] Regarding major enhancement to Linux
Hi, On Sat, 2020-08-01 at 00:02 +0200, Box Arca via security-list wrote: > This is not where i should send mails but i want to hit to your > brains. This list is for contributors to the GNOME Desktop and Developer Platform. If you want to port random applications from some platform (e.g. Windows) to some other platform (e.g. Linux) then you are free to do so, but this is out of scope for this list which is about *GNOME*. Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Regarding behaviour of Gnome and Fedora members
On Fri, 2020-06-12 at 07:48 -0500, Ty Young wrote: > Sorry, what condescending remarks have I made? I would like to > correct them, if possible. And what will be done about GNOME > foundation member's condescending remarks regarding their users: The pattern to first try to make people spend time to collect specific remarks made by someone and then challenge single items in lengthy conversations in public is usually not a good use of time. As written before: https://wiki.gnome.org/Foundation/CodeOfConduct/ReporterGuide If you think that the CoC committee may have a "conflict of interest" then that's unfortunate but up to each self-governed online community which committees and workflows they have to foster a healthy community. HTH, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Regarding behaviour of Gnome and Fedora members
On Fri, 2020-06-12 at 05:50 -0500, Ty Young wrote: > They have engaged in racism and censorship You seem to confuse the terms "censorship" and "moderation". You may want to look up definitions. If that takes too much time, then a short (but likely also "unfriendly") summary could be http://xkcd.com/1357/ Furthermore, Reddit stuff and Fedora lists are third-parties. The scope of this list is about GNOME *development* instead. See https://mail.gnome.org/mailman/listinfo/desktop-devel-list Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GitLab Container Registry scheduled maintenance, Friday May 29, 10 UTC
On Thu, 2020-05-28 at 19:16 +0200, Milan Crha via desktop-devel-list wrote: > On Thu, 2020-05-28 at 17:13 +0200, Bartłomiej Piotrowski wrote: > > We're sorry for this inconvenience and at your disposal in case of > > your questions. > > this is the second time you plan something bigger, some server > maintenance, at the days when the releases are supposed to happen. I don't think that snarky comments are constructive. I'd rather kindly ask to make checking https://wiki.gnome.org/ThreePointThirtyseven part of the process when scheduling future infrastructure maintenance tasks. Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: up-for-grabs.net for newcomers initiative
On Wed, 2019-10-02 at 01:40 +0530, Gaurav Agrawal wrote: > Up for grabs can give us more reach in that regard, because here > people will not search for organizations but rather on their skills > and related areas. In my understanding, up-for-grabs.net requires projects to use the proprietary Github.com service for issue tracking. GNOME does not use Github for issue tracking but gitlab.gnome.org. Please correct me if I misunderstood. Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.34 released
On Fri, 2019-09-13 at 04:56 -0500, Ty Young wrote: > In terms of features, this has to be one of the biggest Gnome releases > in years. Looking forward to using it when Arch Linux decides to release > it in full... they keep breaking it up into segmented updates for some > reason resulting in all sorts of breakage and mismatching between the > old and new versions. Has anyone talked to them about that? Personally I'd say that it's up to distributions how distributions package and ship components, and up to users of distributions to discuss packaging improvements with packagers of the distribution. > Bit of a problem however... A background image that I used was removed > in this version and there isn't any fallback logic to reset the > background image. Can this maybe be fixed in the first point release so > it never happens again please? Pure white desktop backgrounds aren't > very pleasant to look at... Feel free to file a bug report with clear steps to reproduce and version information in https://gitlab.gnome.org - thanks! Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Changes: GNOME 3.35/3.36 release schedule
Hi everyone, The release schedule for GNOME 3.35/3.36 is available at https://wiki.gnome.org/ThreePointThirtyfive There are some changes. Please make yourself familiar. Mainly, * Tarballs are due on Saturday (not Monday anymore) * Stable and unstable Tarball Due on the same day * Stable maintenance releases over a longer period * Releases are published when ready (not necessarily on Wednesday) There is also an ICS file available for your calendar at webcal://www.gnome.org/start/unstable/schedule.ics It's also linked from https://wiki.gnome.org/MaintainersCorner Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GJS Docs now Hosted on gnome.org
On Tue, 2019-06-25 at 08:47 -0400, makep...@firemail.cc wrote:
> On 2019-06-24 21:06, meg ford wrote:
> > https://gjs-docs.gnome.org/
Just for the records:
In a perfect world, this would be on https://developer.gnome.org/
instead.
But understandable because in reality, the site infrastructure
("library-web") is rather unmaintained and falling apart.
See e.g. https://gitlab.gnome.org/Infrastructure/library-web/issues/12
or https://bugzilla.gnome.org/show_bug.cgi?id=785522
andre
--
Andre Klapper | ak...@gmx.net
https://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Good read from a new GNOME user
On Thu, 2019-05-02 at 11:01 +0200, Carmen Bianca Bakker wrote: > I'll summarise the raised points quickly here for everyone's > convenience: For the records, the user also created tasks for many topics: https://gitlab.gnome.org/groups/GNOME/-/issues?scope=all_username=uncertainquark Specific topics brought up should likely be discussed in the corresponding tasks, instead of a catch-all email thread. andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal: Replace all references to master/slave in GNOME modules
On Wed, 2019-05-01 at 15:03 +0300, Alberts Muktupāvels wrote: > > Numbers please? For example how many contributors GNOME has lost last > year? Do you speak about one or two people? Hundreds people? More? General numbers for authors and commits can be found at the beginning of every Release Notes edition [1] since version 3.2. However note that those numbers only include commits/merges in the git master branch. andre [1] https://help.gnome.org/misc/release-notes/ -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal: Replace all references to master/slave in GNOME modules
On Thu, 2019-04-25 at 16:24 +0200, Daniel Mustieles García wrote: > The next change we could discuss is about to remove daemons, parents > killing child process, zombies... Feel free to start that discussion if daemons and zombies bother you. Trying to create a more welcoming environment by choosing your words more carefully is not a "change everything or nothing" debate. I don't see a need for a "But how far should this go?!" straw argument. Phrases like "Kill process or sacrifice child" bother me. They can be rephrased and still be accurate (even if it's only "child process"). Of course you are also free to not be bothered by such phrases. andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal: Replace all references to master/slave in GNOME modules
One coffee later, I guess we discuss different things in this thread:
1) Whether to replace the "master/slave" terminology. I'm slightly in
favor if *both* terms are used in connection.
Terms like "blacklist" and "whitelist" are similar. They have a bad
connotation for some plus are harder to interpret than terms like
"blocklist" and "allowlist" which actually express what they do.
2) Whether to rename the git master branch ("master" having the meaning
of "original copy" as already pointed out) when there is no slave
branch. Which I'm not in favor.
Should have written that already in my previous email instead. Meh.
Sorry, Daniel.
andre
--
Andre Klapper | ak...@gmx.net
https://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal: Replace all references to master/slave in GNOME modules
Daniel,
On Thu, 2019-04-25 at 10:21 +0200, Daniel Mustieles García wrote:
> Do we need to remember you again the incovenients of your change?
> Damned Lies is broken in Geary's module (cherry-pick doesn't work),
> developers and contributors get confused if modules name their master
> branches to whatever maintainers decide, you have broken GNOME's
> standard naming for development branches, your arguments about
> Django, Rust, Linux Kernel are false, you've done this change without
> asking the community, which is clearly against it... do you want more
> reasons?
Damned Lies should get fixed if all branches got renamed (what this
thread is about), developers and contributors do NOT get confused if
ALL master branches are renamed which is EXACTLY what this thread is
about anyway, that someone has "broken standard naming" in one module
is exactly why this thread about changing the standard naming was
started, nobody brought up any "arguments about Django, Rust, Linux
Kernel" but only mentioned what those other projects have done in some
area so there are no "false" arguments as you call it, and asking "the
community" (which one? GNOME? Geary? Something else?) is probably done
in this very thread.
No need to get personal ("Do we need to remember you again") by having
your argumentation missing most of the points made.
andre
--
Andre Klapper | ak...@gmx.net
https://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: I believe we should reconsider our sys-tray removal
On Mon, 2019-03-25 at 10:49 -0400, Pat Suwalski wrote: > On 2019-03-25 10:37 a.m., Emmanuele Bassi wrote: > > On a default gnome install on any modern screen, only > > about 25% of the top bar contains any information at all. It can't be > > "the most important real estate" and be so underutilized. > > > > It's important because it's the UI element that is *always visible* at > > all times. > > So let me hide it. Everyone's happy. Off-topic different conversation - feel free to find the corresponding ticket (which likely will explain GNOME's visual identity to you). > > If an application is in the background, why do you need to see an icon > > all the time? > > Because I got an IM while I was away from my desk. It shows up in the > completely useless notification menu that is under the clock. Its > notification got clobbered by Rhythmbox's notification that the song > changed while I was on the can. I wonder why I never see my original > notification. You may want to disable "Plugins > Notifications" in Rhythmbox to not flood your notification area with things you don't consider helpful. > Alternative: oh hey, the Pidgin icon is flashing! Some flashing stuff is a good description of super annoying distracting behavior (compared to a default notification in the notification area). > > If the application needs to notify you of any state change while it's > > hidden, it can use a notification; if you need an icon to interact with > > a background application, you can literally re-launch it from the dash > > or from the applications grid, and you'll get an application window. > > Keepass: I want the icon so I can click it and it makes the correct > password available o nthe clipboard. I don't see a big issue in switching to a window in which Keepass is running. That's probably two clicks instead of one though, admitted. > Screen recording: I want a place on > screen to click to stop it without recording a window change. Ctrl+Alt+Shift+R exists: https://help.gnome.org/users/gnome-help/stable/shell-keyboard-shortcuts.html > Screen sharing: icon shows me that someone is connected (this > information is useless hidden in a menu). I'd expect an icon in the upper right corner (like for screencasts). Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Annual Gitlab Statistics, anyone?
On Sun, 2019-03-10 at 22:51 -0700, Philip Chimento wrote:
>
> For the record, here's an entry for GJS in your JSON file:
>
> "gjs": {
> "git": ["https://gitlab.gnome.org/GNOME/gjs.git;],
> "gitlab:issue": ["https://gitlab.gnome.org/GNOME/gjs;],
> "gitlab:merge": ["https://gitlab.gnome.org/GNOME/gjs;],
> "pipermail": ["https://mail.gnome.org/archives/javascript-list/;]
> }
*A lot* of such metadata (locations and persons) already exists in the
DOAP file in the top directory of each code repository.
(How up-to-date that data is is written on another paper.)
andre
--
Andre Klapper | ak...@gmx.net
https://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
On Wed, 2019-02-27 at 16:35 +0100, Bastien Nocera wrote: > On Wed, 2019-02-27 at 14:34 +0100, Andre Klapper wrote: > > If you want your project's (open) Bugzilla tasks to get copied to > > Gitlab one day in the future: A ticket at > > https://gitlab.gnome.org/Infrastructure/GitLab/issues/ > > is welcome to sort out things. > > Is there a timeline for migration? I've filed a few of those, and > haven't had any feedback: > https://gitlab.gnome.org/Infrastructure/GitLab/issues/?scope=all=%E2%9C%93=opened_username=hadess=migrate > > (the majority of them I only just opened, the first 3 are getting old > though) Probably requires csoriano et al to find time. (Cannot answer myself as I'm not involved in running or maintaining the migration script.) > > We still have 22015 open tickets in 190 Bugzilla products... > > It would have been easier if closing the products for new bugs didn't > remove those products from the "watched products" section in the > drop- > down, probably on purpose. Good catch, thanks. That should be fixed by https://gitlab.gnome.org/Infrastructure/bugzilla-gnome-org-customizations/commit/75366086f03c3675b7ad93af6ec1cb3910b38d10 once that change gets deployed on the production server. > It seems that the bugzilla migration script might not know how to > migrate private, or security bugs. https://gitlab.gnome.org/World/bztogl/issues/33 > What about the rest of the security bugs? I found left-over security > bugs in gdk-pixbuf and gvfs for example. I also need to defer that question to csoriano et al... andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
On Tue, 2019-02-26 at 08:19 +0100, Andre Klapper wrote: > Currently GNOME Bugzilla does not show the "Browse" product page when a > product has been disabled for new bug entry Fixed now thanks to the help of Carlos and Olav. Pages like https://bugzilla.gnome.org/page.cgi?id=browse.html=gnome-shell work again so you can see all your old boogs and triage them! Right? If you want your project's (open) Bugzilla tasks to get copied to Gitlab one day in the future: A ticket at https://gitlab.gnome.org/Infrastructure/GitLab/issues/ is welcome to sort out things. We still have 22015 open tickets in 190 Bugzilla products... Happy cleanup! andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Anyone who could share their Perl knowledge (to make Bugzilla display a product overview page when new bug entry is disabled)?
Currently GNOME Bugzilla does not show the "Browse" product page when a product has been disabled for new bug entry (that's the case for nearly all Bugzilla products now, as we make progress migrating to Gitlab). Which is annoying for maintainers who want to clean up a bit. https://bugzilla.gnome.org/show_bug.cgi?id=796811 links to the corresponding custom code line. Help welcome to fix that properly (I don't understand Perl enough but am happy to test patches locally). Thanks, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Annual GNOME Bugzilla statistics for 2018 (One last time)
Hi everybody, one last quick look at some basic GNOME Bugzilla activity in 2018. Note that numbers are not directly comparable to previous years as some projects have moved their task tracking from Bugzilla to GitLab. For Gitlab statistics, see this thread instead: https://mail.gnome.org/archives/desktop-devel-list/2018-December/msg00015.html Overall Bugzilla statistics: 2018 2017 2016 2015 Open reports at the end(*): 21815 49788 49593 47205 Opened in that year: 5243 15016 16239 17481 Closed in that year: 34648 14761 13675 16417 (*): Excludes reports marked as enhancements The following people (or scripts) closed more than 300 Bugzilla tickets in 2018: 15538 GNOME Infrastructure Team 6046 André Klapper 2645 GStreamer system administrator 1907 Matthias Clasen 1452 John Ralls 372 Milan Crha 365 Michael Catanzaro 349 Tim-Philipp Müller The following people reported more than 45 Bugzilla tickets in 2018: 73 Sebastian Dröge 59 Mathieu Duponchelle 57 Bastien Nocera 50 Piotr Drąg 49 Jeremy Bicha 46 Nicolas Dufresne The following people attached more than 100 patches in Bugzilla in 2018: 134 Seungha Yang 133 Iñigo Martínez 122 Mathieu Duponchelle 111 Nicolas Dufresne 110 Debarshi Ray 110 Bastien Nocera 105 Guillaume Desmottes 103 Philip Withnall 102 Víctor Manuel Jáquez Leal The following people reviewed more than 150 patches in Bugzilla in 2018: 458 Sebastian Dröge 360 Philip Withnall 357 Nicolas Dufresne 226 Bastien Nocera 186 Tim-Philipp Müller 165 Víctor Manuel Jáquez Leal 160 Michael Catanzaro Enjoy 2019! andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new GNOME Weather maintainers
On Fri, 2018-12-07 at 13:12 -0600, mcatanz...@gnome.org wrote: > There has not yet been a GitLab migration, so bugs and unreviewed > patches are still on Bugzilla. First responsibility of new maintainers > is to review unreviewed patches. But there's no way to list them. https://bugzilla.gnome.org/page.cgi?id=patchreport.html=none_days=1=gnome-weather https://bugzilla.gnome.org/page.cgi?id=patchreport.html=accepted-commit_now_days=1=gnome-weather https://bugzilla.gnome.org/page.cgi?id=patchreport.html=accepted-commit_after_freeze_days=1=gnome-weather https://bugzilla.gnome.org/page.cgi?id=patchreport.html=reviewed_days=1=gnome-weather > To get to the patch list, or just to view all the open bugs, you need to > visit > https://bugzilla.gnome.org/page.cgi?id=browse.html=gnome-weather > but that page is now blocked. There's no reason for it to be blocked, > because it does not allow entering bugs. Just prevents maintainers from > doing their job and reviewing patches. Who can fix this? https://bugzilla.gnome.org/show_bug.cgi?id=796811 Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: projects-old.gnome.org being discontinued
On Thu, 2018-12-06 at 22:42 +0100, Andrea Veri wrote: > Do you see any value in keeping those URLs around even if they're > historical and not relevant since several years? I occasionally get internet search engine results which point to projects-old.gnome.org. For clarification: If I try to visit any URL on projects-old, will my browser/search engine/I get a HTTP 301 redirect to some GNOME URL that will work? Or just a useless "Server not found"? (Anecdote: I still regularly run into/click on links to wiki.gnome.org just to end up on blank pages because some people thought it's a great idea to reorganize content by moving pages without leaving redirects.) andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Annual Gitlab Statistics, anyone?
Hej, for the last decades we had "Annual GNOME Bugzilla statistics" published at the beginning of a Gregorian calendar year. Has anyone experimented already how to get [yearly] statistics of user activity out of GNOME's Gitlab instance, to not reinvent wheels? (Especially having in mind to restrict stats to activity in "issues"?) I'm starring at https://docs.gitlab.com/ce/api/events.html#get-user-contribution-events and https://docs.gitlab.com/ce/api/users.html#list-users but I naïvely hope someone has already found better ways, or even has some code...? Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Retiring app menus - planning for 3.32.0
[on documenting keyboard shortcuts] On Thu, 2018-09-20 at 11:51 +0100, Allan Day wrote: > Adrien Plazas wrote: > ... > > What about updating the name ofthe "Keyboard Shortcuts" entry? > > To be honest, I'm not sure how successful the keyboard shortcut > windows have been and I suspect that they're not being used a great > deal. [...] > I realise that you probably have an interest from a Games > perspective, but I think it would be fine to special-case that and > come up with a bespoke solution. Personally I've always wondered how the "Keyboard Shortcuts" item potentially duplicates dedicated pages in some user docs, such as https://help.gnome.org/users/gnome-help/stable/shell-keyboard-shortcuts.html https://gitlab.gnome.org/GNOME/evolution/blob/master/help/C/intro-keyboard-shortcuts.page [1] https://help.gnome.org/users/five-or-more/stable/shortcuts.html https://help.gnome.org/users/iagno/stable/shortcuts.html Maybe agreeing on a skeleton (strings to translate only once across repos if you use software with a translation memory) / guidelines for a shortcuts Mallard help page (and page name) is an option? andre [1] Can't link to a rendered version due to https://bugzilla.gnome.org/show_bug.cgi?id=785522 -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GitLab minor-reorganization to Community group
[CC'ing gnome-i18n@] On Mon, 2018-09-10 at 11:46 -0600, Britt Yazel wrote: > There's been an ongoing discussion about reorganizing the "community" > top level group from containing both our community partner repos > (purism, ubuntu, fedora) as well as a myriad of other repositories. > As of right now, the Community top level is somewhat of a catch-all, > and we have proposed a fix to split Community into both 'Community' > and 'Teams' repositories, with the new 'Teams' top level being where > we will organize all of our Foundation teams, i.e. Engagement, > Design, Translation, Events, etc. [...] > https://gitlab.gnome.org/Infrastructure/GitLab/issues/294#note_280162 Re Translation: It's unclear to me where in Gitlab people are supposed to file bug reports against a translation in a specific language, which would allow translators of a language to get aware of bugs in their translations. There is a "8. Translation" label at https://gitlab.gnome.org/groups/GNOME/-/labels which allows subscribing but does not allow differentiating per language. It should probably be renamed to "8. Internationalization" and only be about code which does not allow proper translation; the label description could link to https://wiki.gnome.org/TranslationProject/DevGuidelines . Currently there is an "L10N" product in GNOME Bugzilla with subcomponents for each language. Each subcomponent can be watched separately by folks interested in that subcomponent (=language). Maybe some Gitlab setup / ideas already exists that I'm not aware of? andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Documentation - language default
On Fri, 2018-04-06 at 15:51 +0200, Alexandre Franke wrote: > On Thu, Apr 5, 2018 at 10:50 PM, Sriram Ramkrishna <s...@ramkrishna.me > > wrote: > > On Thu, Apr 5, 2018 at 2:18 PM Jeremy Bicha <jbi...@ubuntu.com> wrote: > > > Let me confirm and restate: GNOME has a Docs team. It would be cool if > > > you would work with the existing Docs Team when doing big Docs stuff. > > > > > > > I talked to Petr (on a bugzilla ticket) and they have given their ok on > > going forward as long as we keep them in the loop because they are > > responsible for the developer.gnome.org site. I also promised to > > be a > > liaison between the two teams. > > If discussions happened in the docs channel, there wouldn’t be a need > for liaison, would there? ...plus there is a mailing list at gnome-doc-list@ for non-transient topics, likely with more recipients than a Bugzilla ticket somewhere. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Gnome evolution and RFC 6186
On Tue, 2018-04-03 at 07:30 +0100, André Rodier wrote: > I hope I am posting on the right mailing list. I am working on a > project that installs an email server from scratch. > > I am setting up DNS records for email services automatic discovery (RFC > 6186) but it seems that evolution is ignoring them. > > However, something is definitely working, as my domain is hosted on > Gandi, and the automatic settings come back with Gandi IMAP/SMTP > records, even if I don't use Gandi to host emails. > > What is the logic used by evolution to automatically discover email > parameters? AFAIK Evolution just queries api.gnome.org and does not implement RFC 6186. Some reasons are listed in https://git.gnome.org/browse/evolution/tree/src/mail/e-mail-autoconfig.c#n18 You might get better (and informed) answers by asking on https://mail.gnome.org/mailman/listinfo/evolution-hackers andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: [GitLab] IMPORTANT: Mass migration plan
Thanks for coming up with a plan and working on this! On Tue, 2018-03-20 at 18:01 +0100, Carlos Soriano wrote: > - Bugzilla will only allow comments by June 1st 2018. Reporting new > bugs on Bugzilla will be disabled. New issues will be reported and > managed in GNOME's GitLab. Reporting new tickets is easy to disable per BZ product: editproducts.cgi offers a "Open for bug entry" checkbox. That would still allow editing existing tickets though, like adding comments. It is possible to make all tickets in a BZ product read-only: See https://phabricator.wikimedia.org/T1234 if that is wanted. > - Bugzilla will be phased out and much likely converted into a static > website by February 2020 (the proposed date may vary as we're still > evaluating all the possible solutions to make sure all the bugs will > remain available in read-only mode after Bugzilla's service > decommission). We'll still evaluating possible ways of keeping old > bugs available for historical reasons. Regarding dumping BZ to static HTML pages, https://phabricator.wikimedia.org/T1198 might come handy. You can see the outcome at https://static-bugzilla.wikimedia.org/ > The goal is to have all GNOME projects moved to GitLab by GUADEC > 2018; I left some time for eventual issues between 15th June and 6th > July. I wonder if really all project maintainers who use GNOME Bugzilla do follow devel-announce-list / desktop-devel-list. Has it been considered to mass-contact all email addresses listed as "Developers" on GNOME BZ's product browse pages (e.g. bottom of https://bugzilla.gnome.org/page.cgi?id=browse.html=Evolution ) of active BZ products, to inform them about this mailing list thread? And/or setting up an informational banner on top of Bugzilla? editparams.cgi offers an "announcehtml" parameter "will display whatever is in this field at the top of every HTML page." Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: [GitLab] Projects moved, general comments, tips of the week, question of the week
On Wed, 2018-02-28 at 14:06 +0100, Milan Crha wrote: > But seriously, my main point is that not every developer follows issues > filled in GNOME infrastructure gitlab issue tracker, thus even it's a > public place, it doesn't reach the group of people whose the decision > will influence the most. What's the difference to "not everybody follows activity in Bugzilla / IRC / mailing lists" and how's that a new problem specific to GitLab? I'm afraid I still don't understand the problem. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Annual GNOME Bugzilla statistics for 2017
Hi everybody, a quick look at some basic GNOME Bugzilla activity in 2017. Overall statistics: 2017 2016 2015 Open reports at the end(*): 49788 49593 47205 Opened in that year: 15016 16239 17481 Closed in that year: 14761 13675 16417 (*): Excludes reports marked as enhancements Note that numbers are not directly comparable to previous years as some projects have moved their task tracking from Bugzilla to GitLab. The following people closed more than 400 tickets in 2017: 1285 André Klapper 510 Florian Müllner 505 Milan Crha 499 Philip Withnall 465 Bastien Nocera 443 GNOME Infrastructure Team 414 Georges Basile Stavracas Neto The following people reported more than 100 tickets in 2017: 344 Jeremy Bicha 240 Bastien Nocera 231 Mohammed Sadiq 168 Debarshi Ray 124 Matthias Clasen 115 Florian Müllner 112 Piotr Drąg 105 Daniel Boles The following people contributed more than 250 patches in 2017: 612 Debarshi Ray 404 Florian Müllner 386 Bastien Nocera 335 Adrien Plazas 294 Philip Withnall 290 Philip Chimento The following people reviewed more than 450 patches in 2017: 852 Sebastian Dröge (slomo) 760 Bastien Nocera 656 Debarshi Ray 620 Philip Withnall 606 Rui Matos 493 Florian Müllner 456 Adrien Plazas Enjoy 2018! andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GitLab update: Moving to the next step
On Wed, 2017-12-13 at 08:34 +0100, Milan Crha wrote: > By the way, what were/are your main issues with Bugzilla? See https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-shell 3.26 fedora 27 crashes all the time
Hi Stephen, On Sun, 2017-12-10 at 18:01 -0500, Stephen Adler wrote: > I know this is not the place to post this message, but I'm desperate. Please feel free to report a bug in GNOME Bugzilla: https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/Guidelines Thanks, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Projects page on wiki
On Fri, 2017-09-22 at 09:27 +0900, Tristan Van Berkom wrote: > i think we have an "attic" approach for bugzilla and git Same on wiki.gnome.org: https://wiki.gnome.org/Attic andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GitLab status update
Hi, On Tue, 2017-09-05 at 09:33 +0200, Carlos Soriano wrote: > Issues of the infra are here > https://gitlab.gnome.org/GNOME/Infrastructure/issues Thanks. If that's supposed to be the place where to plans/look up tasks related to the migration (e.g. the data migration script), you may want to include that link in future emails. Or link to it from https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure/Comments > and our wiki for migration steps and limitations is on > https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure/Migration > that I try to update with steps and a small guide for users I'm doing. Where to find a general timeline for the migration and all migration steps broken into milestones? The link offers technical info specifically for maintainers who own repos it seems... Do those short bullet points under "limitations" have a corresponding link to a task in an issue tracker (with more info if someone wanted to fix those)? Are they hard blockers for a test migration of guinea pig projects? Are they hard blockers for full migration of all projects? Or are they "we won't stop data migration because of these issues"? What are the next steps and when for Nautilus? Now I have to look up Nautilus issues in two disconnected places. > What partially private emails? That was my interpretation of "feel free to contact me". As planning docs feel blurry, my interpretation is hopefully totally wrong. :) andre > On Tue, Sep 5, 2017 at 9:28 AM, Andre Klapper <ak...@gmx.net> wrote: > > On Mon, 2017-09-04 at 15:42 +0200, Carlos Soriano wrote: > > > As always, if you have any question, feel free contact me or reply > > > here to this email. > > > > I'm puzzled that planning and managing all aspects and issues of such a > > complex migration seems not to be organized in some public task tracker > > (a central place to see and discuss specific topics) but via (partially > > private) emails to one single person. > > > > I am writing this as I realize I have no clue where to point Alex in > > https://mail.gnome.org/archives/gnome-i18n/2017-September/msg00015.html > > > > andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GitLab status update
On Mon, 2017-09-04 at 15:42 +0200, Carlos Soriano wrote: > As always, if you have any question, feel free contact me or reply > here to this email. I'm puzzled that planning and managing all aspects and issues of such a complex migration seems not to be organized in some public task tracker (a central place to see and discuss specific topics) but via (partially private) emails to one single person. I am writing this as I realize I have no clue where to point Alex in https://mail.gnome.org/archives/gnome-i18n/2017-September/msg00015.html andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.25.91 released
Hi, On Wed, 2017-08-23 at 19:42 +0200, Mariusz W wrote: > What is the easiest way to install gnome? virtualbox? See https://www.gnome.org/getting-gnome/ Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Too many broken modules
On Tue, 2017-08-08 at 18:21 +, Leslie S Satenstein via desktop- devel-list wrote: > Gentlemen > > This message might be slightly off topic. Yes it is, as it is unrelated to non-compiling modules. Please create a new thread for a new topic and summarize your message content in the email subject line. Thanks in advance! andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to deploy GitLab on gnome.org
On Thu, 2017-05-18 at 12:17 +0200, Milan Crha wrote: > please, do not forget of Bugzilla integration with backtraces. It can > colorize them, it can show possible duplicates with score when the > backtrace is opened in its own window, and it can even notify the > reporter that the backtrace matches some other bugs and it offers the > reporter to eventually join an existing bug, instead of filling a new > bug report. Of course, an average user cannot decipher backtrace of > random projects, thus it's fine he/she files a new bug report, but my > main point for Bugzilla is that it knows what to do with inline > backtraces. Does gitlab issue tracker know it too? The Traceparser is another (basically) unmaintained custom extension we have in our Bugzilla, with some confusing bugs (e.g. bug 744491). GNOME Bugzilla does not receive gazillions of crasher bug reports anymore (like after the 2.16 release, which was the reason to write this extension if I remember correctly) and most distributions nowadays ship their own tools (and own backends) for automatic crasher analysis. The Traceparser is convenient but I would not strongly miss it if there was nothing similar in GitLab. I'd say a regression we could live with? > I've seen a screenshot of the gitlab issue tracker in an early stage of > the wiki page [1], which I cannot find right now. It was full of > colored tags, which effectively hid the main purpose, the information > which had been meant to be shared. The page looked like a rainbow, not > like a clean interface to share information between the reporter and > the developer. I do not know GitLab much but I'd expect functionality to set a color when creating a label. So color rules could be established if wanted / needed [4]. I'd call GitLab a way cleaner interface than Bugzilla. :) andre [4] notorious Wikimedia example for project/tag/label coloring rules: https://www.mediawiki.org/wiki/Phabricator/Project_management#Types_of_Projects -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to deploy GitLab on gnome.org
On Tue, 2017-05-16 at 10:51 -0400, Shaun McCance wrote: > That said, here's a potential pain point: in Bugzilla, you can have > different components auto-assign to different accounts, and we made > these @gnome.bugs fake accounts for teams. The docs team uses this to > make it easy to follow docs bugs across products. I don't think GitLab > has any sense of components, preferring the more casual labels for > categorization. When all that overcategorization in a ticket (Bugzilla: 1 "product" per ticket, 1 "component" per ticket, 0-∞ "keywords" per ticket, random freetext in a "whiteboard" entry, upstream's "tags" fields that GNOME hides via custom CSS) is turned into a single "Labels" field, with 0-∞ labels associated to a ticket, and everybody tries to remember adding that #user-docs label, and if a GitLab user can receive notifications for certain labels (so docs team members could follow activity), I don't see a real problem? :) Our "@gnome.bugs virtual assignee" setup in Bugzilla is a horrible hack, due to unavailability of an "allow me to receive notifications for these products / components" functionality for ages [1]. andre [1] To be fair, a downstream bgo extension got upstreamed at https://github.com/bugzilla/extensions-ComponentWatching but that's not shipped /by default/ which makes following anything that is neither a ticket nor a user to stalk rather complicated/cumbersome. -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to deploy GitLab on gnome.org
On Tue, 2017-05-16 at 10:28 -0400, Carlos Soriano wrote: > 2- what are the migration plans for bugzilla: bugzilla URL, bug numbers and > the actual content [...] > Also, different projects might have different needs for migration. While that is true, it is more confusing if I can find all the Bugzilla tickets I created about project X now in GitLab while I cannot find all Bugzilla tickets I created about project Y now in GitLab but you expect me to find out myself what to find where (some BZ, some GitLab?). > For example, for Nautilus we could migrate just specific important > bugs or just file new bugs in GitLab while preserving the old ones in > Bugzilla, where I can still follow/fix/comment them. [...] > As I'm the one maintaining it, I prefer a slow and smooth transition > rather than a hard one and take the opportunity to focus on the > priority ones. If I interpret "slow" and "hard" correctly and if "old ones" means "older unresolved tickets", you propose running two task tracking systems in parallel with some tickets or some projects here and some there and I (simple user) may have no idea where to do or find what. When Wikimedia killed their Bugzilla instance they made a hard cut (first migration step was turning Bugzilla entirely read-only [1]). https://xkcd.com/927/ also applies. andre [1] https://phabricator.wikimedia.org/T1234 -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to deploy GitLab on gnome.org
On Tue, 2017-05-16 at 17:54 +0100, Allan Day wrote: > On Tue, May 16, 2017 at 5:36 PM, <mcatanz...@gnome.org> wrote: > ... > > We need a much better migration plan than that. If we don't have a > > script to migrate Bugzilla issues, comments, and attachments to our > > new GitLab instance, then we should not be considering using > > GitLab's issue tracker at all. > > We're committed to creating the necessary migration tooling; I think > that Alberto already has something in the works. The "Release often, release early" mantra makes me reply by "Please show me the code." andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.25/3.26 Schedule available
On Wed, 2017-04-05 at 11:13 +0200, Sébastien Wilmet wrote: > Is it intentional that the development cycle lasts 25 weeks instead > of 26? > > 365.25 / 7 = 52.18 weeks/year in average. So 26 or 27 weeks per > development cycle. > > But maybe you want to release one week sooner to better fit a certain > distro schedule? Yes it is intentional. Seeing release plans of some distributions this hopefully allows an additional week of integration / testing :) andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Annual GNOME Bugzilla statistics for 2016
Hi everybody, a quick look at some basic GNOME Bugzilla activity in 2016. Overall statistics: 2016 2015 2014 Open reports at the end(*): 49593 47205 46056 Opened in that year: 16239 17481 20695 Closed in that year: 13675 16417 20609 (*): Excludes reports marked as enhancements The following people closed more than 400 bugs in 2016: 716 Matthias Clasen 690 Sebastian Dröge 623 Michael Catanzaro 501 Tim-Philipp Müller 425 Milan Crha The following people reported more than 150 bugs in 2016: 267 Mohammed Sadiq 227 Bastien Nocera 227 Michael Catanzaro 221 Sebastian Dröge 190 vrishab 178 Allan Day The following people contributed more than 250 patches in 2016: 553 Debarshi Ray 346 Bastien Nocera 293 Florian Müllner 291 Sebastian Dröge 278 Philip Chimento 251 Jonas Ådahl The following people reviewed more than 400 patches in 2016: 1650 Sebastian Dröge 775 Debarshi Ray 752 Bastien Nocera 740 Carlos Soriano 595 Matthias Clasen 452 Florian Müllner Enjoy 2017! andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Help on project and guidance
Hi Nikhil, Welcome to GNOME! On Fri, 2016-03-11 at 10:53 -0800, Nikhil Arya wrote: > i have a basic knoledge of C and GTK+ . > I have tried some examples on GTKWidget, pixbuf.. > As i have gone through the ideas page of gnome I guess that's https://wiki.gnome.org/Outreach/SummerOfCode/2016/Ideas > and i am interested on working on this project > photos:upload to google photos project > could you please guide me to get a better understanding about the > project so that i can contribute to it. Please see https://wiki.gnome.org/Newcomers for how to start contributing. If you have specific questions in mind, please ask them so we can help you get a better understanding. Also see http://catb.org/~esr/faqs/smart-questions.html#explicit Thanks, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome project guidance
Hi Simran, On Sat, 2016-03-12 at 15:09 +0530, SIMRAN KAUR wrote: > I am Simran Kaur, a 3rd year undergraduate student at BITS-Pilani and > I would like to contribute to gnome logs-search improvement and > builder-search and also participate in GSOC2016. > I am at good at coding in C++ and have knowledge of C and Java as > well. Can you please guide me about the its source code and issues > and how can I contribute and proceed. Welcome to GNOME! Please see https://wiki.gnome.org/Newcomers for how to start contributing. For specific questions, feel free to ask on https://mail.gnome.org/mailman/listinfo/gnome-love or the #newcomers channel on GNOME IRC. Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Annual GNOME Bugzilla statistics for 2015
Hej hej, a quick look at some basic GNOME Bugzilla activity in 2015. Overall statistics: 20152014 2013 Open reports at the end(*): 47205 46056 46130 Opened in that year: 17481 20695 25137 Closed in that year: 16417 20609 22120 (*): Excludes reports marked as enhancements The following people closed more than 500 bugs in 2015: 988 Milan Crha 973 Matthias Clasen 624 Florian Müllner 588 Sebastian Dröge 509 Bastien Nocera 503 Michael Catanzaro The following people reported more than 150 bugs in 2015: 303 Bastien Nocera 215 Michael Catanzaro 187 Allan Day 167 Matthias Clasen 161 Vineeth The following people contributed more than 250 patches in 2015: 402 Debarshi Ray 306 Bastien Nocera 299 Ray Strode 284 Philip Withnall 281 Carlos Garnacho 264 Florian Müllner The following people reviewed more than 400 patches in 2015: 1274 Sebastian Dröge (slomo) 822 Bastien Nocera 731 Matthias Clasen 527 Debarshi Ray 445 Michael Catanzaro Enjoy 2016! andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: bugzilla commentary...
On Fri, 2015-07-24 at 17:40 +, Sriram Ramkrishna wrote: Maintainers, If you have a bug report where commentators where there are disagreements, please contact the engagement team How? (Or rather: Which Bugzilla account to CC on such reports?) andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Re: Librsvg 2.40.7 is released
On Mon, 2015-05-18 at 21:39 +0200, Michael Brenner wrote: Hello Federico, https://bugzilla.gnome.org/show_bug.cgi?id=749415 https://bugzilla.gnome.org/show_bug.cgi?id=739329 https://bugzilla.gnome.org/show_bug.cgi?id=607931 (patch next weekend) https://bugzilla.gnome.org/show_bug.cgi?id=476507 https://bugzilla.gnome.org/show_bug.cgi?id=340047 Federico: Is reviewing these patches on your (probably way too long) to -do list? (In case you still sometimes look at librsvg) Thanks, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.16 Blocker Report
Blocker bugs are listed on your product's overview page: https://bugzilla.gnome.org/page.cgi?id=browse.html Feel encouraged to take a look / update the status etc. === bijiben == Popover placement issues https://bugzilla.gnome.org/show_bug.cgi?id=728859 === evolution-data-server == Gnome shell keeps poping modal dialog for gmail password https://bugzilla.gnome.org/show_bug.cgi?id=728496 === folks == Store state about enabled BlueZ persona stores https://bugzilla.gnome.org/show_bug.cgi?id=720274 === gnome-calculator == Awkward relationship between input area and results list https://bugzilla.gnome.org/show_bug.cgi?id=743499 === gnome-documents == List view looks messy https://bugzilla.gnome.org/show_bug.cgi?id=723843 === gnome-music == Visible content loading https://bugzilla.gnome.org/show_bug.cgi?id=704257 === gnome-photos == better performing thumbnails https://bugzilla.gnome.org/show_bug.cgi?id=740425 === gnome-shell == Disabled app-menu entries should look disabled https://bugzilla.gnome.org/show_bug.cgi?id=745175 Candidate window not functioning on overview https://bugzilla.gnome.org/show_bug.cgi?id=745167 Legacy tray icons of some applications either too small or appear blank/missing https://bugzilla.gnome.org/show_bug.cgi?id=721596 display legacy status icons somewhere https://bugzilla.gnome.org/show_bug.cgi?id=745162 Previous-/Next-page buttons for IME candidates are wrong https://bugzilla.gnome.org/show_bug.cgi?id=744959 Modal password boxes prevent users from looking up or generating passwords https://bugzilla.gnome.org/show_bug.cgi?id=688434 No follow-up notification after reacting to chat message https://bugzilla.gnome.org/show_bug.cgi?id=744948 mouse hover and keyboard focus identical https://bugzilla.gnome.org/show_bug.cgi?id=745246 Wi-Fi password dialog pops up without invitation https://bugzilla.gnome.org/show_bug.cgi?id=740750 === gnome-software == list of updates disappears after removing an app https://bugzilla.gnome.org/show_bug.cgi?id=739669 doesn't show updates when there are updates https://bugzilla.gnome.org/show_bug.cgi?id=739666 === gnome-user-share == Nautilus infobar for personal file sharing is ambigous https://bugzilla.gnome.org/show_bug.cgi?id=740375 === gtk+ == Frame clock synchronization broken https://bugzilla.gnome.org/show_bug.cgi?id=740424 avahi-discovered CUPS printers don't work https://bugzilla.gnome.org/show_bug.cgi?id=743323 === mutter == [REGRESSION] [Notifications] incomplete screenshots when opened notifications/calendar from top panel https://bugzilla.gnome.org/show_bug.cgi?id=744978 === nautilus == Tooltip display for last item makes item uneditable (when not using status bar) https://bugzilla.gnome.org/show_bug.cgi?id=651293 === totem == Properties should be available from overview https://bugzilla.gnome.org/show_bug.cgi?id=723900 === yelp == Home page isn't very attractive / engaging https://bugzilla.gnome.org/show_bug.cgi?id=740304 Further bugs good to fix (3.16 in the Whiteboard field): === evolution-data-server == Gnome shell keeps poping modal dialog for gmail password https://bugzilla.gnome.org/show_bug.cgi?id=728496 === gdm == login screen stuck after switching users https://bugzilla.gnome.org/show_bug.cgi?id=719418 === mutter == gdm greeter crash https://bugzilla.gnome.org/show_bug.cgi?id=743566 === totem == Add Favorites/bookmarks https://bugzilla.gnome.org/show_bug.cgi?id=357843 -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla
On Sat, 2015-02-14 at 21:27 +0100, Sébastien Wilmet wrote: A bug triager only needs to look at UNCONFIRMED bugs. I strongly disagree with that statement. Triage takes place across the full life cycle of a report [1]. A contributor willing to fix a bug has more chances to find a real bug with the NEW status. A new contributor willing to fix a bug might be better off picking a gnome-love bug. There's a query for them on the product browse page, sorted by latest update so rotting bug reports are listed last. IMO, more chances to find a real bug only applies in a well-gardened bug repository where constant triage takes place so all tickets are in good and up-to-date shape. It's even more important for feature requests. If a contributor provides a patch for an unconfirmed feature request and then the bug is closed as wontfix, I think the contributor won't come back ;-) So triage incoming bug reports and set proper expectations by setting status RESOLVED WONTFIX for such tickets right away, instead of spending the approx. same amount of time for changing status UNCONF to NEW? The UNCONFIRMED status can be kept around to not break URLs, but would be hidden by default, no? Your bookmarked query for open tickets which searches for statuses UNCONFIRMED, NEW, ASSIGNED, REOPEN will not magically include those open tickets with a newly introduced new status (e.g. CONFIRMED)... Cheers, andre [1] See e.g. section Question Time on page 6 of http://thomas-zimmermann.com/publications/files/breu-cscw-2010.pdf -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla
On Sat, 2015-02-14 at 19:02 +0100, Sébastien Wilmet wrote: On Fri, Feb 13, 2015 at 06:43:35PM +0100, Sébastien Wilmet wrote: For example in gedit UNCONFIRMED means that the bug is not triaged. How and to who does it actually matter? If it currently means that no developer will take a look at those tickets (though some of them might be totally valid) and if no other triagers are around, wouldn't it make sense to get rid of UNCONF so developers might suddenly accidentially look at such tickets? ;) What about NEW and CONFIRMED statuses? I am reluctant to rename statuses; see my other email. Or is it possible to search bugs that haven't been touched by any developer of that product? Currently not possible as far as I know: Bugzilla's Custom Search at the bottom of Advanced Search allows Commenter | is not equal to | %group.setproductnamehere_developers% but that criterion is already true when at least one commenter (e.g. reporter) is not member of the developers group for that product. Relatedly, https://bugzilla.gnome.org/page.cgi?id=browse.html now offers a Bugs without a response link again in the sidebar. But that is a lie as it only offers tickets with exactly one comment. Still better than nothing I thought, as long as upstream does not fix https://bugzilla.mozilla.org/show_bug.cgi?id=704842 ... Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla (renaming status names)
On Fri, 2015-02-13 at 21:43 +0100, Alexandre Franke wrote: BTW since 4.0 the new default workflow in bugzilla starts with UNCONFIRMED → CONFIRMED. This can be useful for those that keep UNCONFIRMED because sometimes reporters misinterpret NEW as not touched yet. Renaming the default status names in upstream made sense. For existing instances it breaks any bookmarks in your browser for search queries using URL parameters like bug_status=UNCONFIRMED. To me that is enough reason to be reluctant. andre PS: There is some undocumented alias feature in Bugzilla (no idea if it works with URL parameters) if anyone wants to play with that: http://bzr.mozilla.org/bugzilla/4.4/view/head:/template/en/default/global/value-descs.none.tmpl -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla
On Fri, 2015-02-13 at 18:15 +0100, Rick Opper wrote: Then how will project devs know if a bug is - as the status implies - not yet confirmed? 1) Not all devs care about this. Those who care can keep the UNCONFIRMED status. That's what this thread is about, more or less. 2) Not everybody sees a need to query open bug reports based on status. For some, an I can reproduce this comment in the ticket might be sufficient, instead of expressing that via some ticket status. 3) If the person looking at tickets is a developer, s/he might reproduce the bug and fix it in the same step anyway. No need to spend time setting some status which might be workflow overhead. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing the Severity field value trivial in Bugzilla
On Thu, 2015-02-05 at 02:14 +0100, Andre Klapper wrote: While/after upgrading to Bugzilla 4.4 soon(TM) [1], I would like to get rid of Bugzilla's trivial Severity field value in order to get a slightly shorter list of confusing choices. Done. There are no open tickets with trivial severity anymore, and you cannot set that severity value anymore. Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Killing the Severity field value trivial in Bugzilla
tl;dr Might happen soon. While/after upgrading to Bugzilla 4.4 soon(TM) [1], I would like to get rid of Bugzilla's trivial Severity field value in order to get a slightly shorter list of confusing choices. That means it will not be possible anymore to set that Severity value on a bug report, and I would bump the Severity value //only for those 492 open reports// from trivial to minor (while ignoring closed ones). IMHO, trivial should be expressed by setting the gnome-love keyword. Plus trivial is simply not a severity: A critical crasher bug can be trivial to fix when it's just a typo in a function call. And so this might just happen if noone speaks up to protest. andre (PS: Bikesheds about severity vs priority vs importance vs complexity go to your new separate thread. I prefer my stuff to be actionable chunks.) [1] https://mail.gnome.org/archives/desktop-devel-list/2015-January/msg00066.html -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Standardizing the latest dev code Version field value in GNOME Bugzilla to git master: DONE
Alright,
products in GNOME Bugzilla's {Core, Platform, Bindings, Applications}
classifications now all use git master (or a case variation like Git
master) in the Version field for latest dev code, not expressed via
some version number.
If you work mostly on $your-favorite-project use git-bz have a
default version configured, you might need to adjust your git-bz
settings.
I've also updated the guidelines for creating new Bugzilla projects to
recommend using that name for new projects.
[Offtopic:] If you are generally annoyed by the large dropdown of
versions: Bugzilla 4.4 will allow product maintainers to disable showing
specific entries in the Version dropdown of a bug report.
If you want Bugzilla 4.4, help testing:
https://mail.gnome.org/archives/desktop-devel-list/2015-January/msg00066.html
Cheers,
andre
--
Andre Klapper | ak...@gmx.net
http://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Future of libRSVG
Hi Michael, On Fri, 2015-01-16 at 18:14 +0100, Michael Brenner wrote: I'm searching for information about the future of libRSVG. [...] As libRSVG is missing some major features defined by SVG standard there are some anoying pitfalls. Here I'm asking for a statement what you are planning to do about libRSVG. librsvg is pretty unmaintained these days: https://git.gnome.org/browse/librsvg/stats/?period=yofs=25 That also means bug reports patches receive little to no attention: https://bugzilla.gnome.org/browse.cgi?product=librsvg As far as I understand the situation, new librsvg (co-)maintainers are welcome (interested folks should contact this mailing list to potentially sort out Bugzilla and Git permissions), but be aware that likely there will be nobody answering questions while they ramp up. Speaking as a non-programmer GNOME volunteer (NOT with my Wikimedia hat on), librsvg consumers should evaluate more maintained (and hence also more secure and future-proof?) libraries for dealing with SVG. Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Future of libRSVG
[offtopic; please remove d-d-l@ in case of answering this] Hi Eduard, On Sun, 2015-01-18 at 01:58 +0100, Eduard Braun wrote: With your Wikimedia hat ON: Could you encourage the right people at WMF You can encourage the target audience as much as I can in https://phabricator.wikimedia.org/T40010 or on https://lists.wikimedia.org/mailman/listinfo/wikitech-l . It's not that I have some special powers or such. :) Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Standardizing the latest dev code Version field value in GNOME Bugzilla?
On Mon, 2015-01-12 at 21:28 +0100, Andre Klapper wrote: 2) Shall we standardize this? (I volunteer to rename; git master seems to be the most popular option.) Thank you everybody who replied. Only +1 replies so I'll go ahead and standardize this weekend if I find time. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Standardizing the latest dev code Version field value in GNOME Bugzilla?
Welcome GNOME community to this bikeshed!
Many products in Bugzilla's {Core, Platform, Bindings, Applications}
classifications have entries in the Version field which refer to
latest dev code, not expressed via some version number.
We have 18 different names for describing that in GNOME Bugzilla.
See the list below.
I bring that up on d-d-l because it was brought up ages ago in
https://bugzilla.gnome.org/show_bug.cgi?id=681607 and to some extend
also in https://bugzilla.gnome.org/show_bug.cgi?id=710799
QUESTIONS:
1) Does this variety of names create a real problem?
For example, does it make using git-bz harder (remembering the version
value, assuming you mostly develop against the latest code)?
Do you care / do enough people use git-bz / do people not use git-bz
because of this? Other reasons?
2) Shall we standardize this? (I volunteer to rename; git master seems
to be the most popular option.) Or is that a waste of time?
LIST OF VALUES:
* CVS (head) (2: libxml2, libxslt)
* CVS (1: libxml++)
* CVS HEAD (6: gnome-backgrounds, gnome-menus, gnome-user-share,
atk, anjuta, gconf-editor)
* SVN (2: adwaita-icon-theme, sound-juicer)
* SVN trunk (3: gnome-desktop, gnome-session, libwnck)
* SVN TRUNK (1: anjuta)
* GIT (1: Gnumeric)
* git (2: Gstreamer, cheese)
* git master (56: baobab, dconf, gnome-color-manager,
gnome-dictionary, gnome-font-viewer, gnome-packagekit,
gnome-screenshot, gnome-system-log, gnome-themes-standard,
gsettings-desktop-schemas, gvfs, json-lib, librsvg, mutter,
yelp-tools, yelp-xsl, clutter, cogl, folks, gdk-pixbuf,
gtksourceview, libgdata, libgee, libnotify, libpeas, librest,
NetworkManager, gstreamermm, gstreamermm-plugins-good,
librsvgmm, libvtemm, mm-common, anjuta, caribou, five-or-more,
four-in-a-row, gedit, glade, gnome-chess, gnome-getting-started,
gnome-klotski, gnome-mahjongg, gnome-maps, gnome-mines,
gnome-nettool, gnome-nibbles, gnome-robots, gnome-search-tool,
gnome-sudoku, gnome-tetravex, gnote, iagno, lightsoff,
quadrapassel, swell-foop, transmageddon)
* Git master (1: pygobject)
* Git Master (2: pygtk, pygtksourceview)
* GIT master (1: ekiga)
* git head (2: seed, gitg)
* trunk (5: eog, gnome-control-center, tracker, devhelp,
gnome-games)
* Trunk (2: gnome-keyring, hitori)
* master (10: epiphany, evince, gnome-calculator, gnome-terminal,
gucharmap, vte, brasero, Rygel, vinagre, vino)
* HEAD (4: gnome-common, system-monitor, seahorse, Yelp)
PLEASE NOTE:
This thread is NOT about discussing e.g. Component: General or
Version: unspecified. Also, whether project X should really be in
classification Y, or if project Z is active, is a different topic.
If you want to discuss such topics, start your new thread with a
separate mail subject in a few days. Only one bikeshed at a time!
Cheers,
andre
--
Andre Klapper | ak...@gmx.net
http://blogs.gnome.org/aklapper/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Qt programs in GNOME allowed?
On Sun, 2014-11-23 at 22:29 +0100, Damian Ivanov wrote: would it be possible to get included into GNOME? What does that mean exactly to you? andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: new maintainer for gnome-dictionary?
On Mon, 2014-10-06 at 20:57 +0530, Nirbheek Chauhan wrote: I do agree that Wiktionary is probably the best source we have. Wiktionary has a very limited API so you cannot easily use it as a translation dictionary, for example. See http://en.wiktionary.org/w/api.php and http://stackoverflow.com/questions/2770547/how-to-retrieve-wiktionary-word-content Just saying. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.14 Blocker Report (week 38, what's left.)
Welcome to a last (?) round of TODO:XXX: FIX ME TIL MONDAY!: == gnome-contacts == Make the search provider work again https://bugzilla.gnome.org/show_bug.cgi?id=736147 Untested patch attached. == gnome-photos == gnome-photos: g_str_hash(): gnome-photos killed by SIGSEGV https://bugzilla.gnome.org/show_bug.cgi?id=735746 Stacktrace available but no further investigation yet. == gnome-software == Core dump due to the assertion failed https://bugzilla.gnome.org/show_bug.cgi?id=736362 Reporter provided more info via log attached. == gnome-tweak-tool == tweak_group_shell_extensions.py:321:_got_info:KeyError: 'version' https://bugzilla.gnome.org/show_bug.cgi?id=730177 Anyone willing to try/comment on the attached 10-line Python patch? Not sure if Tweak Tool's maintainer is still alive... == gnome-weather == gnome-weather leaks information of your saved locations in cleartext when not using the app https://bugzilla.gnome.org/show_bug.cgi?id=734048 Unclear if more work needs to be done here? == mutter == Nautilus window becomes larger every time when opening https://bugzilla.gnome.org/show_bug.cgi?id=733315 Cosimo could reproduce this. ===Three more reports that might be good to fix:=== == adwaita-icon-theme == Spinner has ghosting artifacts (alpha issue with xcursorgen) https://bugzilla.gnome.org/show_bug.cgi?id=734429 == gnome-photos == Would be nice to have a smooth sliding transition between photos https://bugzilla.gnome.org/show_bug.cgi?id=726505 Debarshi: Allan says this should get reverted for 3.14. == gnome-settings-daemon == use IBus 1.5 api when obtain keyboard variant option. https://bugzilla.gnome.org/show_bug.cgi?id=734980 andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Giving up maintenership of my modules
On Tue, 2014-09-16 at 07:17 +0200, Juan Rafael García Blanco wrote: Does Gnome keep track of which projects need developers, documentators, maintainers, ...? I mean something similar to gnu's savanah. Developers: Always needed. Documentation: e.g. https://wiki.gnome.org/DocumentationProject/Tasks/ApplicationHelp Maintainers: Not that I am aware of. The latter is a problem. What does Savanah exactly do? I'm only aware of Debian pinging maintainers automatically + regularly to confirm they are still around and not missing in action / away without official leave. I wonder what other FOSS projects do. Thanks to Fred we do have https://people.gnome.org/~fpeters/health/ which lists a code activity score (bus factor?) for each module - the lower the number, the better. But I assume those numbers don't automatically update and might be a bit dusty now. The question is who and how to turn that into something 'actionable'. As far as I know nobody is 'proactively' reaching out (where?) to maintainers on the leave (=making them realize) and finding potential folks to take over. andre (using words like 'proactive' and 'actionable' that he hates) -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME Panel maintainers
Hi, https://git.gnome.org/browse/gnome-panel/stats/?period=yofs=25 shows the general commit activity per year, in case you want numbers. On Mon, 2014-09-08 at 21:48 +0300, Alberts Muktupāvels wrote: What about maintainers that used to maintain gnome-panel while it was official part? Can not they help? You could try to contact them but no idea if they still care: https://git.gnome.org/browse/gnome-panel/log/gnome-panel.doap Also in any case and wherever this is discussed in the end, it would be good to hear the view of the other party. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Report (week 36)
On Thu, 2014-09-04 at 10:38 +0800, 藍挺瑋 wrote: It still doesn't work ... gmake[4]: Entering directory `/home/lantw44/gnome/source/mutter/src' CC x11/events.lo In file included from x11/events.c:39: ./wayland/meta-wayland-private.h:23:10: fatal error: 'wayland-server.h' file not found #include wayland-server.h ^ I am not sure if build issues of one specific software module are of interest to the GNOME developer community on this mailing list. :) libwayland-server-devel package installed? If yes: bug report? andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Glade release to include GtkHeaderBar?
On Thu, 2014-09-04 at 08:11 -0700, Jasper St. Pierre wrote: Google is particularly shit at pointing people to the correct version. If we choose to have multiple versions still, we should put a giant warning at the stop saying it's not the current version, and perhaps have a version switcher. Is there a Bugzilla ticket already about displaying a warning banner? With regard to internet search engine indexing, https://bugzilla.gnome.org/show_bug.cgi?id=509424 was about Only let search engined index stable, unstable versions but I don't see that working for Google results. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.14 Blocker Report (week 36)
== at-spi == Using AtspiCollection to match via interfaces seems broken and causes crashes https://bugzilla.gnome.org/show_bug.cgi?id=734805 Crash should be fixed (commit bb89b1), but more cleanup work listed in last comment == cogl == glx_event_filter_cb: SIGSEGV https://bugzilla.gnome.org/show_bug.cgi?id=733282 Looks like Jasper and alexl are on it. == glib == Failing read() causing flood of GNetworkMonitor::network-changed signals https://bugzilla.gnome.org/show_bug.cgi?id=735325 Waiting for strace output by Elad. == gnome-backgrounds == Review and clear up license for photos and code https://bugzilla.gnome.org/show_bug.cgi?id=735803 Looks like all authors have provided agreements? == gnome-initial-setup == Window seems very tall https://bugzilla.gnome.org/show_bug.cgi?id=734808 == gnome-photos == gnome-photos: g_str_hash(): gnome-photos killed by SIGSEGV https://bugzilla.gnome.org/show_bug.cgi?id=735746 Stacktrace available. == gnome-shell == warnings (and eventually a crash) when dragging window from a workspace thumbnail https://bugzilla.gnome.org/show_bug.cgi?id=735972 Some patches by Carlos awaiting review. == gnome-themes-standard == Many high contrast SVG icons are red circles https://bugzilla.gnome.org/show_bug.cgi?id=735455 Needs decision whether to drop those items or not? == gnome-tweak-tool == tweak_group_shell_extensions.py:321:_got_info:KeyError: 'version' https://bugzilla.gnome.org/show_bug.cgi?id=730177 Patch provided by reporter, needs review. == gtk+ == treeview: column drop target visualization broken https://bugzilla.gnome.org/show_bug.cgi?id=732916 Older WIP patch attached by mclasen but needs more work. == mutter == crashes related to modal windows on 2nd screen https://bugzilla.gnome.org/show_bug.cgi?id=735333 Reporter provided more feedback; needs to get replied to. Gnome+Wayland can't resize windows https://bugzilla.gnome.org/show_bug.cgi?id=735717 Needs further investigation; cursor theme related? ===Further bugs that might be good to fix / take a look at:=== == adwaita-icon-theme == Spinner has ghosting artifacts (alpha issue with xcursorgen) https://bugzilla.gnome.org/show_bug.cgi?id=734429 == gnome-online-accounts == Google Online Account Password Unexpectedly Fails https://bugzilla.gnome.org/show_bug.cgi?id=734298 == gnome-settings-daemon == use IBus 1.5 api when obtain keyboard variant option. https://bugzilla.gnome.org/show_bug.cgi?id=734980 == gsettings-desktop-schemas == Location Service should be disabled by default https://bugzilla.gnome.org/show_bug.cgi?id=735736 andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs (week 33)
On Sun, 2014-08-24 at 11:29 -0500, Michael Catanzaro wrote: On Tue, 2014-08-12 at 18:32 +0200, Andre Klapper wrote: Thanks everybody for cleaning up last week's list by fixing and reassassing quite some items! There are only eight items left marked as blockers: I think we should add https://bugzilla.gnome.org/show_bug.cgi?id=734298 All user comments seem to be about 3.10 but none about 3.12 (yet)? Is there any indication that this is still a problem in 3.12/3.13 code? In any case, a comment by a g-o-a maintainer would be extremely welcome on that ticket (if g-o-a has maintainers). Too silent. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Stable release policy
Hi, On Fri, 2014-08-22 at 19:59 +0100, Ross Lagerwall wrote: Is there any policy about releasing updates to stable branches beyond the .1 release or is it simply up to each project? I couldn't find this info anywhere on the wiki... A stable .2 is listed on https://wiki.gnome.org/ThreePointThirteen#Schedule Core projects are expected to follow the release schedule. See also https://wiki.gnome.org/MaintainersCorner Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs (week 33)
On Tue, 2014-08-12 at 19:15 +0200, Bastien Nocera wrote: On Tue, 2014-08-12 at 18:32 +0200, Andre Klapper wrote: Thanks everybody for cleaning up last week's list by fixing and reassassing quite some items! There are only eight items left marked as blockers: Why was https://bugzilla.gnome.org/show_bug.cgi?id=728496 moved to GNOME 3.16? It still affects existing 3.12 installations, so moving this any further really doesn't help anyone. (GNOME Target hadn't been set before.) I set Whiteboard to 3.16 because e-d-s won't see any 3.14 release anyway (plus the main issue seems to be bug 688434 which won't get solved for 3.14). That shouldn't stop anybody from trying to backport a fix to 3.12. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.14 Blocker Bugs (week 33)
Thanks everybody for cleaning up last week's list by fixing and reassassing quite some items! There are only eight items left marked as blockers: == cogl == glx_event_filter_cb: SIGSEGV https://bugzilla.gnome.org/show_bug.cgi?id=733282 Issue can be worked around by disabling DRI3. == gdm == Changing language from user panel does nothing https://bugzilla.gnome.org/show_bug.cgi?id=730478 Ray wrote that it might be a side-effect of the LANG patch in bug 709105. (Added to list based on feedback from last week.) == gnome-control-center == background: thumbnails are tiny in 3.13.3 https://bugzilla.gnome.org/show_bug.cgi?id=732375 Debarshi and Bastien discussed; might be fixed already but there is one patch left in accepted-commit_now status. == gnome-shell == Sometimes, when I alt+tab to switch apps, my shell freezes completely https://bugzilla.gnome.org/show_bug.cgi?id=727365 Two people can reproduce; more input and analysis highly welcome. == gtk+ == gtk-demo: entry completion doesn't work https://bugzilla.gnome.org/show_bug.cgi?id=695504 Needs a patch using window type hints as short-term fix if possible according to last comment. treeview: column drop target visualization broken https://bugzilla.gnome.org/show_bug.cgi?id=732916 Uncomplete WIP patch by Matthias attached == mutter == [regression] Can't turn off wayland https://bugzilla.gnome.org/show_bug.cgi?id=729490 Jasper wrote Stuff will be broken for a bit in May; status update welcome. == polari == polari 3.13.2 has a lot of transparent text, making it almost impossible to use https://bugzilla.gnome.org/show_bug.cgi?id=734100 Likely fixed already, needs new tarball to retest? ===Further bugs that could be good to fix:=== These items have a status whiteboard entry which says 3.14. Maintainers are free to bump it or remove it if it feels wrong. == adwaita-icon-theme == Clunky pointer spinner https://bugzilla.gnome.org/show_bug.cgi?id=734429 Patch by Jakub available. == Evolution == Google Calendar not syncing properly https://bugzilla.gnome.org/show_bug.cgi?id=734387 but workaround mention in comment 3. == gnome-shell == Modal password boxes prevent users from looking up or generating passwords https://bugzilla.gnome.org/show_bug.cgi?id=688434 Discussion has evolved lately but likely nothing to improve for 3.14? == gtk+ == GtkPlacesSidebar - refine spacing https://bugzilla.gnome.org/show_bug.cgi?id=731443 -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: git.gnome.org changes and new doap file requirements
On Wed, 2014-08-06 at 08:03 -0500, Michael Catanzaro wrote: On Sun, 2014-08-03 at 08:05 +0200, scl wrote: remote: ERROR: babl.doap is not valid: remote:doap:category property should be one of: apps,core,core-apps,deprecated,infrastructure Er, so what category does babl belong in? I'm pretty sure it's not core, but it's the only plausible choice here. In jhbuild's moduleset definitions it's currently listed in: https://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-apps-3.14.modules andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Archived git modules
On Thu, 2014-07-31 at 11:21 +0200, Olav Vitters wrote: On Wed, Jul 30, 2014 at 05:12:53PM +0200, Olav Vitters wrote: The following git modules have been archived: [...] Anything can be unarchived of course. In Bugzilla, I've moved all affected products to the Deprecated classification, closed them for new bug entry, closed remaining open tickets, added a gnome[unmaintained] whiteboard entry, and added a comment explaining the reasons. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.14 Blocker Bugs
A first list of blockers and potential blockers for the upcoming release, based on data in GNOME Bugzilla. Note that there are lots of gnome-themes-standard/HighContrast tickets open. Please take a quick look at the list below, comment (on the ticket), and raise your voice if you see an important issue missing. Thanks! andre == GNOME-CONTROL-CENTER == background: thumbnails are tiny in 3.13.3 https://bugzilla.gnome.org/show_bug.cgi?id=732375 == GNOME-SHELL == desktop menu went missing https://bugzilla.gnome.org/show_bug.cgi?id=731932 Invalid backlight level at startup https://bugzilla.gnome.org/show_bug.cgi?id=727048 == GNOME-THEMES-STANDARD == HighContrast: calendar theming https://bugzilla.gnome.org/show_bug.cgi?id=732490 HighContrast: all white in gtk3-widget-factory https://bugzilla.gnome.org/show_bug.cgi?id=732482 HighContrast: flat button love https://bugzilla.gnome.org/show_bug.cgi?id=732492 HighContrast: invisible pane splitter https://bugzilla.gnome.org/show_bug.cgi?id=732485 HighContrast: expander hover state https://bugzilla.gnome.org/show_bug.cgi?id=732495 HighContrast: inconsistent toggle button unreadable https://bugzilla.gnome.org/show_bug.cgi?id=732487 HighContrast: neuter the statusbar frame https://bugzilla.gnome.org/show_bug.cgi?id=732489 HighContrast: no padding in actionbars https://bugzilla.gnome.org/show_bug.cgi?id=732491 HighContrast: vertical spin buttons look bad https://bugzilla.gnome.org/show_bug.cgi?id=732483 HighContrast: suggested/destructive-action https://bugzilla.gnome.org/show_bug.cgi?id=732493 HighContrast: broken hover for check/radio buttons https://bugzilla.gnome.org/show_bug.cgi?id=732486 HighContrast: popover background missing https://bugzilla.gnome.org/show_bug.cgi?id=732488 == GTK+ == popovers can't always track the widget https://bugzilla.gnome.org/show_bug.cgi?id=729140 gtk-demo: entry completion doesn't work https://bugzilla.gnome.org/show_bug.cgi?id=695504 treeview: column drop target visualization broken https://bugzilla.gnome.org/show_bug.cgi?id=732916 == MUTTER == [regression] Can't turn off wayland https://bugzilla.gnome.org/show_bug.cgi?id=729490 == POLARI == polari 3.13.2 has a lot of transparent text, making it almost impossible to use https://bugzilla.gnome.org/show_bug.cgi?id=734100 Should be fixed already. ===Further bugs that would be good to fix or get progress with:=== == GNOME-NIBBLES == Remove statusbar https://bugzilla.gnome.org/show_bug.cgi?id=666501 == GNOME-SHELL == Modal password boxes prevent users from looking up or generating passwords https://bugzilla.gnome.org/show_bug.cgi?id=688434 == GNOME-SUDOKU == no indication that i've run out of puzzles in print multiple sudokus https://bugzilla.gnome.org/show_bug.cgi?id=580055 gnome-sudoku generates invalid puzzles https://bugzilla.gnome.org/show_bug.cgi?id=619190 == GTK+ == Message dialogs - padding and text justification issues https://bugzilla.gnome.org/show_bug.cgi?id=732882 GtkPlacesSidebar - refine spacing https://bugzilla.gnome.org/show_bug.cgi?id=731443 == TOTEM == Add Favorites/bookmarks https://bugzilla.gnome.org/show_bug.cgi?id=357843 -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
[OT] Re: Unreviewed patches - is the boat sinking?
On Sun, 2014-04-13 at 16:31 -0500, Michael Catanzaro wrote: There's merit in his complaint. or her. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: screen darken when gnome-terminal activated
Hi, On Tue, 2014-03-04 at 07:50 +0800, chenzero wrote: after upgraded to the latest Ubuntu 12.04, 3.2.0-59-generic-pae, I encountered a problem is, screen will darken when gnome-terminal is activated, however, if use the system color in the profile of gnome-terminal, the screen is OK. Please help, thanks! Please report bugs to your distribution: https://bugs.launchpad.net/ubuntu andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.12 Blocker bugs
Here is the current list of 15 tickets, with some annotations: === CLUTTER === https://bugzilla.gnome.org/show_bug.cgi?id=723085 Clutter's event handling can get stuck under ClutterGTK+ - Jasper proposed two potential ways to fix/improve === CLUTTER-GTK === https://bugzilla.gnome.org/show_bug.cgi?id=695737 Add wayland support - attached patches need rework and review === GLIB/GIO === https://bugzilla.gnome.org/show_bug.cgi?id=724916 gio unmount code makes XFCE's Thunar crash - desrt attached patches; waiting for reporter to test them https://bugzilla.gnome.org/show_bug.cgi?id=725023 Can no longer find apps by executable/desktop file name - desrt's patch has accepted-commit_now status; testcase welcome === GNOME-SHELL === https://bugzilla.gnome.org/show_bug.cgi?id=704844 dismissing a notification from an action button doesn't correctly hide the close button https://bugzilla.gnome.org/show_bug.cgi?id=710211 gnome-shell crashes when searching for application with corrupt .desktop file - testcase available https://bugzilla.gnome.org/show_bug.cgi?id=712706 Suspend on idle broken by gnome-shell resetting idletime - problem tracked down to a change in July 2013 https://bugzilla.gnome.org/show_bug.cgi?id=721459 Maximize without title bar causes fullscreen - wondering if potential solution might hit corner cases, input needed (Owen?) https://bugzilla.gnome.org/show_bug.cgi?id=724779 network-agent : cannot connect to new AP (password UI not showing up) - Patch has accepted-commit_now and was successfully been tested by reporter https://bugzilla.gnome.org/show_bug.cgi?id=725273 Can't remove overview application folders; empty folders show up in overview and add to list https://bugzilla.gnome.org/show_bug.cgi?id=725340 Don't show network-offline in the top bar === GNOME-THEMES-STANDARD === https://bugzilla.gnome.org/show_bug.cgi?id=723240 GtkHeaderBar doesn't honour neither Window border nor Interface font setting - mclasen's patch in comment 3 awaiting review === GTK+ === https://bugzilla.gnome.org/show_bug.cgi?id=698730 tooltip: Fix possible wrong placement - 14 lines patch available in comment #4 awaiting review https://bugzilla.gnome.org/show_bug.cgi?id=723668 Message Dialog Layout - mostly padding issues; would be partially addressed by Jon's patch in bug 725345 https://bugzilla.gnome.org/show_bug.cgi?id=725141 Add shortcut to move focus to the GtkHeaderBar - like F10, for accessibility == List of bugs from: https://bugzilla.gnome.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDbug_status=NEEDINFOcf_gnome_target=3.12order=product%2Cbug_id andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Underlying DE for the Fedora Workstation product
On Wed, 2014-02-05 at 15:03 -0500, Alexander GS wrote: It's 2014 and not 1999. Do you expect me to read your mail if you start telling me things that everybody knows and make me wonder if you think I'm stupid? Plus I have no idea how your posting refers to the posting that you replied to. Think about it. I didn't. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Annual GNOME Bugzilla statistics for 2013
Ladies and Gentlemen, the usual quick look at some basic GNOME Bugzilla activity in 2013 (slightly late, but all numbers were gathered on Jan 1st at 20:06UTC). Created by using https://bugzilla.gnome.org/page.cgi?id=weekly-bug-summary.htmldays=365products=100reporters=15hunters=15patchers=15reviewers=15 Overall statistics: 2013 2012 2011 Open reports at the end(*): 46130 43298 44003 Opened in that year: 25137 23642 28287 Closed in that year: 22120 24093 27552 (*): Excludes reports marked as enhancements Half of the large difference (3017 tickets) between opened and closed tickets is due to two projects: ProjectOpen ticketsChange shotwell 967 +428 geary 685 +1051 Here it becomes obvious that there is a bug in Bugzilla's statistics, as Geary did not have a negative number of open tickets one year ago. This data inconsistency is likely related to mass-importing tickets from Yorba's Redmine instance, as there further inconsistencies can be seen (the reporter column on buglist.cgi shows a different reporter [the original reporter in Redmine] than show_bug.cgi [the account of Charles who ran the import script] for many Geary tickets). The following people closed more than 500 bugs in 2013: 1202 Matthias Clasen 864 André Klapper 812 Bastien Nocera 688 Sebastian Dröge 574 Florian Müllner The following people reported more than 250 bugs in 2013: 488 Adam Dingle(᛭) 470 Jim Nelson(᛭) 426 Matthias Clasen 392 William Jon McCann 360 Bastien Nocera 318 Allan Day 280 Giovanni Campagna (᛭): To some extend due to mass-importing Geary tickets, see above. The following people contributed more than 250 patches in 2013: 875 Jasper St. Pierre 652 Giovanni Campagna 450 Bastien Nocera 407 Florian Müllner 262 Ryan Lortie 260 Debarshi Ray 253 Cosimo Cecchi 253 Rui Matos The following people reviewed more than 500 patches in 2012: 1380 Bastien Nocera 1234 Jasper St. Pierre 1230 Sebastian Dröge 769 Matthias Clasen 726 Colin Walters 708 Giovanni Campagna 507 Cosimo Cecchi Enjoy 2014!, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: String additions to 'gnome-backgrounds.master'
On Sun, 2013-10-06 at 17:49 +0200, Bastien Nocera wrote: On 5 Oct 2013, at 22:00, Piotr Drąg piotrd...@gmail.com wrote: 2013/10/5 GNOME Status Pages nore...@gnome.org: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-backgrounds.master': + Bokeh Tails + Dark Ivy + Flower Bed + Lock Screen + Signpost of the Shadows + Stones + Whispy Tails Is there a reason why this landed without i18n approval? Are you going to branch before these commits? The strings aren't user visible and the commits already had acks from the release team. If they aren't user visible, why are they marked for translation? andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcing GNOME's official GitHub mirror
On Thu, 2013-08-15 at 12:07 +0200, Alexandre Franke wrote: I really don't care much about my code being mirrored anywhere. Anyway this is really not what was the most important point to me in my previous email and you didn't answer the question I really cared about, so I'm asking again: is there a way for maintainers to opt out of the github mirroring? I don't see any question in your last email, so you're not asking *again*. If you don't care much about your code being mirrored, it probably means that Can maintainers opt out? is a theoretical question. Or even a non-existing problem (so far). I hope there's no opt-out to avoid a cumbersome You can get most of GNOME's codebase also on the most popular code hosting website, but not everything because not all maintainers liked that idea situation. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcing GNOME's official GitHub mirror
On Thu, 2013-08-15 at 13:39 +0200, Andre Klapper wrote: I don't see any question in your last email, so you're not asking *again*. Ah. Either you asked on foundation-list only and not d-d-l, or my mail filters are wonky. Sorry. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcing GNOME's official GitHub mirror
On Thu, 2013-08-15 at 16:13 +0300, fr33domlover wrote: You're free to use github mirrors, it's your right to do so. But I have the right not to cooperate with this. All Gnome maintainers have this right. [Citation Needed]. Easy workaround: Just ignore the fact that there is a mirror. Problem solved, all happy. You don't need to corporate. And a big thanks to Alberto who spend his time to make GNOME's codebase available to more people by adding another distribution channel to it. Cheers, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcing GNOME's official GitHub mirror
On Thu, 2013-08-15 at 16:27 +0200, Andrea Veri wrote: We are not diverging (and we won't diverge) from our development workflow, I agree with you that leaving pull requests open can take in some confusion and we'll be trying to address that by adding the relevant wiki page [1] on the description of each of the repositories hosted on the mirror so that people are aware of that. As GitHub extracts and renders the README file below the repository file browser, such information could be easily exposed on GitHub. On a general note, GNOME is not the first FLOSS project discussing a GitHub mirror, so there might be evaluations out there already. I know I'm a few hours and dozens of emails too late, anyway: https://www.mediawiki.org/wiki/Git/Gerrit_evaluation#GitHub https://blog.mozilla.org/labs/2010/08/contribute-to-labs-projects-on-github/ andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: I think I found an error in libwnck the name_changed and icon_changed function pointers appear to take the wrong type
On Thu, 2013-06-20 at 12:33 +1000, Francis (Grizzly) Smit wrote: To the libwnck devs Please file bug reports in https://bugzilla.gnome.org under the product libwnck. Thanks, andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.9/3.10 release schedule
On Fri, 2013-04-12 at 19:09 +0200, Andre Klapper wrote: I've published a draft for the GNOME 3.9/3.10 schedule to https://live.gnome.org/ThreePointNine#Schedule Alright, I hereby declare this schedule final, for the records. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: loomio
On Wed, 2013-04-17 at 17:24 +0100, Marco Scannadinari wrote: No, I don't think that GNOME will suddenly become the perfect DE, but certain decisions, such as the location of the close button on fullscreen apps, could be improved a lot and polls could be used as evidence for user testing or feedback, rather than saying We thought it was the right thing to do. (for example) Please not. Polls are popularity contests and cannot replace user testing. http://nat.org/blog/2006/02/dan-winship-on-design-by-committee/ comes to my mind (unfortunately the paintings are not online anymore). andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: loomio
On Tue, 2013-04-16 at 22:08 +0100, Marco Scannadinari wrote: So you want to have random people suddenly join, be of the decision and have equal say? I find that a little bit weird. As opposed to the method that we have now which is..? (I cannot speak for all teams, as I'm not in all teams. Anybody feel free to correct me please.) Most teams have meetings sometimes, mostly IRC based (though some also have phone or Google Hangouts as far as I know). Except for board and release-team, team membership is not exclusive / defined, and (except for board) meetings are public. Newcomers and lurkers are welcome to meetings and to provide input to influence decisions, but when it comes to hard voting (if decision making process is not consense-based) I'd expect only established people to feel like taking part anyway, or at least expect their votes to have way more weight. In the end that's how I understand meritocracy. Also see section 5.5.2 Community of http://www.dgsiegel.net/foss-development-processes andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: loomio
On Tue, 2013-04-16 at 13:49 -0700, Sriram Ramkrishna wrote: I think this particular tools documents what decision was made and in what context. That's a little hard to do if you have to scan through emails at least for hte marketinig team. Of course it implies that we have some discipline to do this. :-) As an example, links to emails with release-team meeting minutes are listed at https://live.gnome.org/ReleasePlanning/Meetings . Would like to know a specific example why this might not be sufficient, to understand the problem better (plus if a problem actually exists). andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
