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

List:       kde-frameworks-devel
Subject:    Re: How to promote less mature Frameworks?
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2014-08-19 13:09:46
Message-ID: CACcA1RoyeZ6jpO9km+ssu-wrLvQGtZBE1HA0Tq=iCECw+L9Jwg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, Aug 19, 2014 at 2:04 PM, Kevin Ottens <ervin@kde.org> wrote:

> On Tuesday 19 August 2014 12:22:17 Aleix Pol wrote:
> > On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens <ervin@kde.org> wrote:
> > > On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> > > > IMHO the solution is just to publicize the upcoming frameworks
> > > > somewhere.
> > >
> > > Which shouldn't be that hard, it's "only" about processing the yaml
> file
> > > and creating a page listing them. I think that's what makes most sense
> > > indeed.
> >
> > Maybe we can show their API documentation as well, in a different
> category.
> > [1]
>
> I'd wait for the demand for that. api.kde.org is already very loaded in
> information no need to add even more IMO.
>
> Cheers.
>

Well, we did some information unloading work back in Randa. Maybe you want
to take a look at it again.

Aleix

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 19, 2014 \
at 2:04 PM, Kevin Ottens <span dir="ltr">&lt;<a href="mailto:ervin@kde.org" \
target="_blank">ervin@kde.org</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

<div class="">On Tuesday 19 August 2014 12:22:17 Aleix Pol wrote:<br>
&gt; On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens &lt;<a \
href="mailto:ervin@kde.org">ervin@kde.org</a>&gt; wrote:<br> &gt; &gt; On Tuesday 19 \
August 2014 08:44:10 David Faure wrote:<br> </div><div class="">&gt; &gt; &gt; IMHO \
the solution is just to publicize the upcoming frameworks<br> &gt; &gt; &gt; \
somewhere.<br> &gt; &gt;<br>
&gt; &gt; Which shouldn&#39;t be that hard, it&#39;s &quot;only&quot; about \
processing the yaml file<br> &gt; &gt; and creating a page listing them. I think \
that&#39;s what makes most sense<br> &gt; &gt; indeed.<br>
&gt;<br>
</div><div class="">&gt; Maybe we can show their API documentation as well, in a \
different category.<br> &gt; [1]<br>
<br>
</div>I&#39;d wait for the demand for that. <a href="http://api.kde.org" \
target="_blank">api.kde.org</a> is already very loaded in<br> information no need to \
add even more IMO.<br> <br>
Cheers.<br></blockquote><div><br></div><div>Well, we did some information unloading \
work back in Randa. Maybe you want to take a look at it \
again.</div><div><br></div><div>Aleix</div></div><br></div></div>



_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel


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