Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion

[Aleix Pol]

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 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. 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

[Michael Reeves]

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

[Adriaan de Groot]

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

[Kevin Funk]

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

[Kevin Ottens]

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

[Albert Astals Cid]

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

[Kevin Ottens]

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

[Albert Astals Cid]

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

[Kevin Funk]

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

[Kevin Funk]

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

[Michael Reeves]

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

[Albert Astals Cid]

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: Aw: Re: KDE inclusion

[Michael Reeves]

Just a not in the at vs. kde. The ported to hf5/qt5 eliminated some of the
code differences between the two. I removed to if defs as obsolete. A third
I replaced with a platform check for Windows as there seems no other need
for it now. I don't have a preference on this.

On Jan 15, 2018 3:09 AM, "Valentin Rusu"  wrote:

* Joachim Eibl  [2018-01-12 01:21:02 +0100]:

> I had a try at it myself, but was quite overwhelmed about the big
changes in KF5.
>
> 
>
> You have my blessing to use the name KDiff3.
>

Great news for a very useful tool! After having ported it to KDE4, I was
also overwhelmed by the changes for KF5. Today I'm unfortunately forced
to use the Qt version. Perhaps we should stick with that version and
simply have it hosted and maintained as a KDE extragear project.

--
Valentin Rusu
IRC: valir

Re: Aw: Re: KDE inclusion

[Albert Astals Cid]

El diumenge, 14 de gener de 2018, a les 12:10:07 CET, Valentin Rusu va 
escriure:
> * Joachim Eibl  [2018-01-12 01:21:02 +0100]:
> > I had a try at it myself, but was quite overwhelmed about the big
> > changes in KF5.
> > 
> > 
> > 
> > You have my blessing to use the name KDiff3.
> 
> Great news for a very useful tool! After having ported it to KDE4, I was
> also overwhelmed by the changes for KF5. Today I'm unfortunately forced
> to use the Qt version. Perhaps we should stick with that version and
> simply have it hosted and maintained as a KDE extragear project.

Or maybe we should do what the person that did the work thinks its a better 
idea :)

Cheers,
  Albert

Re: Aw: Re: KDE inclusion

[Valentin Rusu]

* Joachim Eibl  [2018-01-12 01:21:02 +0100]:

> I had a try at it myself, but was quite overwhelmed about the big 
> changes in KF5.
> 
> 
> 
> You have my blessing to use the name KDiff3.
> 

Great news for a very useful tool! After having ported it to KDE4, I was
also overwhelmed by the changes for KF5. Today I'm unfortunately forced
to use the Qt version. Perhaps we should stick with that version and
simply have it hosted and maintained as a KDE extragear project.

-- 
Valentin Rusu
IRC: valir

Re: KDE inclusion

[Luigi Toscano]

Michael Reeves ha scritto:
> Sorry meant this to go to everyone.
> 
> I did this based off what Ubuntu was using at the time.  The repo is here
> https://bitbucket.org/reporter123/kdiff3
> . Master is currently set the
> require CMake 3.1 but as of this moment that is just a number change. My
> concern here was C++11 feature dectect which is not implemented in earlier
> versions. Right now that is not critical. I was not aware of the parallel
> effort at https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5
> . Command
> line parsing is fully operational on mine. To my knowledge it is fully
> operational and I have been using it on my machine. I generally work with two
> way comparisons.

Adding explicitly Thomas (I don't remember if he reads this list).

Thomas, some context below or better on:
https://marc.info/?t=15156672876=1=2

> 
> On Thu, Jan 11, 2018 at 6:24 PM, Albert Astals Cid  > wrote:
> 
> El dijous, 11 de gener de 2018, a les 12:15:15 CET, Kevin Funk va 
> escriure:
> > On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
> > > 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?
> >
> > Heya,
> >
> > Note: kdiff3 right now is hosted & developed on SourceForge.
> >
> > I'd love to see kdiff3 being adopted by KDE again (it former was KDE
> > extragear if I understood correctly). kdiff3 is a super useful tool -- 
> and
> > right now development has stalled a bit.
> >
> > Talked to Joachim (the original author) a few weeks ago, where he 
> stated he
> > just doesn't have the time maintaining it anymore, really. I've CC'd 
> Joachim
> > so he can tell us whether he's okay with having kdiff3 developed further
> > under the KDE umbrella.
> 
> I guess this is the most important question, if we can keep using the 
> kdiff3
> name under's Joachim's blessing or we have to "fork it" and find a new 
> name.
> 
> Cheers,
>   Albert
> 
> >
> > I don't really know the process of having it integrated either. I'll 
> leave
> > that to others.
> >
> > Kudos for doing the KF5 port!
> >
> > Regards,
> > Kevin
> 

-- 
Luigi

Re: Re: KDE inclusion

[Michael Reeves]

Looks the original is a somewhat modified version of be348bcf1. It doesn't
have some of the windows specific code. Also kreplacements was not always
patched when updating code. I'm working on getting it updated with changes
Joachim has made.

On Fri, Jan 12, 2018 at 12:21 AM, Joachim Eibl <joachim.e...@gmx.de> wrote:

> Hi,
>
> It's great to hear there is some ongoing effort to port KDiff3 to KF5.
> Thanks for informing me.
> I had a try at it myself, but was quite overwhelmed about the big changes
> in KF5.
>
> You have my blessing to use the name KDiff3.
>
> @Michael: It seems the repo at https://bitbucket.org/reporter123/kdiff3
> has no public access.
>
> Kudos,
> Joachim
>
>
> *Gesendet:* Donnerstag, 11. Januar 2018 um 22:28 Uhr
> *Von:* "Michael Reeves" <reeves...@gmail.com>
> *An:* "Albert Astals Cid" <aa...@kde.org>
> *Cc:* kde-core-devel@kde.org, "Joachim Eibl" <joachim.e...@gmx.de>
> *Betreff:* Re: KDE inclusion
> Sorry meant this to go to everyone.
>
> I did this based off what Ubuntu was using at the time.  The repo is here
> https://bitbucket.org/reporter123/kdiff3. Master is currently set the
> require CMake 3.1 but as of this moment that is just a number change. My
> concern here was C++11 feature dectect which is not implemented in earlier
> versions. Right now that is not critical. I was not aware of the parallel
> effort at https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5.
> Command line parsing is fully operational on mine. To my knowledge it is
> fully operational and I have been using it on my machine. I generally work
> with two way comparisons.
>
> On Thu, Jan 11, 2018 at 6:24 PM, Albert Astals Cid <aa...@kde.org> wrote:
>>
>> El dijous, 11 de gener de 2018, a les 12:15:15 CET, Kevin Funk va
>> escriure:
>> > On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
>> > > 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?
>> >
>> > Heya,
>> >
>> > Note: kdiff3 right now is hosted & developed on SourceForge.
>> >
>> > I'd love to see kdiff3 being adopted by KDE again (it former was KDE
>> > extragear if I understood correctly). kdiff3 is a super useful tool --
>> and
>> > right now development has stalled a bit.
>> >
>> > Talked to Joachim (the original author) a few weeks ago, where he
>> stated he
>> > just doesn't have the time maintaining it anymore, really. I've CC'd
>> Joachim
>> > so he can tell us whether he's okay with having kdiff3 developed further
>> > under the KDE umbrella.
>>
>> I guess this is the most important question, if we can keep using the
>> kdiff3
>> name under's Joachim's blessing or we have to "fork it" and find a new
>> name.
>>
>> Cheers,
>>   Albert
>>
>> >
>> > I don't really know the process of having it integrated either. I'll
>> leave
>> > that to others.
>> >
>> > Kudos for doing the KF5 port!
>> >
>> > Regards,
>> > Kevin
>>
>>
>>
>

Aw: Re: KDE inclusion

[Joachim Eibl]

Hi,

 

It's great to hear there is some ongoing effort to port KDiff3 to KF5.

Thanks for informing me.

I had a try at it myself, but was quite overwhelmed about the big changes in KF5.

 

You have my blessing to use the name KDiff3.

 

@Michael: It seems the repo at https://bitbucket.org/reporter123/kdiff3

has no public access.

 

Kudos,

Joachim

 

 

Gesendet: Donnerstag, 11. Januar 2018 um 22:28 Uhr
Von: "Michael Reeves" <reeves...@gmail.com>
An: "Albert Astals Cid" <aa...@kde.org>
Cc: kde-core-devel@kde.org, "Joachim Eibl" <joachim.e...@gmx.de>
Betreff: Re: KDE inclusion


Sorry meant this to go to everyone.

I did this based off what Ubuntu was using at the time.  The repo is here https://bitbucket.org/reporter123/kdiff3. Master is currently set the require CMake 3.1 but as of this moment that is just a number change. My concern here was C++11 feature dectect which is not implemented in earlier versions. Right now that is not critical. I was not aware of the parallel effort at https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5. Command line parsing is fully operational on mine. To my knowledge it is fully operational and I have been using it on my machine. I generally work with two way comparisons.


 
On Thu, Jan 11, 2018 at 6:24 PM, Albert Astals Cid <aa...@kde.org> wrote:

El dijous, 11 de gener de 2018, a les 12:15:15 CET, Kevin Funk va escriure:
> On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
> > 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?
>
> Heya,
>
> Note: kdiff3 right now is hosted & developed on SourceForge.
>
> I'd love to see kdiff3 being adopted by KDE again (it former was KDE
> extragear if I understood correctly). kdiff3 is a super useful tool -- and
> right now development has stalled a bit.
>
> Talked to Joachim (the original author) a few weeks ago, where he stated he
> just doesn't have the time maintaining it anymore, really. I've CC'd Joachim
> so he can tell us whether he's okay with having kdiff3 developed further
> under the KDE umbrella.

I guess this is the most important question, if we can keep using the kdiff3
name under's Joachim's blessing or we have to "fork it" and find a new name.

Cheers,
  Albert


>
> I don't really know the process of having it integrated either. I'll leave
> that to others.
>
> Kudos for doing the KF5 port!
>
> Regards,
> Kevin

 

Re: KDE inclusion

[Michael Reeves]

Sorry meant this to go to everyone.

I did this based off what Ubuntu was using at the time.  The repo is here
https://bitbucket.org/reporter123/kdiff3. Master is currently set the
require CMake 3.1 but as of this moment that is just a number change. My
concern here was C++11 feature dectect which is not implemented in earlier
versions. Right now that is not critical. I was not aware of the parallel
effort at https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5.
Command line parsing is fully operational on mine. To my knowledge it is
fully operational and I have been using it on my machine. I generally work
with two way comparisons.

On Thu, Jan 11, 2018 at 6:24 PM, Albert Astals Cid  wrote:

> El dijous, 11 de gener de 2018, a les 12:15:15 CET, Kevin Funk va escriure:
> > On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
> > > 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?
> >
> > Heya,
> >
> > Note: kdiff3 right now is hosted & developed on SourceForge.
> >
> > I'd love to see kdiff3 being adopted by KDE again (it former was KDE
> > extragear if I understood correctly). kdiff3 is a super useful tool --
> and
> > right now development has stalled a bit.
> >
> > Talked to Joachim (the original author) a few weeks ago, where he stated
> he
> > just doesn't have the time maintaining it anymore, really. I've CC'd
> Joachim
> > so he can tell us whether he's okay with having kdiff3 developed further
> > under the KDE umbrella.
>
> I guess this is the most important question, if we can keep using the
> kdiff3
> name under's Joachim's blessing or we have to "fork it" and find a new
> name.
>
> Cheers,
>   Albert
>
> >
> > I don't really know the process of having it integrated either. I'll
> leave
> > that to others.
> >
> > Kudos for doing the KF5 port!
> >
> > Regards,
> > Kevin
>
>
>

Re: KDE inclusion

[Albert Astals Cid]

El dijous, 11 de gener de 2018, a les 12:15:15 CET, Kevin Funk va escriure:
> On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
> > 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?
> 
> Heya,
> 
> Note: kdiff3 right now is hosted & developed on SourceForge.
> 
> I'd love to see kdiff3 being adopted by KDE again (it former was KDE
> extragear if I understood correctly). kdiff3 is a super useful tool -- and
> right now development has stalled a bit.
> 
> Talked to Joachim (the original author) a few weeks ago, where he stated he
> just doesn't have the time maintaining it anymore, really. I've CC'd Joachim
> so he can tell us whether he's okay with having kdiff3 developed further
> under the KDE umbrella.

I guess this is the most important question, if we can keep using the kdiff3 
name under's Joachim's blessing or we have to "fork it" and find a new name.

Cheers,
  Albert

> 
> I don't really know the process of having it integrated either. I'll leave
> that to others.
> 
> Kudos for doing the KF5 port!
> 
> Regards,
> Kevin

Re: KDE inclusion

[Burkhard Lück]

Am Donnerstag, 11. Januar 2018, 12:22:49 CET schrieb Luigi Toscano:
> Kevin Funk ha scritto:
> > On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
> >> 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?
> > 
> > Heya,
> > 
> > Note: kdiff3 right now is hosted & developed on SourceForge.
> 
> The official one, yes, but see below.
> 
> > I'd love to see kdiff3 being adopted by KDE again (it former was KDE
> > extragear if I understood correctly). kdiff3 is a super useful tool --
> > and right now development has stalled a bit.
> > 
> > Talked to Joachim (the original author) a few weeks ago, where he stated
> > he
> > just doesn't have the time maintaining it anymore, really. I've CC'd
> > Joachim so he can tell us whether he's okay with having kdiff3 developed
> > further under the KDE umbrella.
> > 
> > I don't really know the process of having it integrated either. I'll leave
> > that to others.
> 
> We also have this:
> https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5
> (see https://t-fischer.dreamwidth.org/4327.html)
> 
And scripty also tracks this one:
https://websvn.kde.org/trunk/extragear/utils/kdiff3/

-- 
Burkhard Lück

Re: KDE inclusion

[Luigi Toscano]

Kevin Funk ha scritto:
> On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
>> 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?
> 
> Heya,
> 
> Note: kdiff3 right now is hosted & developed on SourceForge.

The official one, yes, but see below.

> 
> I'd love to see kdiff3 being adopted by KDE again (it former was KDE 
> extragear 
> if I understood correctly). kdiff3 is a super useful tool -- and right now 
> development has stalled a bit.
> 
> Talked to Joachim (the original author) a few weeks ago, where he stated he 
> just doesn't have the time maintaining it anymore, really. I've CC'd Joachim 
> so he can tell us whether he's okay with having kdiff3 developed further 
> under 
> the KDE umbrella.
> 
> I don't really know the process of having it integrated either. I'll leave 
> that to others.

We also have this:
https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5
(see https://t-fischer.dreamwidth.org/4327.html)

Does this new port continues the one on kde.org?

Ciao
-- 
Luigi

Re: KDE inclusion

[Kevin Funk]

On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:
> 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?

Heya,

Note: kdiff3 right now is hosted & developed on SourceForge.

I'd love to see kdiff3 being adopted by KDE again (it former was KDE extragear 
if I understood correctly). kdiff3 is a super useful tool -- and right now 
development has stalled a bit.

Talked to Joachim (the original author) a few weeks ago, where he stated he 
just doesn't have the time maintaining it anymore, really. I've CC'd Joachim 
so he can tell us whether he's okay with having kdiff3 developed further under 
the KDE umbrella.

I don't really know the process of having it integrated either. I'll leave 
that to others.

Kudos for doing the KF5 port!

Regards,
Kevin


-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.

KDE inclusion

[Michael Reeves]

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?