Moving AtCore to Extragear

[Nicolás Alvarez]

Note that changing from GPL2 to GPL2-or-later needs agreement from all
the authors / copyright holders.

-- 
Nicolás

2017-05-26 7:34 GMT-03:00 Jonathan Riddell <jr at jriddell.org>:
> LICENSE file is normally named COPYING in KDE repos
> More importantly the files are GPL 2 only, which isn't allowed in
> KDE's licence policy.  It should be changed to GPL 2 or later (or as
> approved by e.v.) https://community.kde.org/Policies/Licensing_Policy
> LICENSE and README.md both say it uses LGPL, which isn't the case,
> this should be made consistent.
> http://techbase.kde.org/Policies/Kdelibs_Coding_Style links are out of
> date in scripts/*
>
> Jonathan
>
>
>
>
> On 23 May 2017 at 14:17, Lays Rodrigues <laysrodriguessilva at gmail.com> wrote:
>> Good morning everyone,
>> For you that don't know me, I'm Lays Rodrigues, and I work with 3 more
>> guys(Patrick, Chris, Tomaz) on Atelier.
>> Atelier is a software for 3DPrinting that we are building inside KDE. So far
>> we have 10 months of work, and we are ready for the launch of our core, in
>> this case, is AtCore.
>> AtCore is the API responsible for all serial communication, and for
>> validating more of our work, we would like to launch the 0.1 version with
>> the next KDE Applications release.
>> I was told that Extragear applications don't need to follow KDE releases,
>> but we thought that would be better to follow the release schedule on the
>> first launches, so we can fix, for us, a deadline.
>> So for this first step, we want to move AtCore from the Playground to
>> Extragear, and launch it with its test client, where we can make the core
>> stronger, so when we launch Atelier, we know that everything will be stable.
>> Our targets are all Gnu/Linux distros, and we already have inside Craft a
>> port for Windows with packing configured and working.
>>
>> Well, so I would like to require this review and moving to Extragear.
>> This is my first KDE application, so I maybe kind of lost.
>>
>> P.s: You can find more info about the status of the project on my blog here.
>>
>> Thanks all,
>>
>> Ps.:2 I don't know if my first e-mail arrived, because I wasn't subscribed
>> to this mail list, if this is a duplicate, sorry.
>>