Re: Proposal unify back our release schedules

[Valorie Zimmerman]

On Fri, Apr 19, 2024 at 9:39 AM Kevin Ottens  wrote:

> Hello,
>
> ::most history snipped::
>


> And then have a single big marketing
> announcement for a Plasma x.y.2 per year with its own marketing name.
>
> ::snip::
>


> > * Only have one release announcement on our website. We can call it
> > Megarelease 6.XX like we did for Plasma 6/Gear 24.02 or find a better
> name.
> > I would avoid reusing Software Collection first because the name is quite
> > technical and second because these was already used in the past.
>
> Sure, why not. This is not engineering I'm less opinionated about it.
> Apart
> from decoupling more between engineering effort and marketing
> announcements
> that is.
>
> Maybe reconsider the "Megarelease" term though... I've literally been
> laughed
> at for the use of that term outside of our community. Also, I think it was
> a
> fine term for a one off when moving on a major new version of Qt, but
> it'll
> get old quickly for the "business as usual".
>

I suggest that if we move to do any sort of more infrequent "mega releases"
we call it KDE Community Software Release or similar. "KDE" is shorthand
for our community, after all; why not spell it out.

Valorie

>
> Again no strong opinion there, but I thought I'd mention what I've seen
> around
> me.
>
> Regards.
> --
> Kevin Ottens, http://ervin.ipsquad.net
>
> enioka Haute Couture - proud supporting member of KDE
> https://hc.enioka.com/en



-- 
she/her. "Dwell on the beauty of life. Watch the stars, and see yourself
running with them." - Marcus Aurelius

Re: [GSoC Mentors] GSoC 2024 open for org applications January 22 - February 6

[Valorie Zimmerman]

I'm willing to remain on the list of co-admins, but will not be able to be
more active than I was last year.

Valorie

On Tue, Jan 9, 2024 at 6:32 PM Johnny Jazeix  wrote:

>  Hi,
>
> Are there people willing to help co-admin this year? It would be nice to
> be at least 3 to share the workload.
>
> If mentors are interested, there will be a session Thursday (link sent to
> the mentor list, I've removed it from below as I'm not sure if it's
> supposed to be mentors only).
>
> Main point seem to be: "Starting in 2024 we will have small (~90 hour
> projects), medium (~175 hr projects) and large (~350 hour) projects
> available to GSoC contributors. 90 hours projects are optional."
>
> I've updated the skeleton wiki page to create the 2024 season:
> https://community.kde.org/GSoC/2024/Ideas.
>
> Please start discussing among your teams what ideas will be great to have
> this year and who is willing to mentor, as the organisation application
> date needs to apply between the January 22 - February 6 and we need a wiki
> page filled with ideas by then.
> And please don't wait the last moment to fill the page.
>
> Cheers,
>
> Johnny
>
> -- Forwarded message -
> De : 'sttaylor' via Google Summer of Code Mentors List <
> google-summer-of-code-mentors-l...@googlegroups.com>
> Date: ven. 5 janv. 2024 à 00:28
> Subject: [GSoC Mentors] GSoC Organization Application Info Session January
> 11th 1700 UTC
> To: Google Summer of Code Mentors List <
> google-summer-of-code-mentors-l...@googlegroups.com>
>
>
> Happy New Year!
>
> We are very excited to get started on this 20th year of Google Summer of
> Code!  With Organization applications opening in a few weeks, January 22
> - February 6, we wanted to host an information session for organizations
> looking to apply to GSoC as well as for new org admins for veteran orgs so
> they understand the application process.
>
> Date: Thursday, January 11
>
> Time: 17:00 - 17:45 UTC
>
> GSoC Program Lead, Stephanie Taylor will go through the org application
> process and discuss the tips to a solid organization application as well as
> some of the other things to consider when applying as a GSoC organization.
>
> There will be plenty of time for Q as well for the last half of the
> session.
>
> Some quick tips for everyone to consider when submitting an Organization
> application for Google Summer of Code:
>
>1.
>
>Starting in 2024 we will have small (~90 hour projects), medium (~175
>hr projects) and large (~350 hour) projects available to GSoC contributors.
>Orgs should have medium and large projects available in their Project Ideas
>lists. Small project ideas are not required for orgs, but if the smaller
>size project works for your org they should  be included in your
>Organization’s Ideas List.
>2.
>
>Reach out to your community members now to ask if they would like to
>be mentors for the program.
>
> Having a thorough and well thought out list of Project Ideas
> 
> is the most important part of your application.
>
> Open source projects can apply  to
> be mentoring organizations from January 22 - February 6 at 1800 UTC.
>
> Resources:
>
> Mentor Guide 
>
> Timeline 
>
> FAQs 
>
> Roles and Responsibilities
> 
>
> Marketing Materials
> 
> (slide deck, flyers)
>
> Videos 
>
>
> Best,
>
> Stephanie Taylor
>
> GSoC Program Lead
>
> --
>


-- 
she/her. "Dwell on the beauty of life. Watch the stars, and see yourself
running with them." - Marcus Aurelius

Fwd: [GSoC Mentors] GSoC 2022 Org Applications open Feb 7-21

[Valorie Zimmerman]

A few changes to GSoC I want all KDE developers to be aware of.

TLDR: we need both ~175 hr projects and ~350 hour projects included in the
Ideas List. Please begin adding Ideas along with your own /team contact
information NOW. https://community.kde.org/GSoC/2022/Ideas

If you are willing to mentor, please subscribe to KDE-Soc-Mentor ML NOW.
https://mail.kde.org/mailman/listinfo/kde-soc-mentor

Thanks,

Valorie

PS: I also need admin help this year, please. Now.

-- Forwarded message -
From: 'sttaylor' via Google Summer of Code Mentors List <
google-summer-of-code-mentors-l...@googlegroups.com>
Date: Sun, Jan 9, 2022 at 11:16 PM
Subject: [GSoC Mentors] GSoC 2022 Org Applications open Feb 7-21

Happy New Year!

We are excited to announce the full GSoC 2022 timeline
. With
Organization applications opening in a few weeks, February 7 - 21, we
wanted to remind everyone of the important changes to think about when
considering your application.

   1.

   Be sure to have both ~175 hr projects and ~350 hour projects that you
   would like GSoC contributors to work on included in your Ideas List.
   2.

   Reach out to your community members to ask if they would like to be
   mentors for the program. This year with the option of extending projects
   for up to 22 weeks we hope some of your community members that weren’t able
   to participate before will be able to make the more flexible schedule work
   for them.

Having a thorough and well thought out list of Project Ideas

is the most important part of your application.

You can check out the 2022 GSoC Org Application Short Answer Questions

if you’d like to start preparing your responses in advance so you can copy
over your answers once the org applications open February 7 at g.co/gsoc -
there are a couple of different questions this year.

Please encourage other open source orgs to apply -- if you know of other
open source projects that may be interested in applying to GSoC as a first
time org please remind them to check out the available resources below and
have them put your org (or you) down as a reference when they apply.

Open source projects can apply  to be
mentoring organizations from February 7- 21 at 1800 UTC.

Resources:

Mentor Guide 

Timeline 

FAQs 

Roles and Responsibilities


Marketing Materials
 (slide
deck, flyers)

Videos 


Best,

Stephanie

GSoC Program Admin
-- 
http://about.me/valoriez - pronouns: she/her

New question on the KDE application for 2021 GSoC

[Valorie Zimmerman]

The question is, how many of your 2020 GSoC students have been active in
your community in the past 60 days?

As a reminder, these are our students last year. If you know that one of
these students has been recently contributing, or you are one of these
students recently contributing (it does not have to be coding -- it can be
any contribution to KDE) please reply and star the person's name. Rather
than "reply all," please reply directly. I'll post a response in a few days
with the number of students.

Krita: L. E. Segovia, Saurabh Kumar, *Sharaf Zaman, Ashwin Dhakaita

Gcompris: Deepak Kumar, Shubham Mishra

Digikam: Nghia Duong, R Kartik

Cantor: Nikita Sirgienko, Shubham

Kirogi: Kitae Kim

KDE Connect: Aniket Kumar

Kstars: Paritosh Sharma

KDE websites, Anuj Bansal

marK: Jean Lima Andrade

KMyMoney: Prasun Kumar

WikiToLearn: Davide Briani

QtQuickControls: Agisilaos Kounelis

Kdenlive: Sashmitha Raghav

ROCS: Dilson Guimarães

Akonadi: Shashwat Jolly


Thanks!

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

GSoC 2021 Ideas page skeleton is live

[Valorie Zimmerman]

We have not yet updated the main page at https://community.kde.org/GSoC to
accommodate the new rules and timeline.

However, https://community.kde.org/GSoC/2021/Ideas is live, as a skeleton.
I copied the /2020 page and removed all the ideas. If you are adding an
idea, please remember to put your own contact information in the
description as the mentor. Do not add Ideas with no mentor and contact
info.

Other wiki cleanup is welcome! There seems to be a problem with the link to
the 2020 page and I don't know how to fix it. By the way, copying an idea
from the 2020 page you still want to mentor that was not picked up last
year is fine, but remember that the coding period will be much shorter, so
the proposed project ideas should be smaller in scope.

Organizations Apply January 29, 2021 - February 19, 2021 so if you intend
to mentor or co-mentor, please ensure that you have subscribed to the
KDE-Soc-Mentor list. Prospective students - join kde-...@kde.org

-- 
http://about.me/valoriez - pronouns: she/her

Re: Mentors needed

[Valorie Zimmerman]

He cannot officially stay part of GSoC under those conditions. 29th June is
First Evaluations by which time he should have finishing roughly one third
of his project.

Please ask him urgently to withdraw. We're waiting on the story
announcing and welcoming the accepted students until that is done.

We can discuss what can be done unofficially and out of GSoC when he has
the time to do the work.

Valorie

On Tue, May 5, 2020 at 6:51 AM Alexa M  wrote:

> Hi,
>
> Yeah, he's the same student. He says that he could contribute only a
> little until his university exams end date and after that full-time. That
> could mean part or very little time until 10-20 of July and 100% the rest
> of the time, However there is still a possibility that the exams
> dates shift but he can't say for sure as there is no official
> announcement yet regarding the final dates. Concluding, he said that if
> this is ok for us then he would also be ok to continue under these
> conditions.
>
> Best,
> Alexandra
>
> Στις Τρί, 5 Μαΐ 2020 στις 5:45 π.μ., ο/η Valorie Zimmerman <
> valorie.zimmer...@gmail.com> έγραψε:
>
>> Are we discussing the same student, Agisilaos Kounelis who proposed "Port
>> QtQuickControls Calendar widget to QtQuickControls2 module" ? If so, they
>> have not withdrawn. If this indeed the student, if they will not
>> participate officially then need to *now* mark "Withdraw."
>>
>> Valorie
>>
>> On Mon, May 4, 2020 at 2:12 AM Alexa M  wrote:
>>
>>> Hi,
>>>
>>> The student decided to not to participate in GSoC this year due to other
>>> university obligations running late because of the current situation
>>> including uncertain exams dates and he was afraid he would not be able
>>> to comply.
>>>
>>> Best,
>>> AlexandraB
>>>
>>> On Fri, May 1, 2020, 00:06 Timothée Giet  wrote:
>>>
>>>> Le 30/04/2020 à 22:07, Timothée Giet a écrit :
>>>>
>>>> Le 30/04/2020 à 21:38, Valorie Zimmerman a écrit :
>>>>
>>>> Hello folks, we have a project about porting a QtQuickControls module
>>>> to QtQuickControls2 with only one mentor who marked "I want to mentor" on
>>>> the GSoC webapp.
>>>>
>>>> If you have already signed into the GSoC webapp as a mentor, and would
>>>> like to help out with this project, please mark "I want to mentor" in the
>>>> app.
>>>>
>>>> If you have the skills needed to mentor but have not yet logged into
>>>> the app, please:
>>>>
>>>> 1. ensure that you are subscribed to KDE-Soc-Mentor mail list [1]
>>>>
>>>> 2. write to kde-soc-managem...@kde.org and ask to be invited to the
>>>> webapp.
>>>>
>>>> Thanks!
>>>>
>>>> Valorie
>>>>
>>>> 1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>>>
>>>> --
>>>> http://about.me/valoriez - pronouns: she/her
>>>>
>>>>
>>>> I may not be the best mentor this project, but as GCompris would
>>>> benefit a lot from the output of this proposal (this missing module is the
>>>> main blocker we have to migrate to QtQuickControls2), I'm ok to
>>>> backup-mentor it... At least I can provide generic advices and testing.
>>>>
>>>> But some help from someone more specialist of Qt internals would be
>>>> welcome!
>>>>
>>>> Timothée
>>>>
>>>> On second thought, as I'm not so sure I can provide valuable help to
>>>> mentor this project, I unchecked the "want to mentor" button there... but
>>>> again, if there's anyone else willing to help mentoring this project, it
>>>> would be awesome.
>>>>
>>>> Timo.
>>>>
>>>
>>
>> --
>> http://about.me/valoriez - pronouns: she/her
>>
>>
>>

-- 
http://about.me/valoriez - pronouns: she/her

Re: Mentors needed

[Valorie Zimmerman]

Are we discussing the same student, Agisilaos Kounelis who proposed "Port
QtQuickControls Calendar widget to QtQuickControls2 module" ? If so, they
have not withdrawn. If this indeed the student, if they will not
participate officially then need to *now* mark "Withdraw."

Valorie

On Mon, May 4, 2020 at 2:12 AM Alexa M  wrote:

> Hi,
>
> The student decided to not to participate in GSoC this year due to other 
> university
> obligations running late because of the current situation including uncertain
> exams dates and he was afraid he would not be able to comply.
>
> Best,
> AlexandraB
>
> On Fri, May 1, 2020, 00:06 Timothée Giet  wrote:
>
>> Le 30/04/2020 à 22:07, Timothée Giet a écrit :
>>
>> Le 30/04/2020 à 21:38, Valorie Zimmerman a écrit :
>>
>> Hello folks, we have a project about porting a QtQuickControls module to
>> QtQuickControls2 with only one mentor who marked "I want to mentor" on the
>> GSoC webapp.
>>
>> If you have already signed into the GSoC webapp as a mentor, and would
>> like to help out with this project, please mark "I want to mentor" in the
>> app.
>>
>> If you have the skills needed to mentor but have not yet logged into the
>> app, please:
>>
>> 1. ensure that you are subscribed to KDE-Soc-Mentor mail list [1]
>>
>> 2. write to kde-soc-managem...@kde.org and ask to be invited to the
>> webapp.
>>
>> Thanks!
>>
>> Valorie
>>
>> 1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>
>> --
>> http://about.me/valoriez - pronouns: she/her
>>
>>
>> I may not be the best mentor this project, but as GCompris would benefit
>> a lot from the output of this proposal (this missing module is the main
>> blocker we have to migrate to QtQuickControls2), I'm ok to backup-mentor
>> it... At least I can provide generic advices and testing.
>>
>> But some help from someone more specialist of Qt internals would be
>> welcome!
>>
>> Timothée
>>
>> On second thought, as I'm not so sure I can provide valuable help to
>> mentor this project, I unchecked the "want to mentor" button there... but
>> again, if there's anyone else willing to help mentoring this project, it
>> would be awesome.
>>
>> Timo.
>>
>

-- 
http://about.me/valoriez - pronouns: she/her

Re: Mentors needed

[Valorie Zimmerman]

On Mon, May 4, 2020 at 2:12 AM Alexa M  wrote:

> Hi,
>
> The student decided to not to participate in GSoC this year due to other 
> university
> obligations running late because of the current situation including uncertain
> exams dates and he was afraid he would not be able to comply.
>
> Best,
> AlexandraB
>

That's unfortunate. Is is possible the student will still be able to work
on this project part-time if we can find mentoring for him?

Valorie

On Fri, May 1, 2020, 00:06 Timothée Giet  wrote:
>
>> Le 30/04/2020 à 22:07, Timothée Giet a écrit :
>>
>> Le 30/04/2020 à 21:38, Valorie Zimmerman a écrit :
>>
>> Hello folks, we have a project about porting a QtQuickControls module to
>> QtQuickControls2 with only one mentor who marked "I want to mentor" on the
>> GSoC webapp.
>>
>> ::some old snipped::
>>
>> I may not be the best mentor this project, but as GCompris would benefit
>> a lot from the output of this proposal (this missing module is the main
>> blocker we have to migrate to QtQuickControls2), I'm ok to backup-mentor
>> it... At least I can provide generic advices and testing.
>>
>> But some help from someone more specialist of Qt internals would be
>> welcome!
>>
>> Timothée
>>
>> On second thought, as I'm not so sure I can provide valuable help to
>> mentor this project, I unchecked the "want to mentor" button there... but
>> again, if there's anyone else willing to help mentoring this project, it
>> would be awesome.
>>
>> Timo.
>>
>

Mentors needed

[Valorie Zimmerman]

Hello folks, we have a project about porting a QtQuickControls module to
QtQuickControls2 with only one mentor who marked "I want to mentor" on the
GSoC webapp.

If you have already signed into the GSoC webapp as a mentor, and would like
to help out with this project, please mark "I want to mentor" in the app.

If you have the skills needed to mentor but have not yet logged into the
app, please:

1. ensure that you are subscribed to KDE-Soc-Mentor mail list [1]

2. write to kde-soc-managem...@kde.org and ask to be invited to the webapp.

Thanks!

Valorie

1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor

-- 
http://about.me/valoriez - pronouns: she/her

Additional mentors for GSOC project

[Valorie Zimmerman]

Hi all, this was posted to a list I don't subscribe to, but Ralf is still
needing some co-mentors, so am copy/pasting:

Additional mentor for GSOC project searched
> Ralf Habacker ralf.habacker at freenet.de
> Wed Apr 8 11:40:42 BST 2020
> Hi,
> for the appended GSOC project KDE organization wants to have additional
> mentors. The task is to be a backup for the main mentor.
>  From https://google.github.io/gsocguides/mentor/:
> Mentor: Mentors are people from the community who volunteer to work with
> a student. Mentors provide guidance such as pointers to useful
> documentation, code reviews, etc. In addition to providing students with
> feedback and pointers, a mentor acts as an ambassador to help student
> contributors integrate into their project’s community. Some
> organizations choose to assign more than one mentor to each of their
> students. Many members of the community provide guidance to their
> project’s GSoC students without mentoring in an “official” capacity,
> much as they would answer anyone’s questions on the project’s mailing
> list or IRC channel.


This isn't quite correct. If you want to help out, please subscribe to
KDE-Soc-Mentor ML [1]

Then write to kde-soc-managem...@kde.org and ask to be invited to the GSoC
webapp. Accept the invitation to register as Ralf correctly says.

If anyone has interest, please register at the Google GSOC site
> (https://summerofcode.withgoogle.com/) as mentor and click on "Want to
> mentor" at
>
> https://summerofcode.withgoogle.com/dashboard/organization/4610988642402304/proposal/6153080292245504/
> Regards
> Ralf


URL: <
> http://mail.kde.org/pipermail/kde-finance-apps/attachments/20200408/001847f9/attachment-0001.pdf
> >


Thank you! GSoC would like us to have *two* backup mentors per student this
year, given the tenuous health situation in the world right now.

Valorie

1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor

-- 
http://about.me/valoriez - pronouns: she/her

Re: Polish translation of "Cancel"

[Valorie Zimmerman]

On Thu, Apr 16, 2020 at 3:06 PM Luigi Toscano 
wrote:

> Nate Graham ha scritto:
> > [+ kde-devel mailing list since I don't know if I got the right
> localization
> > mailing list and couldn't find a polish-specific one]
> >
> >
> > Hello translators,
> > I don't speak any Polish, but it's come to my attention that some native
> > Polish speakers are complaining about the Polish translation of the word
> > "Cancel", with no resolution on the issue:
> > https://bugs.kde.org/show_bug.cgi?id=404286
> >
> > The bug has 150 votes and a lot of discussion. I think there's a fairly
> strong
> > argument in favor of consistency. Given that consistency was even
> selected as
> > an explicit KDE goal this year, my sense is that it would be good to be
> > consistent with the translation used by the wider software world, even
> if it's
> > maybe not perfect.
> >
> > However not being familiar with the language, I thought I would bring up
> the
> > subject here for wider visibility.
>
> It is a known issue (sadly, you can see various comment there from Albert
> and
> me, and others) and I was personally waiting for a CWG answer (mainly to
> have
> a clear direction and avert a revert war).
>
> --
> Luigi
>

I think without violating confidentiality, I can say that the CWG has
gotten multiple questions about this. I need some information. IF there is
a revert of the "ancient term" in to the "consistent" alternative, will
there be a revert war?

I also do not understand how this one word became a cause worth fighting
for.

Can anyone answer the first question and explain the issue so I understand?
My ignorance of the Polish language and its history is nearly total.

Valorie, as part of the CWG

Re: More GSoC Mentors needed

[Valorie Zimmerman]

Hi Jean-Baptiste,

On Wed, Apr 8, 2020 at 4:22 AM Jean-Baptiste Mardelle 
wrote:

> On 01.04.20 00:11, Valorie Zimmerman wrote:
>
> Hi Valorie,
>
> Did you get my email about me backing up Akhil for mentoring on Kdenlive
> (sent on the 3rd of April)  ? Seems many mails I send are swallowed by spam
> filters.. I didn't get an invite to the webapp...
>
> Probably not; we usually handle this in KDE-Soc-Mentor ML. Are you
subscribed? If not, please do that now.

> You can use my @kdenlive email address.
>
> Thanks a lot and let me know if anything else is required..
>
> Jean-Baptiste Mardelle
>
> Kdenlive maintainer
>

Done. Please look in your spam if you don't see your invitation now.

Valorie

>
> Nico,
>
> Done. Ensure that you are subscribed to KDE-Soc-Mentor mail list.
>
> Thanks,
>
> Valorie
>
> PS: more backups needed!
>
> On Tue, Mar 31, 2020 at 10:06 AM Nicolas Fella 
> wrote:
>
>> On Donnerstag, 26. März 2020 01:08:25 CET Valorie Zimmerman wrote:
>> > Hi folks, we have possibly enough primary mentors for GSoC this year,
>> > however the GSoC admins are urging us during these pandemic times, to
>> have
>> > *two* backup mentors for each student. If you think you can help us out:
>> >
>> > 1. Subscribe to the KDE-Soc-Mentor mail list:
>> > https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>> >
>> > 2. Message one of us admins your google-connected email address, so we
>> can
>> > invite you to the webapp
>> >
>> > 3. Accept the invite from the webapp, and dig into proposals you would
>> like
>> > to help out with. Please comment either to the student in the google
>> doc,
>> > or to your fellow mentors on the mail proposal page.
>> >
>> > Thanks!
>> >
>> > Valorie
>>
>> Hi Valorie,
>>
>> I can act as a backup mentor for KDE Connect. Please invite me:
>> nicolas.fe...@gmx.de
>
>

Re: More GSoC Mentors needed

[Valorie Zimmerman]

Nico,

Done. Ensure that you are subscribed to KDE-Soc-Mentor mail list.

Thanks,

Valorie

PS: more backups needed!

On Tue, Mar 31, 2020 at 10:06 AM Nicolas Fella  wrote:

> On Donnerstag, 26. März 2020 01:08:25 CET Valorie Zimmerman wrote:
> > Hi folks, we have possibly enough primary mentors for GSoC this year,
> > however the GSoC admins are urging us during these pandemic times, to
> have
> > *two* backup mentors for each student. If you think you can help us out:
> >
> > 1. Subscribe to the KDE-Soc-Mentor mail list:
> > https://mail.kde.org/mailman/listinfo/kde-soc-mentor
> >
> > 2. Message one of us admins your google-connected email address, so we
> can
> > invite you to the webapp
> >
> > 3. Accept the invite from the webapp, and dig into proposals you would
> like
> > to help out with. Please comment either to the student in the google doc,
> > or to your fellow mentors on the mail proposal page.
> >
> > Thanks!
> >
> > Valorie
>
> Hi Valorie,
>
> I can act as a backup mentor for KDE Connect. Please invite me:
> nicolas.fe...@gmx.de
>
> Cheers
>
> Nico
>
>
>

-- 
http://about.me/valoriez - pronouns: she/her

More GSoC Mentors needed

[Valorie Zimmerman]

Hi folks, we have possibly enough primary mentors for GSoC this year,
however the GSoC admins are urging us during these pandemic times, to have
*two* backup mentors for each student. If you think you can help us out:

1. Subscribe to the KDE-Soc-Mentor mail list:
https://mail.kde.org/mailman/listinfo/kde-soc-mentor

2. Message one of us admins your google-connected email address, so we can
invite you to the webapp

3. Accept the invite from the webapp, and dig into proposals you would like
to help out with. Please comment either to the student in the google doc,
or to your fellow mentors on the mail proposal page.

Thanks!

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

Re: ROCS project and GSOC

[Valorie Zimmerman]

On Sun, Mar 22, 2020 at 2:33 PM Caio Tonetti  wrote:

> Hi Valorie,
>
> There is no Ideas in the link, but there are many things that can be done
> in ROCS.
>

Cool. If you want more interest in Rocs though, an Idea is the way to do
that.


> I am registered as a mentor for KDE, so I could take some students to work
> in
> ROCS. I know Arthur (he is from my city), and he is interested as a
> student.
>

Well, you can work with more than one to develop a proposal, but we need
two mentors per student, so see how many of your fellow devels you can get
signed up as mentors!

Arthur needs to get his proposal uploaded ASAP so he can get feedback on it.

Valorie

Att,
> Caio Tonetti
>
> Em dom., 22 de mar. de 2020 às 04:05, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> escreveu:
>
>>
>>
>> On Sat, Mar 21, 2020 at 1:28 PM Arthur  wrote:
>>
>>> Hello everyone,
>>>
>>> My name is Arthur Moreira and I'd like to join the ROCS project as a
>>> developer, and also to participate in the Google Summer Of Code 2020.
>>> Recently, I've been talking offline with Caio Tonetti, who participated
>>> in the project last year, and he encouraged me to participate too. I hope I
>>> can help.
>>>
>>> Kind regards,
>>>
>>> ~A
>>>
>>
>> Hello Arthur, are you asking as a student? If so, get in contact with the
>> team as soon as possible. However, I see no Ideas [1] from the Rocs team,
>> which indicates to me that they have no mentors available.
>>
>> If you are volunteering as a mentor, now is a great time to prepare for
>> next year. With a year of developing experience, you will be well equipped
>> to help the team next year for GSoC.
>>
>> Thanks for stepping up!
>>
>> Valorie
>>
>> 1. https://community.kde.org/GSoC/2020/Ideas
>>
>

Re: ROCS project and GSOC

[Valorie Zimmerman]

On Sat, Mar 21, 2020 at 1:28 PM Arthur  wrote:

> Hello everyone,
>
> My name is Arthur Moreira and I'd like to join the ROCS project as a
> developer, and also to participate in the Google Summer Of Code 2020.
> Recently, I've been talking offline with Caio Tonetti, who participated in
> the project last year, and he encouraged me to participate too. I hope I
> can help.
>
> Kind regards,
>
> ~A
>

Hello Arthur, are you asking as a student? If so, get in contact with the
team as soon as possible. However, I see no Ideas [1] from the Rocs team,
which indicates to me that they have no mentors available.

If you are volunteering as a mentor, now is a great time to prepare for
next year. With a year of developing experience, you will be well equipped
to help the team next year for GSoC.

Thanks for stepping up!

Valorie

1. https://community.kde.org/GSoC/2020/Ideas

-- 
http://about.me/valoriez - pronouns: she/her

Re: GSoC Project

[Valorie Zimmerman]

Hi Luis,

On Wed, Mar 18, 2020 at 6:51 AM luis salomao  wrote:

> Hi everyone,
> My name is Luis Salomão, and i would like to apply to a project on ROCS,
> so i can participate com GSoC.
> I am currently talking with Caio Tonetti  on how to apply and reguarding
> the project as well.
>

Great! That is most important. Communication with your team along with the
larger KDE developer group is absolutely crucial to your success.

By subscribing to this list, you have cleared the first hurdle. :-)

So welcome.


> I would like to know how to introduce myself reguarding my programming
> skills, so if any of you could answer this email. it would be of great help.
> Thanks;
>
> LHFS
>

Discussing your skills with your possible mentor and team is great! This
list is more about questions you might have as you decide how to tackle
issues facing you in your proposal and as you begin coding. As you read the
discussion here, you'll also notice developers wrestling with larger issues
affecting all, such as refining the infrastructure, porting and
 deprecations, changes in Qt and other common tools, etc.

My only advice: upload your proposal as soon as possible, and remember to
turn on "suggesting" and then respond to comments and suggestions.

Remember to link to commits you have made in your proposal. If they have
not landed yet, link to the Phab or Invent discussion of your patches.

All the best,

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

Re: start contribute to KDE

[Valorie Zimmerman]

On Wed, Mar 4, 2020 at 11:20 AM Konrad Czapla 
wrote:

> Hello everyone.
> My name is Konrad and I come from Poland.
> I love programming in C++, and I want to increase my programming skills,
> that's why I would like to contribute to KDE and join to Your team.
> I don't know how to start and I need Your help to give me some tips.
> I would like to start by minor bug fixes.
>
> Best regards,
> Konrad.
>

Hi Konrad, nice to see you here. Have you looked through
https://community.kde.org/Get_Involved especially the section on
Development?
We welcome your help to fix bugs!

All the best,

Valorie

Re: Fwd: gsoc ktoblzcheck

[Valorie Zimmerman]

On Tue, Feb 25, 2020 at 1:39 AM Ben Cooksley  wrote:

> On Tue, Feb 25, 2020 at 10:12 AM Victor Kukshiev
>  wrote:
> >
> > I logged in, but Wiki don't allow access to Phabacker link.  screenshot
> https://imgur.com/4GropmI
>
> Hi Victor,
>
> I have investigated this and ascertained that this was caused by an
> issue with your Phabricator account (which unfortunately happens in
> some cases, and which we have never been able to trace the cause of)
> which prevents your email address from being marked as 'confirmed'.
>
> This in turn means your email address was never made available to the
> wiki - which is why it wouldn't allow you to message Ralf, as the
> Community Wiki did not have an email address for you.
>
> I have now corrected all of these issues for your account and synced
> your profile to the wiki, so you should now be able to access that
> page.
>
> Please note however that we prefer for communication to be made via a
> public channel for everything concerning GSoC, so I would recommend
> that you transition to a public mailing list for this as soon as is
> practical.
>
> Thanks,
> Ben Cooksley
> KDE Sysadmin
>

This is a reminder to all mentors and teams that GSoC communication should
*all* be public. Link to your mail lists and public irc/telegram/matrix
channels please.

Free software is made in the open.

Valorie

> пн, 24 февр. 2020 г. в 23:22, Carl Schwan :
> >>
> >> Hello,
> >> You might want to click on the contact Rhabacker link. If you are asked
> to login and don't have an account yet, you can create an account in
> identity.kde.org and then log through phabricator.kde.org.
> >> I hope it help.
> >> Best regards,
> >> Carl
> >>
> >>  Original Message 
> >> On 24 Feb 2020, 9:16 PM, Victor Kukshiev < andrey0bolkon...@gmail.com>
> wrote:
> >>
> >>
> >>
> >> Hello, I is a  student of PetrSU (Petrozavodsk, Russia). I interested
> this idea and  I want to participation.
> >>
> >>
> https://community.kde.org/GSoC/2020/Ideas#Project:_Provide_the_bank_data_needed_for_financial_applications_in_SQLite_format
> >>
> >> How to  participate it? Who I must do?

Re: Call for mentors and project ideas for Google Summer of Code 2020

[Valorie Zimmerman]

Please forward and discuss the below with your teams! Let's get more teams
mentoring and offering ideas in GSoC 2020.

Valorie

On Thu, Jan 16, 2020 at 4:43 AM Caio Jordão Carvalho <
caiojcarva...@gmail.com> wrote:

> Hello, people.
>
> Google has announced that GSoC 2020 organization applications are now open
> and it will close on February 5th [1]. We have an ideas page in the wiki
> [2], but it doesn't have a good number of projects there for now, so try to
> include some ideas there ASAP because we can use that to see if there are a
> sufficient number of contributors interested in mentoring during this GSoC
> edition.
>
> Best,
> Caio Jordão Carvalho
>
> 1.
> https://opensource.googleblog.com/2020/01/google-summer-of-code-2020-is-now-open.html
> 2. https://community.kde.org/GSoC/2020/Ideas
>
> --
> Caio Jordão de Lima Carvalho
> - http://carvalho.site
>

Re: Call for Mentors and Project Ideas for Season of KDE 2020

[Valorie Zimmerman]

It's so great to see Caio stepping up to lead Season of KDE for the first
time. Please everyone support him and help us onboard new contributors!

Valorie

On Thu, Nov 7, 2019 at 6:06 AM Caio Jordão Carvalho 
wrote:

> Hello, everyone!
>
> After a one-year hiatus since the last edition of Season of KDE in 2018,
> we have started to make plans for the next edition!
>
> But before announcing the program, we need to have a significant number of
> mentors and interesting projects. Now we have an Ideas Page (
> https://community.kde.org/SoK/Ideas/2020) where mentors can list their
> projects. Remember that SoK is more general than GSoC, so these ideas are
> not limited only to coding tasks and you can include projects related to
> documentation, artwork, translation, reports and other types of work as
> well as code.
>
> Now we have this timeline schedule and the announcement post is going to
> be published soon, so we need to include the ideas on the page now.
>
> The timeline is:
>
> 2nd December 2019 - 3th January 2020: Participant and Mentor Application
> period
>
> 6th January 2020: Projects announced
>
> 8th January 2020, 00:00 UTC: SoK work period begins
>
> 17th February 2020, 23:59 UTC: End of work
>
> 21th February 2020: Results announced
>
> 28th February 2020: Certificates issued
>
> Beginning of Q3 2020: Merchandise and Swag sent out by courier
>
>
> That's all for now, folks!
>
> Best,
> Caio
>
> --
> Caio Jordão de Lima Carvalho
> - http://carvalho.site
>

Re: Work Branches

[Valorie Zimmerman]

Hey Ben and developers,

On Fri, Oct 4, 2019 at 7:11 PM Ben Cooksley  wrote:

> Hi all,
>
> Recently we had a discussion (which I think may have ended up spread
> over a couple of mailing lists in the end) concerning branches and the
> ability to force push to them.
>
> Current policy forbids force pushing to branches except in very
> limited circumstances (essentially where it is the only option to fix
> a branch)
>
> The discussion ended with two ways forward, but no 100% clear
> consensus on which way we want to go forward. The two proposed ways
> were:
> 1) Only protect 'master' and declared 'stable' branches.
> 2) Protect all branches, aside from a given prefix (proposed to be work/)
>
> I'd like to clean this up and sort out the policy we want to have
> surrounding this so we can move forward.
>
> From my perspective i'd rather we go with Option 2, as this will be
> the approach that will be easier to both implement and maintain in the
> long term and be the least likely to cause collaboration problems (as
> the branch naming conventions will be universal across all our
> repositories).
>
> Thoughts?
>
> Thanks,
> Ben Cooksley
> KDE Sysadmin
>

We in the CWG have been in discussions about this too, since there have
been some people trying to force-push even after being warned by the system
and sysadmin. I see that there seems to be consensus about proposal 2.

My question is how will this be documented and then how do we spread the
word? Our devel announce list does not seem to be as well-read as it should
be.

Perhaps the new policy can be linked to the Manifesto or even added to it?

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

Re: Retirement of notes.kde.org

[Valorie Zimmerman]

Hey Ben,

On Sun, Sep 15, 2019 at 11:58 AM Ben Cooksley  wrote:

> Good evening all,
>
> Currently we're in the situation where the software we use to run
> notes.kde.org is both difficult to maintain, as well as support (for
> things like document confidentiality for various groups within KDE).
>
> We'd therefore like to retire the service, replacing it with the
> Realtime Text Editor within Nextcloud (share.kde.org). Internally this
> editor uses Markdown.
>
> You can find a demo of this at https://share.kde.org/s/gtFcRmwetRKqTZJ
> (no login required)
>
> It would be appreciated if everyone could please test the realtime
> text editor and let us know if they encounter any issues.
>
> In terms of feature differences, we are aware that
> highlighting/authorship information won't be retained by the new
> editor, and there can occasionally be problems when editing the same
> line with someone else simultaneously.
>
> If everyone is okay with this we'd like to go ahead with shutting down
> notes.kde.org as soon as possible.
>
> Thanks,
> Ben Cooksley
> KDE Sysadmin
>

I noticed that most every BoF at Akademy this year used notes to link the
BoF notes. Will all these notes be just disappeared? If so, that is really
unfortunate. There is a reason many of us continue to use notes. One can
see who typed what, one can see the history of the doc - and other points
mentioned on https://share.kde.org/s/gtFcRmwetRKqTZJ.

::sigh::

Valorie
-- 
http://about.me/valoriez - pronouns: she/her

Re: Tipping the apple cart?

[Valorie Zimmerman]

Please lets keep in mind that this is not a thread to complain about
Gitlab. No platform is perfect, and we're not yet on production machines.

This thread is about how to make our review process great for both newbies
and experienced developers, *and reviewers* - on Gitlab.

On Sun, Jun 30, 2019 at 2:53 PM Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:

> Hello folks, as you know, I'm not a coder. However, I'm interested in our
> code quality, and there has been some observation that "lots of patches get
> missed, and submitters get confused due to a lack of auto-populated
> reviewers" on Phabricator. Nate Graham has been adding groups to the
> reviewers by hand, and would like to not do that any more.
>
> However, many developers simply route all Phab emails to folders where
> they sit unread, because Phab sends out an email for every event and
> comment! This is far too spammy. In our move to Gitlab, we can do better.
> Right now, the devel email lists get these emails -- but it is assumed that
> they are often not read, because of the number of patches sitting
> unreviewed, and unused. This is bad for our community, and very
> discouraging to newcomers. One of our best recent initiatives has been the
> improve our onboarding process, and this needs to be part of it.
>
> Improving the workflow on Phabricator is almost pointless, since we're
> leaving it. However, please give your ideas, thoughts and even opinions on
> how best to improve this in Gitlab. I think if we engineer this well, we
> can get more newbie contributors and more new *reviewers.*
>
> I'm ok with starting Yet Another discussion which threatens to tip the
> apple cart, because right now, the apples are already on the ground,
> rotting.
>
> Valorie
>

Re: Tipping the apple cart?

[Valorie Zimmerman]

Please lets keep in mind that this is not a thread to complain about
Gitlab. No platform is perfect, and we're not yet on production machines.

This thread is about how to make our review process great for both newbies
and experienced developers, *and reviewers* - on Gitlab.

On Sun, Jun 30, 2019 at 2:53 PM Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:

> Hello folks, as you know, I'm not a coder. However, I'm interested in our
> code quality, and there has been some observation that "lots of patches get
> missed, and submitters get confused due to a lack of auto-populated
> reviewers" on Phabricator. Nate Graham has been adding groups to the
> reviewers by hand, and would like to not do that any more.
>
> However, many developers simply route all Phab emails to folders where
> they sit unread, because Phab sends out an email for every event and
> comment! This is far too spammy. In our move to Gitlab, we can do better.
> Right now, the devel email lists get these emails -- but it is assumed that
> they are often not read, because of the number of patches sitting
> unreviewed, and unused. This is bad for our community, and very
> discouraging to newcomers. One of our best recent initiatives has been the
> improve our onboarding process, and this needs to be part of it.
>
> Improving the workflow on Phabricator is almost pointless, since we're
> leaving it. However, please give your ideas, thoughts and even opinions on
> how best to improve this in Gitlab. I think if we engineer this well, we
> can get more newbie contributors and more new *reviewers.*
>
> I'm ok with starting Yet Another discussion which threatens to tip the
> apple cart, because right now, the apples are already on the ground,
> rotting.
>
> Valorie
>

Re: Tipping the apple cart?

[Valorie Zimmerman]

On Sun, Jun 30, 2019 at 11:47 PM Kai Uwe Broulik 
wrote:

> Hi,
>
>  > In our move to Gitlab, we can do better.
>
> Given Gitlab emails contain even less information and context than
> Phabricator which themselves contained even less information and context
> than Reviewboard back then, I don't see how this will change or improve
> anything.
>
>  > Phab sends out an email for every event and comment
>
> And Gitlab even unexpectedly submits the comments as soon as you close
> the editor rather than in bulk as I would have expected from a proper
> reviewing workflow.
>
> Cheers
> Kai Uwe
>

Thanks, Kai.

This tells me that Gitlab can be worse, which is not surprising.

And can it be better? Will some folks who have a good experience with this
on Gitlab speak up?

This is something that all of us want and need to know.

Valorie

Tipping the apple cart?

[Valorie Zimmerman]

Hello folks, as you know, I'm not a coder. However, I'm interested in our
code quality, and there has been some observation that "lots of patches get
missed, and submitters get confused due to a lack of auto-populated
reviewers" on Phabricator. Nate Graham has been adding groups to the
reviewers by hand, and would like to not do that any more.

However, many developers simply route all Phab emails to folders where they
sit unread, because Phab sends out an email for every event and comment!
This is far too spammy. In our move to Gitlab, we can do better. Right now,
the devel email lists get these emails -- but it is assumed that they are
often not read, because of the number of patches sitting unreviewed, and
unused. This is bad for our community, and very discouraging to newcomers.
One of our best recent initiatives has been the improve our onboarding
process, and this needs to be part of it.

Improving the workflow on Phabricator is almost pointless, since we're
leaving it. However, please give your ideas, thoughts and even opinions on
how best to improve this in Gitlab. I think if we engineer this well, we
can get more newbie contributors and more new *reviewers.*

I'm ok with starting Yet Another discussion which threatens to tip the
apple cart, because right now, the apples are already on the ground,
rotting.

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

Tipping the apple cart?

[Valorie Zimmerman]

Hello folks, as you know, I'm not a coder. However, I'm interested in our
code quality, and there has been some observation that "lots of patches get
missed, and submitters get confused due to a lack of auto-populated
reviewers" on Phabricator. Nate Graham has been adding groups to the
reviewers by hand, and would like to not do that any more.

However, many developers simply route all Phab emails to folders where they
sit unread, because Phab sends out an email for every event and comment!
This is far too spammy. In our move to Gitlab, we can do better. Right now,
the devel email lists get these emails -- but it is assumed that they are
often not read, because of the number of patches sitting unreviewed, and
unused. This is bad for our community, and very discouraging to newcomers.
One of our best recent initiatives has been the improve our onboarding
process, and this needs to be part of it.

Improving the workflow on Phabricator is almost pointless, since we're
leaving it. However, please give your ideas, thoughts and even opinions on
how best to improve this in Gitlab. I think if we engineer this well, we
can get more newbie contributors and more new *reviewers.*

I'm ok with starting Yet Another discussion which threatens to tip the
apple cart, because right now, the apples are already on the ground,
rotting.

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

Re: Thank you for selecting for GSoC 2019

[Valorie Zimmerman]

On Tue, May 7, 2019 at 11:28 AM Prasenjit Kumar Shaw <
shawprasenji...@gmail.com> wrote:

> Hi everyone,
>
> Thank you KDE community for giving me the opportunity to participate in
> Google Summer of Code 2019, with KDE. I have been selected for the
> project "Data Sync for Falkon"
> (https://summerofcode.withgoogle.com/projects/#513792952320 ).
>
> Any tips on how to make the most out of the Community Bonding Period
> will be welcome.
>
> Thank You,
> Prasenjit Kumar Shaw
>

Hi there Prasenjit,

Have a look again at https://google.github.io/gsocguides/student/

Ask your Falkon team for more specific tips.

Valorie


-- 
http://about.me/valoriez

Re: Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

Awesome, thanks! Please get together with Tomaz and one or the other of you
transfer the info to the spreadsheet and report your magic number on the
Home tab of the spreadsheet.

Valorie

On Sat, Apr 13, 2019 at 3:32 PM Adriaan de Groot  wrote:

> On Saturday, 13 April 2019 23:36:43 CEST Valorie Zimmerman wrote:
> > It's been a few days. Is anyone willing to step up to mentor this
> student?
> > Tomaz cannot mentor two students, but he's willing to co-mentor. Without
> > another mentor, we must turn this one down, rather than over-burden and
> > possibly burn out Tomaz.
> >
> > If you are interested in mentoring but have not yet been invited to the
> > app, please write kde-soc-managem...@kde.org and tell us what
> > google-connected email address you want us in use. Also, subscribe to
> > KDE-Soc-Mentor mail list:
> > https://mail.kde.org/mailman/listinfo/kde-soc-mentor.
> >
> > Valorie
> >
> > On Wed, Apr 10, 2019 at 3:27 PM Valorie Zimmerman <
> >
> > valorie.zimmer...@gmail.com> wrote:
> > > I need comments on this proposal in the app, so I know where we are. Is
> > > anyone besides Tomaz willing to mentor this student? One mentor with
> two
> > > students is burnout country, and we can't send anyone there!
>
> I'll do it (somewhat hesitantly .. I do tend to vanish myself
> occasionally, so
> not sure I'll be there all the time. OTOH, I like graph theory, and my
> kids do
> too, so we'll have some good testers available).
>
> My @kde address was used last year for GSoC, and I think I'm still
> subscribed.
>
> [ade]



-- 
http://about.me/valoriez

Re: Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

It's been a few days. Is anyone willing to step up to mentor this student?
Tomaz cannot mentor two students, but he's willing to co-mentor. Without
another mentor, we must turn this one down, rather than over-burden and
possibly burn out Tomaz.

If you are interested in mentoring but have not yet been invited to the
app, please write kde-soc-managem...@kde.org and tell us what
google-connected email address you want us in use. Also, subscribe to
KDE-Soc-Mentor mail list:
https://mail.kde.org/mailman/listinfo/kde-soc-mentor.

Valorie

On Wed, Apr 10, 2019 at 3:27 PM Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:

> I need comments on this proposal in the app, so I know where we are. Is
> anyone besides Tomaz willing to mentor this student? One mentor with two
> students is burnout country, and we can't send anyone there!
>
> Valorie
>
> On Wed, Apr 10, 2019 at 1:50 AM Tomaz Canabrava 
> wrote:
>
>> I signed as a mentor for analitza so I’m not sure I can mentor two. But
>> if anyone can tag as “mentor”, I can be the actual mentor.
>>
>> Em qua, 10 de abr de 2019 às 10:13, Valorie Zimmerman <
>> valorie.zimmer...@gmail.com> escreveu:
>>
>>> Cool. Now I need mentors to step up, or suggestions for whom to ask. If
>>> you are interested and are all signed up as a mentor, you know what to do.
>>>
>>> If not, write to kde-soc-managem...@kde.org and tell us your
>>> google-connected email address so you can be invited to the GSoC webapp,
>>> and subscribe to the KDE-Soc-Management ML:
>>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>>
>>> Valorie
>>>
>>> On Wed, Apr 10, 2019 at 1:01 AM Tomaz Canabrava 
>>> wrote:
>>>
>>>> Sounds reasonable. The fact that he’s in masters also counts as he can
>>>> do what he is talking about.
>>>>
>>>>
>>>> Em qua, 10 de abr de 2019 às 09:37, Valorie Zimmerman <
>>>> valorie.zimmer...@gmail.com> escreveu:
>>>>
>>>>> Thank you, Tomaz. <3
>>>>>
>>>>> On Wed, Apr 10, 2019 at 12:34 AM Tomaz Canabrava 
>>>>> wrote:
>>>>>
>>>>>> Let me look, give me 30 minutes.
>>>>>>
>>>>>>
>>>>>> Em qua, 10 de abr de 2019 às 09:30, Valorie Zimmerman <
>>>>>> valorie.zimmer...@gmail.com> escreveu:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 10, 2019 at 12:25 AM Tomaz Canabrava 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> He contacted me and participated in a qt course I presented at his
>>>>>>>> university. Inward unsure if he was going to apply.
>>>>>>>>
>>>>>>>
>>>>>>> OK, good to hear that there was some contact. I need some ideas
>>>>>>> about who can look at this proposal and see if there is any chance of
>>>>>>> success.
>>>>>>>
>>>>>>> Valorie
>>>>>>>
>>>>>>>
>>>>>>>> Em qua, 10 de abr de 2019 às 04:24, Valorie Zimmerman <
>>>>>>>> valorie.zimmer...@gmail.com> escreveu:
>>>>>>>>
>>>>>>>>> I'm unsure if this applicant contacted the KDE Edu team in
>>>>>>>>> advance, but I heard nothing from them until seeing this proposal this
>>>>>>>>> morning.
>>>>>>>>>
>>>>>>>>> The short description of the proposal:
>>>>>>>>>
>>>>>>>>> "As a student, I use graphs in almost everything related to my
>>>>>>>>> master’s research. Graph Theory is a great mathematical tool for
>>>>>>>>> programmers and mathematicians, as it facilitates some computational
>>>>>>>>> problems resolution and modelling. However, is not always easy to
>>>>>>>>> understand the underlying theory and algorithms.
>>>>>>>>>
>>>>>>>>> "Rocs (https://kde.org/applications/education/rocs) is a Graph
>>>>>>>>> Theory IDE created in January of 2010, with new updates still being
>>>>>>>>> committed almost every month, currently in the KDE repositories, 
>>>>>>>>> designed
>>>>>>>>> for lecturers, students and researchers. It is composed of a visual 
>>>>>>>>> data
>>>>>>>>> structure and a powerful scripting engine in Javascript. Though 
>>>>>>>>> useful for
>>>>>>>>> creating simple graphs, it is still lacking the tools to simplify the
>>>>>>>>> creation of bigger graphs, and also of basic graph theory algorithms 
>>>>>>>>> for
>>>>>>>>> beginners. Another improvement it should have is a step by step 
>>>>>>>>> execution
>>>>>>>>> system, in order to fully comprehend the algorithms and facilitate
>>>>>>>>> debugging."
>>>>>>>>>
>>>>>>>>> If you are interested in mentoring but have not yet been invited
>>>>>>>>> to the app, please write kde-soc-managem...@kde.org and tell us
>>>>>>>>> what google-connected email address you want us in use. Also, 
>>>>>>>>> subscribe to
>>>>>>>>> KDE-Soc-Mentor mail list:
>>>>>>>>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>>>>>>>>
>>>>>>>>> If you're already a mentor, you can mark "I want to mentor" on the
>>>>>>>>> proposal page. I believe that we can still comment on the draft and 
>>>>>>>>> the
>>>>>>>>> student can read it, although we are not allowed to consider the 
>>>>>>>>> draft in
>>>>>>>>> our consideration of which students to accept.
>>>>>>>>>
>>>>>>>>> All the best,
>>>>>>>>>
>>>>>>>>> Valorie
>>>>>>>>>
>>>>>>>>

Re: Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

I need comments on this proposal in the app, so I know where we are. Is
anyone besides Tomaz willing to mentor this student? One mentor with two
students is burnout country, and we can't send anyone there!

Valorie

On Wed, Apr 10, 2019 at 1:50 AM Tomaz Canabrava  wrote:

> I signed as a mentor for analitza so I’m not sure I can mentor two. But if
> anyone can tag as “mentor”, I can be the actual mentor.
>
> Em qua, 10 de abr de 2019 às 10:13, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> escreveu:
>
>> Cool. Now I need mentors to step up, or suggestions for whom to ask. If
>> you are interested and are all signed up as a mentor, you know what to do.
>>
>> If not, write to kde-soc-managem...@kde.org and tell us your
>> google-connected email address so you can be invited to the GSoC webapp,
>> and subscribe to the KDE-Soc-Management ML:
>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>
>> Valorie
>>
>> On Wed, Apr 10, 2019 at 1:01 AM Tomaz Canabrava 
>> wrote:
>>
>>> Sounds reasonable. The fact that he’s in masters also counts as he can
>>> do what he is talking about.
>>>
>>>
>>> Em qua, 10 de abr de 2019 às 09:37, Valorie Zimmerman <
>>> valorie.zimmer...@gmail.com> escreveu:
>>>
>>>> Thank you, Tomaz. <3
>>>>
>>>> On Wed, Apr 10, 2019 at 12:34 AM Tomaz Canabrava 
>>>> wrote:
>>>>
>>>>> Let me look, give me 30 minutes.
>>>>>
>>>>>
>>>>> Em qua, 10 de abr de 2019 às 09:30, Valorie Zimmerman <
>>>>> valorie.zimmer...@gmail.com> escreveu:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Apr 10, 2019 at 12:25 AM Tomaz Canabrava 
>>>>>> wrote:
>>>>>>
>>>>>>> He contacted me and participated in a qt course I presented at his
>>>>>>> university. Inward unsure if he was going to apply.
>>>>>>>
>>>>>>
>>>>>> OK, good to hear that there was some contact. I need some ideas about
>>>>>> who can look at this proposal and see if there is any chance of success.
>>>>>>
>>>>>> Valorie
>>>>>>
>>>>>>
>>>>>>> Em qua, 10 de abr de 2019 às 04:24, Valorie Zimmerman <
>>>>>>> valorie.zimmer...@gmail.com> escreveu:
>>>>>>>
>>>>>>>> I'm unsure if this applicant contacted the KDE Edu team in advance,
>>>>>>>> but I heard nothing from them until seeing this proposal this morning.
>>>>>>>>
>>>>>>>> The short description of the proposal:
>>>>>>>>
>>>>>>>> "As a student, I use graphs in almost everything related to my
>>>>>>>> master’s research. Graph Theory is a great mathematical tool for
>>>>>>>> programmers and mathematicians, as it facilitates some computational
>>>>>>>> problems resolution and modelling. However, is not always easy to
>>>>>>>> understand the underlying theory and algorithms.
>>>>>>>>
>>>>>>>> "Rocs (https://kde.org/applications/education/rocs) is a Graph
>>>>>>>> Theory IDE created in January of 2010, with new updates still being
>>>>>>>> committed almost every month, currently in the KDE repositories, 
>>>>>>>> designed
>>>>>>>> for lecturers, students and researchers. It is composed of a visual 
>>>>>>>> data
>>>>>>>> structure and a powerful scripting engine in Javascript. Though useful 
>>>>>>>> for
>>>>>>>> creating simple graphs, it is still lacking the tools to simplify the
>>>>>>>> creation of bigger graphs, and also of basic graph theory algorithms 
>>>>>>>> for
>>>>>>>> beginners. Another improvement it should have is a step by step 
>>>>>>>> execution
>>>>>>>> system, in order to fully comprehend the algorithms and facilitate
>>>>>>>> debugging."
>>>>>>>>
>>>>>>>> If you are interested in mentoring but have not yet been invited to
>>>>>>>> the app, please write kde-soc-managem...@kde.org and tell us what
>>>>>>>> google-connected email address you want us in use. Also, subscribe to
>>>>>>>> KDE-Soc-Mentor mail list:
>>>>>>>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>>>>>>>
>>>>>>>> If you're already a mentor, you can mark "I want to mentor" on the
>>>>>>>> proposal page. I believe that we can still comment on the draft and the
>>>>>>>> student can read it, although we are not allowed to consider the draft 
>>>>>>>> in
>>>>>>>> our consideration of which students to accept.
>>>>>>>>
>>>>>>>> All the best,
>>>>>>>>
>>>>>>>> Valorie
>>>>>>>>
>>>>>>>
>>>>
>>>> --
>>>> http://about.me/valoriez
>>>>
>>>>
>>>>
>>
>> --
>> http://about.me/valoriez
>>
>>
>>

-- 
http://about.me/valoriez

Re: Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

Cool. Now I need mentors to step up, or suggestions for whom to ask. If you
are interested and are all signed up as a mentor, you know what to do.

If not, write to kde-soc-managem...@kde.org and tell us your
google-connected email address so you can be invited to the GSoC webapp,
and subscribe to the KDE-Soc-Management ML:
https://mail.kde.org/mailman/listinfo/kde-soc-mentor

Valorie

On Wed, Apr 10, 2019 at 1:01 AM Tomaz Canabrava  wrote:

> Sounds reasonable. The fact that he’s in masters also counts as he can do
> what he is talking about.
>
>
> Em qua, 10 de abr de 2019 às 09:37, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> escreveu:
>
>> Thank you, Tomaz. <3
>>
>> On Wed, Apr 10, 2019 at 12:34 AM Tomaz Canabrava 
>> wrote:
>>
>>> Let me look, give me 30 minutes.
>>>
>>>
>>> Em qua, 10 de abr de 2019 às 09:30, Valorie Zimmerman <
>>> valorie.zimmer...@gmail.com> escreveu:
>>>
>>>>
>>>>
>>>> On Wed, Apr 10, 2019 at 12:25 AM Tomaz Canabrava 
>>>> wrote:
>>>>
>>>>> He contacted me and participated in a qt course I presented at his
>>>>> university. Inward unsure if he was going to apply.
>>>>>
>>>>
>>>> OK, good to hear that there was some contact. I need some ideas about
>>>> who can look at this proposal and see if there is any chance of success.
>>>>
>>>> Valorie
>>>>
>>>>
>>>>> Em qua, 10 de abr de 2019 às 04:24, Valorie Zimmerman <
>>>>> valorie.zimmer...@gmail.com> escreveu:
>>>>>
>>>>>> I'm unsure if this applicant contacted the KDE Edu team in advance,
>>>>>> but I heard nothing from them until seeing this proposal this morning.
>>>>>>
>>>>>> The short description of the proposal:
>>>>>>
>>>>>> "As a student, I use graphs in almost everything related to my
>>>>>> master’s research. Graph Theory is a great mathematical tool for
>>>>>> programmers and mathematicians, as it facilitates some computational
>>>>>> problems resolution and modelling. However, is not always easy to
>>>>>> understand the underlying theory and algorithms.
>>>>>>
>>>>>> "Rocs (https://kde.org/applications/education/rocs) is a Graph
>>>>>> Theory IDE created in January of 2010, with new updates still being
>>>>>> committed almost every month, currently in the KDE repositories, designed
>>>>>> for lecturers, students and researchers. It is composed of a visual data
>>>>>> structure and a powerful scripting engine in Javascript. Though useful 
>>>>>> for
>>>>>> creating simple graphs, it is still lacking the tools to simplify the
>>>>>> creation of bigger graphs, and also of basic graph theory algorithms for
>>>>>> beginners. Another improvement it should have is a step by step execution
>>>>>> system, in order to fully comprehend the algorithms and facilitate
>>>>>> debugging."
>>>>>>
>>>>>> If you are interested in mentoring but have not yet been invited to
>>>>>> the app, please write kde-soc-managem...@kde.org and tell us what
>>>>>> google-connected email address you want us in use. Also, subscribe to
>>>>>> KDE-Soc-Mentor mail list:
>>>>>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>>>>>
>>>>>> If you're already a mentor, you can mark "I want to mentor" on the
>>>>>> proposal page. I believe that we can still comment on the draft and the
>>>>>> student can read it, although we are not allowed to consider the draft in
>>>>>> our consideration of which students to accept.
>>>>>>
>>>>>> All the best,
>>>>>>
>>>>>> Valorie
>>>>>>
>>>>>
>>
>> --
>> http://about.me/valoriez
>>
>>
>>

-- 
http://about.me/valoriez

Re: Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

Thank you, Tomaz. <3

On Wed, Apr 10, 2019 at 12:34 AM Tomaz Canabrava  wrote:

> Let me look, give me 30 minutes.
>
>
> Em qua, 10 de abr de 2019 às 09:30, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> escreveu:
>
>>
>>
>> On Wed, Apr 10, 2019 at 12:25 AM Tomaz Canabrava 
>> wrote:
>>
>>> He contacted me and participated in a qt course I presented at his
>>> university. Inward unsure if he was going to apply.
>>>
>>
>> OK, good to hear that there was some contact. I need some ideas about who
>> can look at this proposal and see if there is any chance of success.
>>
>> Valorie
>>
>>
>>> Em qua, 10 de abr de 2019 às 04:24, Valorie Zimmerman <
>>> valorie.zimmer...@gmail.com> escreveu:
>>>
>>>> I'm unsure if this applicant contacted the KDE Edu team in advance, but
>>>> I heard nothing from them until seeing this proposal this morning.
>>>>
>>>> The short description of the proposal:
>>>>
>>>> "As a student, I use graphs in almost everything related to my master’s
>>>> research. Graph Theory is a great mathematical tool for programmers and
>>>> mathematicians, as it facilitates some computational problems resolution
>>>> and modelling. However, is not always easy to understand the underlying
>>>> theory and algorithms.
>>>>
>>>> "Rocs (https://kde.org/applications/education/rocs) is a Graph Theory
>>>> IDE created in January of 2010, with new updates still being committed
>>>> almost every month, currently in the KDE repositories, designed for
>>>> lecturers, students and researchers. It is composed of a visual data
>>>> structure and a powerful scripting engine in Javascript. Though useful for
>>>> creating simple graphs, it is still lacking the tools to simplify the
>>>> creation of bigger graphs, and also of basic graph theory algorithms for
>>>> beginners. Another improvement it should have is a step by step execution
>>>> system, in order to fully comprehend the algorithms and facilitate
>>>> debugging."
>>>>
>>>> If you are interested in mentoring but have not yet been invited to the
>>>> app, please write kde-soc-managem...@kde.org and tell us what
>>>> google-connected email address you want us in use. Also, subscribe to
>>>> KDE-Soc-Mentor mail list:
>>>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>>>
>>>> If you're already a mentor, you can mark "I want to mentor" on the
>>>> proposal page. I believe that we can still comment on the draft and the
>>>> student can read it, although we are not allowed to consider the draft in
>>>> our consideration of which students to accept.
>>>>
>>>> All the best,
>>>>
>>>> Valorie
>>>>
>>>

-- 
http://about.me/valoriez

Re: Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

On Wed, Apr 10, 2019 at 12:25 AM Tomaz Canabrava  wrote:

> He contacted me and participated in a qt course I presented at his
> university. Inward unsure if he was going to apply.
>

OK, good to hear that there was some contact. I need some ideas about who
can look at this proposal and see if there is any chance of success.

Valorie


> Em qua, 10 de abr de 2019 às 04:24, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> escreveu:
>
>> I'm unsure if this applicant contacted the KDE Edu team in advance, but I
>> heard nothing from them until seeing this proposal this morning.
>>
>> The short description of the proposal:
>>
>> "As a student, I use graphs in almost everything related to my master’s
>> research. Graph Theory is a great mathematical tool for programmers and
>> mathematicians, as it facilitates some computational problems resolution
>> and modelling. However, is not always easy to understand the underlying
>> theory and algorithms.
>>
>> "Rocs (https://kde.org/applications/education/rocs) is a Graph Theory
>> IDE created in January of 2010, with new updates still being committed
>> almost every month, currently in the KDE repositories, designed for
>> lecturers, students and researchers. It is composed of a visual data
>> structure and a powerful scripting engine in Javascript. Though useful for
>> creating simple graphs, it is still lacking the tools to simplify the
>> creation of bigger graphs, and also of basic graph theory algorithms for
>> beginners. Another improvement it should have is a step by step execution
>> system, in order to fully comprehend the algorithms and facilitate
>> debugging."
>>
>> If you are interested in mentoring but have not yet been invited to the
>> app, please write kde-soc-managem...@kde.org and tell us what
>> google-connected email address you want us in use. Also, subscribe to
>> KDE-Soc-Mentor mail list:
>> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>>
>> If you're already a mentor, you can mark "I want to mentor" on the
>> proposal page. I believe that we can still comment on the draft and the
>> student can read it, although we are not allowed to consider the draft in
>> our consideration of which students to accept.
>>
>> All the best,
>>
>> Valorie
>>
>

New GSoC proposal for KDE Partition Manager

[Valorie Zimmerman]

Title: Finish mdraid implementation and implement dmraid

Project Goals:
Finish implementation of mdraid and polish current support

Most of the features such scanning, creating and manipulating software raid
have been completed. My first goal would be to finish resizing of raids and
then working on udev bugs. I am currently understanding the software raid
implementation in raid-support branch and will polish the software raid
implementation.

2.   Implementing fakeRAID with the help of dmraid

Fake RAID is essentially software RAID provided by the BIOS on the
motherboard, however, it has none of the benefits of Software RAID and none
of the benefits of Hardware RAID, hence, Fake RAID. It works along the
device mapper to discover and manipulate ATA RAID devices created by
controllers BIOS. My goal in this project is to offer some basic
functionalities for it, such as displaying, creating, erasing and
manipulating partitions inside of these volumes. Fake raid is accessed with
dmraid utility

==

In my opinion, this is a very slim proposal, but If any KPM devel is
willing to mentor, I would appreciate you giving it a look and talking a
bit with the student. While I hope that the student has already been in
touch with the team, it's my guess that they have not, or we would have had
a draft to comment on.

All the best,

Valorie

Last minute GSoC proposal with Roks - anyone interested in mentoring?

[Valorie Zimmerman]

I'm unsure if this applicant contacted the KDE Edu team in advance, but I
heard nothing from them until seeing this proposal this morning.

The short description of the proposal:

"As a student, I use graphs in almost everything related to my master’s
research. Graph Theory is a great mathematical tool for programmers and
mathematicians, as it facilitates some computational problems resolution
and modelling. However, is not always easy to understand the underlying
theory and algorithms.

"Rocs (https://kde.org/applications/education/rocs) is a Graph Theory IDE
created in January of 2010, with new updates still being committed almost
every month, currently in the KDE repositories, designed for lecturers,
students and researchers. It is composed of a visual data structure and a
powerful scripting engine in Javascript. Though useful for creating simple
graphs, it is still lacking the tools to simplify the creation of bigger
graphs, and also of basic graph theory algorithms for beginners. Another
improvement it should have is a step by step execution system, in order to
fully comprehend the algorithms and facilitate debugging."

If you are interested in mentoring but have not yet been invited to the
app, please write kde-soc-managem...@kde.org and tell us what
google-connected email address you want us in use. Also, subscribe to
KDE-Soc-Mentor mail list:
https://mail.kde.org/mailman/listinfo/kde-soc-mentor

If you're already a mentor, you can mark "I want to mentor" on the proposal
page. I believe that we can still comment on the draft and the student can
read it, although we are not allowed to consider the draft in our
consideration of which students to accept.

All the best,

Valorie

-- 
http://about.me/valoriez

Re: New KDE-Edu proposal not on the Ideas list -- are there mentors?

[Valorie Zimmerman]

Thanks, Tomaz! When you feel confident that she can be successful in the
project she proposes, mark "I want to mentor" and I'll star the proposal.

Gosh I love this KDE community and how we support and rally around students.

Valorie

On Sun, Apr 7, 2019 at 4:54 AM Tomaz Canabrava  wrote:

> I’m talking to her and apol.
> I’ll step up to be her mentor.
>
>
> Em dom, 7 de abr de 2019 às 05:28, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> escreveu:
>
>> Hi everyone, today we had a new proposal called "Improving Khipu and
>> Analitza." Since this was not put up as an Idea by KDE-Edu, there are not
>> now mentors. If this is a good student and proposal, please consider
>> stepping up to mentor or co-mentor. The student is Karina Pereira Passos
>> who has contributed before: https://phabricator.kde.org/p/karinapassos/.
>> Ideas of who else to ask are also welcome.
>>
>> If you are interested in becoming a mentor please reply to me privately
>> telling me your google-connected email, so that I can invite you to the
>> webapp. You will also need to subscribe to the KDE-Soc-Mentor mail list.
>>
>> Thanks for your attention and interest,
>>
>> Valorie
>>
>>

-- 
http://about.me/valoriez

New KDE-Edu proposal not on the Ideas list -- are there mentors?

[Valorie Zimmerman]

Hi everyone, today we had a new proposal called "Improving Khipu and
Analitza." Since this was not put up as an Idea by KDE-Edu, there are not
now mentors. If this is a good student and proposal, please consider
stepping up to mentor or co-mentor. The student is Karina Pereira Passos
who has contributed before: https://phabricator.kde.org/p/karinapassos/.
Ideas of who else to ask are also welcome.

If you are interested in becoming a mentor please reply to me privately
telling me your google-connected email, so that I can invite you to the
webapp. You will also need to subscribe to the KDE-Soc-Mentor mail list.

Thanks for your attention and interest,

Valorie

Purpose GSoC mentors please

[Valorie Zimmerman]

Please login to the GSoC webapp, go to Proposals, and find your possible
student's proposal. Click on "Read in Docs" and comment on that draft.
Afterwards, comment to the other mentors and admins in the webapp (scroll
down). Today.

Time is of the essence. The student and I both need feedback not just in
your public channels, but there in the app. The student needs to have their
final uploaded by the 9th of this month, which is Google's cutoff, not
ours. There are no late admissions.

Valorie

Re: Introduction for GSoC: Koundinya

[Valorie Zimmerman]

Hello Venkata Rama Koundinya Lanka,

On Mon, Apr 1, 2019 at 10:22 PM Venkata Rama Koundinya Lanka <
venkataramakoundinya1...@gmail.com> wrote:

> Hi everyone,
>
> My name is Venkata Rama Koundinya Lanka. I am a final year engineering
> student from India. My key skills include android development, C, C++, and
> Qt. I would like to contribute to the project porting krita to android for
> GSoC 2019.
>
> Yours Sincerely,
> Venkata Rama Koundinya Lanka
>
>
Have you uploaded your proposal to the GSoC webapp? If so, what is your
nickname there? I hope that you've already been working with the Krita team
on your proposal.

A reminder that the deadline for uploading final proposals is the 9th, and
there are *no* late applications or uploads accepted by Google.

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

Is the GSoC Ideas list page still open? YES

[Valorie Zimmerman]

We got a question today about the Ideas page -
https://community.kde.org/GSoC/2019/Ideas - is open for more ideas. YES!

We were accepted as a GSoC org and we are open for business. Prepare to be
inundated by students wondering how to make themselves useful to you;
please make them welcome and help them find something productive to do.

If you see any way to improve our GSoC pages or other suggestions, please
pitch in! If you want to mentor and have not yet subscribed to the mentor
list, please do that now, and also ask to be invited to the webapp. You
should also be listed somewhere on that Ideas page as a mentor.

Please write to kde-soc-managem...@kde.org if you need help with any of
this.

All the best,

Valorie, for KDE Student Programs

-- 
http://about.me/valoriez

Re: GSoC 2019: Project Proposal for a New Game

[Valorie Zimmerman]

On Tue, Feb 5, 2019 at 3:24 AM Pranam Lashkari 
wrote:

> On Tue, Feb 5, 2019 at 4:43 PM Stefan Derkits  wrote:
>
>> Hi,
>>
>> You can also write the full proposal and then find a mentor, maybe it's
>> easier that way around.
>>
>
> Surely, I'll look forward to it. Thank you for your help.
>

Hi Pranan, in KDE we work in teams, so please take this discussion to KDE
Games. That doesn't mean that your mentor *must* be part of the KDE Games
team, but you will need buy-in from the team, because the team as a whole
takes care of the whole suit of games. Needing a mentor isn't about how
good your coding skills are -- it's about who are the experts you might
need to consult about a particular  problem? How is your code fitting into
the team's coding style? Is the way you are managing your project on the
right track? Even expert coders do better with the feedback of the team and
particular experts.

Even our coding stars submit their patches and new bits of code for review,
and our codebase is the better for rigorous review.

Please embed yourself into the KDE Games team and start helping them with
fixing some bugs, triaging bug reports, or whatever else they might ask of
you. Those are the folks who will decide whether or not they want to work
with you, so work with them now.

All the best,

Valorie

Re: GSoC Ideas page

[Valorie Zimmerman]

On Wed, Jan 30, 2019 at 1:21 PM Simon Redman  wrote:

> Hi Valorie,
>
> Thanks for organizing this!
>
> I have just added myself as the KDE Connect mentor for the Windows port:
> https://community.kde.org/GSoC/2019/Ideas#KDE_Connect_for_Windows_port
>
> What is the skill level expected of students? Is it reasonable to assume
> they should be able to figure out reasonably complicated problems on their
> own, like getting Windows set up for development?
>
> Thanks,
> Simon
>
> On 1/30/19 12:51 AM, Valorie Zimmerman wrote:
>
> Hi all, tonight I've moved the project headings which were empty of ideas
> from the 2019 page. I pasted them into the end of last year's Ideas page
> [1] in case some of you (choqok, kopete, kdevelop, kgpg, kwin, peruse,
> plasma, wikitolearn) are going to add ideas late and want those headers
> back. I added all the relevant information I could find before opening up
> the page to ideas; I should have alphabetized them first!
>
> They are alphabetized them now [2]. Better late than never.
>
> A few ideas still have no mentors listed; please get that done now.
> (KDEConnect, LabPlot, Okular). TBD or "the team" are not good enough for
> our proposal!
>
> Reminder: our deadline is 6 February; less than a week. The org
> application is done except for the Ideas page.
>
> Valorie
>
> 1. https://community.kde.org/GSoC/2018/Ideas
> 2. https://community.kde.org/GSoC/2019/Ide
> <https://community.kde.org/GSoC/2019/Ideas>as
>
>
Hey Simon, thanks!

If you have a requirement for students like that, it seems to me it should
be added to the Idea. For most projects, getting a Win devel environment is
not important, so please mention it. If you read through the main GSoC page
[1] (and all propective mentors, please do), you will notice that we
*require* some KDE commits to be linked in the student proposals. That
means that the students have at least 1. a KDE identity, 2. a login to Phab
or Gitlab, 3. a checkout of the part of the codebase they will be working
with, te 4. the skill to upload a diff.

I think it's important, as you work with prospective students, to remind
them of these requirements and that this process is competitive. We can
work with kids who don't yet have all the skills they will need to complete
their projects, but they have to be willing to step up and show off their
skills before we can choose them for GSoC.

Experienced mentors will tell you that mentoring is work. Rewarding work,
but harder than you think it will be. For those of you that find
communication with students difficult, ensure that you have a backup mentor
who can help you with this part. Communication is about *half* of a
successful GSoC. Students need to know if they are heading in the right
direction, have their blind spots pointed out, and sometimes, be encouraged
when they feel lost. We can lose even brilliant students when the
communication isn't good, and that makes all of us feel bad.

Let's all of us communicate early and often! And that includes mentors and
admins, too. We admins are here for you mentors as well as the students.

PS: we could use another GSoC admin or two!

Valorie

1. https://community.kde.org/GSoC

GSoC Ideas page

[Valorie Zimmerman]

Hi all, tonight I've moved the project headings which were empty of ideas
from the 2019 page. I pasted them into the end of last year's Ideas page
[1] in case some of you (choqok, kopete, kdevelop, kgpg, kwin, peruse,
plasma, wikitolearn) are going to add ideas late and want those headers
back. I added all the relevant information I could find before opening up
the page to ideas; I should have alphabetized them first!

They are alphabetized them now [2]. Better late than never.

A few ideas still have no mentors listed; please get that done now.
(KDEConnect, LabPlot, Okular). TBD or "the team" are not good enough for
our proposal!

Reminder: our deadline is 6 February; less than a week. The org application
is done except for the Ideas page.

Valorie

1. https://community.kde.org/GSoC/2018/Ideas
2. https://community.kde.org/GSoC/2019/Ideas

-- 
http://about.me/valoriez

Re: GSoC org application time

[Valorie Zimmerman]

Now I see that I neglected the link to the Ideas page. :(

Here it is: https://community.kde.org/GSoC/2019/Ideas

On Wed, Jan 16, 2019 at 11:24 PM Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:

> Hi all, I've started our application.
>
> The deadline for applications: February 6, 2019 at 12:00 (PST).
>
> By the deadline, we need to have an absolutely *splendid* Ideas page (1).
> Before the deadline, I'll remove all the placeholders such as teams with no
> Ideas listed, or ideas with no mentors listed. Teams which have
> participated in the past but are empty still: KDE Partition
> Manager, Kopete, Choqok, Peruse, KGpg, KWin, Plasma, WikiToLearn, KDevelop
> and Xdg-desktop-portal-kde.
>
> So far, I'm the only admin listed. Anyone game to help administer this
> year? It works well when we have a team, so that any of us can have an
> off-week (or week off) sometimes. There are two aspects to being an org
> admin: working with mentors, and working with students. "Paperwork" is a
> very small part of the job.
>
> The mentor work is all about helping mentors and their teams work well
> with their student. Some need coaching on communication, poking to do their
> evaluations, etc.
>
> The student work in the beginning is coaching students in getting
> involved, creating their devel environment, helping them craft their
> proposals and get linked into the teams, and so forth. Later, it will be
> helping them through the tough spots, especially when their mentors aren't
> being helpful, or even helping withdraw gracefully.
>
> We need at least one more admin, and can have up to five. Please write to
> kde-soc-managem...@kde.org (not me personally please!) about your
> interest.
>
> All the best,
>
> Valorie
>
> --
> http://about.me/valoriez
>
>
>

-- 
http://about.me/valoriez

Fwd: Request from Finland

[Valorie Zimmerman]

Hi all, is there a better list for this inquiry? If so, please forward it
there.

Valorie

-- Forwarded message -
From: edward krogius 
Date: Sat, Jan 12, 2019 at 9:04 AM
Subject: Request from Finland
To: 

Hello !

In Finland the upper secondary
national examination board
provides an exam with KDEutilities
KCalc calculator. Now there is a
demand among students to
get a standalone version of the
calculator to run on their laptop
operating systems.

How can we get that to work?

STEM teacher
Edward Krogius
edward.krog...@eduvantaa.fi

Google Summer of Code Ideas

[Valorie Zimmerman]

Hi folks, a few teams have added their ideas to
https://community.kde.org/GSoC/2019/Ideas but many have not yet done so.
Those of you reading this plea have participated in the past but do not
have ideas posted yet.

PLEASE get this done before the end of the year! We need to submit our
application  15 January 2019 which is about one month away.

So I beg of you, please get your ideas up soon.

Valorie

-- 
http://about.me/valoriez

Ideas for GSoC

[Valorie Zimmerman]

Hi folks, a few teams have added their ideas to
https://community.kde.org/GSoC/2019/Ideas but many have not yet done so.
PLEASE get this done before the end of the year! We need to submit our
application January 15 2019 which is about one month away.

Please don't make me write to every application development list and beg.

Valorie

-- 
http://about.me/valoriez

Fwd: Google Summer of Code

[Valorie Zimmerman]

Oops, forwarding because I forgot to CC KDE-devel too.
To: KDE community 
Cc: Kde Soc Mentor 

I know it's only December, but GSoC is beginning earlier this year on the
organization end, at least. Now is the time to join the mentor's list if
you may mentor, and for all teams who want to mentor to add their ideas to
the Ideas page:

https://community.kde.org/GSoC/2019/Ideas

Please also take a look at the main GSoC page:
https://community.kde.org/GSoC and see if it needs any changes. Please
discuss those with us on kde-soc-men...@kde.org.

We need to submit our application January 15 2019 which is only 5 or so
weeks away! So please get those Ideas filled in *now*.

Thanks,

Valorie

PS: Please feel free to forward along to your team mail list to start
discussion about Ideas if that would be useful.

D16588: Change package manager icons to emblems

[Valorie Zimmerman]

valorie added a comment.


  Could not Muon be updated in this way as well? It now uses a package icon for 
all packages which seems a waste of space.

REPOSITORY
  R266 Breeze Icons

BRANCH
  package-manager-icons (branched from master)

REVISION DETAIL
  https://phabricator.kde.org/D16588

To: ndavis, #vdg, ngraham
Cc: valorie, bruns, ngraham, #vdg, kde-frameworks-devel, michaelh

D16395: Update the "About KDE" text

[Valorie Zimmerman]

valorie added a comment.


  My only suggestion: KDE creates the efficient, powerful Plasma desktop 
environment, hundreds of high-quality applications and the many software 
libraries that support them.
  
  Past tense makes the present version seem static.

REPOSITORY
  R263 KXmlGui

REVISION DETAIL
  https://phabricator.kde.org/D16395

To: ngraham, #vdg, #plasma, #frameworks, #kde_applications, #kde_promo
Cc: valorie, davidc, xyquadrat, rizzitello, ltoscano, aspotashev, abetts, 
kde-frameworks-devel, michaelh, ngraham, bruns

Google Code-in

[Valorie Zimmerman]

Hello folks, we are still very low on mentors (only 11 have signed up so
far) and tasks: about 45 at last glance.

Please get with your teams and find some more mentors, and get creative
with some tasks. Assign writing some unit tests! Get some bug reports
tested! Help kids get your application installed in Windows, Mac or Linux!

Look at https://community.kde.org/GCi for guidelines and ideas.

If you have not yet subscribed to KDE-Soc-Mentor ML please do that, and
then ask for an invite to the webapp, and put in your tasks! The contest
starts for student October 23rd 2018.

Let's get ready!

Valorie

-- 
http://about.me/valoriez

Google Code-in

[Valorie Zimmerman]

Hello folks, GCi is much earlier this year, so we need to gather tasks NOW.
The org application period is now open, and I see a good start on tasks on
https://community.kde.org/GCi. However, they are all from GCompris!

Please look over their tasks and copy some for your own project!

Yes, this contest is quite a bit of work, however this year it will not run
through the Christmas holidays which should make life easier. We've had
time to rest from Akademy travel so it's time to gear up and get some bugs
fixed, unit tests written, wiki pages composed, and get some testing done!

Please join the kde-soc-mentor list if you plan to mentor, and ask in
#kde-soc-admin or write to kde-soc-managem...@kde.org if you are willing to
help out with administration for the contest.

All the best,

Valorie

-- 
http://about.me/valoriez

Welcome GSoC students!

[Valorie Zimmerman]

On the Dot: 
https://dot.kde.org/2018/05/18/welcome-our-new-google-summer-code-students

Please spread via social media.

Valorie

-- 
http://about.me/valoriez

Re: Latte Dock and tangerine font

[Valorie Zimmerman]

This discussion is icky to me.

1. I do not want to login to Github to discuss a KDE project

2. We are not engaging with the authors and maintainer to make this
application fully within the KDE community (which includes licensing)

3. The discussion is about licensing instead of helping to improve the logo
by bringing in the VDG. The VDG just created a kickass logo for Falkon;
surely they can make something better than the Latte Dock present logo?

Valorie

On Tue, Feb 27, 2018 at 6:45 AM, Michail Vourlakos 
wrote:

> Jonathan can you please participate at:
> https://github.com/psifidotos/Latte-Dock/issues/884#issuecomment-368876977
>
> for this?
>
> the ubuntu member I think responded there...
>
> 2018-02-27 14:52 GMT+02:00 Jonathan Riddell :
>
>> On 27 February 2018 at 09:24, Michail Vourlakos 
>> wrote:
>> > Today I received from RikMills that Latte was rejected from ubuntu
>> because
>> > it contains an OPL-licensed font (tangerine).
>> >
>> > The discussion is at: https://github.com/psifidotos/
>> Latte-Dock/issues/884
>> >
>> > The font is used just for a label in the configuration window to draw
>> the
>> > "Latte"  text at the top-left corner. I thought that an alternative
>> could be
>> > to just screenshot the label in a png and use that one and drop totally
>> the
>> > tangerine font distrubution through Latte code...
>> >
>> > Do you have any ideas what we can do for this and if this is acceptable
>> for
>> > OPL?
>>
>> Font licencing is a bit of a quagmire but I really don't see any issue
>> here.
>>
>> The font is freely licenced and .ttf can be considered preferred
>> modifiable form so there's no freedom issue.
>>
>> He says "Source embeds and uses at runtime a GPL-incompatible
>> (OPL-Licensed) font; "  but I see no embedding happening, it just
>> ships the file which doesn't make it a derived work.  Loading a font
>> file at runtime is done by every GUI program very often, it doesn't
>> make it a derived work so there's no effect on copyleft licencing
>> requirements.
>>
>> I recommend Ubuntu discuss this with their archive admins to see why
>> they consider it a derived work.  I am an Ubuntu archive admin and can
>> take part in that conversation if wanted.  If that doesn't get
>> anywhere then play a political workaround and just upload it without
>> the .ttf font, I presume the text where it's used will just fall back
>> to some other font.  Maybe Latte-dock code can be changed to
>> explicitly fall back to a generic cursive font if it doesn't find it
>> but only if there's a desire to go out of the way for incorrectly
>> applied rules.
>>
>> Jonathan
>>
>
>


-- 
http://about.me/valoriez

Now is the time for all prospective GSoC mentors to gear up!

[Valorie Zimmerman]

Hello everyone, our application to become a part of Google Summer of Code
has been accepted! So, if you are going to become a mentor, now is the time
to:

1. Ensure you are subscribed to KDE-Soc-Mentor mail list [1].

2. Write to kde-soc-men...@kde.org to be invited to the GSoC web app. This
way we can ensure that one of us invites you. All you need is a
google-enabled email account.

The email from the OSPO says,

"Inviting Mentors to your Org

"Org Admins should now be sending potential mentors invitations to be a
part of their organization. The mentor will need to click the link in the
email they receive to accept the invitation and create their account. All
mentors must be invited by an Org Admin."

3. Click the link in that email to get into the webapp and set up your
account there. None of your information from previous years is saved.

What we org admins need is all mentors to complete all three steps within
the next few days.

Thanks!

Valorie

1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor

-- 
http://about.me/valoriez

Re: KDE and Google Summer of Code 2018

[Valorie Zimmerman]

I'm very discouraged to see so little movement on this. After skipping GCi
this past fall, are we now also considering skipping GSoC? Or downsizing
the number of students we are mentoring?

Without Ideas we will not get students. More important, we must complete
the Org application soon, and the Ideas page is the core of that
application.

This is good for your team and your project, in the long run. It brings in
new contributors and fresh ideas.

If you need some guidance, please read
https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html

I should have linked to it for the last email.

Valorie

On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:

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

Re: Looking for mentor for new KDE developer

[Valorie Zimmerman]

Hi, adding kde-community as this is actually a community matter as well as
a -devel issue.

On Sun, Jan 7, 2018 at 3:15 PM, Albert Astals Cid  wrote:

> El dilluns, 8 de gener de 2018, a les 0:07:00 CET, Albert Astals Cid va
> escriure:
> > El dilluns, 8 de gener de 2018, a les 8:15:54 CET, Ben Cooksley va
> escriure:
> > > Hi all,
> > >
> > > Just following up on this - is there anyone who is looking into
> > > helping Christian here?
> >
> > I don't understand why we're forcing this "he needs a mentor". As Dominik
> > says, he seems to know stuff since he actually ported the code.
> >
> > If he needs help with "kde bureaucracy stuff" it means that we actually
> need
> > to improve our onboarding documentation, so instead of giving him someone
> > he can ask things in private, we should try to improve that
> documentation,
> > or at least answer the questions in this list so they are public and can
> be
> > referenced in the future.
>

So this new contributor would be a *perfect* person to point out kinks in
our onboarding documentation. For instance, that it is hard to find, where
it is incomplete or out-of-date. In line with our new push (
https://phabricator.kde.org/T7116) please Albert if you are going to
mentor, gently push for that while the pain is still fresh for our new
contributor.

All other mentors, formal or informal, please also help out here.
Old-timers already know some or all, so are not as helpful in finding those
pain-points. For those, beginners have the super-powers we need!


> > I will be happy to answer any question he may have related to that (and
> > hopèfully I know the question)
> >
> > Regarding the "In addition, translations would need to be imported into
> our
> > infrastructure, or recovered from our SVN history. That needs
> intervention
> > by our i18n experts, possibly before the code is imported." that Nicolás
> > mentioned, yes, that needs the i18n team helping, but that's what the
> kde-
> > i18n-doc mailing list is for, unless the mentor was part of the i18n team
> > that wouldn't get solved anyway.
>
> P.S: I guess that was my long way of saying "i can be his mentor if we
> really
> need to write someone elses name in the 'who to blame if he screws up'
> list".
>
> Cheers,
>   Albert
>
> >
> > Cheers,
> >   Albert
> >
> > > Thanks,
> > > Ben Cooksley
> > > KDE Sysadmin
>

Thank you for stepping up, Albert. <3

Valorie

-- 
http://about.me/valoriez

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

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

Google Summer of Code -- now!

[Valorie Zimmerman]

Hello folks, I know that some of you are just beginning to mentor your
Season of KDE students. However, Google has made the prep phase for GSoC
even earlier this year, so it is time to start NOW.

For more information: https://g.co/gsoc/faq
More: http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/ and
https://google.github.io/gsocguides/mentor

I would strongly suggest talking with your team and finding out who can
mentor this year, and what your team would like to propose for the Ideas
page. The sooner we get our ducks in a row, the better. *The strength of
our Ideas page is the most important part of our organization application.*

If you will be mentoring GSoC this year, please ensure that you are
subscribed to KDE-Soc-Mentor list. You'll need to ping one of us admins if
you aren't soon accepted. We don't allow any students on that list, and
sometimes can't tell who is who. I can't stress strongly enough -- every
mentor must be subscribed. You will be invited to the GSoC app after (if!)
we are accepted. Once again this year we'd like two mentors per student.

People interested in helping to administer this year should join
#kde-soc-admin (IRC or matrix-only) and the KDE-Soc-Management ml after
discussing how you can contribute with the present admins.

All the best,

Valorie

-- 
http://about.me/valoriez

Re: Frameworks release schedule?

[Valorie Zimmerman]

On Wed, Oct 25, 2017 at 1:44 AM, Harald Sitter <sit...@kde.org> wrote:
> On Wed, Oct 25, 2017 at 10:35 AM, laurent Montel <mon...@kde.org> wrote:
>> Hi,
>> I send this email to kde-frameworks-devel
>>
>> It's the correct ML for having an answer about it
>>
>> Regards.

Hi Laurent, I thought that frameworks-devel was being deprecated but I
guess I'm out of the loop. So thanks.

>> Le mercredi 25 octobre 2017, 09:29:58 CEST Valorie Zimmerman a écrit :
>>> Hello folks, with my Kubuntu release manager hat on, I was filling in
>>> the calendar for the next 6 months. For Frameworks, this page:
>>> https://community.kde.org/Schedules/Frameworks is now on a provisional
>>> schedule - 5.40 (expected) Sat November 4th, 2017 for tagging,
>>> (expected) Sat November 11th, 2017.
>>>
>>> Is the schedule for the next 6 months still undecided, or has the wiki
>>> page just not been filled in yet?
>
> "... and so on. Until further notice: tagging happens the first
> saturday of every month, and the public release is one week later."
>
> That generally holds true unless something causes or needs an
> extraordinary delay (which in the past has never been more than a
> couple of days).
>
> HS

Thanks Harald!

Valorie

-- 
http://about.me/valoriez

Re: Frameworks release schedule?

[Valorie Zimmerman]

On Wed, Oct 25, 2017 at 1:44 AM, Harald Sitter <sit...@kde.org> wrote:
> On Wed, Oct 25, 2017 at 10:35 AM, laurent Montel <mon...@kde.org> wrote:
>> Hi,
>> I send this email to kde-frameworks-devel
>>
>> It's the correct ML for having an answer about it
>>
>> Regards.

Hi Laurent, I thought that frameworks-devel was being deprecated but I
guess I'm out of the loop. So thanks.

>> Le mercredi 25 octobre 2017, 09:29:58 CEST Valorie Zimmerman a écrit :
>>> Hello folks, with my Kubuntu release manager hat on, I was filling in
>>> the calendar for the next 6 months. For Frameworks, this page:
>>> https://community.kde.org/Schedules/Frameworks is now on a provisional
>>> schedule - 5.40 (expected) Sat November 4th, 2017 for tagging,
>>> (expected) Sat November 11th, 2017.
>>>
>>> Is the schedule for the next 6 months still undecided, or has the wiki
>>> page just not been filled in yet?
>
> "... and so on. Until further notice: tagging happens the first
> saturday of every month, and the public release is one week later."
>
> That generally holds true unless something causes or needs an
> extraordinary delay (which in the past has never been more than a
> couple of days).
>
> HS

Thanks Harald!

Valorie

-- 
http://about.me/valoriez

Frameworks release schedule?

[Valorie Zimmerman]

Hello folks, with my Kubuntu release manager hat on, I was filling in
the calendar for the next 6 months. For Frameworks, this page:
https://community.kde.org/Schedules/Frameworks is now on a provisional
schedule - 5.40 (expected) Sat November 4th, 2017 for tagging,
(expected) Sat November 11th, 2017.

Is the schedule for the next 6 months still undecided, or has the wiki
page just not been filled in yet?

Valorie

-- 
http://about.me/valoriez

Re: Add your tasks to the Idea page for GCI

[Valorie Zimmerman]

Yes, as I said in a previous mail, since no experienced admin stepped
up to take the lead, we'll not participate in GCi this year. We would
like to have a Season of KDE however.

So admins and mentors, please ensure you are on KDE-Soc-admin (this
includes former GSoC students!) and ping one of us admins if your
subscription request doesn't get accepted.

Valorie

On Sun, Oct 22, 2017 at 9:59 AM, JAZEIX Johnny  wrote:
> Hi,
>
> In the page, there are less than 20 tasks, does this mean KDE does not
> participate this year?
>
> Johnny
>
>
> On 10/17/17 04:44, vijay krishnavanshi wrote:
>>
>> Hi everyone,
>>
>> I have added few tasks on the GCI page and would like to ask other
>> interested mentors to add their ideas to the idea page.
>>
>> I have also reused some of the ideas from the last year GCI. We need
>> minimum 25 tasks for participation before the date 21st October so that time
>> for doing the required things for applying as an organization is reserved.
>> More ideas can be added later.
>>
>> Any sort of task can be added to the idea page if they are doable by
>> students of age group 13-17. It can include any type of tasks like design,
>> outreach, documentation, user interface, or code.
>>
>> I will continue adding ideas to the idea page.
>> Link: https://community.kde.org/GoogleCodeIn/2017/Ideas
>> Some ideas on the idea page added by me are not clear and need some
>> refactoring. I will do it later today.
>>
>> Regards,
>> Vijay Krishnavanshi
>
>
>



-- 
http://about.me/valoriez

Re: Participation of KDE in GCI 2018

[Valorie Zimmerman]

On Mon, Oct 23, 2017 at 1:04 AM, Bhushan Shah  wrote:
> Hey Vijay,
>
> On Mon, Oct 23, 2017 at 01:42:31AM +0530, vijay krishnavanshi wrote:
>> My opinion is that we should participate. Thoughts?
>
> My personal opinion about GCI this year is we should take a rest this
> year, this is due to two reasons,
>
> 1) Changed timelines of GSoC, we need to prepare and submit GSoC
> application much more early (even if after GCI ends, we don't have much
> of time in between0
>
> 2) Currently we need ~25 tasks for org applications but for the
> competition itself we need to have more like 50 unique and ~100 of total
> tasks IIRC at everytime, this is stressful task for both mentors and
> org-admins.. (I know people have promised to put tasks, and I trust
> them, but based on previous year's experience, often this effort is not
> enough to meet numbers, not blaming anyone).
>
> So yeah, my idea is, take a break this year, and use this time to
> document the junior jobs for next upcoming GCI and also others who want
> to work on KDE stuff out of this programs.
>
> (Also, just to be clear, I am not blocking anyone from participating.. I
> will be happy to help and mentor ( pun intended :P) willing org-admin..
>
> Thanks!

Given the fact that nobody has stepped up as lead admin on this, and
that the deadline for submitting is tomorrow, I think it is clear that
we will not participate this year.

I do want us to think about having a Season of KDE though. We have
lots of successful GSoC students who could co-mentor in a low-stress
environment, perhaps with one of their own mentors. Again, I am
willing to help administer, but not take the lead.

If you think this is a good idea and are willing to lead, let's talk
about this in the kde-soc-management mail list, and get a timeline and
rules hammered out.

Valorie

-- 
http://about.me/valoriez

Re: Is there interest in participating in Google Code-in this year?

[Valorie Zimmerman]

We don't need one mentor though, we need up to 50, and probably 400
tasks by January. We also need admins, and tasks NOW.

Thanks for offering, and of course you are good enough! -v

On Thu, Oct 12, 2017 at 3:40 PM, Lays Rodrigues
<laysrodriguessi...@gmail.com> wrote:
> Hi Valorie,
> I feel sorry to hear that.
> I could give it a try on the mentorship. I just don't know if I'm good
> enough to fill the purpose.
> Cheers
>
> On Thu, Oct 12, 2017 at 6:15 PM, Valorie Zimmerman
> <valorie.zimmer...@gmail.com> wrote:
>>
>> Hello folks, when I've written about GCi before this, I got few to no
>> replies. My feeling is that previous enthusiastic mentors are without
>> the energy and time to participate this year.
>>
>> Org applications are open, but unless I hear a swell of enthusiasm
>> here, I'm inclined to not apply.
>>
>> Thoughts?
>>
>> Valorie, for Student Programs admin team
> --
> Lays Rodrigues

Is there interest in participating in Google Code-in this year?

[Valorie Zimmerman]

Hello folks, when I've written about GCi before this, I got few to no
replies. My feeling is that previous enthusiastic mentors are without
the energy and time to participate this year.

Org applications are open, but unless I hear a swell of enthusiasm
here, I'm inclined to not apply.

Thoughts?

Valorie, for Student Programs admin team

-- 
http://about.me/valoriez

Re: time to review the goal proposals

[Valorie Zimmerman]

Wow, this is a GREAT lineup of possible goals. It will be difficult to
choose just one. On the other hand, we will have this list as a
resource when it's time to choose the next goal.

Great work!

On Mon, Oct 2, 2017 at 11:58 AM, Lydia Pintscher  wrote:
> Hey folks :)
>
> A little over a month ago I asked KDE contributors to submit proposals
> for goals that KDE should focus on over the next 3 to 4 years
> (http://blog.lydiapintscher.de/2017/08/20/evolving-kde-lets-set-some-goals/).
> I am very happy with the proposals that were submitted from different
> parts of the community. A lot of work and thought went into them and
> they all would make great focus areas for KDE over the coming years.
>
> From today until the end of October we will go into the next phase and
> refine these proposals. You can help make them ready for the vote in
> November. Read them and add your thoughts and ideas as a comment to
> the proposal. What do you like about the proposal? What can you add to
> the proposal? What isn’t ideal or worth pursuing? Are they ambitious
> but achievable? Is now the right time to push them forward? Are they
> specific enough so we know what everyone needs to do to move them
> forward? Are they bringing us closer to our vision of a world in which
> everyone has control over their digital life and enjoys freedom and
> privacy? Those are just some of the questions you should ask yourself
> and comments about. Then if you are interested in seeing the goal
> pursued add your name to the list of interested people. Even better,
> if you are willing to put work into a particular goal add your name to
> the list of people who want to work on the goal.
>
> Head over to the list of all submitted goal proposals and start
> reading: https://phabricator.kde.org/project/board/244/  ;-)
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors / KDE Community Working Group
> http://kde.org - http://open-advice.org



-- 
http://about.me/valoriez

17.08 Applications Release announcement text

[Valorie Zimmerman]

Hello folks, I noticed that there was not much progress on the release
announcement text, and I had some time last night, so I worked up an
announcement text based on those we've had in the past, and the notes
left by developers on
https://notes.kde.org/p/applications_17.08_new_features .

I found some of these notes rather difficult to make sense of, so
please check! Here is the text so you need not login to notes just to
see:

KDE Ships KDE Applications 17.08.0

Also available in:  English ...

August 17, 2017

KDE Applications 17.04 is here.

We have worked to make both the applications and the underlying
libraries more stable and easier to use. By ironing out wrinkles and
listening to your feedback, we have made the KDE Applications suite
less prone to glitches and much friendlier. Enjoy your new apps!

We're pleased that the following applications which were based on
kdelibs4 are now based on KDE Frameworks 5: kmag, kmousetool,
kgoldrunner, kigo, konquest, kreversi, ksnakeduel, kspaceduel,
ksudoku, kubrick, lskat, and umbrello. Thanks to the hard-working
developers who volunteered their time and work to make that happen.
Ktorrent, separately released, has also been updated to KDE Frameworks
5.

What's new in 17.08

Dolphin
Dolphin developers report that Dolphin now shows "Deletion Time" in
the Trash, and shows "Creation Time" if the OS supports it such as on
BSDs.

KIO-Extras
Kio-Extras now provides better support for Samba shares.

KAlgebra
The KAlgebra developers have worked on improving their Kirigami
front-end on the desktop, and implemented code completion.

KDE PIM

In KMailtransport, developers have reactivated akonadi transport
support, created plugins support, and recreated sendmail mail
transport support.
In SieveEditor, a lot of bugs in autocreate scripts have been fixed
and closed. Along with general bug-fixing, a regexp editor line-editor
has been added.
In KMail the ability to use an external editor has been recreated as a plugin.
The Akonadi-import-wizard now has the "convert all converter" as a
plugin, so that developers can create new converters easily.
Kdepim*apps* now depends on Qt5.7. Developers have fixed a lot of
compile errors on windows. All of kdepim does not compile on windows
yet but the developers have made big progress. To begin, the
developers created a craft-recipe for it. Much bug fixing has been
done to modernize code (c++11) Wayland support on Qt 5.9.
Kdepim-runtime adds a facebook resource.

Kdenlive
In Kdenlive, the team fixed the broken "Freeze effect." In recent
versions, it was impossible to change the frozen frame for the freeze
effect. Now a keyboard shortcut for Extract Frame feature is allowed.
Now the user can save screenshots of their timeline with a keyboard
shortcut, and a name is now suggested based on frame number
https://bugs.kde.org/show_bug.cgi?id=381325. Fix downloaded transition
lumas do not appear in interface:
https://bugs.kde.org/show_bug.cgi?id=382451. Fix audio clicks issue
(for now, requires building the dependency MLT from git until a MLT
release): https://bugs.kde.org/show_bug.cgi?id=371849.

Krfb
Developers have finished porting the X11 plugin to Qt5, and krfb is
working again using a X11 backend that is much faster than the Qt
plugin. There's a new Settings page, allowing the user to change
preferred framebuffer plugin.

Konsole
Konsole now allows unlimited scrollback to extend past 2GB (32bit)
limit. Now Konsole allows users to enter any location to store
scrollback files. Also, a regression was fixed, Konsole can once again
allow KonsolePart to call the Manage Profile dialog.

KAppTemplate
In KAppTemplate there is now an option to install new templates from
the filesystem. More templates have been removed from KAppTemplate and
instead integrated  into related products; ktexteditor plugin template
and kpartsapp template (ported to Qt5/KF5 now) have become part of KDE
Frameworks KTextEditor and KParts since 5.37.0. These changes should
simplify creation of templates in KDE applications.

https://community.kde.org/Applications/17.08_Release_Notes

Valorie

-- 
http://about.me/valoriez

NOW is the time to fill in the Ideas page for GSoC! Application deadline 9 Feb.

[Valorie Zimmerman]

Hello GSoC mentors, and teams supporting mentors,

We've asked for more time to get ramped up for GSoC, and so the
calendar has been moved back to early February. However, that means
that our Ideas page needs to be filled NOW, so that it can be taken
into consideration once the Org Applications are all in. 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, and ensure that it is comprehensive and accurate.

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. 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 thin our
proposals, and raise the quality.

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

Valorie

-- 
http://about.me/valoriez

NOW is the time to fill in the Ideas page for GSoC! Application deadline 9 Feb.

[Valorie Zimmerman]

Hello GSoC mentors, and teams supporting mentors,

We've asked for more time to get ramped up for GSoC, and so the
calendar has been moved back to early February. However, that means
that our Ideas page needs to be filled NOW, so that it can be taken
into consideration once the Org Applications are all in. 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, and ensure that it is comprehensive and accurate.

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. 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 thin our
proposals, and raise the quality.

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

Valorie

-- 
http://about.me/valoriez

NOW is the time to fill in the Ideas page for GSoC! Application deadline 9 Feb.

[Valorie Zimmerman]

Hello GSoC mentors, and teams supporting mentors,

We've asked for more time to get ramped up for GSoC, and so the
calendar has been moved back to early February. However, that means
that our Ideas page needs to be filled NOW, so that it can be taken
into consideration once the Org Applications are all in. 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, and ensure that it is comprehensive and accurate.

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. 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 thin our
proposals, and raise the quality.

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

Valorie

-- 
http://about.me/valoriez

Re: As Google Code-in ends, time to plan for Google Summer of Code

[Valorie Zimmerman]

On Fri, Jan 13, 2017 at 1:38 PM, Valorie Zimmerman
<valorie.zimmer...@gmail.com> wrote:
> I've just finished preparing the new Ideas page for 2017:
> https://community.kde.org/GSoC/2017/Ideas
>
> It is basically the same as every other year, and has no previous
> ideas on it. If you or your project plan to present a former idea
> again, click on the 2016 Ideas link, and copy/paste it into the 2017
> page as soon as possible.
>
> Of course, new ideas are welcome as well, as long as there are mentors
> available. We'll remove ideas with no mentor listed. Please ensure
> that there is contact information for each mentor.

Sorry for replying to myself again, but I just heard an excellent idea
on #gsoc - pictures! Terri said, "lots of code doesn't need it, but if
you're writing code for a visualizer? an image analyzer?  graphing
software? a game?"

I think a few screenshots where appropriate would spice up our Ideas
page quite a bit. I'm going to add it as an optional part to our
suggested format for Ideas.

> *Please* do no maintain a separate Ideas page which you present to
> students. We need one central place for Ideas, and rules and
> guidelines as well.
>
> Speaking of guidelines: please read over
> https://community.kde.org/GSoC and see what you think. We've tried to
> clarify the language and make our general expectations clear, as we
> think being upfront about our standards is one way to get better
> proposals and better students.

I'm serious about the above request. We need to all be on the same
page about the quality of work we expect, and that includes
communication from the students.

Valorie

-- 
http://about.me/valoriez

Re: As Google Code-in ends, time to plan for Google Summer of Code

[Valorie Zimmerman]

On Fri, Jan 13, 2017 at 1:38 PM, Valorie Zimmerman
<valorie.zimmer...@gmail.com> wrote:
> I've just finished preparing the new Ideas page for 2017:
> https://community.kde.org/GSoC/2017/Ideas
>
> It is basically the same as every other year, and has no previous
> ideas on it. If you or your project plan to present a former idea
> again, click on the 2016 Ideas link, and copy/paste it into the 2017
> page as soon as possible.
>
> Of course, new ideas are welcome as well, as long as there are mentors
> available. We'll remove ideas with no mentor listed. Please ensure
> that there is contact information for each mentor.

Sorry for replying to myself again, but I just heard an excellent idea
on #gsoc - pictures! Terri said, "lots of code doesn't need it, but if
you're writing code for a visualizer? an image analyzer?  graphing
software? a game?"

I think a few screenshots where appropriate would spice up our Ideas
page quite a bit. I'm going to add it as an optional part to our
suggested format for Ideas.

> *Please* do no maintain a separate Ideas page which you present to
> students. We need one central place for Ideas, and rules and
> guidelines as well.
>
> Speaking of guidelines: please read over
> https://community.kde.org/GSoC and see what you think. We've tried to
> clarify the language and make our general expectations clear, as we
> think being upfront about our standards is one way to get better
> proposals and better students.

I'm serious about the above request. We need to all be on the same
page about the quality of work we expect, and that includes
communication from the students.

Valorie

-- 
http://about.me/valoriez

As Google Code-in ends, time to plan for Google Summer of Code

[Valorie Zimmerman]

I've just finished preparing the new Ideas page for 2017:
https://community.kde.org/GSoC/2017/Ideas

It is basically the same as every other year, and has no previous
ideas on it. If you or your project plan to present a former idea
again, click on the 2016 Ideas link, and copy/paste it into the 2017
page as soon as possible.

Of course, new ideas are welcome as well, as long as there are mentors
available. We'll remove ideas with no mentor listed. Please ensure
that there is contact information for each mentor.

*Please* do no maintain a separate Ideas page which you present to
students. We need one central place for Ideas, and rules and
guidelines as well.

Speaking of guidelines: please read over
https://community.kde.org/GSoC and see what you think. We've tried to
clarify the language and make our general expectations clear, as we
think being upfront about our standards is one way to get better
proposals and better students.

Valorie

-- 
http://about.me/valoriez

As Google Code-in ends, time to plan for Google Summer of Code

[Valorie Zimmerman]

I've just finished preparing the new Ideas page for 2017:
https://community.kde.org/GSoC/2017/Ideas

It is basically the same as every other year, and has no previous
ideas on it. If you or your project plan to present a former idea
again, click on the 2016 Ideas link, and copy/paste it into the 2017
page as soon as possible.

Of course, new ideas are welcome as well, as long as there are mentors
available. We'll remove ideas with no mentor listed. Please ensure
that there is contact information for each mentor.

*Please* do no maintain a separate Ideas page which you present to
students. We need one central place for Ideas, and rules and
guidelines as well.

Speaking of guidelines: please read over
https://community.kde.org/GSoC and see what you think. We've tried to
clarify the language and make our general expectations clear, as we
think being upfront about our standards is one way to get better
proposals and better students.

Valorie

-- 
http://about.me/valoriez

GCi ending; Google Summer of Code preparations

[Valorie Zimmerman]

Hello folks,

Last fall, some of us attended the GSoC Mentor Summit, and one of the
things we asked for was more time between the beginning of the contest
to "Coding begins." It looks like we got our wish. I just looked at
the timeline, which says:

* January 19 16:00 UTC Mentoring organizations can begin submitting
applications to Google

* February 9 16:00 UTC Mentoring organization application deadline

* February 10 - 26 Google program administrators review organization
applications

* February 27 16:00 UTC List of accepted mentoring organizations published

* February 27 - March 20 Potential student participants discuss
application ideas with mentoring organizations

* March 20 16:00 UTC Student application period opens

* April 3 16:00 UTC Student application deadline

*May 4 16:00 UTC Accepted student proposals announced
Community Bonding Period Students get to know mentors, read
documentation, get up to speed to begin working on their projects

*May 30 Coding officially begins!

So now is the time to begin discussions within your team about ideas
you would like to publish as a guide to students you want as GSoC
students. While you're doing that, take note of ideas of how to test
or otherwise evaluate possible students. We intend to be more strict
this year about accepting students and mentors in an effort to improve
our success rate even more.

What a great start to the year!

Valorie

-- 
http://about.me/valoriez

Google Code-in tasks -- we need them NOW

[Valorie Zimmerman]

Hello folks, November 28th looms, and we are below our needed task count.

* If you have already been invited to the GCi webapp, please get your
tasks into the system now. We especially need beginning tasks, which
can be the same as tasks last year, and they can be reused as often as
we need them.

* If you have not yet been invited, or have not been able to accept
the invitation, please write to kde-soc-managem...@kde.org and ask.

** If you want to mentor but are not subscribed to
kde-soc-men...@kde.org, please do so ASAP, and remember to confirm
your email before pinging us to be accepted. It is important that this
list be only for mentors, so that we can speak openly and honestly
about issues. Unfortunately this means that those doing SoK projects
right now will not be able to function as mentors.

* Former Google Summer of Code students, however, are especially
welcome to come on board as mentors. Please connect with your team
about tasks and timing.

As the webapp says:

Contest begins: November 28, 2016

You have 5 days to create your minimum of 75 tasks for the initial
launch and invite and assign mentors to the tasks.

At this point we have not even 40!

Valorie

-- 
http://about.me/valoriez

Google Code-in begins soon: Nov. 28, 2016

[Valorie Zimmerman]

Hello folks, we've finally worked out a glitch in getting me as one of
the org admins for GCi. I was greeted by this message when logging in:

Welcome back

Contest begins: November 28, 2016

You have 19 days to create your minimum of 75 tasks for the initial
launch and invite and assign mentors to the tasks.

So if you wish to mentor at any point in the contest, please ask now
to be invited to the webapp so that you can add your task(s). You do
not have to *publish* the task unless you are available to help
students accomplish the task on November 28th.

Remember to also subscribe to KDE-Soc-Mentor ML if you have not
already done so. If you have subbed and confirmed your email (look in
your spam if you don't see it), ping one of us on IRC or email if you
don't get your 'you are subscribed' email. If you want to be an org
admin, or have other organizational questions, talk to us about that
in #kde-soc-admin or on the KDE-soc-management ML.


We are below the minimum required number of available tasks.


Start creating more tasks and publish ASAP. Remember to get a good
spread across each of the 5 categories and ensure there are enough
beginner tasks. Consult the website if you want more detail about
tasks.

Something to consider: creating a good, *simple* title for your task
is the most important part to drawing good students to do it!

Once we get into the swing of the contest, good students can be urged
to create their own tasks, based on bugs they find, etc.

We can create tasks such as Present the work you are doing for GCi to
your school, create a short youtube presentation of application X, or
new feature Y, run this test, *write* a test, create a docker setup
for other students -- use your creativity, and remember that we can
create new tasks as we go along, as well as re-using some tasks many
times.

Remember to use "they" or "them" when necessary, not "he" or "him". We
want all students to feel welcome.

I want all mentors to feel welcome as well, especially former GCi, SoK
and GSoC students!

Valorie

-- 
http://about.me/valoriez

Fwd: [GSoC Mentors] Announcing Google Summer of Code 2017 and Google Code-in 2016

[Valorie Zimmerman]

Hello folks, it is time to start thinking of tasks you would like
students to do this fall-winter. Remember, these tasks are for teens
who are dealing with schoolwork and teen life, so they need to be
small enough to be done within a day or two.

In addition, we always need "beginner" tasks, for kids who are working
in open source for the first time. Mentoring these can range from
frustrating to rewarding, and I urge all of you to think of a few of
them. You can schedule your tasks for when you have time to mentor.

We'll need tasks not only in coding, but also Documentation /
Training, Outreach / Research, Quality Assurance and User Interface.

Valorie


-- Forwarded message --
From: 'sttaylor' via Google Summer of Code Mentors List

Date: Mon, Oct 10, 2016 at 10:11 AM
Subject: [GSoC Mentors] Announcing Google Summer of Code 2017 and
Google Code-in 2016
To: Google Summer of Code Mentors List



Hello all,


We are pleased to announce Google Summer of Code 2017, the 13th
straight year of the program.


The GSoC 2017 timeline has been updated with next year's important
dates. More information including some changes to the Program Rules
will be updated in early November on the program site.


Organizations -- If you would like to apply for the 2017 program
please start thinking about the projects you would like students to
work on and also reach out to your community members to ask if they
would like to be mentors for the program.


We are looking forward to another exciting year of GSoC!


Today we also announced the Google Code-in 2016 contest that will be
open for past GSoC mentoring organizations to apply to be a part of
this exciting 7 week contest bringing teenagers into the open source
community. Organization applications are open for GCI from October
24th - November 7th.  GCI opens for student participants on November
28th!


For any questions about the programs please email us at gsoc-supp...@google.com


Best,

Google OSPO team

Re: Season of KDE -- please add your ideas

[Valorie Zimmerman]

On Sat, Oct 8, 2016 at 12:32 AM, Alexander Semke  wrote:
> Hi Valorie,
>
>> Projects from past Seasons of KDE include new application features,
>> the KDE Continuous Integration system, new reporting for developers, a
>> web framework, porting and a lot of other work.
> We would benefit a lot from some help on our new homepage:
>
> 1) improve and bring the documentation of the application and of the APIs to
> the new sections on our site
> 2) create couple of examples in different themes (the new theme manager was a
> GSoC2016-project) and add a show-case section for this on the webpage to
> demonstrate this feature.
>
> Can this be qualified as SoK-tasks?
>
> Regards,
> Alexander

Alexander, would this take a student several months to do this work?
That is the sort of thing we're looking for, for Season of KDE.

If you are thinking about shorter tasks which take a younger student a
few days per task, those should be saved up for Google Code-in, which
begins in November and lasts until January.

Valorie

-- 
http://about.me/valoriez

Season of KDE -- please add your ideas

[Valorie Zimmerman]

Hello developers,

Do you have a project in mind which will help KDE? Season of KDE might
be for you.

KDE Student Programs has announced the 2016-2017 Season of KDE for
those who want to participate in mentored projects which enhance KDE
in some way.

Projects from past Seasons of KDE include new application features,
the KDE Continuous Integration system, new reporting for developers, a
web framework, porting and a lot of other work.

Successful mentees earn a certificate of completion along with  a very
cool tee shirt and other goodies. Any person who wants to complete a
project is eligible to enter.

Those who want to mentor are asked to add ideas here:
https://community.kde.org/SoK/Ideas/2016. The sooner the better,
please!  *This means you!*

Students are asked to begin discussion about your ideas or those on
the various KDE mail lists and IRC channels even before applications
open. The more consultation is done with the team you want to work
with, the more likely you are to succeed.

The schedule this year will be:
* 7 October to 31 October:  Student and mentor applications
* 1 November: Official coding period begins. Students can start work
after once mentor and student agree on the project scope and the
timeline
* 28 February : End of coding period

To apply as a mentor or student, please visit https://season.kde.org

Valorie, on behalf of the Student Programs team

Season of KDE -- please add your ideas

[Valorie Zimmerman]

Hello developers,

Do you have a project in mind which will help KDE? Season of KDE might
be for you.

KDE Student Programs has announced the 2016-2017 Season of KDE for
those who want to participate in mentored projects which enhance KDE
in some way.

Projects from past Seasons of KDE include new application features,
the KDE Continuous Integration system, new reporting for developers, a
web framework, porting and a lot of other work.

Successful mentees earn a certificate of completion along with  a very
cool tee shirt and other goodies. Any person who wants to complete a
project is eligible to enter.

Those who want to mentor are asked to add ideas here:
https://community.kde.org/SoK/Ideas/2016. The sooner the better,
please!  *This means you!*

Students are asked to begin discussion about your ideas or those on
the various KDE mail lists and IRC channels even before applications
open. The more consultation is done with the team you want to work
with, the more likely you are to succeed.

The schedule this year will be:
* 7 October to 31 October:  Student and mentor applications
* 1 November: Official coding period begins. Students can start work
after once mentor and student agree on the project scope and the
timeline
* 28 February : End of coding period

To apply as a mentor or student, please visit https://season.kde.org

Valorie, on behalf of the Student Programs team

Mentoring, student programs coming up

[Valorie Zimmerman]

Hi folks, I have no announcements, but was thinking about our Season
of KDE and how we can enlarge and improve it. I believe we've been
thinking of it too much like GSoC, when it can be so much more.

For instance, I've seen a few announcements from maintainers wanting
to step back from a large piece of code for which they have been
responsibie. Sometimes seasoned developers step up, but what happens
when they don't? We don't have to settle for abandoned code, or
burning out maintainers. How about writing up a good description of
what is required, and offering to mentor a new maintainer for a few
months?

We all know that we have some large projects that need doing
(www.kde.org for instance) that have been too challenging to get done
so far. How about offering to mentor a specific part of such a task?
In SoK, we've never had a rule that the task had to be handled by one
person -- it could be a small team, so keep that in mind. Mentors can
act as a team, as well.

Think of all the work that Scarlett has done building the CI with the
help of Ben and the sysadmin team. Has that helped almost every KDE
developer? I think so!

These are just a few thoughts off the top of my head. Please think of
work you can mentor which will involve your mentee (SoK mentees do
*not* have to be students) more deeply in KDE and making the world
better.

If you are not subscribed to KDE-Soc-Mentor [1], please subscribe and
discuss your ideas.

Oh, and GCi [2] is happening this fall, so if you have a number of
small tasks, please start writing those up.

Valorie

1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor

2. https://developers.google.com/open-source/gci/

-- 
http://about.me/valoriez

Mentoring, student programs coming up

[Valorie Zimmerman]

Hi folks, I have no announcements, but was thinking about our Season
of KDE and how we can enlarge and improve it. I believe we've been
thinking of it too much like GSoC, when it can be so much more.

For instance, I've seen a few announcements from maintainers wanting
to step back from a large piece of code for which they have been
responsibie. Sometimes seasoned developers step up, but what happens
when they don't? We don't have to settle for abandoned code, or
burning out maintainers. How about writing up a good description of
what is required, and offering to mentor a new maintainer for a few
months?

We all know that we have some large projects that need doing
(www.kde.org for instance) that have been too challenging to get done
so far. How about offering to mentor a specific part of such a task?
In SoK, we've never had a rule that the task had to be handled by one
person -- it could be a small team, so keep that in mind. Mentors can
act as a team, as well.

Think of all the work that Scarlett has done building the CI with the
help of Ben and the sysadmin team. Has that helped almost every KDE
developer? I think so!

These are just a few thoughts off the top of my head. Please think of
work you can mentor which will involve your mentee (SoK mentees do
*not* have to be students) more deeply in KDE and making the world
better.

If you are not subscribed to KDE-Soc-Mentor [1], please subscribe and
discuss your ideas.

Oh, and GCi [2] is happening this fall, so if you have a number of
small tasks, please start writing those up.

Valorie

1. https://mail.kde.org/mailman/listinfo/kde-soc-mentor

2. https://developers.google.com/open-source/gci/

-- 
http://about.me/valoriez

links on https://techbase.kde.org/Getting_Started/Sources/en

[Valorie Zimmerman]

Hi folks, someone in #kde-www mentioned at many links to
projects.kde.org are still on techbase, so I logged in and started
cleaning them up.

This page: https://techbase.kde.org/Getting_Started/Sources/en has
loads of links, and I don't seem to be able to find Quickgit
alternatives. Examples:

"The '''Qt KDE''' module is a clone of the latest Qt release." - but I
can find no quickgit link.

kdesupport -- same.

In fact, I'm giving up on fixing that page, and would ask for someone
more knowledgeable than me to login and fix it.

I believe that at some point it will probably be moved to Community
wiki once accurate and up-to-date, since it no longer fits the
definition of what Techbase is for.

Valorie

-- 
http://about.me/valoriez

Ranking and mentors needed for GSoC student

[Valorie Zimmerman]

Hello to all readers. I'm writing to you to ask you to mentor this
student who needs a primary mentor. The Dolphin maintainer and
community can't step up and do this, although the maintainer can help.
Pinak Ahuja has offered to be backup co-mentor already. Anyone
somewhat familiar with Baloo and/or Dolphin would be qualified.


Please give your attention to
https://summerofcode.withgoogle.com/dashboard/organization/6327828735852544/proposal/5979393230897152/

If you are not yet invited to the webapp but wish to mentor this
student, please reply to me privately with your google-connected
account email, and I'll invite you to the app. If you have not seen
this student's proposal yet, his draft can be seen at

https://docs.google.com/document/d/1TJc77tlkPlEeivCFiFOzUAguPOoJSPW8R0Z997orMjU/edit

Once invited to the webapp, please subscribe to KDE-Soc-Mentor list if
you have not already, and remind us to invite you to the spreadsheet
where final rankings are being done. This student should have two
mentors: one primary contact and a backup person. In addition, I hope
the entire core developer community will gather around to support your
new student devel.

Time is of  the essence.

Valorie

--
http://about.me/valoriez

Re: GSoC 2016 Proposal for KDE Dolphin

[Valorie Zimmerman]

Hi all, especially Dolphin and Baloo devs,

On Mon, Mar 7, 2016 at 9:08 AM, Arnav Dhamija  wrote:
> Hi everyone!
>
> I'm excited to give the GSoC a shot this year. I am a first CSc
> undergraduate at BITS Pilani, Hyderabad Campus in India. I have an original
> idea for the Dolphin file manager to make it easy to select files from
> disjoint directory trees.
>
> I have written the proposal I will submit to KDE here: https://goo.gl/BYOWdG
>
> I look forward to the feedback of the KDE community on this idea and this
> proposal : )
>
> arnav dhamija

Arnav is very enthusiastic about improving Dolphin, but has been
getting not much help from the community thus far. His patch is
sitting in Reviewboard with no replies. [1]

Do we want Dolphin to continue? An application with no developers will
slowly bit-rot. So I would ask any of you who have an interest to read
over Arnav's proposal and give him some feedback. Same with his patch.
If you feel you could mentor him in his proposal or something else
related, please talk to him about it.

GSoC is our chance to draw new developers to our community. It does
take some work, however! If you don't think you could be a primary
mentor, how about a backup? It takes a village to grow a child, and a
community to grow a young developer. :-)

Valorie

1. https://git.reviewboard.kde.org/r/127054/

PS: he has had one patch reviewed and shipped:
https://git.reviewboard.kde.org/r/126467/. I would ask the same
thoughtful treatment here.

-- 
http://about.me/valoriez

Re: KDE file dialog

[Valorie Zimmerman]

I realize I'm slightly orthagonal to the original topic, but

On Sat, Mar 5, 2016 at 11:14 PM, Kai Uwe Broulik  wrote:
> Hi,
>
>> Distributions set up distribution-wide "Sans", "Serif" and "Monospace" 
>> aliases for a reason. The fonts are carefully selected by the distribution 
>> based on a variety of criteria, including glyph coverage
>
> We tried to keep font decisions to distributions before Plasma 5 and it 
> always made me cringe how terrible fonts looked in screenshots from other 
> people and was one of the first things I had to change on every fresh 
> install. Now we pick some sane defaults that make it look good and unified 
> across distributions.
>
> Cheers,
> Kai Uwe

We've recently had a group working on trying to improve KDE <> distro
relationships by improving communication. Yes, there is the packager
list and release-team, but they are about the nitty-gritty of released
packages. So the Distribution Outreach Program has asked for the
Distributions list [1] to be created, where larger issues like these
can be hashed out. All interested KDE people and all interested
distribution people are invited to participate, no matter what your
role.

The KDE community wants KDE software to work well everywhere. And the
wonderful people working to distribute KDE software want it to work
well in each of our distros. Together we can make magic happen.

Valorie

1. https://mail.kde.org/mailman/listinfo/distributions


-- 
http://about.me/valoriez

Re: Google Summer of Code 2016 - C# bindings for Qt

[Valorie Zimmerman]

Hi all,

On Thu, Mar 3, 2016 at 2:41 PM, Sebastian Kügler  wrote:
> Hi Joao,
>
> On Thursday, March 03, 2016 19:36:05 Joao Matos wrote:
>> Hi Sebastian and the rest of the KDE community,
>>
>> I'd like to propose to mentor Dimitar but I have no idea what the policy of
>> the KDE project
>> is regarding the possibility of allowing mentors external to the community.
>>
>> I believe I am the best person to mentor Dimitar due to a couple of factors:
>
> Cool. :)
>
>> - Succesfully mentored Dimitar and several other students on previous GSoC
>> editions.
>> - I am the maintainer of the CppSharp project that QtSharp is based on.
>> - I am also a contributor to QtSharp so I know pretty well what needs to be
>> done and how to do it.
>>
>> In fact, I was already planning on mentoring Dimitar under GSoC as part of
>> the Mono community,
>> but Mono was not accepted as an organization this year.
>
> Best is to get in touch with the KDE SoC admins on the mailinglist kde-
> s...@kde.org , they can answer your questions and get you set up to mentor.
>
>> On Thu, Mar 3, 2016 at 5:58 PM, Sebastian Kügler  wrote:
>> > On Thursday, March 03, 2016 06:20:49 PM Arno Rehn wrote:
>> > > having worked with Dimitar before, I'd recommend to accept QtSharp as a
>> > > project under the KDE umbrella for this year's gsoc (if that's
>> > > possible).
>> > > Dimitar has done some good work on Qyoto and SMOKE in the past. I think
>> > > C# and Qt are a good fit, so I fully support creating bindings for it.
>> > > This project might even attract some more people from the Windows side
>> > > to contribute to Qt and KDE.
>> >
>> > A question that is probably important down the road: Can you or someone
>> > else
>> > mentor Dimitar and his project?
>
> --
> sebas
>
> Sebastian Kügler|http://vizZzion.org| http://kde.org

I've invited Joao to the webapp and approved the list subscription and
post, and answered a bit there. However, since Joao and the student
are both new to KDE, I would like to ask another experienced KDE
mentor to step up to co-mentor this task.

If you are not already invited to the webapp, please send me your
google-connected account, and sub to KDE-Soc-Mentor ML.

We always like to have co-mentors for GSoC, but I think it is
mandatory for this proposal.

Thanks.

Valorie

Re: Google Summer of Code 2016 - C# bindings for Qt

[Valorie Zimmerman]

Hi all,

On Thu, Mar 3, 2016 at 2:41 PM, Sebastian Kügler  wrote:
> Hi Joao,
>
> On Thursday, March 03, 2016 19:36:05 Joao Matos wrote:
>> Hi Sebastian and the rest of the KDE community,
>>
>> I'd like to propose to mentor Dimitar but I have no idea what the policy of
>> the KDE project
>> is regarding the possibility of allowing mentors external to the community.
>>
>> I believe I am the best person to mentor Dimitar due to a couple of factors:
>
> Cool. :)
>
>> - Succesfully mentored Dimitar and several other students on previous GSoC
>> editions.
>> - I am the maintainer of the CppSharp project that QtSharp is based on.
>> - I am also a contributor to QtSharp so I know pretty well what needs to be
>> done and how to do it.
>>
>> In fact, I was already planning on mentoring Dimitar under GSoC as part of
>> the Mono community,
>> but Mono was not accepted as an organization this year.
>
> Best is to get in touch with the KDE SoC admins on the mailinglist kde-
> s...@kde.org , they can answer your questions and get you set up to mentor.
>
>> On Thu, Mar 3, 2016 at 5:58 PM, Sebastian Kügler  wrote:
>> > On Thursday, March 03, 2016 06:20:49 PM Arno Rehn wrote:
>> > > having worked with Dimitar before, I'd recommend to accept QtSharp as a
>> > > project under the KDE umbrella for this year's gsoc (if that's
>> > > possible).
>> > > Dimitar has done some good work on Qyoto and SMOKE in the past. I think
>> > > C# and Qt are a good fit, so I fully support creating bindings for it.
>> > > This project might even attract some more people from the Windows side
>> > > to contribute to Qt and KDE.
>> >
>> > A question that is probably important down the road: Can you or someone
>> > else
>> > mentor Dimitar and his project?
>
> --
> sebas
>
> Sebastian Kügler|http://vizZzion.org| http://kde.org

I've invited Joao to the webapp and approved the list subscription and
post, and answered a bit there. However, since Joao and the student
are both new to KDE, I would like to ask another experienced KDE
mentor to step up to co-mentor this task.

If you are not already invited to the webapp, please send me your
google-connected account, and sub to KDE-Soc-Mentor ML.

We always like to have co-mentors for GSoC, but I think it is
mandatory for this proposal.

Thanks.

Valorie

Re: KDE has been selected as a Google Summer of Code 2016 mentor organization

[Valorie Zimmerman]

Just as a reminder

On Tue, Mar 1, 2016 at 1:54 PM, Valorie Zimmerman
<valorie.zimmer...@gmail.com> wrote:
> Yesterday we got the email we'd been waiting for, beginning:
> "Congratulations! KDE has been selected as a Google Summer of Code
> 2016 mentor organization.
>
> Please click here to visit your organization profile and start adding 
> mentors."
>
> That last bit is new. If you plan to mentor, please
>
> 1. Message one of us admins with your google-connected account email
> as soon as possible


** This is necessary even if you are already on KDE-Soc-Mentor list,
have mentored before, even if you mentored for GCi.**


Also, if you messaged one of us, and you have not yet been invited to
the new GSoC webapp, please ping one of us admins again. So far we
have only 19 mentors and 5 admins.

> 2. Subscribe to KDE-Soc-Mentor ML:
> https://mail.kde.org/mailman/listinfo/kde-soc-mentor
>
> 3. Check out your team and ideas on the GSoC Ideas page, and improve
> if necessary: https://community.kde.org/GSoC/2016/Ideas
>
> Pay particular attention to communication methods; many of the
> students are new to open source, and may not be familar with/or cannot
> access IRC channels. Telegram is a good free-ish fallback which is
> working well for some teams.
>
> The wikis are open for edits again; if you run into difficulties
> logging in, please see
> https://community.kde.org/Sysadmin/Wiki-Phablogin or stop by #kde-www
> in freenode if all else fails.

Valorie

Google Summer of Code Ideas needed now

[Valorie Zimmerman]

Org applications open on 8 February, so we need to get moving on this.
Unfortunately, our wikis are close for editing right now, because of
two spam attacks. Until they are open again, we have a Google Doc.

Google Summer of Code 2016 Ideas page is here:
https://community.kde.org/GSoC/2016/Ideas . It's a simple copy/paste
of last year's page, minus all the project ideas. I left team names;
please add or remove as appropriate. Look at previous year's pages if
you've not done this before.

Remember: if you add an idea, include a mentor name or names, and
contact info. Students often report that they are unable to use IRC,
so if you have Telegram, you could include that or just your email, or
even the team list as a contact. The page needs to be complete if we
want to be accepted as a mentoring org. The deadline is 19 February
19:00 UTC.

Google Doc:

https://docs.google.com/document/d/1k1ESLkh6-0Hz4rGR02yEasjjx0_Kz12Y_6SZR3AWMVU/edit?usp=sharing

We'll transfer to the wiki and close that GDoc as soon as possible.

Valorie

PS: While you're thinking about it, once you have written out your
idea, please subscribe to the mentor list:
https://mail.kde.org/mailman/listinfo/kde-soc-mentor

Re: Saying hello

[Valorie Zimmerman]

Hello to both of you, Christian and Ayrton. Most people here got
involved as you are doing, either creating or helping to create some
project, or fixing a favorite bit that needs some love.

Be sure to also join the KDE Community list, and also specific lists
and IRC channels corresponding to your interests. Fixing bugs is
great, answering user's common questions is also useful! And read
though documentation and fix the bits that are behind or incorrect.
More senior people often can't see those parts, because of too much
familiarity.

KDE-community ML: https://mail.kde.org/mailman/listinfo/kde-community

https://mail.kde.org/mailman/listinfo gives an overview of some KDE
lists; not exhaustive though (and maybe not fully up-to-date)

https://userbase.kde.org/IRC_Channels is again an overview. If I'm
looking for a specific channel to refer users to, I usually use
"alis", freenode's channel search service. Use it like so: /msg alis
list *searchterm* and read the output in your server tab.

It would be cool if you have a blog to add it to the KDE Planet. If
you don't have one, start! It's a wonderful way to get the word out
about your projects, or what you are learning. https://planetkde.org/

All the best,

Valorie

On Tue, Jan 5, 2016 at 1:54 PM, Ayrton Cavalieri de Almeida
 wrote:
> Hello!
>
> My name is Ayrton Cavalieri, I’m new to the KDE too! :-)
> I’m working with my team on the Br-Print project, a 3D printer host written
> in Qt/C++. Be welcome to the community! Your project seams interesting, hope
> you have success!
> Enjoy!
>
>
>
> Ayrton Cavalieri de Almeida
> Back-End Developer of the Br-Print3D Project at KDE
> Computer Science Student at UFF/PURO
> “Força pela estabilidade."
>
>
>
> On 5 Jan, 2016, at 19:31, Christian Kalkhoff  wrote:
>
> Hi!
>
> I just joined this list and therefor wanted to introduce myself. My name is
> Christian Kalkhoff, I live in Munich, Germany and have been a KDE user on
> different OSes and GNU/Linux distributions for a long time now (started at
> pre-1.0).
>
> I am a proud Fellow of FSFE and try to promote Free Software whereever and
> whenever I can. My native language is german, I speak/write english for many
> years now and started with swedish about a year ago.
>
> I always wanted to contribute to KDE as a developer but did not find the
> motivation and time to get into C++/QT until recently. I have about 10 years
> experience developing enterprise Java applications, but I join KDE as an
> absolute novice of KDE, QT and C++.
>
> I am planning to write a simple electrical resistor calculator as my first
> app. I also would like to contribute to some junior tasks but I haven't
> found
> something appealing yet. Perhaps you can help me to help you? :)
>
> Best,
> Christian
> --
> Christian Kalkhoff - Softwarebefreier - software liberator
> Fellow of FSFE - Support FSFE!
> https://softmetz.de
> https://blogs.fsfe.org/softmetz
>
> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
>
>
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
>>> <<
>



-- 
http://about.me/valoriez

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Change to Mail Infrastructure - SPF and DKIM verification will now be enforced

[Valorie Zimmerman]

I just submitted a request to Ubuntu to upgrade their list infra. I
showed Ben a sample email header and they were not compliant. I
included a link to Ben's explanatory post:
http://marc.info/?l=kde-core-devel=144956641505429=1

It took less than five minutes to file the ticket.

All the best,

Valorie

On Wed, Dec 9, 2015 at 3:22 AM, Boudhayan Gupta  wrote:
> Hi all,
>
> I'm going recount a personal experience here. I have my own domain
> (BaloneyGeek.com) and I use Google Apps for Business for my E-Mail.
>
> A couple of months ago I shifted DNS providers and took the
> opportunity to properly set up E-Mail verification and signing. Using
> Google's documentation, I enabled SPF, and then tested. Then I enabled
> DKIM and tested.
>
> So far, everything was fine.
>
> Then I enabled DMARC and all hell broke loose. Even though Google's
> configuration checker gave me a green tick on DMARC configuration, I
> couldn't send mail to any non Google-handled e-mail ID, without it
> being sent to spam. I know this because I tested with one Windows Live
> Mail (or whatever they call it these days) account and one Yahoo
> account. Both of them had a history of receiving e-mails from me.
>
> I would also get an XML file delivered to my inbox from every single
> e-mail server that handled my mail, with stats of how many mails they
> handled, how many passed auth, how many failed and how many were sent
> to spam. Apart from the annoyance of receiving tens of these mails per
> day, I noted that every single provider (other than Google) was
> failing auth on all my mails and sending them to spam.
>
> I dug around multiple docs (including RFC 7489, Google's docs, etc)
> and couldn't find any configuration errors I'd made.
>
> In they end I had to roll back DMARC (which took two days to propagate
> across all DNS caches, btw), while keeping SPF and DKIM enabled.
> Everything has been fine since then.
>
> So here's my two cents - SPF **should** always be enabled, that's the
> bare minimum you can do. DKIM enforces SPF using signing, so if you
> guys can implement that well, awesome. But be very careful when
> dealing with DMARC. From what I saw when I tried to set it up, no
> e-mail provider other than Google knows what to do with it.
>
> -- Boudhayan



-- 
http://about.me/valoriez

Re: Change to Mail Infrastructure - SPF and DKIM verification will now be enforced

[Valorie Zimmerman]

Can we please lower the temperature on this discussion a bit?

On Wed, Dec 9, 2015 at 1:54 AM, Ben Cooksley  wrote:
> On Wed, Dec 9, 2015 at 4:37 AM, Jan Kundrát  wrote:
>> On Tuesday, 8 December 2015 16:09:43 CET, Nicolás Alvarez wrote:
>>>
>>> It is irrelevant what our personal preference about doing modifications to
>>> messages is (like the tag in the subject). The fact of life is that there
>>> *are* mail providers out there (like Yahoo) which are already enforcing
>>> DMARC and may reject messages with such DKIM-breaking modifications, and
>>> these mail providers won't change their config to accommodate us.
>>
>>
>> Nicely said. Yes, there are providers such as Yahoo, AOL, and nobody else :)
>> who decided to break a long-working infrastructure. The question is whether
>> we want to join this club.
>
> What you're basically saying is - you don't care about potential
> contributors who use these service providers.
> Lovely.
>
> I'm afraid that's unacceptable. A chunk of our users certainly do use
> them, and i'm sure we'd like them to be able to interact with our
> community.
>
>>
>> Should we start enforcing the same rules that Yahoo is enforcing? (Ben
>> didn't say what SPF and DKIM rules he's planning to publish for @kde.org,
>> btw.) Do we have many Yahoo/AOL users among our developers?
>
> The domain owner is actually the one that sets the policy under DMARC.
> All we'd be doing is following their wishes.
> I haven't said anything, because I don't plan to change our own
> policies at this time.
>
>>
>> Should we start publishing rules which effectively instruct others to
>> discard all e-mails from @kde.org once they go through a non-DMARC mailing
>> list?
>>
>> Should we discard e-mails which are intended for our developers because they
>> went through a non-DMARC mailing list?
>
> From the server's point of view, these messages could also be
> forgeries, containing spam, phishing attacks, or otherwise attempting
> to misrepresent the sender.
> If the domain owner has stated the message should have a valid
> signature, we'd be right to follow what they've requested.
>
>>
>> My answer to these two questions is "no" and "no", obviously. I don't know
>> how else to say this -- Debian is not exactly a small open source project,
>> and their sysadmins apparently haven't cared about DKIM so far. It's a
>
> DKIM has been around for an extremely long time.
> It means they've not worked on improving their email deliverability.
>
>> technology which requires Everybody Else™ to perform extra work and to
>> configure new services on the servers which host various mailing lists. Are
>
> Configuration of new services is not required, as noted in my earlier mail.
>
>> we seriously trying to push an unspecified number of third-party ML
>> providers to deploy DKIM because Ben decided that it's worth the effort?
>
> Nice to demonise me here.
>
> The mailing list hosts don't have to deploy DKIM. All they have to do
> is not break signatures on mails bearing a DKIM signature.
> Which, as I noted in my email is something that only requires a few
> toggles within the Mailman administration interface.
> (And, using the withlist tool can be changed on all lists on an entire
> server with relative ease). This is what Debian has chosen to do.
>
>> Seriously, the Internet just doesn't work this way. Even if Debian's
>> ifnrastructure is changed, there is still a number of mailing lists which
>> have worked well in the past years, and now they will stop working for
>> @kde.org accounts.
>>
>>
>> Cheers,
>> Jan
>
> Regards,
> Ben

Ben isn't the only person wrestling with these issues. We're dealing
with it on a much smaller scale in Linuxchix. Anyone who runs lists is
having to deal with spam, malware, forgeries, phishing, and so forth.

While the tools to mitigate some of this are complicated, we will have
to make changes at some time. I suggest that we calmly pull together
and figure out how we can make KDE email and lists more secure, as
well as all of those lists with which we use our KDE.org accounts.

We *can* do this, we need to do this, and Ben doesn't have time to do
all the work himself. So we need to do our part to help.

Valorie

Re: Sprint: Reorganize the wikis

[Valorie Zimmerman]

On Wed, Dec 2, 2015 at 3:10 PM, Olivier Churlaud  wrote:
> Hi,
>
> I'm coming here with this observation: the wiki are quite a mess. And very
> often KDE4 and KF5 things are mixed.
> That everyone do it at their scale is impossible. That's why I have a
> proposition. (I've thought about it for a while)
>
> It would be easier to do this like in a sprint, in team.
>
> 1) Define what structure the wiki should have: What is techbase? What is
> Community? Are the manuals in Userbase or on doc? and so on
> 2) then take each page and order => Archive KDE4 | Mess | KF5 | To remove
> 3) Do a list of what is missing and what should be tidied.
> 4) Write to the corresponding teams so that they take care of it.
> 5) Remove what should be
>
> What I mean in 2) is: for example there are N pages about how to configure
> Git. We take the good one, put the other in a namespace "To remove"
>
> What I mean in 4) is: for example in https://community.kde.org/Sonnet, it's
> very old, and not much documented (sorry if some of you are reading this, I
> pick it randomly), so we can put a mail on the ML and tell them 'well we saw
> that...'
>
> Basically this is my vision of what could be done.
>
> Since I don't always know what is old what is still usable and so on, people
> with this knowledge would be required.
>
> I think we should plan it very carefully, to have a battle plan, and then
> go.
>
> What do you think?
> Would people be interested to give a hand?
> How and when do we begin?
>
>
> Cheers
> Olivier

Sounds good to me! And I certainly would be willing to help, whether
remotely or at a physical sprint.

Valorie

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Review Request 126078: [OS X] modernising the KIdleTime plugin (WIP!)

[Valorie Zimmerman]

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126078/#review88573
---


Hello folks, Martin Graesslin has asked the CWG to step in here. This is 
Valorie writing. I can't comment on the technical aspects here, but I'm 
disappointed in the way this was handled. The review process is really 
important to the entire KDE community. We share our proposals, ask for 
feedback, then engage in dialog. This is *thinking together.* Instead, I'm 
seeing defensiveness, exasperation, and finally anger.

Please, everyone step back, calm down, and let's reconsider the issue afresh. 
Surely we can do a better job in providing great software to our users.

- Valorie Zimmerman


On Nov. 18, 2015, 4:35 p.m., René J.V. Bertin wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/126078/
> ---
> 
> (Updated Nov. 18, 2015, 4:35 p.m.)
> 
> 
> Review request for KDE Software on Mac OS X, KDE Frameworks and Dario Freddi.
> 
> 
> Repository: kidletime
> 
> 
> Description
> ---
> 
> I noticed that the KIdleTime example doesn't work properly on OS X, and that 
> the plugin for OS X still uses the deprecated Carbon-based algorithm that I 
> already patched for KDE4.
> 
> This patch is a work-in-progress (hence the qDebugs) update to use IOKit, 
> IORegistry and CoreServices to do idle-time calculation as it should be done, 
> and allow simulated user activity through a "less deprecated" function.
> 
> 
> Diffs
> -
> 
>   src/plugins/osx/CMakeLists.txt e1b50b8 
> 
> Diff: https://git.reviewboard.kde.org/r/126078/diff/
> 
> 
> Testing
> ---
> 
> On OS X 10.9 with Qt 5.5.1 and frameworks 5.16.0 .
> 
> The example now works: when I set a QTimer with interval==0, the expected 
> wait for user input (`resumingFromIdle` signal) works. However, I am getting 
> a `stopCatchingIdleEvents` signal which means the application waits forever, 
> without ever getting to compare idle time to the list of timeouts.
> I haven't been able to figure out where that signal comes from, nor why this 
> doesn't happen on Linux.
> 
> Surely I'm missing something, but what?
> 
> 
> Thanks,
> 
> René J.V. Bertin
> 
>

___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel