KDE inclusion

Post by 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?

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 | ***@kde.org | http://kfunk.org

Luigi Toscano

2018-01-11 11:22:49 UTC

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

The official one, yes, but see below.

Post by Kevin Funk
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

Burkhard Lück

2018-01-11 13:07:01 UTC

Post by Luigi Toscano

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

The official one, yes, but see below.

Post by Kevin Funk
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.

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

Albert Astals Cid

2018-01-11 18:24:37 UTC

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

Post by Kevin Funk
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

Michael Reeves

2018-01-11 21:28:11 UTC

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.

Post by 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

Post by Michael Reeves
considered for inclusion in kde?

and

Post by Kevin Funk
right now development has stalled a bit.
Talked to Joachim (the original author) a few weeks ago, where he stated

Post by Kevin Funk
just doesn't have the time maintaining it anymore, really. I've CC'd

Joachim

Post by Kevin Funk
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

Post by Kevin Funk
I don't really know the process of having it integrated either. I'll

leave

Post by Kevin Funk
that to others.
Kudos for doing the KF5 port!
Regards,
Kevin

Joachim Eibl

2018-01-12 00:21:02 UTC

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div>Hi,</div> <div> </div> <div>It's great to hear there is some ongoing effort to port KDiff3 to KF5.</div> <div>Thanks for informing me.</div> <div>I had a try at it myself, but was quite overwhelmed about the big changes in KF5.</div> <div> </div> <div>You have my blessing to use the name KDiff3.</div> <div> </div> <div>@Michael: It seems the repo at <a href="https://bitbucket.org/reporter123/kdiff3" target="_blank">https://bitbucket.org/reporter123/kdiff3</a></div> <div>has no public access.</div> <div> </div> <div>Kudos,</div> <div>Joachim</div> <div> </div> <div>  <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Donnerstag, 11. Januar 2018 um 22:28 Uhr<br/> <b>Von:</b> "Michael Reeves" <***@gmail.com><br/> <b>An:</b> "Albert Astals Cid" <***@kde.org><br/> <b>Cc:</b> kde-core-***@kde.org, "Joachim Eibl" <***@gmx.de><br/>
<b>Betreff:</b> Re: KDE inclusion</div>

<div>
<div>Sorry meant this to go to everyone.
<div><br/>
I did this based off what Ubuntu was using at the time.  The repo is here <a href="https://bitbucket.org/reporter123/kdiff3" target="_blank">https://bitbucket.org/reporter123/kdiff3</a>. 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 <a href="https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5" target="_blank">https://cgit.kde.org/scratch/thomasfischer/kdiff3.git/log/?h=kf5</a>. 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.</div> </div> <div class="gmail_extra">  <div class="gmail_quote">On Thu, Jan 11, 2018 at 6:24 PM, Albert Astals Cid <span><<a href="mailto:***@kde.org" onclick="parent.window.location.href='***@kde.org'; return false;" target="_blank">***@kde.org</a>></span> wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">El dijous, 11 de gener de 2018, a les 12:15:15 CET, Kevin Funk va escriure:<br/> <span>> On Tuesday, 9 January 2018 21:06:36 CET Michael Reeves wrote:<br/>
> > I have a version of kdiff3 that I ported to kf5. I like to what build<br/>
> > requirements kf5 as a whole has. Also what would be the process for being<br/>
> > considered for inclusion in kde?<br/>
><br/>
> Heya,<br/>
><br/>
> Note: kdiff3 right now is hosted & developed on SourceForge.<br/>
><br/>
> I'd love to see kdiff3 being adopted by KDE again (it former was KDE<br/>
> extragear if I understood correctly). kdiff3 is a super useful tool -- and<br/>
> right now development has stalled a bit.<br/>
><br/>
> Talked to Joachim (the original author) a few weeks ago, where he stated he<br/>
> just doesn't have the time maintaining it anymore, really. I've CC'd Joachim<br/>
> so he can tell us whether he's okay with having kdiff3 developed further<br/>
> under the KDE umbrella.</span><br/>
<br/>
I guess this is the most important question, if we can keep using the kdiff3<br/>
name under's Joachim's blessing or we have to "fork it" and find a new name.<br/>
<br/>
Cheers,<br/>
  Albert
<div class="HOEnZb">
<div class="h5"><br/>
><br/>
> I don't really know the process of having it integrated either. I'll leave<br/>
> that to others.<br/>
><br/>
> Kudos for doing the KF5 port!<br/>
><br/>
> Regards,<br/>
> Kevin<br/>
<br/>
 </div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>

Michael Reeves

2018-01-13 02:47:57 UTC

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.

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

Post by 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

Post by Michael Reeves
considered for inclusion in kde?

and

Post by Kevin Funk
right now development has stalled a bit.
Talked to Joachim (the original author) a few weeks ago, where he

stated he

Post by Kevin Funk
just doesn't have the time maintaining it anymore, really. I've CC'd

Joachim

Post by Kevin Funk
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

Post by Kevin Funk
I don't really know the process of having it integrated either. I'll

leave

Post by Kevin Funk
that to others.
Kudos for doing the KF5 port!
Regards,
Kevin

Michael Reeves

2018-01-14 04:35:31 UTC

Fixed local file handling prevented merges from being saved. Thin rapper
class created to insure scheme is never blank. QUrl::isLocal returns false
in this case.

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

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

Post by 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

Post by Michael Reeves
considered for inclusion in kde?

and

Post by Kevin Funk
right now development has stalled a bit.
Talked to Joachim (the original author) a few weeks ago, where he

stated he

Post by Kevin Funk
just doesn't have the time maintaining it anymore, really. I've CC'd

Joachim

Post by Kevin Funk
so he can tell us whether he's okay with having kdiff3 developed

further

Post by Kevin Funk
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

Post by Kevin Funk
I don't really know the process of having it integrated either. I'll

leave

Post by Kevin Funk
that to others.
Kudos for doing the KF5 port!
Regards,
Kevin

Valentin Rusu

2018-01-14 11:10:07 UTC

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

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

Albert Astals Cid

2018-01-15 21:56:22 UTC

El diumenge, 14 de gener de 2018, a les 12:10:07 CET, Valentin Rusu va

Post by Valentin Rusu

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

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

Cheers,
Albert

Michael Reeves

2018-01-15 21:39:37 UTC

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.

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

Albert Astals Cid

2018-01-15 22:47:38 UTC

El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va

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

Post by Michael Reeves
Hi,
You have my blessing to use the name KDiff3.

Michael Reeves

2018-01-17 20:40:49 UTC

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" <***@kde.org> wrote:

El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va

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

Post by Michael Reeves
Hi,
You have my blessing to use the name KDiff3.

Kevin Funk

2018-01-19 20:52:44 UTC

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

Post by Michael Reeves
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.
El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va

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

Post by Michael Reeves
Hi,
You have my blessing to use the name KDiff3.

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

Kevin Funk

2018-01-24 16:34:16 UTC

A little confused on where to start with this sponsor thing.

Huh? 'sponsor thing'? :)

Care to elaborate what you mean?

Regards,
Kevin

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.
https://community.kde.org/Craft
Cheers,
Kevin

kde4.

Post by Michael Reeves
El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va

Post by 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

Post by Michael Reeves

Post by Michael Reeves
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

Post by Michael Reeves
but it's basically importing the project into our git and then making

sure

Post by Michael Reeves
it
generally follows our rules & procedures.
I understand you want to continue maintaining the new kdiff3 and you are

not

Post by Michael Reeves
just "dumping it" into us, right?
Cheers,
Albert
El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va

Post by Michael Reeves
Hi,
You have my blessing to use the name KDiff3.

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

Albert Astals Cid

2018-01-24 23:08:03 UTC

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

Post by Kevin Funk
Care to elaborate what you mean?
Regards,
Kevin

kde4.

Post by Michael Reeves
El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va

Post by 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

Post by Michael Reeves

Post by Michael Reeves
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

Post by Michael Reeves
but it's basically importing the project into our git and then making

sure

Post by Michael Reeves
it
generally follows our rules & procedures.
I understand you want to continue maintaining the new kdiff3 and you are

not

Post by Michael Reeves
just "dumping it" into us, right?
Cheers,
Albert
El divendres, 12 de gener de 2018, a les 1:21:02 CET, Joachim Eibl va

Post by Michael Reeves
Hi,
You have my blessing to use the name KDiff3.

Kevin Ottens

2018-01-25 08:01:10 UTC

Hello,

A little confused on where to start with this sponsor thing.

Huh? 'sponsor thing'? :)

Was supposed to be for any project born outside the community and joining in.
So not quite so voluntary.

Post by Albert Astals Cid
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

Albert Astals Cid

2018-01-25 21:35:37 UTC

Post by Kevin Ottens
Hello,

El dimecres, 24 de gener de 2018, a les 17:34:16 CET, Kevin Funk va

A little confused on where to start with this sponsor thing.

Huh? 'sponsor thing'? :)

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.

Post by Kevin Ottens

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?

Post by Kevin Ottens
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

Post by Kevin Ottens
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.

Kevin Ottens

2018-01-26 07:27:55 UTC

Hello,

Post by Kevin Ottens

Post by Albert Astals Cid
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. ;-)

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

Post by Albert Astals Cid
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.

Post by Albert Astals Cid
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

Kevin Funk

2018-01-26 11:54:33 UTC

Post by Kevin Ottens
Hello,

Post by Kevin Ottens

Post by Albert Astals Cid
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. ;-)

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

Post by Kevin Ottens
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...

Post by Albert Astals Cid
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.

Post by Albert Astals Cid
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 | ***@kde.org | http://kfunk.org

Adriaan de Groot

2018-01-26 16:51:13 UTC

A little confused on where to start with this sponsor thing.

Huh? 'sponsor thing'? :)

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]

Aleix Pol

2018-01-29 01:53:59 UTC

Hi Michael,
If you are interested in having the incubation happen, please get in
touch. I'll be glad to help.

Aleix

Post by 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.
El dimarts, 9 de gener de 2018, a les 20:06:36 CET, Michael Reeves va

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

Post by Michael Reeves
Hi,
You have my blessing to use the name KDiff3.

Luigi Toscano

2018-01-14 13:38:21 UTC

Post by 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
<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
<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=151566728700006&r=1&w=2

Post by Michael Reeves