Re: 2 New Plasmoids in Kdereview

[Ingo Klöcker]

On Donnerstag, 11. Januar 2018 23:18:38 CET Ingo Klöcker wrote:
> On Donnerstag, 11. Januar 2018 21:10:51 CET Ben Cooksley wrote:
> > On Thu, Jan 11, 2018 at 1:15 PM, Martin Kostolný 
> wrote:
> > > I'd like to move forward with my new plasmoid projects that landed in
> > > kdereview some time ago.
> > > 
> > > https://phabricator.kde.org/source/plasma-redshift-control/
> > > https://phabricator.kde.org/source/plasma-active-window-control/
> > 
> > Given that the review period has long since passed I think we can
> > safely say that these two applets can move to their final place from
> > KDE Review.
> 
> I don't think that Martin has emailed "kde-core-devel and other relevant
> mailing lists with details of your project and what the expected destination
> is for the repo" which is point 3 under kdereview on
> https://community.kde.org/Policies/Application_Lifecycle
> 
> Therefore, I think the review period did not actually start yet. Or have the
> projects already been reviewed elsewhere, e.g. on the plasma ml?

I just realized that technically the review period probably did start approx. 
10 hours ago with Martin's email. :-)


Regards,
Ingo



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

Re: 2 New Plasmoids in Kdereview

[Ingo Klöcker]

On Donnerstag, 11. Januar 2018 21:10:51 CET Ben Cooksley wrote:
> On Thu, Jan 11, 2018 at 1:15 PM, Martin Kostolný  
wrote:
> > I'd like to move forward with my new plasmoid projects that landed in
> > kdereview some time ago.
> > 
> > https://phabricator.kde.org/source/plasma-redshift-control/
> > https://phabricator.kde.org/source/plasma-active-window-control/
> 
> Given that the review period has long since passed I think we can
> safely say that these two applets can move to their final place from
> KDE Review.

I don't think that Martin has emailed "kde-core-devel and other relevant 
mailing lists with details of your project and what the expected destination 
is for the repo" which is point 3 under kdereview on
https://community.kde.org/Policies/Application_Lifecycle

Therefore, I think the review period did not actually start yet. Or have the 
projects already been reviewed elsewhere, e.g. on the plasma ml?


Regards,
Ingo


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

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?

KDE and Google Summer of Code 2018

[Valorie Zimmerman]

Hello GSoC mentors, and teams supporting mentors,

TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
https://community.kde.org/GSoC. Now.

Every year, we've asked for more time to get ramped up for GSoC, and so now
is the time for organizations to apply[1]. We have begun to write our
application, and  that means that our Ideas page needs to be filled NOW,
because that is the prime consideration for the GSoC team once the Org
Applications deadline has passed.

The quality of our ideas and the guidance they give our students are the
most important part of our application. Please begin filling in your ideas
now if you have not already, and ensure that that page is comprehensive,
accurate and attractive. Including screenshots and other images is allowed,
if it enriches the idea for a project. *Please ensure complete information
about how to contact the team*; this is crucial.

Also, take a look at the landing page https://community.kde.org/GSoC.
Experienced mentors agree that:

1. commits must be made before the student proposal is submitted, and
linked on that proposal, and

2. that regular communication from the student must be initiated by the
student at least weekly, and we expect daily or nearly daily communication
with the team in a more informal way.

Be sure to point students to that information, as this should lower the
number of proposals, while raising the quality.

1. https://developers.google.com/open-source/gsoc/timeline

PS: If your team has an Idea, ensure that you have mentors for it, and that
those mentors are subscribe to KDE-Soc-Mentor list. Remove any ideas
without mentors available, please. Now, before you forget!

Valorie
-- 
http://about.me/valoriez