How to promote less mature Frameworks?

[Aleix Pol]

On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens <ervin at kde.org> wrote:

> On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> > On Friday 15 August 2014 12:51:58 Kevin Ottens wrote:
> > > And that's the problem if we release them. If it's released "with the
> > > rest" expect people to have wrong expectations about them.
> > >
> > > A possibility would be perhaps to produce nightly tarballs for those
> > > frameworks which don't have the "release: true" flag. This way they
> keep
> > > not being part of a release, and early adopters have something easy to
> > > grab.
> >
> > Wouldn't early adopters just checkout and build from git ?
>
> Well, I guess some of them might just want to grab something and run with
> it.
> Maybe not the majority indeed...
>
> > I don't know about you, but I almost never download a source tarball,
> > because a git checkout is just so much easier to update later.
> > We mostly make tarballs for packagers, and the non-mature frameworks
> we're
> > talking about should definitely NOT be packaged.
>
> Agreed.
>
> > 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.
>
> Regards.
>

Maybe we can show their API documentation as well, in a different category.
[1]

Aleix

[1] http://api.kde.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140819/57e861d0/attachment.html>