From kde-frameworks-devel Tue Aug 19 10:22:17 2014 From: Aleix Pol Date: Tue, 19 Aug 2014 10:22:17 +0000 To: kde-frameworks-devel Subject: Re: How to promote less mature Frameworks? Message-Id: X-MARC-Message: https://marc.info/?l=kde-frameworks-devel&m=140844376713357 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1297932993406022122==" --===============1297932993406022122== Content-Type: multipart/alternative; boundary=001a11c15c50e0acd80500f8dd7f --001a11c15c50e0acd80500f8dd7f Content-Type: text/plain; charset=UTF-8 On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens 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/ --001a11c15c50e0acd80500f8dd7f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Aug 19, 2014 at 9:33 AM, Kevin Ottens <ervin@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 th= em. 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 th= ose
> > frameworks which don't have the "release: true" fla= g. This way they keep
> > not being part of a release, and early adopters have something ea= sy 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 tarba= ll,
> because a git checkout is just so much easier to update later.
> We mostly make tarballs for packagers, and the non-mature frameworks w= e're
> talking about should definitely NOT be packaged.

Agreed.

> IMHO the solution is just to publicize the upcoming frameworks somewhe= re.

Which shouldn't be that hard, it's "only" about pro= cessing the yaml file and
creating a page listing them. I think that's what makes most sense inde= ed.

Regards.

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

--001a11c15c50e0acd80500f8dd7f-- --===============1297932993406022122== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel --===============1297932993406022122==--