[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: web server for appstream metadata screenshots
From:       "Yuri Chornoivan" <yurchor () ukr ! net>
Date:       2016-06-12 4:46:10
Message-ID: op.yixgu8i9l2zvei () mycomp ! myhome
[Download RAW message or body]

=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=B5 Sun, 12 Jun 2016 04:17:=
07 +0300, Albert Astals Cid  =

<aacid@kde.org>:

> El dimecres, 8 de juny de 2016, a les 19:32:32 CEST, Yuri Chornoivan v=
a
> escriure:
>> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=B5 Wed, 08 Jun 2016 19:=
27:23 +0300, Burkhard L=C3=BCck
>>
>> <lueck@hube-lueck.de>:
>> > Am Mittwoch, 8. Juni 2016, 12:45:13 CEST schrieb Nicol=C3=A1s Alvar=
ez:
>> >> 2016-06-08 8:33 GMT-03:00 Friedrich W. H. Kossebau  =

>> <kossebau@kde.org>:
>> >> > Am Mittwoch, 8. Juni 2016, 13:10:04 CEST schrieb Sebastian K=C3=BC=
gler:
>> >> >> Hey,
>> >> >>
>> >> >> I've been adding appstream metadata to one of the apps I mainta=
in,
>> >>
>> >> among
>> >>
>> >> >> that are also screenshots, in the form of a URL. That means tha=
t I
>> >>
>> >> have
>> >>
>> >> >> to
>> >> >> put the screenshots on a webserver.
>> >> >>
>> >> >> Do we already have a canonical location for these screenshots? =
If
>> >>
>> >> not,
>> >>
>> >> >> let's create one before we get people hosting them on imgur, th=
eir
>> >> >> private webserver or their router-behind-a-dsl-line. :)
>> >> >
>> >> > Good idea, also when it comes to long-term availability of  =

>> referenced
>> >> > images>
>> >> >
>> >> > :)
>> >> >
>> >> > It might make sense to reuse/share the screenshots with the ones=
  =

>> used
>> >>
>> >> for
>> >>
>> >> > the KDE app catalog we have at kde.org/applications/. For  =

>> consistency
>> >>
>> >> and
>> >>
>> >> > for efficiency.
>> >> >
>> >> > Not sure though what a stable url would be like, given people
>> >>
>> >> planning to
>> >>
>> >> > rework kde.org (and thus those app catalog pages), so perhaps  =

>> relying
>> >>
>> >> on
>> >>
>> >> > the current screenshot urls used by kde.org/applications is not
>> >>
>> >> perfect.
>> >> The screenshots on kde.org/applications are stored in SVN and they=
  =

>> are
>> >> the main reason why I couldn't migrate that website to Git. I woul=
d
>> >> prefer if you don't add even more there...
>> >
>> > www/sites/www/screenshots (svn) has 176 pngs
>> >
>> > websites/edu-kde-org/ (git) has 1287 pngs
>> >
>> > master kf5 / doc[s] (git) folders have  2079 pngs
>> >
>> > master kde4 / doc[s] (git) folders have 1702 pngs
>> >
>> > I do not understand why the 176 pngs in www/sites/www/screenshots a=
re  =

>> a
>> > problem for migration to git
>>
>> Hi,
>>
>> I might be wrong, but is the hotlinking to Phabricator/Git files
>> (screenshots in this case) a good thing?
>
> Nobody suggested that, right?

I might misunderstand the whole thing. If it is, just ignore this messag=
e.

The typical size of AppData screenshot is ~100 kB. Let's say that there =
 =

are ~1000 users that use Discover features to explore KDE applications i=
n  =

a release day. They can overview ~10 screenshots in average. This will b=
e  =

1 GB of traffic + load on Phabricator to resolve commits.kde.org links (=
if  =

files are stored in git).

Recently, Ben Cooksley removed the page with Calligra Icons from  =

community.kde.org for similar hotlinking:

https://community.kde.org/Calligra/Icons/3.0

That was the source of my concerns.

On the other hand, if screenshots will be stored in different  =

places/hostings (each application stores its screenshot in its own place=
)  =

it can leverage the load on our infrastructure.

Sorry again, if I misunderstand something.

Best regards,
Yuri
[prev in list] [next in list] [prev in thread] [next in thread]