Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
Hi Michael, If you are interested in having the incubation happen, please get in touch. I'll be glad to help. Aleix On Wed, Jan 17, 2018 at 9:40 PM, Michael Reeveswrote: > Yes I use this myself so I won't simply abandon it. That said I work in > mostly in Unix world and could use help with the windows specific testing > although I should be able to setup a build envirionment to do basic > functionality testing. I'll have look at what needs done. Currently working > on getting merging in changes from Thomas as needed. Just got through > bringing it up to date with Joachim's code. Real fun since it's still kde4. > > > On Jan 15, 2018 5:47 PM, "Albert Astals Cid" wrote: > > El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va > escriure: >> I have a version of kdiff3 that I ported to kf5. I like to what build >> requirements kf5 as a whole has. Also what would be the process for being >> considered for inclusion in kde? > > So now that we have Joachim's blessing to use the name, the process is > basically outlined at https://community.kde.org/Incubator/Incubation_Process > but it's basically importing the project into our git and then making sure > it > generally follows our rules & procedures. > > I understand you want to continue maintaining the new kdiff3 and you are not > just "dumping it" into us, right? > > > Cheers, > Albert > > El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va > escriure: >> Hi, > >> You have my blessing to use the name KDiff3. > >
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
A little confused on where to start with this sponsor thing. On Jan 19, 2018 3:52 PM, "Kevin Funk"wrote: > On Wednesday, 17 January 2018 21:40:49 CET Michael Reeves wrote: > > Yes I use this myself so I won't simply abandon it. That said I work in > > mostly in Unix world and could use help with the windows specific testing > > although I should be able to setup a build envirionment to do basic > > functionality testing. > > Heya, > > For that please join #kde-windows and get in touch with kfunk (me) or > TheOneRing (Hannah von Reth) there. > > We could guide setting up the development environment. > > We use Craft to build Qt/KDE projects on Windows, read more here: > https://community.kde.org/Craft > > Cheers, > Kevin > > > I'll have look at what needs done. Currently working > > on getting merging in changes from Thomas as needed. Just got through > > bringing it up to date with Joachim's code. Real fun since it's still > kde4. > > > > On Jan 15, 2018 5:47 PM, "Albert Astals Cid" wrote: > > > > El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va > > > > escriure: > > > I have a version of kdiff3 that I ported to kf5. I like to what build > > > requirements kf5 as a whole has. Also what would be the process for > being > > > considered for inclusion in kde? > > > > So now that we have Joachim's blessing to use the name, the process is > > basically outlined at https://community.kde.org/ > Incubator/Incubation_Process > > but it's basically importing the project into our git and then making > sure > > it > > generally follows our rules & procedures. > > > > I understand you want to continue maintaining the new kdiff3 and you are > not > > just "dumping it" into us, right? > > > > > > Cheers, > > Albert > > > > El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va > > > > escriure: > > > Hi, > > > > > > You have my blessing to use the name KDiff3. > > > -- > Kevin Funk | kf...@kde.org | http://kfunk.org
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
On Wednesday, January 24, 2018 6:08:03 PM EST Albert Astals Cid wrote: > El dimecres, 24 de gener de 2018, a les 17:34:16 CET, Kevin Funk va escriure: > > On Wednesday, 24 January 2018 16:24:10 CET Michael Reeves wrote: > > > A little confused on where to start with this sponsor thing. > > > > Huh? 'sponsor thing'? :) > > I guess it's regarding the > https://community.kde.org/Incubator/Incubation_Process > > Which to my understanding was supposed to be a voluntary thing but it seems > some people are forcing it on every single new project. The amounts of "must" and "can't" on the page make it seem very non-voluntary. And like Kevin and Kevin, I have thought that this was *not* voluntary. Same time, the states can be described as "provides absolutely minimal information needed to be a project", "communicates well with one person, the sponsor", "participates in the KDE community", "dead". Those are not a lot of bureaucracy (well, there is mention of a "committee", which I don't see defined anywhere). The role of the sponsor described in the process is quite an active one: there's a number of steps to be taken, and communication to be handled. Probably not more than a few hours across several weeks, but it needs watching over. [ade] signature.asc Description: This is a digitally signed message part.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
On Friday, 26 January 2018 08:27:55 CET Kevin Ottens wrote: > Hello, > > On Thursday, 25 January 2018 22:35:37 CET Albert Astals Cid wrote: > > El dijous, 25 de gener de 2018, a les 9:01:10 CET, Kevin Ottens va escriure: > > > On Thursday, 25 January 2018 00:08:03 CET Albert Astals Cid wrote: > > > > As I did with the last person that also was confused and annoyed by > > > > all > > > > this burocracy, just ask me any question you may have. > > > > > > Oh come on... the bad mean bureaucracy argument now. Wanna look at the > > > Eclipse incubation process? Or the Apache one? > > > > Can I use the "if all your friends jump from a balcony will you do it" > > defense? > > Not really since my point was more that what we have in place is very very > far from bureaucracy not that we should replicate other's bureaucracy. If > you want an example of bureaucracy look at those friends who jump from a > balcony. ;-) > > > Seriously it's just about having a person already within the community > > > making sure the new project needs get catered to and also making sure > > > the > > > new project is on the right path to put in place rules and procedures > > > compatible with the rest of the community (and the Manifesto). > > > > But how do you find that person? You're just an 'outsider', how do you > > find > > a random person to be your incubator guy? Because as it happens, it's the > > second time in a month or something that i have to volunteer. > > Ah! That is interesting feedback. You're correct that we're currently > assuming that someone will step in to do that and that there's enough of us > and that we're responsible enough to do that when we see something we're > interested in. > > Personally for kdiff3, I'd have expected Kevin Funk to end up doing it, > indeed he was first responder with "I'd love to see kdiff3 being adopted by > KDE again". To me he sounded like a perfect sponsor. Heya, Sorry that wasn't clear from my mail. Several reasons I'd be rather not do it: I'm reaaally lacking time and focus to go through the whole process at this point; and adding to that I'm not familiar with the incubation process myself either... I just expressed that I'd love to see it happen, in general. Somehow. :) Regards, Kevin > I'd like to see that fixed. Right now, I'm not sure how, but if you're the > only one indeed caring about new projects getting in, we have a more general > community problem, it's just that the incubator makes it visible... > > I think it's much easier if we had guidelines and the rest was just "ask > > in > > kde-devel mailing list if you have further questions", > > It'd be easier, but not better. Because then it's no different than "ask the > GitHub support if you have further questions", and it's not what it's > about. > > In my previous email I mentioned this is *also* for the "sponsor" to touch > base with the joining project to verify it's getting into fruition to *be* a > KDE project (which is not just about having a repository on our > infrastructure)... I know, pesky people and culture thing. > > > and sure if you find a dedicated person for you, great, but requiring it > > feels weird, and also makes it for less scalability, as an example I > > already have an email from Michael that was sent only to me but anyone > > else in this list would have been able to answer, but he had to wait at > > least 14 hours for me to have time to answer it. > > Maybe that needs to be made clearer in the wiki? I'd expect the sponsor to > push the involved persons to ask these type of questions on public mailing > lists indeed. One on one discussions are likely to happen but they must be > the minority of the communication going on. The sponsor in that case is the > fail safe mechanism to make sure an answer indeed happens in those public > forums or trying to solve the case if no answer happened for some reason. > > Regards. -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
Hello, On Thursday, 25 January 2018 22:35:37 CET Albert Astals Cid wrote: > El dijous, 25 de gener de 2018, a les 9:01:10 CET, Kevin Ottens va escriure: > > On Thursday, 25 January 2018 00:08:03 CET Albert Astals Cid wrote: > > > As I did with the last person that also was confused and annoyed by all > > > this burocracy, just ask me any question you may have. > > > > Oh come on... the bad mean bureaucracy argument now. Wanna look at the > > Eclipse incubation process? Or the Apache one? > > Can I use the "if all your friends jump from a balcony will you do it" > defense? Not really since my point was more that what we have in place is very very far from bureaucracy not that we should replicate other's bureaucracy. If you want an example of bureaucracy look at those friends who jump from a balcony. ;-) > > Seriously it's just about having a person already within the community > > making sure the new project needs get catered to and also making sure the > > new project is on the right path to put in place rules and procedures > > compatible with the rest of the community (and the Manifesto). > > But how do you find that person? You're just an 'outsider', how do you find > a random person to be your incubator guy? Because as it happens, it's the > second time in a month or something that i have to volunteer. Ah! That is interesting feedback. You're correct that we're currently assuming that someone will step in to do that and that there's enough of us and that we're responsible enough to do that when we see something we're interested in. Personally for kdiff3, I'd have expected Kevin Funk to end up doing it, indeed he was first responder with "I'd love to see kdiff3 being adopted by KDE again". To me he sounded like a perfect sponsor. I'd like to see that fixed. Right now, I'm not sure how, but if you're the only one indeed caring about new projects getting in, we have a more general community problem, it's just that the incubator makes it visible... > I think it's much easier if we had guidelines and the rest was just "ask in > kde-devel mailing list if you have further questions", It'd be easier, but not better. Because then it's no different than "ask the GitHub support if you have further questions", and it's not what it's about. In my previous email I mentioned this is *also* for the "sponsor" to touch base with the joining project to verify it's getting into fruition to *be* a KDE project (which is not just about having a repository on our infrastructure)... I know, pesky people and culture thing. > and sure if you find a dedicated person for you, great, but requiring it > feels weird, and also makes it for less scalability, as an example I already > have an email from Michael that was sent only to me but anyone else in this > list would have been able to answer, but he had to wait at least 14 hours > for me to have time to answer it. Maybe that needs to be made clearer in the wiki? I'd expect the sponsor to push the involved persons to ask these type of questions on public mailing lists indeed. One on one discussions are likely to happen but they must be the minority of the communication going on. The sponsor in that case is the fail safe mechanism to make sure an answer indeed happens in those public forums or trying to solve the case if no answer happened for some reason. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
El dijous, 25 de gener de 2018, a les 9:01:10 CET, Kevin Ottens va escriure: > Hello, > > On Thursday, 25 January 2018 00:08:03 CET Albert Astals Cid wrote: > > El dimecres, 24 de gener de 2018, a les 17:34:16 CET, Kevin Funk va > > escriure: > > > On Wednesday, 24 January 2018 16:24:10 CET Michael Reeves wrote: > > > > A little confused on where to start with this sponsor thing. > > > > > > Huh? 'sponsor thing'? :) > > > > I guess it's regarding the > > https://community.kde.org/Incubator/Incubation_Process > > > > Which to my understanding was supposed to be a voluntary thing but it > > seems > > some people are forcing it on every single new project. > > Was supposed to be for any project born outside the community and joining > in. So not quite so voluntary. Ok, that's not really how i understood it, but fair enough. > > > As I did with the last person that also was confused and annoyed by all > > this burocracy, just ask me any question you may have. > > Oh come on... the bad mean bureaucracy argument now. Wanna look at the > Eclipse incubation process? Or the Apache one? Can I use the "if all your friends jump from a balcony will you do it" defense? > Seriously it's just about having a person already within the community > making sure the new project needs get catered to and also making sure the > new project is on the right path to put in place rules and procedures > compatible with the rest of the community (and the Manifesto). But how do you find that person? You're just an 'outsider', how do you find a random person to be your incubator guy? Because as it happens, it's the second time in a month or something that i have to volunteer. I think it's much easier if we had guidelines and the rest was just "ask in kde-devel mailing list if you have further questions", and sure if you find a dedicated person for you, great, but requiring it feels weird, and also makes it for less scalability, as an example I already have an email from Michael that was sent only to me but anyone else in this list would have been able to answer, but he had to wait at least 14 hours for me to have time to answer it. Cheers, Albert > Call it bureaucracy if you wish, but I think it's good to avoid people > dropping code in a corner to then be ignored by everyone and wondering what > to do next. > > Regards.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
Hello, On Thursday, 25 January 2018 00:08:03 CET Albert Astals Cid wrote: > El dimecres, 24 de gener de 2018, a les 17:34:16 CET, Kevin Funk va escriure: > > On Wednesday, 24 January 2018 16:24:10 CET Michael Reeves wrote: > > > A little confused on where to start with this sponsor thing. > > > > Huh? 'sponsor thing'? :) > > I guess it's regarding the > https://community.kde.org/Incubator/Incubation_Process > > Which to my understanding was supposed to be a voluntary thing but it seems > some people are forcing it on every single new project. Was supposed to be for any project born outside the community and joining in. So not quite so voluntary. > As I did with the last person that also was confused and annoyed by all this > burocracy, just ask me any question you may have. Oh come on... the bad mean bureaucracy argument now. Wanna look at the Eclipse incubation process? Or the Apache one? Seriously it's just about having a person already within the community making sure the new project needs get catered to and also making sure the new project is on the right path to put in place rules and procedures compatible with the rest of the community (and the Manifesto). Call it bureaucracy if you wish, but I think it's good to avoid people dropping code in a corner to then be ignored by everyone and wondering what to do next. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
El dimecres, 24 de gener de 2018, a les 17:34:16 CET, Kevin Funk va escriure: > On Wednesday, 24 January 2018 16:24:10 CET Michael Reeves wrote: > > A little confused on where to start with this sponsor thing. > > Huh? 'sponsor thing'? :) > I guess it's regarding the https://community.kde.org/Incubator/Incubation_Process Which to my understanding was supposed to be a voluntary thing but it seems some people are forcing it on every single new project. As I did with the last person that also was confused and annoyed by all this burocracy, just ask me any question you may have. Cheers, Albert > Care to elaborate what you mean? > > Regards, > Kevin > > > On Jan 19, 2018 3:52 PM, "Kevin Funk"wrote: > > > On Wednesday, 17 January 2018 21:40:49 CET Michael Reeves wrote: > > > > Yes I use this myself so I won't simply abandon it. That said I work > > > > in > > > > mostly in Unix world and could use help with the windows specific > > > > testing > > > > although I should be able to setup a build envirionment to do basic > > > > functionality testing. > > > > > > Heya, > > > > > > For that please join #kde-windows and get in touch with kfunk (me) or > > > TheOneRing (Hannah von Reth) there. > > > > > > We could guide setting up the development environment. > > > > > > We use Craft to build Qt/KDE projects on Windows, read more here: > > > https://community.kde.org/Craft > > > > > > Cheers, > > > Kevin > > > > > > > I'll have look at what needs done. Currently working > > > > on getting merging in changes from Thomas as needed. Just got through > > > > bringing it up to date with Joachim's code. Real fun since it's still > > > > > > kde4. > > > > > > > On Jan 15, 2018 5:47 PM, "Albert Astals Cid" wrote: > > > > > > > > El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va > > > > > > > > escriure: > > > > > I have a version of kdiff3 that I ported to kf5. I like to what > > > > > build > > > > > requirements kf5 as a whole has. Also what would be the process for > > > > > > being > > > > > > > > considered for inclusion in kde? > > > > > > > > So now that we have Joachim's blessing to use the name, the process is > > > > basically outlined at https://community.kde.org/ > > > > > > Incubator/Incubation_Process > > > > > > > but it's basically importing the project into our git and then making > > > > > > sure > > > > > > > it > > > > generally follows our rules & procedures. > > > > > > > > I understand you want to continue maintaining the new kdiff3 and you > > > > are > > > > > > not > > > > > > > just "dumping it" into us, right? > > > > > > > > > > > > Cheers, > > > > > > > > Albert > > > > > > > > El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va > > > > > > > > escriure: > > > > > Hi, > > > > > > > > > > You have my blessing to use the name KDiff3. > > > > > > -- > > > Kevin Funk | kf...@kde.org | http://kfunk.org
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
On Wednesday, 24 January 2018 16:24:10 CET Michael Reeves wrote: > A little confused on where to start with this sponsor thing. Huh? 'sponsor thing'? :) Care to elaborate what you mean? Regards, Kevin > On Jan 19, 2018 3:52 PM, "Kevin Funk"wrote: > > On Wednesday, 17 January 2018 21:40:49 CET Michael Reeves wrote: > > > Yes I use this myself so I won't simply abandon it. That said I work in > > > mostly in Unix world and could use help with the windows specific > > > testing > > > although I should be able to setup a build envirionment to do basic > > > functionality testing. > > > > Heya, > > > > For that please join #kde-windows and get in touch with kfunk (me) or > > TheOneRing (Hannah von Reth) there. > > > > We could guide setting up the development environment. > > > > We use Craft to build Qt/KDE projects on Windows, read more here: > > https://community.kde.org/Craft > > > > Cheers, > > Kevin > > > > > I'll have look at what needs done. Currently working > > > on getting merging in changes from Thomas as needed. Just got through > > > bringing it up to date with Joachim's code. Real fun since it's still > > > > kde4. > > > > > On Jan 15, 2018 5:47 PM, "Albert Astals Cid" wrote: > > > > > > El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va > > > > > > escriure: > > > > I have a version of kdiff3 that I ported to kf5. I like to what build > > > > requirements kf5 as a whole has. Also what would be the process for > > > > being > > > > > > considered for inclusion in kde? > > > > > > So now that we have Joachim's blessing to use the name, the process is > > > basically outlined at https://community.kde.org/ > > > > Incubator/Incubation_Process > > > > > but it's basically importing the project into our git and then making > > > > sure > > > > > it > > > generally follows our rules & procedures. > > > > > > I understand you want to continue maintaining the new kdiff3 and you are > > > > not > > > > > just "dumping it" into us, right? > > > > > > > > > Cheers, > > > > > > Albert > > > > > > El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va > > > > > > escriure: > > > > Hi, > > > > > > > > You have my blessing to use the name KDiff3. > > > > -- > > Kevin Funk | kf...@kde.org | http://kfunk.org -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
On Wednesday, 17 January 2018 21:40:49 CET Michael Reeves wrote: > Yes I use this myself so I won't simply abandon it. That said I work in > mostly in Unix world and could use help with the windows specific testing > although I should be able to setup a build envirionment to do basic > functionality testing. Heya, For that please join #kde-windows and get in touch with kfunk (me) or TheOneRing (Hannah von Reth) there. We could guide setting up the development environment. We use Craft to build Qt/KDE projects on Windows, read more here: https://community.kde.org/Craft Cheers, Kevin > I'll have look at what needs done. Currently working > on getting merging in changes from Thomas as needed. Just got through > bringing it up to date with Joachim's code. Real fun since it's still kde4. > > On Jan 15, 2018 5:47 PM, "Albert Astals Cid"wrote: > > El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va > > escriure: > > I have a version of kdiff3 that I ported to kf5. I like to what build > > requirements kf5 as a whole has. Also what would be the process for being > > considered for inclusion in kde? > > So now that we have Joachim's blessing to use the name, the process is > basically outlined at https://community.kde.org/Incubator/Incubation_Process > but it's basically importing the project into our git and then making sure > it > generally follows our rules & procedures. > > I understand you want to continue maintaining the new kdiff3 and you are not > just "dumping it" into us, right? > > > Cheers, > Albert > > El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va > > escriure: > > Hi, > > > > You have my blessing to use the name KDiff3. -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
Yes I use this myself so I won't simply abandon it. That said I work in mostly in Unix world and could use help with the windows specific testing although I should be able to setup a build envirionment to do basic functionality testing. I'll have look at what needs done. Currently working on getting merging in changes from Thomas as needed. Just got through bringing it up to date with Joachim's code. Real fun since it's still kde4. On Jan 15, 2018 5:47 PM, "Albert Astals Cid"wrote: El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va escriure: > I have a version of kdiff3 that I ported to kf5. I like to what build > requirements kf5 as a whole has. Also what would be the process for being > considered for inclusion in kde? So now that we have Joachim's blessing to use the name, the process is basically outlined at https://community.kde.org/Incubator/Incubation_Process but it's basically importing the project into our git and then making sure it generally follows our rules & procedures. I understand you want to continue maintaining the new kdiff3 and you are not just "dumping it" into us, right? Cheers, Albert El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va escriure: > Hi, > You have my blessing to use the name KDiff3.
Importing kdiff3 - was - Re: Aw: Re: KDE inclusion
El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va escriure: > I have a version of kdiff3 that I ported to kf5. I like to what build > requirements kf5 as a whole has. Also what would be the process for being > considered for inclusion in kde? So now that we have Joachim's blessing to use the name, the process is basically outlined at https://community.kde.org/Incubator/Incubation_Process but it's basically importing the project into our git and then making sure it generally follows our rules & procedures. I understand you want to continue maintaining the new kdiff3 and you are not just "dumping it" into us, right? Cheers, Albert El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va escriure: > Hi, > You have my blessing to use the name KDiff3.