Re: Mentors needed

[Timothée Giet]

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

Re: Mentors needed

[Timothée Giet]

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

Re: GCompris change

[Timothée Giet]

Le 14/02/2020 à 21:54, Timothée Giet a écrit :
> Hi all,
>
> I want to inform you that from today, I decided to make GCompris
> binaries completely free of cost for all platforms.
>
> I updated the website accordingly, you can read the announcement here:
> https://gcompris-net/index-en.html#2020-02-14
>
> Cheers,
> Timothée
>
>
Little typo in the link:

https://gcompris.net/index-en.html#2020-02-14

GCompris change

[Timothée Giet]

Hi all,

I want to inform you that from today, I decided to make GCompris
binaries completely free of cost for all platforms.

I updated the website accordingly, you can read the announcement here:
https://gcompris-net/index-en.html#2020-02-14

Cheers,
Timothée

Re: Changes to Phabricator review subscriptions

[Timothée Giet]

Le 09/05/2018 à 12:11, Ben Cooksley a écrit :

On Wed, May 9, 2018 at 9:25 PM, Timothée Giet  wrote:

Le 09/05/2018 à 10:33, Boudewijn Rempt a écrit :

On Wednesday, May 9, 2018 10:08:28 AM CEST you wrote:

Hi all,

To improve the user experience around email and in-application
notifications from Phabricator, sysadmin have made some changes to the
configuration of our Herald rules.

Going forward, instead of subscribing projects to reviews, we will
only be subscribing mailing lists now.

So, should we now get all phabricator mail at, say, kimages...@kde.org, or
should we create a second mailing list, say krita-p...@kde.org? I do want
to
receive mail for everything krita-related that happens on phabricator!


For those reviews which have
already been created, they will be updated to reflect the new practice
the next time they are changed.

This means that individual project members will no longer receive
notifications and emails for every single review or task change that
affects their project. Instead, they will only receive notifications
and emails for reviews they have been individually subscribed to.

:-(


To help this change take full effect, it would be appreciated if
people refrain from adding Projects as reviewers, as that will have
the effect of subscribing the Project to the review as well

But what if that's what a project really wants?


That is also exactly what we use to do in GCompris... it's the best solution
for us to easily connect the diff to the relevant group of people.
Subscribing our current mailing list is surely not what we want.

If you could elaborate on your use case here that would be appreciated.
Traditionally most development has taken place via mailing lists, so
it's interesting to see people who don't follow that model.

(To date all Herald rule setup requests have been for mailing lists)

I note that GCompris also doesn't appear to have any rules setup,
which is possibly why this hasn't come up before.



Thanks a lot Ben for the clarification :)
So it seems we are unaffected by the change and can continue to work 
like we do.
To elaborate as you asked for it, we try to use phabricator as much as 
possible for task management and review request.
For review requests we ask people to add GCompris or one of the 
appropriate subprojects (like GCompris: Improvements) as Group-reviewer.
This way all people subscribed to this project/sub-project gets a mail 
notification, but most importantly has it listed in his 
https://phabricator.kde.org/differential/


See http://gcompris.net/wiki/Contribution_process , especially "Asking 
for a Review Request"


It seems that Krita is doing the same, since I also see lot of diffs 
with Krita reviewer in my list and notifications (which I also like to 
have ;) )


Only "issue" for me is I have some mail duplicates from kde-edu list. It 
would be great to find a way to avoid them, but if not possible I can 
live with that.


Our devel mailing list is now mostly used for occasional wider dev 
communication, and for occasional contributors.


Cheers,
Timothée

Re: Changes to Phabricator review subscriptions

[Timothée Giet]

Le 09/05/2018 à 10:33, Boudewijn Rempt a écrit :

On Wednesday, May 9, 2018 10:08:28 AM CEST you wrote:

Hi all,

To improve the user experience around email and in-application
notifications from Phabricator, sysadmin have made some changes to the
configuration of our Herald rules.

Going forward, instead of subscribing projects to reviews, we will
only be subscribing mailing lists now.

So, should we now get all phabricator mail at, say, kimages...@kde.org, or
should we create a second mailing list, say krita-p...@kde.org? I do want to
receive mail for everything krita-related that happens on phabricator!


For those reviews which have
already been created, they will be updated to reflect the new practice
the next time they are changed.

This means that individual project members will no longer receive
notifications and emails for every single review or task change that
affects their project. Instead, they will only receive notifications
and emails for reviews they have been individually subscribed to.

:-(


To help this change take full effect, it would be appreciated if
people refrain from adding Projects as reviewers, as that will have
the effect of subscribing the Project to the review as well

But what if that's what a project really wants?


That is also exactly what we use to do in GCompris... it's the best 
solution for us to easily connect the diff to the relevant group of people.

Subscribing our current mailing list is surely not what we want.




(Phabricator does not require you specify a reviewer)

I know. Most newcomers don't and do not specify any reviewer, so review
requests often fall between the cracks.

Should anyone have any questions regarding this, please open a thread
on the kde-devel@kde.org mailing list.


I discovered today that I did not have a subscription to this list and that
there are no archives, so I've missed all discussions, if there have been any.
I would have expected the discussion to happen on kde-community, but maybe we
just have too many mailing lists.


I am subscribed to this list but didn't see much discussion on the topic 
before this change announcement.


Timothée

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

[Timothée Giet]

Hi,

On GCompris side, we have some tasks and a few mentors.
Not that much, but if there are more from other KDE projects we can
participate.

Timothée


Le 13/10/2017 à 00:53, Valorie Zimmerman a écrit :
> 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
>  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
>>  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