Web lists-archives.com

Re: Removing code from kdeexamples dir




Thanks for the input

2018-06-13 18:12 GMT-03:00 Albert Astals Cid <aacid@xxxxxxx>:
> You don't need a branch, you can just remove everything and tell people the
> hash they can checkout if they're interested in kdelibs4 code.
>
> Ideally we would have a maintained kdeexamples dir, but since we don't your
> solution seems sensible.

Done: https://commits.kde.org/kdeexamples/bb5399d65f56745d8da0077180f3d45f92650f30

>
> Also ask sysadmins to move it to the "virtual" unmaintained module, though
> maybe it is already.

Also done: https://phabricator.kde.org/T9019

>
> Cheers,
>   Albert
>
>
>



-- 
Luiz Romário Santana Rios

2018-06-13 18:12 GMT-03:00 Albert Astals Cid <aacid@xxxxxxx>:
> El diumenge, 10 de juny de 2018, a les 8:23:43 CEST, Luiz Romário Santana Rios
> va escriure:
>> From what I can see, the kdeexamples repo is mostly unmaintained (the
>> last useful commit dates back to 2014), the master branch only
>> contains KDE 4 code and the frameworks-scratch branch is just as
>> ancient.
>>
>> I propose the following:
>> 1. Create a branch (or tag) called master-unmaintained, master-old or
>> whatever you prefer, pointing to the current HEAD
>> 2. Obliterate everything from the repo, leaving only a
>>
>> README.unmaintained file, reading:
>> > This repository is unmaintained. To see the code, checkout the
>> > master-unmaintained branch
>> Most (if not all) the examples would have to be deleted anyway if
>> someone wanted to revive this repo, so I say we don't have a lot to
>> lose in terms of git history either.
>>
>> Opinions?
>
> You don't need a branch, you can just remove everything and tell people the
> hash they can checkout if they're interested in kdelibs4 code.
>
> Ideally we would have a maintained kdeexamples dir, but since we don't your
> solution seems sensible.
>
> Also ask sysadmins to move it to the "virtual" unmaintained module, though
> maybe it is already.
>
> Cheers,
>   Albert
>
>
>



-- 
Luiz Romário Santana Rios