Introduction, Documenting Workstation
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I'm acquainted with many of you already, but an introduction seems
fitting anyway. I've been involved with the project for a few years now,
primarily on the Docs team but also some light packaging and lately
light infrastructure things. I live in Montana, US, where the population
density is almost as low as the temperature. I work for a small
government agency doing user and systems support.
Why should you care? Well, the Docs team reached a decision this last
weekend to proactively work with the Product WGs to assess documentation
needs. I volunteered to liaison with the Workstation team. As we
approach the release cycle, I'd like everyone to keep documentation in
mind and the discussion open about not only implementation, but how to
represent that implementation to the users. An undocumented feature
isn't featured :)
I'm looking forward to working with everyone, perhaps saying hello at
the next meeting - there are meetings, right? - and developing a
presentation of the Workstation Product that shows off the capabilities
and character of your work.
- --
- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTNW1PAAoJEL1wZM0+jj2Zos4H/37WaPQMRumzi766cXv6x3mb
ADJuFmZ+mZwosTynurCAKG5p8PczOHKhRrZNslf9nFNx4dczc94QJFlO7hPOq3Mr
WOzkSn6pUXppukAd6UxX7qAjtrNomYCM8kDlmyK+ArZmVbo78O2IppeSwZk4R/tJ
ILnktcYl4sXJjlOrA28X5uiZ0dvreuZPBT+UsiDZHVvFBQfaYqjUKIioW/R4wQYp
FoFvLbXe2XCn609LuHl0TcEP9DIwd2ShKROqw2fhXXSPe4jWWwkm0+FktwEKAt46
DqKBpIZeeIIZfiKXRPS6CCGNOULboepDKj+7RfqmtrjUIqdPQZ4ZP+Hdr1vSC3M=
=G3EO
-----END PGP SIGNATURE-----
9 years, 9 months
Fedora.next Product Branding
by Ryan Lerch
*This is sent with my Fedora Design Team hat on*
With the creation of 3 products for Fedora, the Fedora Design Team
anticipates manynewquestions aroundFedora'sbrand. As the main caretakers
of the Fedora brand, weare going to have to figure these things out
within the next few months. For example, the Design Team is starting to
think about how to answer these types of questions:
• Should each product have its own logo? or
• Can you add our product to the Fedora website? or
• Can you make our product its own website? (How should we represent
these products on the website? Should we allow products to have their
own separate websites?)
To start off the rebranding discussion, the Fedora Design Teamhas4 basic
questions for each of the 3 product-focused working groups to answer:
(1) What problem does your product solve, in one sentence?
(2) Who is the target audience for your product, in one sentence?
(3) List at least 5 products that successfully target the same target
audience you are after.
(4) List at least 5 products that try to solve the same problem.
We are reaching out to each group individually to ask that you discuss
these questions and come back to us with answers by Wednesday, December
4th2013.
cheers,
ryanlerch
9 years, 11 months
arm support of workstation product
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
I noticed that in the hardware supported in the tech specs says 64 bit
only. I believe that in the f21 time frame we should be able to
integrate etnaviv [1][2] and be able to offer a viable arm based
option. note that arm ships in two formats, disk image that's ready to
run and install tree. there is no support to run anaconda and do a
liveinstall type install. For some possible systems putting the image
onto a sdcard and running will be fine. But for some others there may
be a desire to install onto a hard drive to use.
I personally believe that it is a viable target.
Dennis
[1] https://github.com/laanwj/etna_viv
[2] https://plus.google.com/+ArndBergmann/posts/bjja7uW9vA4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJTGgdfAAoJEH7ltONmPFDR5kcQAKqL85+d0TAKA7umDpmmi6pH
6wx60mgWjH5TM4v2fbbqKBA8kL8RF8040liQHCrCYD0zwFE9NIquPL6pxgyDouGX
Xaq6F+mQ0UQHitVC2cvrTAFAeygoW41JGL6WvYMApTg86HnCW+mNE/EdzhOKCCUU
A59UBwLONc5HJ2ei7oAmyxjxqbPiWzzmh9kGUKmU+HQ1yXNi7p/cVl7GXUuMvbiW
PPvJw53osnvu1gz9AArRC9ZWJEtaByDCM5hm5EKZQUOCwN27SQ9d114mClRrZRJi
NDUtPzGuuk2c0MdVpE/W4fUd5NLjsuAaDxrRHRTrdwKcKi+sDrXnOiui2wBDdVzV
qx+YbJRsWB1DBOuTMCheX2ZYipoqx8a4VWXP6nf7lyiowwzlEIyQDZ15s1CvDK9Q
j25doND/XImXPFcu7FVy8GBfw/yUr3FBPxlarXRruEH0/za7f5I4pw8NKUtMLtAl
p1Wc4u54P1UjbZpXsNAQzZTS7Us0rl3Q8I06mQW+NqBadWNqWIXarzsftBx5xsdS
xRRiC0aP6Na0m0W6jXNH07/gT6iQdPeY+D5T0bpyOzgxbdifigCDcQZpe18LyDtL
95bW7Q9S5f+3P9m31VBGEwLcvHPzYgDpZ8RRF2yK1PMXDXitFItOSg3fp330BtGk
Ne1ETUEAS4zCoW6Fd+cM
=5Sr6
-----END PGP SIGNATURE-----
10 years
how are upgrades supposed to work in fedora.next?
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
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.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJTGgP7AAoJEH7ltONmPFDRd8IP/A3e0hkuiBiY3aLrmpBGcwwX
4uv/PCTWbtU/8d3fb9kHGqEwyeujJw2kcHvdxjCqDTeZ3DVp0fwAc+fk5XhAZEnI
Y3eNWAU8NuMJNePMerH6pjfVkbHeHDFx2TG13yDZSXQooD+7oENsyrx8OhOSqxxa
F3yMVTDnn1JLBspE9D6njSPVTdzsOxQtQFrYvvvJKRr1pvYSteNgqTHswqInw7Hm
tr0iLqOkzoBWKkrWDMd3IsHuE56TICTqfo39C27IwpSdPIKruidsl2XpTtzucFgc
p2YOGhplOFbh5v2E8vMwYh3uloouQc3FaF2FFUObTzN9c8DP+la83ve2nbBHoQyk
WYE3t1iLmqB5n0SpTfmZgXzLo/Gd8JewqeH6mWAfhQXmxO1sTG0kJmPHPWLxsOOO
u0/jT7pS16MwOdzvGQC26ZfNL5OVC0mU0rLenw8/IBcyEufFmxVclrFP8Yspw3Aa
hCeaInrK4AMrmmBN5X9h+HDfELwV7mCG8KOX6rxp5MnWyqfcODrdcpvkdHGfTQG/
J2DpNPpjOhHKWdne3QjG7HID08LKdfgIkg0xOge8s0DlNxy4nTdKzqnDH644zCdJ
6IHPkfhLQyM3zMnAP7QrouLWS5G/FADgaawohuw/s5iYs+yOLA5FAHDueA3w9TMv
bicsUFuEy9oK2S4K9umJ
=B84D
-----END PGP SIGNATURE-----
10 years
Rethinking of global menu on Gnome Shell
by Luya Tshimbalanga
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
example:
http://codropspz.tympanus.netdna-cdn.com/codrops/wp-content/uploads/2013/...
Some websites created an interesting menu system like this example by
hovering:
http://www.autoblog.com/
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
Luya
10 years
Trying Wayland
by Matthias Clasen
With GNOME 3.12 in rawhide today (or in the F20 copr), it is for the
first time really easy to try GNOME with Wayland. You can just select
'GNOME on Wayland' from the session chooser on the login screen.
If you do so, you'll get a desktop that looks just like regular GNOME,
and a great many things work just fine. Just be aware of the few things
that don't work yet:
- Drag-and-drop doesn't work
- No touch support
- some popups (eg entry completion) do not appear
Most seriously, right clicks and double-clicks on applications that are
running under xwayland have the tendency to bring down the session.
Of course, we are working on all of these issues. Any help is welcome!
Matthias
10 years
KDE integration/status for Workstation
by Josh Boyer
Hi All,
During the default DE discussions, a number of WG members expressed
interest in keeping KDE as a release blocking DE for Workstation. QA
is now asking FESCo about KDE's status as well in
https://fedorahosted.org/fesco/ticket/1243
So if KDE is going to be a release blocking DE for Workstation, we
need to figure out how exactly it gets installed and what manner it
would be tested in. In the above ticket I came up with the following:
install the Workstation live image, install KDE through
software-installer (if necessary), log into KDE from GDM after
install, test
However, that was entirely off the top of my head. Would the live
image be large enough to contain the KDE Workstation already or would
a user/QA tester need to install it through the software-installer?
What tests should be done? Etc.
Thoughts?
josh
10 years
unoconv in F20 gained dependency on strange GUI applications
by Michael Catanzaro
Hey,
If you've ever used Sushi or GNOME Documents to preview an ODT document,
you've probably noticed (or will soon notice) that strange GUI
applications were installed after a recent F20 update: Chainsaw,
LogFactor5, and LibreOffice Base. This is [1] and it's currently CLOSED
WONTFIX.
I just want to draw some attention to this, since post-release
dependencies impact the desktop team's ability to control the default
set of applications. I'm pretty sure we don't want users to have these
strange Java logging utilities by default.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1065776
10 years, 1 month
