Javier Jardón | 29 May 19:56 2015
Picon

GNOME 3.15.2

Hey GNOMErs!

here is the second snapshot of the GNOME 3.17 development cycle, the
3.17.2 release.
Don't miss the Bastien blog post about some cool stuff new on this release [1]

To build GNOME 3.17.2, you can use the jhbuild [1] modulesets [2]
(which use the exact tarball versions from the official release).

[1] http://www.hadess.net/2015/05/iio-sensor-proxy-10-is-out.html
[2] http://library.gnome.org/devel/jhbuild/
[3] http://download.gnome.org/teams/releng/3.17.2/

The release notes that describe the changes between 3.17.1 and 3.17.2
are available. Go read them to learn what's new in this release:

core - http://download.gnome.org/core/3.17/3.17.2/NEWS
apps - http://download.gnome.org/apps/3.17/3.17.2/NEWS

The GNOME 3.17.2 release is available here:

core sources - http://download.gnome.org/core/3.17/3.17.2
apps sources - http://download.gnome.org/apps/3.17/3.17.2

WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of early development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate development status.
(Continue reading)

Justine O'Neil | 28 May 23:52 2015

Does GNOME Terminal need a UI update?

Hey all,


I want to get my feet wet contributing to GNOME.

One thing I have noticed is that the terminal app hasn't gotten the same UI attention as many other GNOME apps.  I personally turn off the menu bar so that it looks more like the other GNOME apps.  I don't miss it [the menu bar], in fact it looks strange to me now whenever I see it.

Some of the functionality exposed in the menu bar is duplicated in the application menu.  Here is a non-exhaustive list:

* "File/Open Terminal" is exposed in the app menu as "Open new terminal"
* "Edit/Preferences" and exposes the same preference dialog as "Preferences" in the app menu
* "File/New Profile" and "Edit/Profile Preferences" are exposed under Profile tab in the preferences dialog 

Other functionality exposed in the menu bar might be exposed other ways.  For example, text size and terminal dimensions could be exposed in a popover menu like the icon size setting in Nautilus.

There are a few challenges inherited from the use of control sequences in POSIX terminals.  Ctrl-Shift-C for copy and Ctrl-Shift-V for paste are non-obvious variants of the standard Ctrl-C/Ctrl-V motif.  The only way to learn these shortcuts is through the hint in the menu bar.

Thoughts?  I would be willing to work on this.  I am good with C and I am learning Vala, which GNOME Terminal is written in.  I'm still learning GLib.  I'm not really a designer, but I know some basic principles and I have studied the HIG.

Cheers!
Justine

P.S.  Since this is my first post to the list, I suppose I should give a little introduction. I am a 23 year-old young lady going to university to study science and computing.  I am getting my minor in computer science, but I have been programming on and off for the last decade.  I like to cook, and I love to argue passionately about things that matter to me.  And of course, I love FLOSS and GNOME!
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Alex G.S. | 27 May 21:37 2015
Picon

VSYNC problems on Fedora 21/22 and Intel HD graphics...

Hello,

First of all I love the new GNOME 3.16 release.  The notifications and system tray icons (in the left) are great and productivity boosters.  However, I'm having some issues with Intel HD graphics on X11 that make things very difficult.  Though these problems are solved by the Wayland session it's still too unstable for me to use in production as a day-to-day desktop.

Hardware:
Intel® Core™ i5-4200M CPU <at> 2.50GHz × 4
Intel® Haswell Mobile (HD 4600, i965) 

GNOME:
Version 3.16.2

Kernel:
4.0.4-301.fc22.x86_64

Problem:

At work I use two external monitors in addition to the laptop screen.  VSYNC often breaks when using either SNA or UXA at random intervals.  It also breaks also when I fullscreen any application in any monitor.  Even when I force VSYNC in both xorg.conf and drirc it doesn't seem to help.

These are configurations for reference:

/etc/environment: 
CLUTTER_VBLANK=True

/etc/X11/xorg.conf.d/20-intel.conf 
Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
  Option      "AccelMethod" "sna"
  Option      "TearFree" "true"
  Option      "SwapbuffersWait" "true"
EndSection

/etc/drirc
<device screen="0" driver="i965">
<application name="Default">
            <option name="force_s3tc_enable" value="true" />
            <option name="no_rast" value="false" />
            <option name="always_flush_batch" value="false" />
            <option name="always_flush_cache" value="false" />
            <option name="shader_precompile" value="true" />
            <option name="hiz" value="true" />
            <option name="clamp_max_samples" value="-1" />
            <option name="bo_reuse" value="1" />
            <option name="allow_glsl_extension_directive_midshader" value="false" />
            <option name="force_glsl_extensions_warn" value="false" />
            <option name="disable_throttling" value="false" />
            <option name="disable_glsl_line_continuations" value="false" />
            <option name="disable_blend_func_extended" value="false" />
            <option name="vblank_mode" value="3" />
</application>

I even have a GNOME extension I created that autoloads the following GNOME JS function: 
Meta.disable_unredirect_for_screen(global.screen)

This still doesn't help at all.  There is a bug report for this item and has been confirmed but I haven't heard anything and status is still NEW and not yet confirmed.  Please, any help on this would be appreciated. Things like this should just work out of the box especially on Intel HD graphics. This is a bewildering problem as this is my work machine and I may end up switching to a Mac or Ubuntu Unity if this cannot be fixed. 

Thank you!

Best,
Alex


_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Johan Bilien | 26 May 17:53 2015
Picon
Picon

Marco

I unfortunately have some terrible news, Marco Pesenti Gritti passed away last Saturday in London, after a long fight against cancer. He was with his family and in good medical hands. He leaves behind his girlfriend Daniela and 4 year old daughter Daniela. I had the chance to say goodbye last week, and convey thoughts and support for his coworkers, current and passed.

I was lucky to have worked with Marco for many years at litl, on a very broad range of projects, and had the chance to count him as a good friend. He was the most passionate and dedicated hacker I knew, and I know he was extremely respected in the GNOME community, for his work on Epiphany, Evince and Sugar among many others, just like he was at litl. Those who knew him personally know he was also an awesome human being.

We will try to help his family as much as we can. He will be sorely missed.
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Release Team | 22 May 02:00 2015
Picon

GNOME 3.17.2 unstable tarballs due

Hello all,

Tarballs are due on 2015-05-25 before 23:59 UTC for the GNOME 3.17.2
unstable release, which will be delivered on Wednesday. Modules which
were proposed for inclusion should try to follow the unstable schedule
so everyone can test them.  Please make sure that your tarballs will
be uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.17.2. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!

For more information about 3.17, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.17
page:
   http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
   https://wiki.gnome.org/Schedule

Thanks,
-- 
Automatically generated email. Source at:
https://git.gnome.org/browse/releng/tree/tools/schedule/automail.py
--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/devel-announce-list

Matthias Clasen | 14 May 00:36 2015
Picon

GNOME 3.16.2 released

Hello all,

The second update of GNOME 3.16 is out with many bug fixes,
documentation improvements, translations updates, and more.
We hope you'll like it.

For more information about the major changes in GNOME 3.16, please
visit our release notes:

 https://help.gnome.org/misc/release-notes/3.16/

Individual modules may get more stable 3.16 releases, but we are now
shifting our focus to new development. The schedule leading towards
the 3.18 release in October has been published and the first
development snapshot was released two weeks ago.

==============================
Release Details and References
==============================

The lists of updated modules and changes are available here:
  core   -  https://download.gnome.org/core/3.16/3.16.2/NEWS
  apps   -  https://download.gnome.org/apps/3.16/3.16.2/NEWS

The source packages are available here:
  core   -  https://download.gnome.org/core/3.16/3.16.2/sources/
  apps   -  https://download.gnome.org/apps/3.16/3.16.2/sources/

If you want to compile GNOME 3.16.2 by yourself, you can use the
jhbuild modulesets available here:
  https://download.gnome.org/teams/releng/3.16.2/

See you next time!

        Matthias
--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/devel-announce-list

Allan Day | 13 May 15:51 2015
Picon

Reminder: Board of Directors candidacy period ends on 18th May

Hi all,

In case you missed it, the candidacy period for the Board of Directors
elections ends on Monday 18th May. This is the final date on which you
can announce your intention to run for the board.

Full details can be found in Andrea's original announcement:

https://mail.gnome.org/archives/foundation-announce/2015-May/msg00000.html

Allan
Andrea Veri | 11 May 20:32 2015
Picon

Network switch for irc.gnome.org: Thursday, 14th May, 2015, 22 - 23 CET+1

Dear GNOME Community,

after testing the new IRCD and its integration with services 
(ChanServ, NickServ) [1] we are delighted to announce we will be 
moving the testing servers to production this upcoming thursday from 
22 to 23 CET+1.

The downtime should not take more than a few minutes: old ircds will 
be shutdown and the new ones will be restarted for properly binding 
to the default ports. (being 6667 for non-ssl connections and 6697 for 
ssl-enabled connections)

The new network will come with new features:

 - SSL (reachable by connecting to port 6697 on each of the servers 
   hosted within the network)
 - IRC services (ChanServ, NickServ), that will allow you to register 
   your nickname and channel in a safe and straightforward way. 
   Instructions on how to interact with services are available at [1], 
   [2] will receive a revamp in the next couple of days including all 
   the details and support contacts
 - Improved IPv6 support now available on both irc.acc.umu.se and 
   irc.poop.nl

As a side note the GNOME Bot known as 'Services' will be removed from 
channels that previously requested it unless a specific team requires 
its MeetBot capability. I'll give [3] a look and see which teams made 
use of it in the past years and leave it connected on those channels. 
If you want the bot to join a new channel as you would be willing to 
manage a meeting through it opening a bug at [4] should be the ideal way for 
having it added to the requested channel.

The Operators Team will be available on the #opers channel during and 
after the migration, questions and support requests should be 
redirected to that channel.

This is the list of servers that will populate the network:

 - irc.acc.umu.se: IPv4: 130.239.18.215, IPv6: 2001:6b0:e:2018::215
 - irc.eagle.y.se, IPv4: 82.99.16.155
 - irc.gimp.ca, IPv4: 142.4.222.129
 - irc.poop.nl, IPv4: 83.98.201.42 - IPv6: 2001:16f8:4::42

The irc.gimp.org (the record irc.gnome.org points to) round robin will 
be updated with the new IPs on the same day, it might take a few hours
for all the DNS resolvers to get in sync, in case make use of the IPs of
the machines to connect as listed above.

As usual keep an eye at [5].

[1] https://mail.gnome.org/archives/gnome-announce-list/2015-April/msg00010.html
[2] https://wiki.gnome.org/Sysadmin/IRC
[3] https://meetbot.gnome.org/
[4] https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin&component=IRC
[5] https://status.gnome.org

--

-- 

Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin Team Coordinator,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Takao Fujiwara | 8 May 11:17 2015
Picon

Ambiguous-width for CJK on gnome-terminal

gnome-terminal has the "Ambiguous-width chars" option.

"Edit" -> "Profile Preferences" -> "Compatibility" -> "Ambiguous-width chars"

I think almost CJK fonts have the width for the chars it could be "width" for CJK locales by default.
E.g. the character of $B-!(B
I think the value could be i18ned with g_dpgettext().

Thought?
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Release Team | 8 May 02:00 2015
Picon

GNOME 3.16.2 stable tarballs due

Hello all,

Tarballs are due on 2015-05-11 before 23:59 UTC for the GNOME 3.16.2
stable release, which will be delivered on Wednesday. Modules which
were proposed for inclusion should try to follow the unstable schedule
so everyone can test them.  Please make sure that your tarballs will
be uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.16.2. If you are not able to
make a tarball before this deadline or if you think you'll be late,
please send a mail to the release team and we'll find someone to roll
the tarball for you!

For more information about 3.17, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.17
page:
   http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
   https://wiki.gnome.org/Schedule

Thanks,
-- 
Automatically generated email. Source at:
https://git.gnome.org/browse/releng/tree/tools/schedule/automail.py
--

-- 
devel-announce-list mailing list
devel-announce-list <at> gnome.org
https://mail.gnome.org/mailman/listinfo/devel-announce-list

Andrea Veri | 5 May 18:51 2015
Picon

Current status of the GNOME Github mirror

Hey,

more than half a year has passed since the GNOME Github mirror was
setup and we are incredibly happy that it has contributed positively
to bring more contributors to the GNOME Project. While new
contributors joined the GNOME community and started contributing
through the usual workflow of submitting patches to Bugzilla many more
made use of Pull Requests (PRs) which we explicitly requested not to
use on the description of the mirror itself [1].

It's clear PRs might be seen as a handy and straightforward way to
contribute code or documentation to a specific GNOME module especially
for contributors that aren't familiar with GNOME's procedures of
submitting patches. On this matter I contacted the Github team asking
whether it was possible to remove PRs on our specific organization.
Unfortunately at this moment of time there's no simple way for that to
happen.

Apparently we don't have a simple solution we could apply to solve the
problem all together but the ideal way to start limiting the waste of
contributions and patches on Github would be shipping a
CONTRIBUTING.md file on each of the hosted repositories. Creating such
file will automatically create a warning when the user will try to
open a PR against one of the modules. An example of what the
CONTRIBUTING.md file should contain:

"""The GNOME contributing guidelines do require patches to be
forwarded to GNOME's Bugzilla instance hosted at
https://bugzilla.gnome.org, as such please do not open Pull Requests
(PRs) against any of the modules under the GNOME organization as they
will be ignored. More information is available at the following wiki
page:

  https://wiki.gnome.org/Sysadmin/GitHub"""

That said, I would like to invite anyone interested to include the
sample file above on the module/s they contribute to. If you have a
different opinion on how this should be managed, please follow up to
this thread.

Have an awesome day!

[1] https://wiki.gnome.org/Sysadmin/GitHub

--

-- 
Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Infrastructure Team Coordinator,
GNOME Foundation Board of Directors Secretary,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av

Gmane