Thanks for clarifying. I like the idea.
On Thu, Nov 7, 2019 at 21:08 Kenneth Knowles wrote:
> On Thu, Nov 7, 2019 at 10:22 AM Matt Sicker wrote:
>
> > On Tue, 5 Nov 2019 at 21:49, Kenneth Knowles wrote:
> > >- should we (diversity@apache) take an active monitoring role so we
> > see
> > >
On Thu, Nov 7, 2019 at 10:22 AM Matt Sicker wrote:
> On Tue, 5 Nov 2019 at 21:49, Kenneth Knowles wrote:
> >- should we (diversity@apache) take an active monitoring role so we
> see
> >some of what happens on Jira, code review, and mailing lists? (is
> this just
> >way too much?)
>
On Tue, 5 Nov 2019 at 21:49, Kenneth Knowles wrote:
>- should we (diversity@apache) take an active monitoring role so we see
>some of what happens on Jira, code review, and mailing lists? (is this just
>way too much?)
Can you elaborate on this? Are you talking about watching the
Hi folks,
- I think it would be a very good idea to interview the Outreachy interns
to have a better overview of the necessary fields of the friction log template
and to perform any updating if required.
- Also, I think having an open space could be very useful in order to, as
Hi folks,
Thank you, @Kenneth Knowles and @Laura Alejandra Zanella
Calzada for the amazing work done so far.
I agree, to make this successful, it should be super easy to fill out. To
pre-fill all the data fields, for the Outreachy program:
1. would it be a good idea to interview our Outreachy
Kenneth Knowles wrote on 2019-11-5 10:49PM EST:
...snip...> We had some other ideas about how to make this useful:
>
>- mentor should write friction log on behalf of the intern (intern could
>also write their own)
Allowing both seems useful; interns that get into the process will
provide
Hi all,
Laura and I chatted on Slack about the friction log and we decided that the
template from Tensorflow is about right.
I tried to create a fresh document for ASF that captures the same idea.
Here is the first draft: https://s.apache.org/friction-log. That link gives
comment access, but I
