On Thu, 2014-04-03 at 23:00 +0530, Gerard Ryan wrote:
> From what I remember, videos directly in my home directory were
> displayed as thumbnails on the main window and they would play fine.
> If I tried to add/open a local video from another location (even
> subdirectory of my home) by clicking on the + at the corner, nothing
> happened. I wasn't given an open file dialog or anything like that.
> As I said, it may not actually still be a problem. Maybe someone else
> can verify?
This looks like https://bugzilla.gnome.org/show_bug.cgi?id=725063
-----BEGIN PGP SIGNED MESSAGE-----
So I asked in the FESCo meeting how you expect upgrades to work without
an install tree? the building on the upgrade initramfs and the tree for
upgrades is tied into the creation of an install tree. additionally all
the future options that have been looked at for livecd creation plan to
use anaconda, as such an install tree really is a requirement.
I am trying to understand how you expect things to work if you do not
produce an install tree.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----
Hughsie's GNOME 3.12 copr has seen quite a bit of publicity recently.
>From what I can tell, people who have managed to get it installed are
generally happy, but a number of people have also run into rpm dep hell
while updating, and gone back to F20 proper.
Last night, adamw pointed out the fedoramagazine article about GNOME
3.12  and asked if I could look through the broken dep issues
mentioned in the article comments and rebuild the packages in the copr.
At first, I went ahead and rebuilt a few, but then realized this doesn't
really scale. We are only going to be playing catch up with F20 proper
when new builds that use old cogl / tracker / gnome-bluetooth /
gnome-desktop / evolution-data-server libraries are pushed out to updates.
I spent some time today on this and built parallel installable compat
packages with the 3.10 ABI for those libraries. This is hopefully enough
to get out of the dep hell and the need of constant rebuilds in
What would be a good way to manage the git repos for such compat
packages? So far, the copr has only gotten straight rebuilds of rawhide
packages and we haven't had a need for separate git branches. I guess I
could create special f20-gnome-3-12 branches for those 5 in git, or
would it be weird to have something in pkgdb git that's only meant for copr?
the Change Proposals Submission Deadline is coming in one week!
The date is Tuesday, 2014-04-08 for System Wide Changes. Self
Contained Changes deadline will be set later.
I'd like to ask especially WGs to work on the PRD/Tech
Specs break out into the Change Proposals - so the scope of release
can be evaluated and also for tracking purposes to know where we are
with Fedora 21/Next release.
One particular topic that should be included are product deliverables,
to get a wider agreement on how each product will be distributed and
to allow release engineering team (and others as websites) to adjust
for product needs.
See https://fedoraproject.org/wiki/Changes/Policy for current policy for
submissions and start a new proposal using this template
Let me know in case of any issues, I'll try to help you!
Global menu was a matter of controversial topic because of presence in
Apple OS X or its earlier Mac OS. Ubuntu adopted it in their Unity
desktop environment. Gnome Shell took a different approach of global
menu but did not fully explore the potential.
Gnome takes on global menu has an interesting parallel to the responsive
menu system found on most websites running on mobile device like this
Some websites created an interesting menu system like this example by
Combining both elements provides the result attached on this message.
It is surprising that idea did not show on Gnome website. The benefits are:
- less clutter on the window
- touch screen friendly
- easy to implement on complex applications like Gimp.
- Can use existing method
- More possibilities like the use found on sugar interface.
Comments are welcome. Perhaps I should post it on Gnome mailing list