On Wed 06 Mar 2013 05:03:15 PM EST, Richard Hughes wrote:
On 6 March 2013 21:58, Ryan Lerch <rlerch@xxxxxxxxxx> wrote:
No central point of failure but screenshots which you previously suggested
was be served via the web.
Sure, I think many fewer users will be looking at the details for each
application. Most users know pretty much what they want to install or
remove (e.g. install gimp, or update firefox) and this doesn't involve
looking at screenshots. Only users that want to know what apps are
will want to drill down to the screenshots and ratings for each app.
Of course, we could include screenshots for common apps like firefox
and gimp, and also include offline ratings too, but you've got to
balance local storage v.s. remove bandwidth and I decided screenshots
were probably the right point to cut.
Richard.
The Application-focused installation tool is an issue that we really
need to solve in Fedora, hoever, this discussion is seemingly devolving
into a low-level argument about technologies and implementation
details.
Is there a high-level writeup anywhere of the design of the
GNOME-software tool? How it each feature in the GNOME-software tool is
supposed to interact with the technologies that keep popping up in this
discussion (OCS, AppStream)? Using this, we can start thinking on how
to leverage the current fedora infratructure we have (Fedora Packages,
Tagger, Fedora Accounts System) to either complement or replace things
like OCS in this ecosystem.
Either way, having clear documentation on how this is supposed to
function would be a good place to start.
cheers,
ryanlerch
--ryanlerch
--
desktop mailing list
desktop@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/desktop
