Looking at the threads, it seems like we have a few ideas as below:

supporting Apache Arrow
Supporting a history server.
Supporting more application DSLs

Any other ideas would be welcome to be suggested on this thread.
Wonook


2019년 1월 16일 (수) 오후 2:53, 송원욱 <[email protected]>님이 작성:

> It looks like GSoC 2019 is coming on the way. We’ve had a successful year
> last summer, with two GSoC students contributing to our project. If we are
> to receive students this year as well, I think it’s a good time to start
> brainstorming.
>
> How do you all think?
>
>
> Begin forwarded message:
>
> *From: *"'sttaylor' via Google Summer of Code Mentors List" <
> [email protected]>
> *Subject: **[GSoC Mentors] GSoC 2019 Org applications now open*
> *Date: *16 January 2019 at 5:02:47 AM GMT+9
> *To: *Google Summer of Code Mentors List <
> [email protected]>
> *Reply-To: *sttaylor <[email protected]>
>
> Hi all,
>
> If your open source organization is interested in being a mentoring
> organization for Google Summer of Code 2019 please be sure to submit your
> organization's application via g.co/gsoc before February 6 at 20:00 UTC.
>
> Organizations chosen for GSoC 2019 will be announced on February 26th.
>
> Best,
> Google Open Source Programs Office
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Summer of Code Mentors List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to
> [email protected].
> Visit this group at
> https://groups.google.com/group/google-summer-of-code-mentors-list.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/05249bbe-76be-4d16-8cab-afcd23c03268%40googlegroups.com
> <https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/05249bbe-76be-4d16-8cab-afcd23c03268%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

Reply via email to