From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [GSoC 2019] Introduction Email - Atharva Lele
Date: Wed, 8 May 2019 14:21:04 +0200 [thread overview]
Message-ID: <20190508122104.GC31209@scaer> (raw)
In-Reply-To: <CABM+sgryAAcEjpJiBAGxQ3pyDLGiDjavoxN0X4o8pdfqz_da9g@mail.gmail.com>
Atharva, All,
On 2019-05-08 17:04 +0530, Atharva Lele spake thusly:
> I read both of your replies.
> > We'll see to schedule a longer meeting, probably hang-out or something,
> > on Sat or Sun, so we can debrief more in depth. ?
> ?
> Since Yann can't make it to a meeting/hangout on weekdays, we can schedule
> it on weekends. I'll be available during the time slot I mentioned (10am to 10pm IST)
Let's all speak UTC (or GMT) for the sake of synchronizing; always
switching between timezones is error-prone. 10am IST is 04:30Z, 10pm IST
is 16:30Z.
Actually, I can make it on Tuesdays and Thursdays without any problem,
if we can schedule it between 14:30Z and 16:30Z; other days of the week,
we'd have to schedule it between 15:30Z and 16:30Z.
> > Maybe it would be useful to create a calendar to easily track absences (exams,
> > holidays, ...) of both Atharva and the mentors (Yann and me)?
> Regarding the calendar to track absences (as Arnout suggested), do you
> have any particular service in mind or do we just note it down somewhere?
What about creating a page on the elinux.org wiki, which is where we
already have the Buildroot wiki pages, to track all your GSoC-related
activity? You'd report progress, pain-points, proposals, achievements,
and so on in there, it can act as a journal, etc...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-05-08 12:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 13:46 [Buildroot] [GSoC 2019] Introduction Email - Atharva Lele Atharva Lele
2019-03-26 22:09 ` Arnout Vandecappelle
[not found] ` <d528d059-b900-7b18-7772-dbb3350f1af6@mind.be>
[not found] ` <CABM+sgpVOb0gxPeA3fTm4Luup6wDgyE56DPB1taVouCB4JmryA@mail.gmail.com>
2019-04-01 16:58 ` Atharva Lele
2019-04-02 9:21 ` Arnout Vandecappelle
2019-04-02 15:30 ` Atharva Lele
2019-04-02 18:19 ` Yann E. MORIN
2019-04-04 15:55 ` Atharva Lele
2019-04-09 18:38 ` Atharva Lele
2019-05-02 19:27 ` Atharva Lele
2019-05-02 19:57 ` Yann E. MORIN
2019-05-07 13:26 ` Atharva Lele
2019-05-07 21:17 ` Yann E. MORIN
2019-05-07 22:12 ` Arnout Vandecappelle
2019-05-08 11:34 ` Atharva Lele
2019-05-08 12:21 ` Yann E. MORIN [this message]
2019-05-08 12:51 ` Atharva Lele
2019-05-08 13:44 ` Arnout Vandecappelle
2019-05-08 13:55 ` Atharva Lele
2019-05-08 21:28 ` Arnout Vandecappelle
2019-05-09 6:49 ` Atharva Lele
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190508122104.GC31209@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.