Hi all,
As you may already know, unfortunately, our application for GSoD was
unsuccessful.
But the thinking we have made for this is also very helpful to the Flink
community, such as the optimization of the document structure proposed
by @Fabian
Hueske the addition of better tutorials, Add Chine
Thank you so much for driving this, really great job!
About Flink internals: Agreed, that is not a good match. It needs to deep
technical understanding. Also, the benefit of having a technical writer
(make this easily understandable to less involved developers) is not as
helpful there.
Also regis
Hi everyone,
I have just submitted our application :)
@Stephan Ewen , @David Anderson :
Please remember to register as mentor by Tuesday:
https://docs.google.com/forms/d/e/1FAIpQLSe-JjGvaKKGWZOXxrorONhB8qN3mjPrB9ZVkcsntR73Cv_K7g/viewform
Cheers,
Konstantin
On Thu, Apr 18, 2019 at 1:04 PM jinch
Hi Konstantin&all,
The blog post is released, please see
https://flink.apache.org/news/2019/04/17/sod.html
And I think is better to spread the word by https://twitter.com/ApacheFlink,
but I found that only PMC can manage and publish messages.
Help spread the word here:
https://twitter.com/sunji
Thanks Konstantin!
I registered as an alternative administrator, and have had left few
comments at the blog post.
Best,
Jincheng
Fabian Hueske 于2019年4月18日周四 上午12:36写道：
> Thanks Konstantin!
>
> I registered as a mentor and will have a look at the blog post.
>
> Best, Fabian
>
> Am Mi., 17. Apr
Thanks Konstantin!
I registered as a mentor and have left comments on the blog pull request.
Regards,
Jark
On Thu, 18 Apr 2019 at 00:36, Fabian Hueske wrote:
> Thanks Konstantin!
>
> I registered as a mentor and will have a look at the blog post.
>
> Best, Fabian
>
> Am Mi., 17. Apr. 2019 um
Thanks Konstantin!
I registered as a mentor and will have a look at the blog post.
Best, Fabian
Am Mi., 17. Apr. 2019 um 18:14 Uhr schrieb Konstantin Knauf <
konstan...@ververica.com>:
> Hi everyone,
>
> a few updates on our application:
>
> 1. As Aizhamal (Thanks!) has suggested I also added t
Hi everyone,
a few updates on our application:
1. As Aizhamal (Thanks!) has suggested I also added the information to
submit during our application to the Google doc [1] and Fabian added a
description for the SQL project idea (Thanks!).
2. I had a quick chat with Fabian offline and we concluded,
+Konstantin Knauf this is looking good, thanks
for sharing!
I also created a similar doc for Apache Airflow [1]. It is a bit messy, but
it has questions from the application form that you can work with.
Cheers,
Aizhamal
[1]
https://docs.google.com/document/d/1HoL_yjNYiTAP9IxSlhx3EUnPFU4l9WOT9En
Hi all,
I'm very happy to see this project happening!
Thank you for the proposal Konstantin! One idea for the "related material":
we could also link to talks or blog posts about concepts / monitoring /
operations. Potential writers could feel overwhelmed by our demand for
improvements, without any
Hi everyone,
thanks @Aizhamal Nurmamat kyzy . As we only have one
week left until the application deadline, I went ahead and created a
document for the project ideas [1]. I have added the description for the
"stream processing concepts" as well as the "deployment & operations
documentation" projec
Hello everyone,
@Konstantin Knauf - yes, you are correct.
Between steps 1 and 2 though, the open source organization, in this case
Flink, has to be selected by SoD as one of the participating orgs *fingers
crossed*.
One tip about organizing ideas is that you want to communicate potential
project
Hi all,
I read through the SoD documentation again, and now I think, it would
actually make sense to split (1) up into multiple project ideas. Let me
summarize the overall process:
1. We create & publish a list of project ideas, e.g. in a blog post. (This
can be any number of ideas.)
2. Potential
Hi all,
I'm fine with only preparing the first proposal. I think it's reasonable
because the first proposal is more attractive
and maybe there is not enough Chinese writer. We can focus on one project
to come up with a concrete and
attractive project plan.
One possible subproject could be rework
I am honored to have the opportunity to do a second organization
administrator‘s works!
It seems that one project and multiple projects have their own advantages.
My understanding is that even if we only have one project, we also can have
multiple mentors and recruit enough writers.
Fabian Huesk
Hi all,
thanks Ken & Jark for your comments regarding the Chinese translation
proposal. I seems there is a agreement that project (1) (Improve English
documentation) has a higher priority for us than project (2) (Chinese
translation). We could still write two proposals and indicate priorities
acco
Yes, I think we would get at most one project accepted.
Having all options in a rather generic proposal gives us the most
flexibility to decide what to work on once the proposal is accepted.
On the other hand, a more concrete proposal might look more attractive for
candidates.
I'm fine either way,
I would suggest to make one proposal and have the subsections only in the
project plan.
My understanding is that we need to indicate priorities between proposals
and might get only one, so it would be good to not subdivide.
On Fri, Apr 12, 2019 at 9:58 AM Fabian Hueske wrote:
> Hi everyone,
>
>
Now that you mentioned configuration, I think the descriptions of the
various configuration options could also be a potential topic. The
descriptions follow very different styles and are often more geared
towards Flink developers than actual users.
On 12/04/2019 09:57, Fabian Hueske wrote:
Hi
Hi everyone,
I think we can split the first project that Stephan proposed into smaller
ones:
> (1) Create or rework setup / tutorials / concepts docs
> (2) Complete (or advance) the Chinese translation
1.1 Improving (extracting) the documentation of stream processing concepts:
Event-time, Timers
Hi Konstantin, Ken,
I agree that Chinese documentation is mainly a translation.
> Does anyone from the Blink team have input on whether there is existing,
original Chinese documentation which should be translated to English?
There is a public Blink documentation [1] which is English.
We have a
Hi Konstantin,
Comments inline below…
— Ken
> On Apr 11, 2019, at 9:05 AM, Konstantin Knauf
> wrote:
>
> Hi everyone,
>
> I will start going through the registration process tomorrow (CET).
> Jincheng (cc) reached out to me directly and offered to be the second
> organization administrator.
Hi everyone,
I will start going through the registration process tomorrow (CET).
Jincheng (cc) reached out to me directly and offered to be the second
organization administrator. So, we are all set in that regard.
In terms of mentors, we now have
* myself
* Fabian
* David
* Stephan
* Jark (Chine
So we have two ideas for docs projects now:
(1) Create or rework setup / tutorials / concepts docs
(2) Complete (or advance) the Chinese translation
Should we apply for both (and let the SoD committee select whichever they
want to sponsor) or select one of them?
For project (2), this sounds to m
Thanks for the clarification Aizhamal!
This is really helpful and will make it a lot easier to coordinate :-)
As for next steps, I found this email on the d...@community.apache.org
mailing list:
==
Hi All,
As mentioned the applications for the Goog
Hi Aizhamal,
That's really interesting. We have an ongoing proposal for supporting
Chinese documentation, see FLIP-35 [1].
I think it's a good idea to propose Chinese translation as a project. It's
a good chance to improve the localization user experience of Flink
documentation.
I can help as a m
Hello everyone,
@Fabian Hueske - SoD setup is a little bit different.
The ASF determined that each project would be allowed to apply
individually[1], rather than applying as a single large organization.
Each project applies as an org, with two organizers (administers) and at
least two mentors. A
Hi Aizhamal,
I assume SoD is language-agnostic, so one possible project would be to get a
tech writer for the Chinese versions of all of the Flink documentation, yes?
Regards,
— Ken
> On Apr 5, 2019, at 3:43 PM, Aizhamal Nurmamat kyzy
> wrote:
>
> Hello everyone,
>
> TL;DR If you need some
Hi,
Thanks for stepping up Konstantin! Yes, I'd be up to serve as a mentor as
well.
I assume the set up is similar as for Google Summer of Code (GSoC).
For GSoC the whole Apache Software Foundation applied as an organization
(not every individual project).
Hence, there should be only two organize
Hi all,
I am happy to start our application process and help as a mentor. For our
application, we need a second organization administrator (assuming I am the
first). The tasks as an administrator are listed in [1] (basically only
guiding the organization through the SoD process). Is anyone interes
Hi all!
This is a really great initiative, I think the Flink docs could benefit big
time from this.
Aside from some nice tutorials, I think that especially the docs about
concepts, architecture, and deployment need a lot of work, so users
understand how powerful Flink really is.
I quickly connect
Hi Aizhamal, hi everyone,
Thanks for sharing this opportunity with our community!
I can think of a few projects that could be done as part of GSoD.
1) Flink's user documentation is (IMO) fairly extensive and mostly
complete, but its structure could be improved in some areas (event-time,
state man
Hello everyone,
TL;DR If you need some improvements for Flink documentation, apply to
Season of Docs before April 23rd.
Background:
Season of Docs is like Google Summer of Code, but for documentation.
Projects write ideas on how they would like to improve their documentation,
then if they are ac
33 matches
Mail list logo
