[gsoc] Weekly meeting tomorrow

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[gsoc] Weekly meeting tomorrow

Eric Barnhill
Let's have another weekly gathering tomorrow for GSoC mentees at the usual
time.

Everyone should have written at least some code, and a unit test that goes
with that code, and submitted it for review via a PR.

If you have difficulties doing this, please raise questions on the Slack.

Thanks to the contributors who are  helping out so much at these meetings.
Reply | Threaded
Open this post in threaded view
|

Re: [gsoc] Weekly meeting tomorrow

Alex Herbert
Reply | Threaded
Open this post in threaded view
|

Re: [gsoc] Weekly meeting tomorrow

Eric Barnhill
That looked like a list of times. How is this one for you all

https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=6&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800


On Wed, Jun 5, 2019 at 11:59 AM Alex Herbert <[hidden email]>
wrote:

> Time for another meeting to discuss progress.
>
> Shall we change to UTC +4 this time? Here is the meeting time clock for
> everyone:
>
>
> https://www.timeanddate.com/worldclock/meetingtime.html?iso=20190606&p1=136&p2=224&p3=265&p4=1249&p5=1860
> <
> https://www.timeanddate.com/worldclock/meetingtime.html?iso=20190606&p1=136&p2=224&p3=265&p4=1249&p5=1860
> >
>
> Alex
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [gsoc] Weekly meeting tomorrow

Alex Herbert


> On 5 Jun 2019, at 20:47, Eric Barnhill <[hidden email]> wrote:
>
> That looked like a list of times.

It showed ideal points for a meeting from all times of day. UTC +3 or +4 should be daytime hours for everyone except those in IST.

> How is this one for you all
>
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=6&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800 <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=6&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800>

Better. UTC +4, I will be there.

Alex

>
>
> On Wed, Jun 5, 2019 at 11:59 AM Alex Herbert <[hidden email]>
> wrote:
>
>> Time for another meeting to discuss progress.
>>
>> Shall we change to UTC +4 this time? Here is the meeting time clock for
>> everyone:
>>
>>
>> https://www.timeanddate.com/worldclock/meetingtime.html?iso=20190606&p1=136&p2=224&p3=265&p4=1249&p5=1860
>> <
>> https://www.timeanddate.com/worldclock/meetingtime.html?iso=20190606&p1=136&p2=224&p3=265&p4=1249&p5=1860
>>>
>>
>> Alex
>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: [gsoc] Weekly meeting tomorrow

Alex Herbert
Time for a weekly meeting.

Thursday UTC +4.

https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=13&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800 <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=13&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800>

Here’s a preliminary agenda:

- Present progress
— What have you done last week?
— What are your plans for the next week?
— What is blocking your progress?

- Daily stand-up?
There was a positive response from my suggestion to daily stand-ups. But no-one participated. Please bring your thoughts to the meeting tomorrow. I would favour a 5 minute daily stand-up just so that we all know how work is moving forward.

- Mailing list vs. Slack vs. Jira
We tried to clear up the different channels and how to use them in a Slack discussion. Please bring your thoughts on this:

- Slack - for quick questions and on-line discussion
- Mailing list - where all ideas are discussed with the wider community and decisions are made on a project direction
- Jira - used to track issues or progress on a specific topic. Jira tickets usually arise directly from bug reports, out of decisions made on mailing list discussions, or as an alternative to a discussion on the mailing list*

* In this case the ticket may be referred to the mailing list to seek more input

If it didn’t happen on the mailing list, it didn’t happen. So decisions made on slack should be recorded through a post to the mailing list.

See you tomorrow.

Alex

Reply | Threaded
Open this post in threaded view
|

Re: [gsoc] Weekly meeting tomorrow

Gilles Sadowski-2
Hi.

Le mer. 12 juin 2019 à 21:34, Alex Herbert <[hidden email]> a écrit :
>
> Time for a weekly meeting.
>
> Thursday UTC +4.

I won't be present at 6 PM (Brussels time).

>
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=13&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800 <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=6&day=13&hour=16&min=0&sec=0&p1=136&p2=224&p3=265&p4=1249&p5=1860&iv=1800>
>
> Here’s a preliminary agenda:
>
> - Present progress
> — What have you done last week?
> — What are your plans for the next week?
> — What is blocking your progress?
>
> - Daily stand-up?
> There was a positive response from my suggestion to daily stand-ups. But no-one participated. Please bring your thoughts to the meeting tomorrow. I would favour a 5 minute daily stand-up just so that we all know how work is moving forward.
>
> - Mailing list vs. Slack vs. Jira
> We tried to clear up the different channels and how to use them in a Slack discussion. Please bring your thoughts on this:
>
> - Slack - for quick questions and on-line discussion
> - Mailing list - where all ideas are discussed with the wider community and decisions are made on a project direction

Most of what I've seen on slack should have been on the ML.

> - Jira - used to track issues or progress on a specific topic. Jira tickets usually arise directly from bug reports, out of decisions made on mailing list discussions, or as an alternative to a discussion on the mailing list*
>
> * In this case the ticket may be referred to the mailing list to seek more input
>
> If it didn’t happen on the mailing list, it didn’t happen. So decisions made on slack should be recorded through a post to the mailing list.

Moreover, decisions *about code* made on slack are not decisions: they
will become so only after nobody objects to them on the "dev" ML. ;-)

Regards,
Gilles

>
> See you tomorrow.
>
> Alex
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]