> On Samstag, 23. April 2016 19:35:47 CEST Michael Pyne wrote: >> Well there is a kde-sdk-scripts repository already, though it's really more >> of a buffet of different, barely-related scripts than an a curated "we >> think *every* KDE dev should have these files with them".
Do you mean kde-dev-scripts? I think apol also started a scratch repo for 'kdescripts' that were a start on useful new dev scripts? Plasma seems to have one too? And why do I suddenly have a feeling of deja-vu, have we discussed this all before? >> I wouldn't mind moving the recommended kdesrc-build configs to a separate >> SDK repo though, if we create it or repurpose a different repo to also do >> that. I'm not 100% sure of the idea, especially if they are tightly tied to the version of kdesrc-build being used? I could imagine some more specialised configs for particular apps perhaps? On 24 April 2016 at 11:33, Thomas Pfeiffer <thomas.pfeif...@kde.org> wrote: > Therefore, from my perspective it would make sense to link to just put the > files we're discussing here in the kde-sdk-scripts repo (maybe in their own > folder) and recommend to clone that repo in the wiki? > > Would that make sense to you all? It looks a good place, but I agree we would need to tidy the repo up first, organise it into subfolders in line with the sections in the README, maybe remove old Qt3/KDE3 stuff or even KDE4 stuff. A rebrand from KDE may also be needed? (dfaure, your fingerprints are everywhere on this repo, are you maintainer for it?). I could also imagine a simple python script to ask a new dev for name, email, KDE account, root dir, etc and do a default setup depending on their dev goals (App vs Plasma vs Frameworks). Maybe scripts to install required packages for the big distros? All that sort of thing. But perhaps we should hear from the people who were planning the whole new dev experience and sdk thing at Randa? We'd need to sync up with what they are planning. John.
