Re: [kde-community] Renaming KScreenGenie

Selfie is better than Kapture for sure.. :) On Saturday, September 19, 2015 08:38:41 PM Eike Hein wrote: > On 09/19/2015 08:32 PM, Rajeev Bhatta wrote: > > If we can choose the name Selfie and then it is important to have the > > users > > relate to it as a product too then it works, if we cannot

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 19 September 2015 at 21:08, Eike Hein wrote: > > > On 09/19/2015 08:58 PM, Kevin Krammer wrote: >> Even using a review tool in the first place is something that the maintainer >> asks people to do. > > No. We advertise ReviewBoard (and later Phab) as a general > interface to

Re: [kde-community] Help for sprint guidance/organization

Hey, so I haven't really organized any sprints myself but have participated in many, some good, some less good. So here's my personal take on this speaking from experience: * always make everyone feel like they belong to the group and to the sprint * if it's a random group that have never met

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 09/19/2015 08:58 PM, Kevin Krammer wrote: > Even using a review tool in the first place is something that the maintainer > asks people to do. No. We advertise ReviewBoard (and later Phab) as a general interface to throw code at our maintainers. "I don't look at ReviewBoard" is not a

Re: [kde-community] What is a GitHub pull request exactly?

On 09/19/2015 08:43 PM, Kevin Krammer wrote: > Well, the github side review will make the job of the KDE contributor who > brings the patch into KDE a lot easier, because when they put the patch up > for > review as "their" contribution, most of the things that the contributor knew > about

Re: [kde-community] Renaming KScreenGenie

You made me giggle with that : On Sat, Sep 19, 2015 at 3:16 PM, Eike Hein wrote: > > > On 09/19/2015 11:36 AM, rajeev bhatta wrote: >> Like the name selfie..but it will be nightmare finding the app in google >> if looking for selfie > > No it won't. People aren't too dumb to add an

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, 2015-09-19, 20:56:31, Eike Hein wrote: > On 09/19/2015 08:43 PM, Kevin Krammer wrote: > > Well, the github side review will make the job of the KDE contributor who > > brings the patch into KDE a lot easier, because when they put the patch up > > for review as "their" contribution,

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 19 September 2015 at 21:24, Ivan Čukić wrote: >> Could you mention at least one KDE git repo that belongs to multiple > > Eike already mentioned that Plasma has a single repo in which > different parts are maintained by different people. But is Plasma a single project or

Re: [kde-community] What is a GitHub pull request exactly?

On 09/19/2015 09:55 PM, Kevin Krammer wrote: > Exactly. > So why would one continue to do the prelimiary review in addition to the > required one? > As soon as there is a stream of patches from a new contributor, that > contributor will be asked to get an account of their own. > Need for

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 09/19/2015 09:13 PM, Jaroslaw Staniek wrote: > Could you mention at least one KDE git repo that belongs to multiple > projects? And thus maybe multiple even multiple groups of maintainers? I have previously in the thread: Different subfolders in plasma-desktop.git have different maintainers,

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, 2015-09-19, 20:32:43, Eike Hein wrote: > On 09/19/2015 08:25 PM, Kevin Krammer wrote: > > Saying "I don't look at the KDE review tool" would be like saying "I am > > not > > interested in your patch". > > Saying "My personal productivity and efficiency matters more > to me in the

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, 2015-09-19, 21:08:27, Eike Hein wrote: > On 09/19/2015 08:58 PM, Kevin Krammer wrote: > > Even using a review tool in the first place is something that the > > maintainer asks people to do. > > No. We advertise ReviewBoard (and later Phab) as a general > interface to throw code at

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, 2015-09-19, 22:11:10, Eike Hein wrote: > On 09/19/2015 09:55 PM, Kevin Krammer wrote: > > Exactly. > > So why would one continue to do the prelimiary review in addition to the > > required one? > > As soon as there is a stream of patches from a new contributor, that > > contributor

Re: [kde-community] What is a GitHub pull request exactly?

On 19 September 2015 at 23:06, Eike Hein wrote: > > > On 09/19/2015 10:32 PM, Kevin Krammer wrote: >> I don't see there this github review is coming from. > > Review is an interactive process where you ask for changes and > iterate. Once you open the door to doing it on GitHub, you

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, 2015-09-19, 20:20:56, Eike Hein wrote: > On 09/19/2015 08:13 PM, Kevin Krammer wrote: > > I am afraid my understanding of the technical background of this is still > > too hazy. > > How would review "move" from KDE to github? > > If review on reviewboard is required (per project's

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 09/19/2015 09:36 PM, Kevin Krammer wrote: > So, right now, a maintainer is expected to check reviewboard even if they are > content with all holders of commit accounts to push directly. > But that as soon as there is a second option, then not checking reviewboard > becomes acceptable?

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 2015-09-19, Kevin Krammer wrote: >> No, I'm afraid of code review slowly moving from KDE to github up to = > the >> final point where I need to get a github account because otherwise I = > cannot >> contribute code. > > You mean that a KDE project would ignore your review

Re: [kde-community] Write our own pull request bot?

Hi Martin, On Sat, Sep 19, 2015 at 6:49 PM, Martin Klapetek wrote: > On Sat, Sep 19, 2015 at 1:42 PM, Laszlo Papp wrote: >> >> >> Sure, but why would increase this situation further on? > > > Sorry, I don't understand this question. I missed the

Re: [kde-community] Write our own pull request bot?

On Sat, Sep 19, 2015 at 1:55 PM, Eike Hein wrote: > On 09/19/2015 07:49 PM, Martin Klapetek wrote: > > We wouldn't get no lock-in though. Not even remotely. It will simply > > be another path for an incoming patch. If the patch in question ends > > up on Phabricator and gets

Re: [kde-community] What is a GitHub pull request exactly?

On 09/19/2015 08:13 PM, Kevin Krammer wrote: > I am afraid my understanding of the technical background of this is still too > hazy. > How would review "move" from KDE to github? > If review on reviewboard is required (per project's unwritten social > contract), it cannot not happen. > If it

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, 2015-09-19, 19:58:26, Eike Hein wrote: > On 09/19/2015 07:52 PM, Kevin Krammer wrote: > > You mean that a KDE project would ignore your review request it it comes > > from reviewboard/phabricator? > > I think that's a realistic, even likely concern. We already > know that some devs

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 09/19/2015 08:25 PM, Kevin Krammer wrote: > Saying "I don't look at the KDE review tool" would be like saying "I am not > interested in your patch". Saying "My personal productivity and efficiency matters more to me in the long-run than your patch, so please use the tool I prefer to reach

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 1:12 PM, Martin Graesslin wrote: > On Friday, September 18, 2015 5:29:01 PM CEST Albert Vaca wrote: > > From my experience, I was already mirroring KDE Connect in Github and > I've > > received valuable patches there. That's a big enough reason for me

Re: [kde-community] Official KDE mirror on github

On Saturday, 19 September 2015, Albert Astals Cid wrote: > El Divendres, 18 de setembre de 2015, a les 23:42:02, Jaroslaw Staniek va > escriure: >> >> Your experience may differ and I value that. Opt-in - nobody forces you. > > It does, once person X submits a patch using github to

Re: [kde-community] Official KDE mirror on github

On Saturday, 19 September 2015, Martin Graesslin wrote: > On Friday, September 18, 2015 5:29:01 PM CEST Albert Vaca wrote: >> From my experience, I was already mirroring KDE Connect in Github and I've >> received valuable patches there. That's a big enough reason for me to

Re: [kde-community] Official KDE mirror on github

On Saturday, September 19, 2015 10:25:05 AM CEST Jaroslaw Staniek wrote: > On Saturday, 19 September 2015, Shantanu Tushar Jha > > wrote: > > On Sat, Sep 19, 2015 at 1:12 PM, Martin Graesslin > > wrote: > >> On Friday, September 18, 2015 5:29:01 PM CEST

Re: [kde-community] Official KDE mirror on github

On 2015-09-19, Jaroslaw Staniek wrote: > > Sounds like a bit superficial premature complain. If only we had a flood of > pull requests... It is not premature to complain! I personally feel a bit fucked over right now. All this started with a KDE github mirror and *just a

Re: [kde-community] Official KDE mirror on github

On Sat, 19 Sep 2015, Sune Vuorela wrote: On 2015-09-19, Jaroslaw Staniek wrote: Sounds like a bit superficial premature complain. If only we had a flood of pull requests... It is not premature to complain! I personally feel a bit fucked over right now. All this started

Re: [kde-community] Official KDE mirror on github

> All this started with a KDE github mirror and *just a mirror*. > No pull requests. No bugtracker. +100 Although I don't like the idea of what I'm about to say, here it goes. If you want to have a project that has issue tracking and pull requests on github - just create personal clone (just

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 12:09 PM, Ivan Čukić wrote: > alternatives. Just as they do not have access to my personal inbox >> where much corresponse often happens, and patches are discussed. > > Not sure that this is a statement you want to advertise, since it > implies that the

Re: [kde-community] Official KDE mirror on github

Am Samstag, 19. September 2015, 11:53:22 CEST schrieb Vishesh Handa: > > So, if _you_ accept pull requests to a repo in the KDE official mirror, > > you > > are making decisions for others, and are making other people do things. > > No I'm not. > > Boud, you're shipping Krita on Windows. You're

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Sat, Sep 19, 2015 at 2:12 PM, Myriam Schweingruber wrote: > Wow, over 150 mails over that whole Github stuff, I am amazed. > > Let me chime in to give you a non-developer perspective: Caveat: some > strong language ahead, but please take all this with a grain of salt > :) > >

Re: [kde-community] Official KDE mirror on github

On Sat, 19 Sep 2015, Vishesh Handa wrote: On Sat, Sep 19, 2015 at 11:13 AM, Boudewijn Rempt wrote: On Sat, 19 Sep 2015, Vishesh Handa wrote: So if project X which is part of KDE also relies on GitHub, but in no way recommends it, that will alienate people? That's not

Re: [kde-community] Official KDE mirror on github

Il 19 settembre 2015 12:00:11 CEST, Vishesh Handa ha scritto: > On Sat, Sep 19, 2015 at 11:44 AM, Luca Beltrame > wrote: > > > > And besides... hasn't the BitKeeper story taught us *anything*? > > > > I don't know about you guys, but it has taught me that we

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 1:04 PM, Martin Steigerwald wrote: >> > So, if _you_ accept pull requests to a repo in the KDE official mirror, >> > you >> > are making decisions for others, and are making other people do things. >> >> No I'm not. >> >> Boud, you're shipping Krita on

Re: [kde-community] Have repo maintainers opt-in for github mirroring (was: Re: Official KDE mirror on github)

> > > > I was under the impression they were disabled by the options we had > > selected. Unfortunately that is not the case. > > Thanks for clarifying on this. > > I hope they can still be disabled. > > They can't. I had spent some time looking before. Sorry. However, we have solid hard data

Re: [kde-community] Official KDE mirror on github

Am Samstag, 19. September 2015, 02:22:44 CEST schrieb Riccardo Iaconelli: > On Friday, September 18, 2015 11:43:34 PM Vishesh Handa wrote: > > It depends on our end goal: creating free software or creating free > > software with only free tools? If it is the latter then I fear we have > > already

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 5:23 AM, Michael Pyne wrote: > The end result of that type of thought is something like what happened with > BitKeeper. > > I'm not going to say it's impossible to use proprietary tools without having > that type of drama occur, but I think it would be

Re: [kde-community] Renaming KScreenGenie

I personally agree with Luigi that the name should not be a generic name, specifically to not get multiple confusing results in search engines. Like the name selfie..but it will be nightmare finding the app in google if looking for selfie Thanks Sent from Yahoo Mail on Android From:"Luigi

Re: [kde-community] Official KDE mirror on github

Am Samstag, 19. September 2015, 11:20:32 CEST schrieb Vishesh Handa: > * Reporting Bugs in 2 places - The default place should still > bugs.kde.org for now. For bug triaging KDEPIM I will ignore anything but the official KDE infrastructure. I know bugzilla is not the most friendly to use bug

Re: [kde-community] Official KDE mirror on github

Am Samstag, 19. September 2015, 11:53:22 CEST schrieb Vishesh Handa: > > If _you_ want to use an official KDE thing to promote the use of non-free > > software, you're not just "selling your own soul", you're compromising > > KDE's message. > > I'm not promoting its usage. I'm advocating for

Re: [kde-community] Official KDE mirror on github

Am Samstag, 19. September 2015, 13:09:31 CEST schrieb Vishesh Handa: > On Sat, Sep 19, 2015 at 1:04 PM, Martin Steigerwald wrote: […] > > So you can argue for github.com: But its opt-in and only for some repos? > > How do you make sure it doesn´t create pressure and

Re: [kde-community] Official KDE mirror on github

On Friday 18 September 2015 23:28:37 Vishesh Handa wrote: > In general, I'm quite alarmed by how people are advocating their > principles for ALL kde projects without any scope for negotiations for > different projects. I fear that this will just drive people/projects > away from KDE. from this

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 9:46 AM, Shantanu Tushar Jha wrote: > +1 to that. And adding to it, IMO the most important thing here is > consistency. The last thing we want to have is newcomers getting confused > "erm, so for this KDE project do I use reviewboard? or do I create a

Re: [kde-community] Official KDE mirror on github

On Sat, 19 Sep 2015, Vishesh Handa wrote: So if project X which is part of KDE also relies on GitHub, but in no way recommends it, that will alienate people? That's not the issue: the issue is having our official Github mirror allowing a git-hub based workflow. That should not be possible.

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 2:06 PM, Sune Vuorela wrote: > I personally feel a bit fucked over right now. All this started with a > KDE github mirror and *just a mirror*. No pull requests. No bugtracker. > No nothing else. Just a mirror. And it was repeatedly said in the thread >

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 11:44 AM, Luca Beltrame wrote: > Il Sat, 19 Sep 2015 11:30:39 +0200, Vishesh Handa ha scritto: > > >> * There is nothing to do with selling your soul. Each of us has > > We have a Manifesto, and we should, ideally, strive to respect it. The manifesto is

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 12:17 PM, Laszlo Papp wrote: >> No I'm not. >> >> Boud, you're shipping Krita on Windows. You're uploading them on the >> KDE official website, you're thereby making me pay for Windows if I >> want to test it and contribute to the project, you are making >>

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 12:57 PM, Martin Steigerwald wrote: > How is "I'm advocating for utilizing its resources in addition to our own" not > advocating GitHub? > > My logical thought process does not get that Sorry. Perhaps the wording was not correct. I'm not advocating

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 3:33 PM, Boudhayan Gupta wrote: > Hi all, > > This discussion is becoming nothing but a royal waste of time. > > Let me summarise: > > 1. We generally agreed before starting that this was going to be a > read-only mirror. > > 2. For consistency's sake, we

Re: [kde-community] Have repo maintainers opt-in for github mirroring (was: Re: Official KDE mirror on github)

On Saturday, September 19, 2015 13:04:55 David Edmundson wrote: > > > I was under the impression they were disabled by the options we had > > > selected. Unfortunately that is not the case. > > > > Thanks for clarifying on this. > > > > I hope they can still be disabled. > > > > They can't. I

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 09/19/2015 02:12 PM, Myriam Schweingruber wrote: > Some of you wanted the mirror on Github because apparently there are > developers out there who are too lazy (or too dumb) to learn to use > new tools. Are those developers we want? Developer recruitment should be our #1 problem for the next

Re: [kde-community] Official KDE mirror on github

On Saturday, 2015-09-19, 16:26:04, Luigi Toscano wrote: > Kevin Krammer ha scritto: > > On Saturday, 2015-09-19, 12:29:31, Vishesh Handa wrote: > >> On Sat, Sep 19, 2015 at 12:09 PM, Ivan Čukić wrote: > >>> alternatives. Just as they do not have access to my personal inbox >

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Sat, September 19, 2015 16:24:13 Eike Hein wrote: > On 09/19/2015 02:12 PM, Myriam Schweingruber wrote: > > Some of you wanted the mirror on Github because apparently there are > > developers out there who are too lazy (or too dumb) to learn to use > > new tools. Are those developers we want? >

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, September 19, 2015 04:24:13 PM Eike Hein wrote: > Developer recruitment should be our #1 problem for the > next two years, and along those lines "GitHub might get > us contributors" is by far the strongest argument that > side's come up with. Somebody once defined Github as the

Re: [kde-community] Have repo maintainers opt-in for github mirroring

On Saturday, September 19, 2015 16:25:13 Luigi Toscano wrote: > Teo Mrnjavac ha scritto: > > It is also a fact that KDE is an aging community, and in its future I > > expect a slow decline unless we find a way to bring in a steady influx of > > new contributors. Recruiting a new generation of

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 19 September 2015 at 20:28, Michael Pyne wrote: > My personal feeling is that opting to go the actual-development-on-Github > route would simply introduce a schism in development workflow, despite the > best intentions of any party. And if you think *these* threads are filled

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 4:37 PM, Boudhayan Gupta wrote: > On 19 September 2015 at 19:34, Vishesh Handa wrote: >> Please note that consistency isn't a requirement to be part of KDE. If >> I decide to write an application in Rust, which is only for Windows, >> and

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, 2015-09-19, 17:19:16, Riccardo Iaconelli wrote: > On Saturday, September 19, 2015 10:58:09 AM Michael Pyne wrote: > > Is anyone actually arguing this point in the way you ask? No one's asking > > to prevent "one offs" entirely, the core of the issue is that KDE > > development should

Re: [kde-community] Official KDE mirror on github

On 09/19/2015 11:35 AM, Vishesh Handa wrote: > Then we will deal with them on a case-by-case basis. Lets not take > blanket bans on new ideas just because of their potential destructive > power. Each action of ours has positive and negative benefits. How > about we focus on the positive? You're

Re: [kde-community] Official KDE mirror on github

Hi all, This discussion is becoming nothing but a royal waste of time. Let me summarise: 1. We generally agreed before starting that this was going to be a read-only mirror. 2. For consistency's sake, we cannot enable issues/pull requests for only some repos and disable for others. 3. Basing

Re: [kde-community] Official KDE mirror on github

Kevin Krammer ha scritto: > On Saturday, 2015-09-19, 12:29:31, Vishesh Handa wrote: >> On Sat, Sep 19, 2015 at 12:09 PM, Ivan Čukić wrote: >>> alternatives. Just as they do not have access to my personal inbox >>> where much corresponse often happens, and patches are

Re: [kde-community] Official KDE mirror on github

Its sad that this got completely ignored by the members of this discussion, the argument is very valid. On Sat, Sep 19, 2015 at 3:47 PM, Luigi Toscano wrote: > Il 19 settembre 2015 12:00:11 CEST, Vishesh Handa ha > scritto: > > On Sat, Sep 19, 2015 at

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Sat, September 19, 2015 16:42:54 Riccardo Iaconelli wrote: > If somebody happened to send me some material for WikiToLearn through the > Facebook page (it has happened), I don't reject it asking him/her to resend > it to the mailing list, because that would never work. I accept the > material,

[kde-community] What is a GitHub pull request exactly?

I have some difficulty understanding the perceived difference in workflow, so I'd like to get some input on where my line of thinking and reality differ :-) The following example deals with clones of a repository and the revision of HEAD in the master branch. Example: akonadiclient, three

Re: [kde-community] Official KDE mirror on github

Just leaving that here, though borderline off-topic and I am not really qualified, If the issue is the (granted, a bit outdated) Bugzilla/Reviewboard/Quickgit toolset not being user-friendly enough, why not have a look at the libre github clone GitLab instead? That could be hosted on KDE servers

Re: [kde-community] Have repo maintainers opt-in for github mirroring (was: Re: Official KDE mirror on github)

El Dissabte, 19 de setembre de 2015, a les 16:23:26, Teo Mrnjavac va escriure: > On Saturday, September 19, 2015 13:04:55 David Edmundson wrote: > > > > I was under the impression they were disabled by the options we had > > > > selected. Unfortunately that is not the case. > > > > > > Thanks for

Re: [kde-community] Official KDE mirror on github

On Sat, Sep 19, 2015 at 8:07 PM, Boudhayan Gupta wrote: > On 19 September 2015 at 19:34, Vishesh Handa wrote: > > Please note that consistency isn't a requirement to be part of KDE. If > > I decide to write an application in Rust, which is only for Windows, > >

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, September 19, 2015 10:58:09 AM Michael Pyne wrote: > Is anyone actually arguing this point in the way you ask? No one's asking > to prevent "one offs" entirely, the core of the issue is that KDE > development should happen *within* KDE-the-whole-community, not *apart > from* KDE.

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, September 19, 2015 5:19:16 PM CEST Riccardo Iaconelli wrote: > On Saturday, September 19, 2015 10:58:09 AM Michael Pyne wrote: > > Is anyone actually arguing this point in the way you ask? No one's asking > > to prevent "one offs" entirely, the core of the issue is that KDE > >

Re: [kde-community] Official KDE mirror on github

On Saturday, September 19, 2015 04:26:04 PM Luigi Toscano wrote: > But that's not using the pull request. Such workflow would mean that the > pull request is not accepted anyway, but the code is pushed through the > infrastructure and not trough Github interface. > > Just to be sure, question for

Re: [kde-community] Write our own pull request bot?

To further expand on the idea, the workflow would be as follows: * bot looks through our repos * bot finds a pull request * bot downloads the diff between requested branch and mirror HEAD * bot uploads it to phabricator as any other patch * bot posts message to github "Thanks for your patch, in

Re: [kde-community] Write our own pull request bot?

On 2015-09-19, Martin Klapetek wrote: > To further expand on the idea, the workflow would be as follows: > > * bot looks through our repos > * bot finds a pull request > * bot downloads the diff between requested branch and mirror HEAD > * bot uploads it to phabricator

Re: [kde-community] Official KDE mirror on github

On 19 September 2015 at 17:36, Riccardo Iaconelli wrote: > On Saturday, September 19, 2015 04:26:04 PM Luigi Toscano wrote: >> But that's not using the pull request. Such workflow would mean that the >> pull request is not accepted anyway, but the code is pushed through the >>

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, 2015-09-19, 12:06:18, Michael Pyne wrote: > On Sat, September 19, 2015 17:32:33 Kevin Krammer wrote: > > So (a) and (b) workflows differ in that in (a) github mirror and > > git.kde.org have the same state, while in (b) the mirror is for a period > > of time not actually a mirror, but

Re: [kde-community] Write our own pull request bot?

On Saturday, September 19, 2015 01:17:18 PM Martin Klapetek wrote: > To further expand on the idea, the workflow would be as follows: > > * bot looks through our repos > * bot finds a pull request > * bot downloads the diff between requested branch and mirror HEAD > * bot uploads it to

Re: [kde-community] Renaming KScreenGenie

People are not dumb.. especially those already familiar with KDE and linux... however in my opinion we need to think of newbies too. I search apps on google all the time, some time in youtube to see a demo of it.. Searching for selfie will result in all the smartphones, all the different

Re: [kde-community] Write our own pull request bot?

On Sat, Sep 19, 2015 at 1:28 PM, Sune Vuorela wrote: > > What happens if contributor doesn't follows? How do I as a reviewer know > why the contributor doesn't follow on? How can I reach them? > > No. let's just say no to pull requests. > Same thing as when someone emails you

Re: [kde-community] Renaming KScreenGenie

On 09/19/2015 07:32 PM, techie.raj...@yahoo.in wrote: > I search apps on google all the time, some time in youtube to see a demo of > it.. Searching for selfie will result in all the smartphones, all the > different > selfie related stuff which is currently viral among the masses. Yeah. And

Re: [kde-community] Write our own pull request bot?

On Sat, Sep 19, 2015 at 6:37 PM, Martin Klapetek wrote: > On Sat, Sep 19, 2015 at 1:28 PM, Sune Vuorela wrote: >> >> >> What happens if contributor doesn't follows? How do I as a reviewer know >> why the contributor doesn't follow on? How can I reach

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On 09/19/2015 07:52 PM, Kevin Krammer wrote: > You mean that a KDE project would ignore your review request it it comes from > reviewboard/phabricator? I think that's a realistic, even likely concern. We already know that some devs don't like using multiple code review sites concurrently from

Re: [kde-community] What is a GitHub pull request exactly?

On 09/19/2015 10:32 PM, Kevin Krammer wrote: > I don't see there this github review is coming from. Review is an interactive process where you ask for changes and iterate. Once you open the door to doing it on GitHub, you will: * Have a hard time making some contributors understand why they

Re: [kde-community] What is a GitHub pull request exactly?

On Sat, Sep 19, 2015 at 5:32 PM, Kevin Krammer wrote: > Where "ahead" could also mean wrong if "klmn" needs to be modified or gets > rejected. > > Is (b) the problem people keep discussing about? > > Because as far as I can tell it is not really an option given that it can lead >

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > If the problem is somewhere in (a), where is it? I'm afraid of code review happening through the pull request instead of our infrastructure. To me github pull requests are not just the "here's the patch", but also the code

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Sat, Sep 19, 2015 at 5:53 PM, Martin Graesslin wrote: > My fear here is that if we allow pull request, people will also start to use > them for code review at which point we have split the development team in > those doing code review through reviewboard and those through

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, September 19, 2015 5:57:09 PM CEST Eike Hein wrote: > On 09/19/2015 05:54 PM, Riccardo Iaconelli wrote: > > while rejecting them autmatically isjust a great way to drive potential > > contributors away... > > Which is a good reason why the mirror shouldn't have happened > - regret

Re: [kde-community] What is a GitHub pull request exactly?

On Sat, September 19, 2015 17:32:33 Kevin Krammer wrote: > So (a) and (b) workflows differ in that in (a) github mirror and git.kde.org > have the same state, while in (b) the mirror is for a period of time not > actually a mirror, but "ahead". > > Where "ahead" could also mean wrong if "klmn"

Re: [kde-community] Official KDE mirror on github: code searching facility

Am Samstag, 19. September 2015, 21:15:41 CEST schrieb Boudhayan Gupta: > On 19 September 2015 at 20:52, Vishesh Handa wrote: […] > > I think we're talking about different things. The read-only mirror is > > done, and shipped. I was talking about projects being able to also use > >

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Sat, Sep 19, 2015 at 6:04 PM, Martin Graesslin wrote: >> * Google+ Hangouts (Just discussed some things related to the Baloo >> KCM a week ago) > closed Martin. There are weekly Plasma meetings on Google+! Those are as essential as code review. They control the direction

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 05:47:38 PM Martin Graesslin wrote: > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > > If the problem is somewhere in (a), where is it? > > I'm afraid of code review happening through the pull request instead of our > infrastructure. To me

[kde-community] Help for sprint guidance/organization

Hi all, (hoping to break the thousands of emails currently being written...) we're having our first sprint at WikiToLearn!!! It's an exciting news since most of the participants are absolutely newcomers to FOSS development (let alone to KDE), and to various degrees to WikiToLearn too. The

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 6:11:21 PM CEST you wrote: > On Saturday, September 19, 2015 05:47:38 PM Martin Graesslin wrote: > > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > > > If the problem is somewhere in (a), where is it? > > > > I'm afraid of code review

Re: [kde-community] What is a GitHub pull request exactly?

On Sat, Sep 19, 2015 at 12:07 PM, Boudhayan Gupta wrote: > On 19 September 2015 at 21:17, Martin Graesslin > wrote: > > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > >> If the problem is somewhere in (a), where is it? > > > > I'm

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 12:26:34 PM CEST Martin Klapetek wrote: > On Sat, Sep 19, 2015 at 12:07 PM, Boudhayan Gupta wrote: > > On 19 September 2015 at 21:17, Martin Graesslin > > > > wrote: > > > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin

Re: [kde-community] What is a GitHub pull request exactly?

On 09/19/2015 06:22 PM, Martin Graesslin wrote: > And how do we do that? Can we enforce this technically or will that be > weakened over the time the same way as we just turned the mirror into "let's > accept pull requests"? This wishy-washy stuff is nonsense. The sole argument for enabling

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Saturday, 2015-09-19, 17:53:17, Martin Graesslin wrote: > On Saturday, September 19, 2015 5:46:07 PM CEST Kevin Krammer wrote: > > The patch would still go through review at KDE. Even with no github at all > > a patch could have been through several revisions before being submitted. > > The

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, 2015-09-19, 17:47:38, Martin Graesslin wrote: > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > > If the problem is somewhere in (a), where is it? > > I'm afraid of code review happening through the pull request instead of our > infrastructure. To me github

Re: [kde-community] What is a GitHub pull request exactly?

On Sat, Sep 19, 2015 at 6:37 PM, Martin Graesslin wrote: > What's important to realize: the people have already written the patch at the > point. Some time ago I wrote a patch for a software I hadn't contributed for > before: figuring out how to submit the patch was more way

Re: [kde-community] What is a GitHub pull request exactly?

On Saturday, September 19, 2015 6:40:47 PM CEST Kevin Krammer wrote: > On Saturday, 2015-09-19, 17:47:38, Martin Graesslin wrote: > > On Saturday, September 19, 2015 5:32:33 PM CEST Kevin Krammer wrote: > > > If the problem is somewhere in (a), where is it? > > > > I'm afraid of code review

Re: [kde-community] Bikeshedding - our strength apparently *sigh*

On Sat, Sep 19, 2015 at 6:24 PM, Eike Hein wrote: > > I expect you'll ignore this as much as my other mail, but > all of these are ephemeral in nature instead of offering > a persistent record -- that's why we submit minutes of the > Hangouts to the plasma-devel mailing list, for

  1   2   >