Re: [kde-community] Updating TechBase Getting_Started pages
On Monday 17 of August 2015 09:53:58 John Layt wrote: My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. Is it really s/removed/moved/, right? We already have name-spaced historical information around (for example https://techbase.kde.org/Development/Architecture/KDE4 ) so I guess it would be just an addition to them. Ciao -- Luigi ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Updating TechBase Getting_Started pages
Hi, I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? John. [1] https://techbase.kde.org/KF5/Getting_Started [2] Probably https://techbase.kde.org/Development/Build? ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, Aug 17, 2015 at 08:48:15AM +0100, John Layt wrote: I would note from reading the Gnome wiki on Github that you can't globally turn off pull requests for an organisation, you need to do it for each repo. If we set up mirroring I assume we need to write something that automates creating repos on github using the github API, and the API has a function to disable issues. And if I understand the Github API docs correctly it treats issues the same way as pull requests, so if you turn off issues for a project you also disable pull requests. -- Martin Sandsmark ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On Mon, Aug 17, 2015 at 8:58 PM, David Edmundson da...@davidedmundson.co.uk wrote: On Mon, Aug 17, 2015 at 9:53 AM, John Layt jl...@kde.org wrote: Hi, I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? Just want to say Thanks for taking this task on - it's quite an important one to make our software more accessible to new contributors. We have one for Plasma here. https://community.kde.org/Plasma/Building I'm happy for this to become a redirect and unifying them all. Cheers, Ben John. [1] https://techbase.kde.org/KF5/Getting_Started [2] Probably https://techbase.kde.org/Development/Build? ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, Aug 17, 2015 at 7:46 AM, Martin Graesslin mgraess...@kde.org wrote: Hi community, over the last months I observed the following: * people not finding our git repositories * people being surprised that our code is not on github * some projects starting to use github in addition to our own infrastructure Whether we like it or not, github has become a place to look for free software nowadays and if you are not on github your software just doesn't exist. Given that we can say KDE doesn't produce source code because we are not on github. Other projects have an official mirror (see e.g. [1]) which solves the three points I have listed above. I suggest that we: * introduce an official mirror for all KDE repositories on github * replace all existing (non-official) clones * disallow pull-requests on github to not replace our development model by a proprietary platform. Comments? I support this proposal. Here's a comprehensive list of projects that use Github as a mirror [1] Cheers Rohan Garg [1] https://help.github.com/articles/about-github-mirrors/ ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday, 2015-08-17, 09:12:18, Martin Graesslin wrote: On Monday, August 17, 2015 08:55:57 AM Jos van den Oever wrote: On Monday 17 August 2015 07:46:44 Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories Searching on ixquick: 'calligra git' https://community.kde.org/Calligra/Git 'kde git' https://community.kde.org/Sysadmin/GitKdeOrgManual 'kwin git' https://github.com/faho/kwin-tiling 'plasma git' https://community.kde.org/Plasma/Active/Development Searching on Google: 'calligra git' https://community.kde.org/Calligra/Building/2 'kde git' https://techbase.kde.org/Development/Git 'kwin git' http://blog.martin-graesslin.com/blog/2014/04/kwin-moved-to-an-own-reposit o ry/ 'plasma git' - https://aur.archlinux.org/packages/plasma-desktop-git/ On google the highest link to github was in position 4. Not too bad. There was no link to https://projects.kde.org/ or https://quickgit.kde.org/ What part of the KDE infrastructures can be fixed to make the repositories easier to find? * people being surprised that our code is not on github This is good moment to educate them on the ideals of KDE. Yes certainly, I start with lecturing a potential new contributor /sarcasm I know, sarcasm tag and all, but that is not what Jos was saying. Educating doesn't imply lecturing, laying out reasons for decisions that resulted in a situation can be done in a non confrontational or belitteling way. Not all potential new contributors will be developers of proprietary software who just happen to use our software in some way. Some will be developers specifically interested in contributing to FOSS but they might not have thought about the problem of proprietary services yet. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On Mon, Aug 17, 2015 at 9:53 AM, John Layt jl...@kde.org wrote: Hi, I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? We have one for Plasma here. https://community.kde.org/Plasma/Building I'm happy for this to become a redirect and unifying them all. John. [1] https://techbase.kde.org/KF5/Getting_Started [2] Probably https://techbase.kde.org/Development/Build? ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On Mon, August 17, 2015 09:53:58 John Layt wrote: Hi, I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? This has been sorely needed, and I've never quite had the time to bring kdesrc-buildrc-setup up to speed. But do let me know if there's things I should take *out* of kdesrc-build.git to make it easier, or some kind of feature that's sorely needed. Regards, - Michael Pyne ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, 17 Aug 2015, Jeremy Whiting wrote: Boud, That page is generated by the contents of https://websvn.kde.org/trunk/www/sites/www/applications/apps/krita.json?view=log and the image file relative to it and such. If you don't have svn Are you sure? That svn link still mentions koffice, and https://www.kde.org/applications/graphics/krita/development doesn't. https://www.kde.org/applications/graphics/krita/ does, though... I need some time to come up with a better description, better screenshot, and more. Boudewijn ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday, August 17, 2015 07:46:44 AM Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories * people being surprised that our code is not on github * some projects starting to use github in addition to our own infrastructure Whether we like it or not, github has become a place to look for free software nowadays and if you are not on github your software just doesn't exist. Given that we can say KDE doesn't produce source code because we are not on github. Other projects have an official mirror (see e.g. [1]) which solves the three points I have listed above. I suggest that we: * introduce an official mirror for all KDE repositories on github * replace all existing (non-official) clones * disallow pull-requests on github to not replace our development model by a proprietary platform. Comments? Cheers Martin [1] https://github.com/GNOME As a user of Github for 5 years, I’m against KDE moving any code to that platform. KDE is probably one of the few projects that’s stood tall when it comes to holding its F/OSS ideals and I’ve always looked up to that. I think that in order for KDE to continue said standards, making use of something like Gitlab[1] would stand to work better. For those who are ‘hell-bent’ on using Github, they can sign in with it and work as if they were in Github (it has a similar interface). [1]: http://gitlab.com/ -- Jacky Alciné - https://jacky.wtf Work: https://jacky.wtf/work --- They can READ + SEE everything in this email. In your texts. The NSA's been spying on US citizens for too long. Read more: https://www.eff.org/nsa-spying signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
As a user of Github for 5 years, I’m against KDE moving any code to that platform. KDE is probably one of the few projects that’s stood tall when it comes to holding its F/OSS ideals and I’ve always looked up to that. I think that in order for KDE to continue said standards, making use of something like Gitlab[1] would stand to work better. For those who are ‘hell-bent’ on using Github, they can sign in with it and work as if they were in Github (it has a similar interface). We're not moving anything anywhere, we will mirror our code on Github and nothing else, we have nothing to lose and everything to gain by mirroring our code elsewhere. Cheers Rohan Garg ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On 17 August 2015 at 14:42, Jeremy Whiting jpwhit...@kde.org wrote: Boud, That page is generated by the contents of https://websvn.kde.org/trunk/www/sites/www/applications/apps/krita.json?view=log and the image file relative to it and such. If you don't have svn karma to update it feel free to send me a patch or new icon and I can do that for you (or ask sysadmin for karma if you rather). Interesting. Shouldn't we be auto-generating that json from the appdata file in each repo? I think I suggested such a thing a while back... John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday, August 17, 2015 03:56:00 PM Rohan Garg wrote: As a user of Github for 5 years, I’m against KDE moving any code to that platform. KDE is probably one of the few projects that’s stood tall when it comes to holding its F/OSS ideals and I’ve always looked up to that. I think that in order for KDE to continue said standards, making use of something like Gitlab[1] would stand to work better. For those who are ‘hell-bent’ on using Github, they can sign in with it and work as if they were in Github (it has a similar interface). We're not moving anything anywhere, we will mirror our code on Github and nothing else, we have nothing to lose and everything to gain by mirroring our code elsewhere. Noted, Rohan. Sorry, just saw the thread leader and a chord in my heart jumped! -- Jacky Alciné - https://jacky.wtf Work: https://jacky.wtf/work --- They can READ + SEE everything in this email. In your texts. The NSA's been spying on US citizens for too long. Read more: https://www.eff.org/nsa-spying signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
El Dilluns, 17 d'agost de 2015, a les 14:49:59, John Layt va escriure: On 17 August 2015 at 14:42, Jeremy Whiting jpwhit...@kde.org wrote: Boud, That page is generated by the contents of https://websvn.kde.org/trunk/www/sites/www/applications/apps/krita.json?vi ew=log and the image file relative to it and such. If you don't have svn karma to update it feel free to send me a patch or new icon and I can do that for you (or ask sysadmin for karma if you rather). Interesting. Shouldn't we be auto-generating that json from the appdata file in each repo? I think I suggested such a thing a while back... Sadly suggestions don't automagically convert into code :D Cheers, Albert John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 17 August 2015 at 10:56, Alex Merry alex.me...@kde.org wrote: At some point we will need to address this extra info as well - there's no point leaving a jumbled mess around. Yes, there lots of more advanced scenarios that we need to provide docs for. There's also a serious need for people to review all of TechBase for KF5 and Git, for example the Application Lifecycle page still refers to SVN! If anyone has time to spare, jump in. I'm wondering though if we shouldn't try organise a week where *everyone* stops coding and writes or cleans-up some docs instead? I think we want a brief next steps at the end of the build instructions - hey, you did the thing, look here for what to do next. The obvious next step is to submit a patch (either claiming a junior job on b.k.o, say, or some pet issue the person already wants to solve). Yeap, linking to Contribute is appropriate here. Most of the stuff is still very draft, but it has had all the unnecessary guff chainsawed out, so now I'm shuffling things around trying to get the right flow before fleshing out the details. John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 2015-08-17 16:47, Sebastian Kügler wrote: The following doc takes the point of view of a new developer or designer who would like to contribute, it has high-level starting points: https://community.kde.org/Plasma/Mobile/Contributing The general equivalent of this page is https://community.kde.org/Get_Involved - it gives an overview of the areas you can get involved in, and links to pages with more detail about how to get involved in that way. I think it makes a nice jumping-off point, and is good for emphasising that writing code is far from the be-all-and-end-all of KDE. It's very much a community involvement page, though, and techbase needs an equivalent whose selection is more along the lines of I want to write code / I want to use the Frameworks in my own project / I want to deploy KDE software to 20 000 computers. The how to build our software is just one part of that. Co-ordinating the development track on the community wiki and the build / send in patches track on the techbase wiki is going to take some thought, though. Alex ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
El Dilluns, 17 d'agost de 2015, a les 09:53:58, John Layt va escriure: Hi, I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? I think kdesrc-build is a bit of an overkill for the Build an app only using packaged Qt and KF5 scenario. I find it easier to just clone, cmake and make than having to learn how to use kdesrc-build. Cheers, Albert John. [1] https://techbase.kde.org/KF5/Getting_Started [2] Probably https://techbase.kde.org/Development/Build? ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
Thanks all for whipping the pages into shape :) On Mon, Aug 17, 2015 at 11:47 AM, Sebastian Kügler se...@kde.org wrote: On Monday, August 17, 2015 09:53:58 John Layt wrote: I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? Yes. I'm giving the Plasma Mobile docs some love, but have discovered that also most of the other Plasma documentation for new developers is pretty disjoint and lacking. It certainly doesn't guide someone new well to becoming a productive contributor. I much welcome your initiative and want to pitch in. One of the pages I've written last week may serve as an example of what I have in mind for this kind of pages, it's directed at designers how want to contribute. It gives an overview of principles we use, tools, workflows and communication channels. https://community.kde.org/Plasma/Mobile/Design The following doc takes the point of view of a new developer or designer who would like to contribute, it has high-level starting points: https://community.kde.org/Plasma/Mobile/Contributing I think this documentation should probably not be specific to Plasma Mobile but generally should refer to Plasma or even more generic resources -- without losing level-of-detail. I think giving users a too generic guide can be off-putting for some. Thanks for getting this ball rolling. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
It should be coming from that file and the krita_generated.json file. Maybe the actual web site doesn't use all the fields from the .json file? Ah, the description is on https://www.kde.org/applications/graphics/krita not the /development sub page. That page does mention Koffice. On Mon, Aug 17, 2015 at 8:26 AM, Boudewijn Rempt b...@valdyas.org wrote: On Mon, 17 Aug 2015, Jeremy Whiting wrote: Boud, That page is generated by the contents of https://websvn.kde.org/trunk/www/sites/www/applications/apps/krita.json?view=log and the image file relative to it and such. If you don't have svn Are you sure? That svn link still mentions koffice, and https://www.kde.org/applications/graphics/krita/development doesn't. https://www.kde.org/applications/graphics/krita/ does, though... I need some time to come up with a better description, better screenshot, and more. Boudewijn ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 17 August 2015 at 17:57, Alex Merry alex.me...@kde.org wrote: The general equivalent of this page is https://community.kde.org/Get_Involved - it gives an overview of the areas you can get involved in, and links to pages with more detail about how to get involved in that way. I think it makes a nice jumping-off point, and is good for emphasising that writing code is far from the be-all-and-end-all of KDE. It's very much a community involvement page, though, and techbase needs an equivalent whose selection is more along the lines of I want to write code / I want to use the Frameworks in my own project / I want to deploy KDE software to 20 000 computers. The how to build our software is just one part of that. Co-ordinating the development track on the community wiki and the build / send in patches track on the techbase wiki is going to take some thought, though. You mean like https://techbase.kde.org/Contribute? :-) It may help to have standard names for these sorts of matching pages. But yes, ideally we would have an overall design to follow, complete with personas for target audience, then lock down the pages so no-one can dilute the message (while leaving it open enough to edit as things change!). John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 17 August 2015 at 10:25, Luigi Toscano luigi.tosc...@tiscali.it wrote: Is it really s/removed/moved/, right? We already have name-spaced historical information around (for example https://techbase.kde.org/Development/Architecture/KDE4 ) so I guess it would be just an addition to them. Yes, one of the joys of the ambiguity/redundancy built into English, here 'removed to' is the same as 'moved to' :-) Yes, was thinking of moving the https://techbase.kde.org/Getting_Started/Build/Historic page (instructions since 2.2.2!) to Development/Build/Historic and adding all the KDE4 stuff to it, leaving the top level Development/Build page to the detailed yet-to-be-written KF5 stuff. John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On 17 August 2015 at 10:56, Alex Merry alex.me...@kde.org wrote: At some point we will need to address this extra info as well - there's no point leaving a jumbled mess around. Yes, there lots of more advanced scenarios that we need to provide docs for. There's also a serious need for people to review all of TechBase for KF5 and Git, for example the Application Lifecycle page still refers to SVN! If anyone has time to spare, jump in. I'm wondering though if we shouldn't try organise a week where *everyone* stops coding and writes or cleans-up some docs instead? I think we want a brief next steps at the end of the build instructions - hey, you did the thing, look here for what to do next. The obvious next step is to submit a patch (either claiming a junior job on b.k.o, say, or some pet issue the person already wants to solve). Yeap, linking to Contribute is appropriate here. Most of the stuff is still very draft, but it has had all the unnecessary guff chainsawed out, so now I'm shuffling things around trying to get the right flow before fleshing out the details. John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, Aug 17, 2015 at 12:54 PM, Jos van den Oever j...@vandenoever.info wrote: There is a (non-standard) instruction for robots.txt which reduces the crawl- frequency. E.g. Crawl-delay: 10 says only 10 requests per second are allowed. Neither projects.kde.org nor quickgit.kde.org are using this atm. http://stackoverflow.com/questions/17377835/robots-txt-what-is-the-proper-format-for-a-crawl-delay-for-multiple-user-agent If we do not let search engines index our primary product (source code), then it's not strange that people cannot find it. There is no point in allowing to index whole source codes IMO. But as sandsmark mentioned above there should be one page of where to find source code, how to get it, and how to contribute further and that should be indexed. -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, Aug 17, 2015 at 7:46 AM, Martin Graesslin mgraess...@kde.org wrote: I suggest that we: * introduce an official mirror for all KDE repositories on github * replace all existing (non-official) clones * disallow pull-requests on github to not replace our development model by a proprietary platform. Comments? +1 on mirroring. There is an ecosystem around github that I for one find rather useful for releaseme [1], where I use a bunch of stuff to conduct static analysis of the code and CI it. This is even more hadny considering releaseme is written in ruby, so if one wanted to do the same stuff on jenkins (which one could do) the sysadmins would have to maintain a ruby stack for one repo which isn't even a product in of itself. https://github.com/apachelogger/releaseme ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, Aug 17, 2015 at 7:05 PM, Bhushan Shah bhus...@gmail.com wrote: Hi, Thank you for starting this thread. On Mon, Aug 17, 2015 at 12:24 PM, Jos Poortvliet jospoortvl...@gmail.com wrote: On Monday 17 August 2015 07:46:44 Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories * people being surprised that our code is not on github * some projects starting to use github in addition to our own infrastructure In my opinion first two are too wrong arguments to begin with.. If our repositories can not be found from outside then it requires improvement from our side. Putting source code on Github is not going to solve this problem. Even if people will use github to search projects eventually they will have to use our infrastructure to contribute. And about people being surprised that our code is not on Github, it is really clear that Github is _not_ standard place to get open source software. I'd say the main benefit of Github is that it makes it easy for the many developers used to it to do a pull request - effectively widening our potential contributor base. Some might send in one or two minor pull requests, not being interested in becoming regular contributors, others might be convinced, after a few patches, to join KDE and then get on our infrastructure. On other side it will be hard project management wise to monitor two places for new patches/contributions.. and eventually people will start to report bugs or issues there and that is going to be mess.. It will be like someone fixes bug on our infrastructure just to realize in end that someone sent pull requests on github. Also there are some problems with Github that I am sure going to make our sysadmins life little bit harder, like email address verification and stuffs like that. We have seen this problems when importing code from the Github. So, In short IMO there is nothing wrong with having Github mirror but that should be read-only and we should have real reason to do it. Currently sysadmins are reworking our git infrastructure. So lets wait little bit and see how it goes and then think of this. Note that no mirror on Github would permit writes except from the canonical git.kde.org server. Otherwise it isn't a mirror - but an independent repository. If Pull Requests were to be left enabled (which would be opt-in per repository if we did it at all), the KDE developer(s) in question would have to fetch it from Github then push it to KDE Infrastructure to accept it. Thanks! Regards, Ben -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, Aug 17, 2015 at 7:43 PM, Boudewijn Rempt b...@valdyas.org wrote: On Mon, 17 Aug 2015, Jos van den Oever wrote: On Monday 17 August 2015 07:46:44 Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories Searching on ixquick: 'calligra git' https://community.kde.org/Calligra/Git 'kde git' https://community.kde.org/Sysadmin/GitKdeOrgManual 'kwin git' https://github.com/faho/kwin-tiling 'plasma git' https://community.kde.org/Plasma/Active/Development Searching on Google: 'calligra git' https://community.kde.org/Calligra/Building/2 'kde git' https://techbase.kde.org/Development/Git 'kwin git' http://blog.martin-graesslin.com/blog/2014/04/kwin-moved-to-an-own-repository/ 'plasma git' - https://aur.archlinux.org/packages/plasma-desktop-git/ Wow... krita git leads to https://www.kde.org/applications/graphics/krita/development Which I didn't even knew existed and wouldn't know how to update with the new icon, a better text, a link to the Cat's guide for building Krita from git. That's not so good :-( Our main website needs a huge overhaul, yes. Unfortunately a chunk of that text is highly templatized and thus fixed in concrete. That's a separate issue though :) On google the highest link to github was in position 4. Not too bad. There was no link to https://projects.kde.org/ or https://quickgit.kde.org/ What part of the KDE infrastructures can be fixed to make the repositories easier to find? * people being surprised that our code is not on github This is good moment to educate them on the ideals of KDE. People even get pissed that we're not on github, github is, after all the, Official Git Place. They don't trust a git repo that's not on github... Boudewijn Cheers, Ben ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday 17 August 2015 09:16:02 Martin Sandsmark wrote: On Mon, Aug 17, 2015 at 12:35:09PM +0530, Bhushan Shah wrote: In my opinion first two are too wrong arguments to begin with.. If our repositories can not be found from outside then it requires improvement from our side. Putting source code on Github is not going to solve this problem. I don't think improving discoverability of our own infrastructure and putting mirrors of our code on Github are mutually exclusive. I think both will improve our visibility so to speak. Even if people will use github to search projects eventually they will have to use our infrastructure to contribute. In my opinion all of our projects should have a short description about how and where to send us their patches, even if we don't push things to Github. If we ensure that our git repositories can be found via search engines people still need to know how to contribute. Agree. This is a good idea regardless of mirroring on GitHub. A mandatory preamble in the README.md for each KDE project could go something like this: == $name is a [KDE](https://www.kde.org/) project. The source code for $name can be found at [$git.kde.org/$name](https://$git.kde.org/$name). KDE welcomes you to [join KDE](https://community.kde.org/Get_Involved) and contribute to $name. You can report [issues and wishes]($git.kde.org/$name] (https://$git.kde.org/$name). img style=float: right; src=images/kdelogo.png alt=KDE logo/ == In this way, even if our repos are not completely indexed, the pagerank will increase a lot. And I think lowering the threshold for people to contribute in general is also something that should be done (and is being worked on already), and is a bit separate from this thing about mirroring stuff on Github. And about people being surprised that our code is not on Github, it is really clear that Github is _not_ standard place to get open source software. We might think so, but I don't think the rest of the world agrees. So, In short IMO there is nothing wrong with having Github mirror but that should be read-only and we should have real reason to do it. Currently sysadmins are reworking our git infrastructure. So lets wait little bit and see how it goes and then think of this. Yeah, I agree that the reworking of our own infrastructure should be prioritized, and we should disable the pull requests, bug reporting, etc. for everything we put on github. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Updating TechBase Getting_Started pages
On Monday, August 17, 2015 09:53:58 John Layt wrote: I've started to update the old TechBase Getting_Started pages for the new KF5 world [1]. My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4 3) There is only kdesrc-build, no manual messing around The three build scenarios (= new dev personas) that will be presented will be: 1) Build an app only using packaged Qt and KF5 2) Build Plasma only using packaged Qt and KF5 3) Build Frameworks using packaged Qt All the more detailed or historic information will be removed to other parts of TechBase [2]. New build instructions for external devs just wanting to use a Framework or two should also go here and not Getting_Started. This may result in some default build configs needing to be added to the kdesrc-build repo to make life easier. There may also need to be a couple of simple scripts to set-up kdesrc-build to start with, and to actually run things seeing as kdesrc-build doesn't. The less the new dev has to worry about the better. Thoughts? Is anyone else working on something similar? Yes. I'm giving the Plasma Mobile docs some love, but have discovered that also most of the other Plasma documentation for new developers is pretty disjoint and lacking. It certainly doesn't guide someone new well to becoming a productive contributor. I much welcome your initiative and want to pitch in. One of the pages I've written last week may serve as an example of what I have in mind for this kind of pages, it's directed at designers how want to contribute. It gives an overview of principles we use, tools, workflows and communication channels. https://community.kde.org/Plasma/Mobile/Design The following doc takes the point of view of a new developer or designer who would like to contribute, it has high-level starting points: https://community.kde.org/Plasma/Mobile/Contributing I think this documentation should probably not be specific to Plasma Mobile but generally should refer to Plasma or even more generic resources -- without losing level-of-detail. I think giving users a too generic guide can be off-putting for some. Thanks for getting this ball rolling. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
2015-08-17 3:55 GMT-03:00 Jos van den Oever j...@vandenoever.info: On Monday 17 August 2015 07:46:44 Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories Searching on ixquick: 'calligra git' https://community.kde.org/Calligra/Git 'kde git' https://community.kde.org/Sysadmin/GitKdeOrgManual 'kwin git' https://github.com/faho/kwin-tiling 'plasma git' https://community.kde.org/Plasma/Active/Development Searching on Google: 'calligra git' https://community.kde.org/Calligra/Building/2 'kde git' https://techbase.kde.org/Development/Git 'kwin git' http://blog.martin-graesslin.com/blog/2014/04/kwin-moved-to-an-own-repository/ 'plasma git' - https://aur.archlinux.org/packages/plasma-desktop-git/ On google the highest link to github was in position 4. Not too bad. There was no link to https://projects.kde.org/ or https://quickgit.kde.org/ What part of the KDE infrastructures can be fixed to make the repositories easier to find? http://quickgit.kde.org/robots.txt asks search engines not to index quickgit at all. http://projects.kde.org/robots.txt asks search engines not to index the repository, but the project information, news, etc. should be indexable. See https://www.google.com/search?q=site:projects.kde.org for stuff that does get indexed currently. Both of these blocks were done for server performance reasons: search engines wer crawling the hell out of dynamically-generated repository history and bringing our servers to their knees. -- Nicolás ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday, August 17, 2015 08:57:24 AM Martin Sandsmark wrote: Hi! Just to preface this a bit; I argued pretty vehemently against doing this some time ago on IRC (like, years ago I think), so I hate myself a bit for agreeing with you here. I know how you feel and I hate myself also for having written the mail in the first place :-( On Mon, Aug 17, 2015 at 07:46:44AM +0200, Martin Graesslin wrote: Whether we like it or not, github has become a place to look for free software nowadays and if you are not on github your software just doesn't exist. Given that we can say KDE doesn't produce source code because we are not on github. I still don't like the Github UI personally, and I think the behavior it encourages wrt. pull requests and whatnot is bad, but I agree with you that open source code (whether it is free software isn't important in this context) doesn't really exist for a growing amount of developers if it isn't on github. I guess you could say that Github is the biggest marketing platform for open source today. I suggest that we: * introduce an official mirror for all KDE repositories on github * replace all existing (non-official) clones * disallow pull-requests on github to not replace our development model by a proprietary platform. I agree with this, and fwiw for the last point I find the way pull requests are done on Github to be bad in general (for once I agree with Linux Torvalds). We also need to ensure that the README files for as many as possible of the projects we push to Github have a short but prominent notice about where and how people can send patches for review. As for some more practical aspects, I think it makes sense to contact this person and ask politely if we could have the name: https://github.com/kde signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
Hi! On Mon, Aug 17, 2015 at 08:55:57AM +0200, Jos van den Oever wrote: What part of the KDE infrastructures can be fixed to make the repositories easier to find? https://quickgit.kde.org/robots.txt https://projects.kde.org/robots.txt I think the reason for this should be pretty obvious; a ton of crawlers indexing everything we have is going to add an immense load, we have a huge amount of projects and source that they'll try to crawl now and then. And part of the reason for this (I think) is that both gitphp and chiliproject aren't the most performant. I don't remember the reason we run gitphp in the first place, but replacing it is not a trivial task in any way, and our sysadmins already have a ton of other work to do. Just guessing, but if we switch to e. g. cgit I think the load should be more realistic to handle (I run cgit on my own server, and it is extremely efficient). So, I think the answer to your question is a) fix or replace our web interface(s) for git, and b) remove the robots.txt. -- Martin Sandsmark ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On 17 August 2015 at 07:54, Jos Poortvliet jospoortvl...@gmail.com wrote: I'd say the main benefit of Github is that it makes it easy for the many developers used to it to do a pull request - effectively widening our potential contributor base. Some might send in one or two minor pull requests, not being interested in becoming regular contributors, others might be convinced, after a few patches, to join KDE and then get on our infrastructure. Why make people first join a mailing list and/or go through other hoops before we allow them to help make KDE better? Of course, you can leave it up to individual sub projects if they're interested in more contributions or not. I'll address this separately while I decide if the main topic is a good thing or not. Given how hard it is to just build a KDE app or Framework, and the efforts potential contributors have to go to just to get a working build, then I think making them go through the normal submission channels is the least of our worries. If they were by some miracle able to build something and create a patch, then it's really not much harder to create and upload a patch to Bugzilla or Reviewboard (we could script it). I'm hoping Phabricator solves this by allowing a push like Gerrit does? is so then even easier then... We need to solve the build problem first. John. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
Hi, Thank you for starting this thread. On Mon, Aug 17, 2015 at 12:24 PM, Jos Poortvliet jospoortvl...@gmail.com wrote: On Monday 17 August 2015 07:46:44 Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories * people being surprised that our code is not on github * some projects starting to use github in addition to our own infrastructure In my opinion first two are too wrong arguments to begin with.. If our repositories can not be found from outside then it requires improvement from our side. Putting source code on Github is not going to solve this problem. Even if people will use github to search projects eventually they will have to use our infrastructure to contribute. And about people being surprised that our code is not on Github, it is really clear that Github is _not_ standard place to get open source software. I'd say the main benefit of Github is that it makes it easy for the many developers used to it to do a pull request - effectively widening our potential contributor base. Some might send in one or two minor pull requests, not being interested in becoming regular contributors, others might be convinced, after a few patches, to join KDE and then get on our infrastructure. On other side it will be hard project management wise to monitor two places for new patches/contributions.. and eventually people will start to report bugs or issues there and that is going to be mess.. It will be like someone fixes bug on our infrastructure just to realize in end that someone sent pull requests on github. Also there are some problems with Github that I am sure going to make our sysadmins life little bit harder, like email address verification and stuffs like that. We have seen this problems when importing code from the Github. So, In short IMO there is nothing wrong with having Github mirror but that should be read-only and we should have real reason to do it. Currently sysadmins are reworking our git infrastructure. So lets wait little bit and see how it goes and then think of this. Thanks! -- Bhushan Shah http://bhush9.github.io IRC Nick : bshah on Freenode ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday, August 17, 2015 08:55:57 AM Jos van den Oever wrote: On Monday 17 August 2015 07:46:44 Martin Graesslin wrote: Hi community, over the last months I observed the following: * people not finding our git repositories Searching on ixquick: 'calligra git' https://community.kde.org/Calligra/Git 'kde git' https://community.kde.org/Sysadmin/GitKdeOrgManual 'kwin git' https://github.com/faho/kwin-tiling 'plasma git' https://community.kde.org/Plasma/Active/Development Searching on Google: 'calligra git' https://community.kde.org/Calligra/Building/2 'kde git' https://techbase.kde.org/Development/Git 'kwin git' http://blog.martin-graesslin.com/blog/2014/04/kwin-moved-to-an-own-reposito ry/ 'plasma git' - https://aur.archlinux.org/packages/plasma-desktop-git/ On google the highest link to github was in position 4. Not too bad. There was no link to https://projects.kde.org/ or https://quickgit.kde.org/ What part of the KDE infrastructures can be fixed to make the repositories easier to find? * people being surprised that our code is not on github This is good moment to educate them on the ideals of KDE. Yes certainly, I start with lecturing a potential new contributor /sarcasm No, I say sorry that our code is so difficult to find. * some projects starting to use github in addition to our own infrastructure We have a manifesto that disallows this. Yes we have. Do you want to enforce it in this point and kick out projects which just won the akademy award, because they are interested in more contributors? The manifesto is there to guide us, but it's not put in stone to not allow to change to reality. Whether we like it or not, github has become a place to look for free software nowadays and if you are not on github your software just doesn't exist. Given that we can say KDE doesn't produce source code because we are not on github. And Android has become the only phone OS. Windows the only PC os. Microsoft Office is the only office suite. Google is the only search engine. Chrome is the only browser. Facebook is the only way for communicating with other humans (even if they are in view). And in all cases we integrate with those examples: * we have software for Android * we have software for Microsoft Windows * We have google as default search engine * We used to have a bridge to Facebook chat system So apparently we do integrate with proprietary services without losing our identity. So I fail to see your point here. Other projects have an official mirror (see e.g. [1]) which solves the three points I have listed above. I suggest that we: * introduce an official mirror for all KDE repositories on github * replace all existing (non-official) clones * disallow pull-requests on github to not replace our development model by a proprietary platform. Comments? GitHub might be over the top of its popularity. If KDE moves to GitHub, we will make our hits in search engines point to GitHub more often. I am not suggesting to moving to github. I'm suggesting to setup an official mirror. I've started using GitLab for repositories that I have to collaborate on with non-KDE people. The reason for this is that GitLab allows moving to servers that are under my control. There are other GitHub alternative coming up such as Gogs. The point why I wrote the mail is that people expect things to be on github. All these alternatives are great but miss the one point: they are not github. And for what is worth: let's also get official mirrors on those infrastructure. If KDE mirrors to GitHub but not to the alternatives, KDE is giving GitHub an advantage over the open competition. yes, let's do that, too. If KDE mirrors to GitHub, it should keep a policy of never linking to GitHub. The route from GitHub to KDE should be only one direction. In practice people will start pointing to GitHub instead of fully agree, though it might be difficult in practice. E.g. if we have this setup I would do a post that KWin is now on github and link it. So maybe just in official documentation. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
* Jos van den Oever j...@vandenoever.info [2015-08-17 09:51:02 +0200]: On Monday 17 August 2015 09:43:04 Boudewijn Rempt wrote: People even get pissed that we're not on github, github is, after all the, Official Git Place. They don't trust a git repo that's not on github... In real life, I very often have to correct people who conflate git and github. Github was very successful in hijacking git. That's a big achievement, but having one big player is not healthy for the ecosystem and its inhabitants. The network effect is the big enabler here. GitHub, just like Facebook, Windows, and more recently WhatsApp, grew because people felt they could not avoid it. (I left out political examples ;-) Just my 2cents. Github is not in the same game as Windows from a political standpoint. Like the other apps/systems you mentioned, Github shares the simplicity, the ease of use. It's very easy to have a Github account, then simply fork that repo if something bothers you. You fix it for you, then eventually make the pull request. No fancy workflows or overengineered processes here. That's key to public adoption. That's the opposite of politics ;-) -- Valentin Rusu IRC: valir ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Monday, August 17, 2015 10:10:17 AM Jos van den Oever wrote: On Monday 17 August 2015 09:16:02 Martin Sandsmark wrote: On Mon, Aug 17, 2015 at 12:35:09PM +0530, Bhushan Shah wrote: In my opinion first two are too wrong arguments to begin with.. If our repositories can not be found from outside then it requires improvement from our side. Putting source code on Github is not going to solve this problem. I don't think improving discoverability of our own infrastructure and putting mirrors of our code on Github are mutually exclusive. I think both will improve our visibility so to speak. Even if people will use github to search projects eventually they will have to use our infrastructure to contribute. In my opinion all of our projects should have a short description about how and where to send us their patches, even if we don't push things to Github. If we ensure that our git repositories can be found via search engines people still need to know how to contribute. Agree. This is a good idea regardless of mirroring on GitHub. A mandatory preamble in the README.md for each KDE project could go something like this: == $name is a [KDE](https://www.kde.org/) project. The source code for $name can be found at [$git.kde.org/$name](https://$git.kde.org/$name). KDE welcomes you to [join KDE](https://community.kde.org/Get_Involved) and contribute to $name. You can report [issues and wishes]($git.kde.org/$name] (https://$git.kde.org/$name). img style=float: right; src=images/kdelogo.png alt=KDE logo/ == In this way, even if our repos are not completely indexed, the pagerank will increase a lot. and is also something we could actually install with the software. And I think lowering the threshold for people to contribute in general is also something that should be done (and is being worked on already), and is a bit separate from this thing about mirroring stuff on Github. And about people being surprised that our code is not on Github, it is really clear that Github is _not_ standard place to get open source software. We might think so, but I don't think the rest of the world agrees. So, In short IMO there is nothing wrong with having Github mirror but that should be read-only and we should have real reason to do it. Currently sysadmins are reworking our git infrastructure. So lets wait little bit and see how it goes and then think of this. Yeah, I agree that the reworking of our own infrastructure should be prioritized, and we should disable the pull requests, bug reporting, etc. for everything we put on github. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Mon, 17 Aug 2015, Jos van den Oever wrote: On Monday 17 August 2015 09:43:04 Boudewijn Rempt wrote: People even get pissed that we're not on github, github is, after all the, Official Git Place. They don't trust a git repo that's not on github... In real life, I very often have to correct people who conflate git and github. Github was very successful in hijacking git. That's a big achievement, but having one big player is not healthy for the ecosystem and its inhabitants. That's exactly what I meant. Boudewijn ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
