Help with sorting out unmaintained repos in the playground

[Milian Wolff]

On Montag, 6. April 2020 11:52:57 CEST Ben Cooksley wrote:
> On Mon, Apr 6, 2020 at 7:38 PM Milian Wolff <mail at milianw.de> wrote:
> > On Sonntag, 5. April 2020 14:00:50 CEST Bhushan Shah wrote:
> > > On Sun, Apr 05, 2020 at 04:43:32PM +0530, Bhushan Shah wrote:
> > > > Hello community,
> > > > 
> > > > In preparation for upcoming move of KDE repositories to Gitlab we
> > > > sysadmins wants to move the unused/inactive repositories to
> > > > unmaintained/.
> > > > 
> > > > Current list of all repositories: https://phabricator.kde.org/T12916
> > > 
> > > Sorry for wrong wording here, but this list contains *all* playground
> > > repositories, idea is to remove the maintained repos from this list, so
> > > in end only unmaintained remains.
> > 
> > What will happen to unmaintained repos? Will they be removed? There are
> > quite a few in there, which are dead but I would like to keep for
> > archiving purposes. If KDE's repositories are not the right place for
> > this, I'll move them to GitHub? Or is there a better solution?
> 
> They will be imported into Gitlab, and then archived.
> Archiving a project in Gitlab makes it read-only and removes it from
> the normal search processes but still leaves it accessible should you
> be looking for archived projects (or have the url for that project to
> hand)

And where could we place repos that may just see a commit every few months to 
keep them compiling but being otherwise unmaintained? I.e. read-only won't cut 
it for e.g. kdev-css as apparently it's otherwise somewhat usable or so I 
heard.

What's the advantage of making a repo read only and archived compared to 
keeping it a "normal" playground app? Is CI or similar being run regularly? 
Could this be disabled instead on these repos?

Thanks a lot

> > There are a few in there which should probably transition through
> > kde-review since they are already used by people. But there is noone with
> > the resources to maintain them for real... So what should we do?
> > 
> > devtools/plugins/kdev-verapp
> > devtools/plugins/kdev-valgrind
> > devtools/plugins/kdev-ruby
> > devtools/plugins/kdev-xdebug
> > devtools/plugins/kdev-upload
> > devtools/plugins/kdev-css
> > devtools/plugins/kdev-executebrowser
> > devtools/plugins/kdev-mercurial
> > devtools/plugins/kdev-embedded
> > devtools/plugins/kdev-krazy2
> > devtools/plugins/kdev-control-flow-graph
> > devtools/quanta
> > 
> > Having them in playground was a nice way to create something that may or
> > may not work, quasi the "use on your own risk" place for code with no
> > guarantees... Or something which only worked for the person working on it
> > at some time.
> 
> Cheers,
> Ben
> 
> > Cheers
> > --
> > Milian Wolff
> > mail at milianw.de
> > http://milianw.de


-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20200406/7840bae9/attachment.sig>