>>
> > >> wrote:
> > >>
> > >> > Hello,
> > >> >
> > >> > Absent any comments, I was attempting to create a connector FLIP as
> > >> > described above, however it appears that I do not have permissions
> to
e:
> >>
> >> > Hello,
> >> >
> >> > Absent any comments, I was attempting to create a connector FLIP as
> >> > described above, however it appears that I do not have permissions to
> >> edit
> >> > confluence to do so. Can
>> >
>> > -Daniel
>> >
>> > On Mon, Feb 27, 2023 at 10:28 AM Daniel Collins
>> > wrote:
>> >
>> > > Hello Martijn,
>> > >
>> > > Thanks for the redirect!
>> > >
>> > > > The process f
r me?
> >
> > -Daniel
> >
> > On Mon, Feb 27, 2023 at 10:28 AM Daniel Collins
> > wrote:
> >
> > > Hello Martijn,
> > >
> > > Thanks for the redirect!
> > >
> > > > The process for contributing a connector is to create
hat I do not have permissions to edit
> confluence to do so. Can someone please add access for me?
>
> -Daniel
>
> On Mon, Feb 27, 2023 at 10:28 AM Daniel Collins
> wrote:
>
> > Hello Martijn,
> >
> > Thanks for the redirect!
> >
> > > The
ijn,
>
> Thanks for the redirect!
>
> > The process for contributing a connector is to create a Connector FLIP
> [1], which needs to be discussed and voted on in the Dev mailing list [2]
>
> I don't mind doing this, but would like to get a read of the room before
> doing
Hello Martijn,
Thanks for the redirect!
> The process for contributing a connector is to create a Connector FLIP
[1], which needs to be discussed and voted on in the Dev mailing list [2]
I don't mind doing this, but would like to get a read of the room before
doing so. If people obje
Hi Daniel,
Thanks for reaching out. Keep in mind that you weren't subscribed to the
Flink Dev mailing list, I've just pushed this through the mailing list
moderation.
The process for contributing a connector is to create a Connector FLIP [1],
which needs to be discussed and voted on
ale- what would be the
process for contributing this to flink?
I've opened a JIRA to do this
https://issues.apache.org/jira/projects/FLINK/issues/FLINK-31229, if this
seems like a reasonable thing to do could someone assign it to me?
The code for the connector currently lives here
https://g
sign it to me.
> > > >
> > > > Best regards,
> > > > Jörn
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Feb 8, 2023 at 11:38 AM Matthias Pohl
> > > > wrote:
> > > >
> > > &
x27;s a good pick? If yes, please assign it to me.
> > >
> > > Best regards,
> > > Jörn
> > >
> > >
> > >
> > >
> > > On Wed, Feb 8, 2023 at 11:38 AM Matthias Pohl
> > > wrote:
> > >
> > >
& Table API).
> >
> > Do you think that's a good pick? If yes, please assign it to me.
> >
> > Best regards,
> > Jörn
> >
> >
> >
> >
> > On Wed, Feb 8, 2023 at 11:38 AM Matthias Pohl
> > wrote:
> >
> > > Just as a
pick? If yes, please assign it to me.
>
> Best regards,
> Jörn
>
>
>
>
> On Wed, Feb 8, 2023 at 11:38 AM Matthias Pohl
> wrote:
>
> > Just as a reminder for everyone: Please label issues using the "starter"
> > label if you have Jira issues that are
t; Just as a reminder for everyone: Please label issues using the "starter"
> label if you have Jira issues that are suitable for people that want to
> start contributing. This is documented in the Flink Jira process
> documentation [1].
>
> Happy coding! Best,
> Matth
Just as a reminder for everyone: Please label issues using the "starter"
label if you have Jira issues that are suitable for people that want to
start contributing. This is documented in the Flink Jira process
documentation [1].
Happy coding! Best,
Matthias
[1]
https://cwiki.
bueingto SQL part, i would like to recommend the
> FLINK-6810[1] FLINK-20787 [2] as a start. By contributing it, you may get
> more familiar to the stack of Flink SQL. I have no right to assign ticket,
> but i think you can just comment in the jira you're interested in and ask
>
Hi, Joern.
Weclome to contribute.
As for contritbueingto SQL part, i would like to recommend the FLINK-6810[1]
FLINK-20787 [2] as a start. By contributing it, you may get more familiar to
the stack of Flink SQL. I have no right to assign ticket, but i think you can
just comment in the jira
Hello all,
I contributed 2 -3 commits once to fix small issues I found in Flink, and
would love to start contributing again.
I am interested in working on Testing or SQL (or anything else where help
is needed).
Is there anyone here who could assign me a smaller Jira ticket so I can get
started
recommend opening a Jira
ticket with a description of the bug/problem and how you want to fix it.
Then it can also be assigned to you and a PR can be created.
Let me know if you have any more questions!
Best regards,
Martijn
[1] https://flink.apache.org/contributing/contribute-code.html
[2] https
Hi Flink Dev,
My company uses flink, and we have some code changes that we'd like to
contribute to the main fork.
Can I get your advice on what to do here?
The features we wish to contribute are as follow:
1. JDBC connector filter pushdown, already tracked on JIRA:
https://issues.apache.o
Hi Shubham,
Apologies for the late reply. It's great to hear that you're so willing and
enthusiastic to contribute towards Flink.
As a next step after your starter tasks, one of the best ways to get
involved is to have a look at some tickets that are test stabilities. For
example, you could have
Gentle reminder!!
On Sat, May 21, 2022 at 7:34 PM Shubham Bansal
wrote:
> Hi Everyone,
>
> I have been looking at some starter tagged JIRA in the last couple of
> weeks.
>
> https://issues.apache.org/jira/browse/FLINK-27506
> https://issues.apache.org/jira/browse/FLINK-27508
> https://issues.apa
Hi Everyone,
I have been looking at some starter tagged JIRA in the last couple of weeks.
https://issues.apache.org/jira/browse/FLINK-27506
https://issues.apache.org/jira/browse/FLINK-27508
https://issues.apache.org/jira/browse/FLINK-27507
https://issues.apache.org/jira/browse/FLINK-27509
One of
Hi Martijn,
I am happy to start wherever you recommend, but typically like moving
to complex tasks soon.
My interest and expertise lies in runtime and query processing.
Atri
On Mon, May 9, 2022 at 8:13 PM Martijn Visser wrote:
>
> Hi Atri, thanks for reaching out! How familiar are you with Fli
Hi Atri, thanks for reaching out! How familiar are you with Flink? I could
imagine that it might make sense to start with addressing a test stability
to understand the Flink codebase, but you could of course also help out
with a review of a PR. For example,
https://github.com/apache/flink/pull/1840
Gentle reminder, please
On Mon, 9 May 2022, 01:15 Atri Sharma, wrote:
> Hi Folks,
>
> I have recently started using Flink and am excited to contribute to
> the same. I am looking at two subcomponents:
>
>
> https://issues.apache.org/jira/browse/FLINK-26041?jql=project%20%3D%20FLINK%20AND%20compo
Hi Folks,
I have recently started using Flink and am excited to contribute to
the same. I am looking at two subcomponents:
https://issues.apache.org/jira/browse/FLINK-26041?jql=project%20%3D%20FLINK%20AND%20component%20%3D%20%22Runtime%20%2F%20Coordination%22%20AND%20status%20%3D%20Open
https://
Hi Mason,
Thanks for the efforts. I could see that Ingo has already assigned it to
you (and thanks Ingo for the action).
Best Regards,
Yu
On Tue, 12 Apr 2022 at 14:42, Mason Chen wrote:
> Hi Devs,
>
> Could a committer assign me this ticket:
> https://issues.apache.org/jira/browse/FLINK-27195
Hi Devs,
Could a committer assign me this ticket:
https://issues.apache.org/jira/browse/FLINK-27195? I have been taking a
deeper look into the Kafka Source and would like to contribute back a
bugfix. I have a minimal test case and the fix should be simple. Thanks all!
Best,
Mason
Hi, Vivin!
Thanks for your interest in participating in Google Season of Docs (GSoD)
and contributing to Apache Flink! We're glad that you enjoyed working with
Flink before, and that it motivated you to now apply to GSoD.
Regarding what you can work on, there are no strict requirements
Respected Sir
I am currently a final year undergrad student at National Institute of
Technology Surathkal, India.
I have extensively worked on Apache Flink in my previous internship where I
had to create a database of billions of IPs in the world along with data
associated with it.
The power of F
Chesnay Schepler created FLINK-15765:
Summary: Contributing section in README should point to
contribution guide
Key: FLINK-15765
URL: https://issues.apache.org/jira/browse/FLINK-15765
Project
e.org/contributing/how-to-contribute.html
Best,
Congxian
hechao <13250818...@163.com> 于2019年12月25日周三 下午4:24写道：
>
>
> HiGuys,
>
> I want to contribute to ApacheFlink.Would you please give me the
> permission as a contributor?My JIRA ID is hechao.
> | |
> hechao
> |
HiGuys,
I want to contribute to ApacheFlink.Would you please give me the permission as
a contributor?My JIRA ID is hechao.
| |
hechao
|
|
13250818...@163.com
|
签名由网易邮箱大师定制
n a list of starter
> issues. Hence, I would recommend to take a look at the open issues and ask
> on issues which are interesting to you whether this could be a good starter
> issue or not.
>
> Cheers,
> Till
>
> On Thu, Sep 12, 2019 at 7:23 AM Anoop Hallur
> wrote:
>
ng to you whether this could be a good starter
issue or not.
Cheers,
Till
On Thu, Sep 12, 2019 at 7:23 AM Anoop Hallur wrote:
> Hello Flink Devs,
> I am interested in contributing to Apache Flink and I am looking for
> beginner friendly issues/tasks to hit the ground running. *Can somebo
Hello Flink Devs,
I am interested in contributing to Apache Flink and I am looking for
beginner friendly issues/tasks to hit the ground running. *Can somebody
recommend good issues for first time contributors* ?
Also, can somebody add me to JIRA project for Flink ? My JIRA username is
anoophallur
t;, or is it more
> appropriate to create a JIRA ?
>
> [1] - "Is this a contribution just for the sake of getting a commit in an
> open source project (fixing typos, style changes merely for taste reasons".
> ~ contribute code guide
> <https://flink.apache.org/contributin
Yun Tang created FLINK-13067:
Summary: Fix broken links to contributing docs
Key: FLINK-13067
URL: https://issues.apache.org/jira/browse/FLINK-13067
Project: Flink
Issue Type: Bug
r taste reasons".
~ contribute code guide
<https://flink.apache.org/contributing/contribute-code.html>
[2] - "Whenever you are about to copy/paste some code, or reproduce a
similar type of functionality in a different place, think about the ways
how to refactor/reuse/abstract the changes to a
Hi Fabian,
Yes, I think so.
We can find a way to move the translated content to crowdin to reuse the
translation effort if we want to migrate to Docusaurus in the future.
Regards,
Jark
On Fri, 15 Feb 2019 at 15:19, Fabian Hueske wrote:
> Hi Jark,
>
> Thanks so much for evaluating Docusaurus an
Hi Jark,
Thanks so much for evaluating Docusaurus and Crowdin and writing up this
report!
It seems that staying with the current approach and avoiding the effort of
porting the documentation is the best solution for now.
We might want to reconsider Docusaurus if we want to restructure the
documen
Hi all,
Qianjing Xu and I have been exploring Docusaurus and crowdin in recent days
to see how can Flink fit into them to support multi-language.
Here is the summary from our side:
(we didn't learn deeply, so we may miss something or misunderstand. Please
correct us if we are wrong)
# What is Do
Hi,
I agree with the proposal, Gordon and Jark, and I think it's a good solution
for major doc changes. We also created separated JIRAs for English
documentation in the past.
For minor doc changes, I think it’s better to encourage Chinese-speaking
contributors to participate in the reviewing p
Hi @Sijie,
Thank you for the valuable information. I will explore Docusaurus and
feedback here.
Best,
Jark
On Tue, 12 Feb 2019 at 18:18, Fabian Hueske wrote:
> Hi everyone,
>
> +1 to what Gordon and Jark proposed.
> We should make use of the review bot to ensure that new features are
> documen
Hi everyone,
+1 to what Gordon and Jark proposed.
We should make use of the review bot to ensure that new features are
documented at least in English.
If the Chinese docs are not updated, a Jira issue must be created.
@Sijie, thank for the pointer to Docusaurus! IMO, this looks very
interesting a
Hi,
Sorry for interrupting the thread. But this topic sounds interesting to me.
It might be worth for you guys checking out docusaurus
https://docusaurus.io/docs/en/translation . Docusaurus is a documentation
framework open sourced by Facebook. It has handled versioning and
localization (via crowd
On Tue, Feb 12, 2019 at 3:17 PM Jark Wu wrote:
> Hi Gordon,
>
> I totally agree with your proposal.
>
> A minor comment: "updated required English documentation" should be
> "updated required Chinese documentation" ?
>
Actually, that was what I meant to say.
My intention is that at least the Eng
Hi Gordon,
I totally agree with your proposal.
A minor comment: "updated required English documentation" should be
"updated required Chinese documentation" ?
Btw, I like the "zh-doc" label!
Regards,
Jark
On Tue, 12 Feb 2019 at 14:48, Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> While I 100% agree wi
Hi,
While I 100% agree with @Xingcan that we should try to avoid adding extra
burden for contributors, at the very least, creating JIRA issues for adding
missing Chinese / English document updates must be done.
In the past, even with English documentation only, we already had the
problem of mergi
Hi @Xingcan,
> I think assigning pages to someones and synchronizing them regularly may
be a better idea.
> 1. We encourage contributors who are familiar with Chinese and would like
to do the translation to provide Chinese doc updates in sync, but should
not add extra burden (even like creating tr
Hi all,
Thanks @Jark for creating the translation terminology document! I think the
idea of keeping some of the terminologies untranslated and keeping such
document in place is absolutely good.
I actually share the same concern with @Shaoxuan regarding the discrepancy
getting larger. The dilemma i
Hi,
Thank you for working on this.
I think assigning pages to someones and synchronizing them regularly may be a
better idea.
1. We encourage contributors who are familiar with Chinese and would like to do
the translation to provide Chinese doc updates in sync, but should not add
extra burden
Hi Shaoxuan,
Thank you for your feedback.
If the author is not familiar with Chinese, he/she should create a
translation JIRA before the pull request is merged in.
The created JIRA can be attached a "chinese-translation" tag so that it can
be searched easily. Then a Chinese contributor can take t
Thanks for spending efforts to build a Flink web in Chinese, everyone.
Good job, Jark!
This looks look to me. I have only one concern about the synchronization of
the English and Chinese website. We can not expect the author of the
English doc to produce Chinese doc at the same time. If no one fo
Jark Wu created FLINK-11555:
---
Summary: Translate "Contributing Code" page into Chinese
Key: FLINK-11555
URL: https://issues.apache.org/jira/browse/FLINK-11555
Project: Flink
Issue Type
n the long run the differences might pile
> up.
>
> Looking forward to contributing to this effort!
>
> Thanks,
> Rong
>
>
>
> On Tue, Feb 5, 2019 at 4:10 AM Jark Wu wrote:
>
> > Hi all,
> >
> > Thanks for the positive feedback we received so far.
&
long run the differences might pile
up.
Looking forward to contributing to this effort!
Thanks,
Rong
On Tue, Feb 5, 2019 at 4:10 AM Jark Wu wrote:
> Hi all,
>
> Thanks for the positive feedback we received so far.
>
> I have created two umbrella JIRA for tracking the efforts:
&g
Hi all,
Thanks for the positive feedback we received so far.
I have created two umbrella JIRA for tracking the efforts:
For flink-web: https://issues.apache.org/jira/browse/FLINK-11526
For flink-docs: https://issues.apache.org/jira/browse/FLINK-11529
I'm working on the framework changes for fli
Nice proposal
+1
On Tue, Feb 5, 2019 at 8:16 AM Hequn Cheng wrote:
> Hi,
>
> big +1 for this!
> Thank you Jark for writing the great document. I totally agree with the
> proposal. It not only keep the English document same as before but also
> proposes a way to integrate with Chinese ones.
>
>
Hi,
big +1 for this!
Thank you Jark for writing the great document. I totally agree with the
proposal. It not only keep the English document same as before but also
proposes a way to integrate with Chinese ones.
Best, Hequn
On Mon, Feb 4, 2019 at 6:18 PM Fabian Hueske wrote:
> Happy Chinese
Happy Chinese New Year!
Thank you Jark for working on a prototype and writing up the this great
proposal.
+1 for the suggested approach
Best,
Fabian
Am Mo., 4. Feb. 2019 um 11:05 Uhr schrieb jincheng sun <
sunjincheng...@gmail.com>:
> +1 ， Happy Chinese New Year! :)
>
> Best，Jincheng
> From Sin
+1 ， Happy Chinese New Year! :)
Best，Jincheng
>From Singapore
Jark Wu 于2019年2月4日 周一13:23写道：
> Hi all,
>
> I have drafted the proposal:
>
> https://docs.google.com/document/d/1R1-uDq-KawLB8afQYrczfcoQHjjIhq6tvUksxrfhBl0/edit#
> Please feel free to give any feedbacks!
>
> I have also created a pro
+1 for the proposal.
Cheers,
Till
On Mon, Feb 4, 2019 at 9:50 AM Robert Metzger wrote:
> Hey Jark,
>
> Happy New Year :)
>
> thanks a lot for the proposal and the prototype. I fully agree with your
> proposal and I think it's good to go!
>
> Regarding the review-bot: We can add another item for
Hey Jark,
Happy New Year :)
thanks a lot for the proposal and the prototype. I fully agree with your
proposal and I think it's good to go!
Regarding the review-bot: We can add another item for documentation in both
English and Chinese, once the framework for the Flink docs has been merged.
On
Hi all,
I have drafted the proposal:
https://docs.google.com/document/d/1R1-uDq-KawLB8afQYrczfcoQHjjIhq6tvUksxrfhBl0/edit#
Please feel free to give any feedbacks!
I have also created a prototype to integrate Chinese for flink-web, here is
the branch: https://github.com/wuchong/flink-web/tree/mult
Hi,
Great seeing efforts in pushing this forward, Jark!
A bit late in the party here, but I just want to also point out that:
- +1 to https://flink.apache.org/zh/ as the website address
- Add to the contribution checklist in PRs that both English / Chinese docs
have been updated accordingly.
I
Hi Jark,
Thanks for working out a plan to integrate the Chinese translation!
I would propose to first contribute and integrate the Chinese version of
the main page (flink.apache.org).
It is much smaller than the docs and a smaller scope might help to find
tricks to ease the integration of the doc
Hi,
Thank you all for welcoming this proposal.
I will draft a detailed proposal about how to do contribute it step by step
in the next few days, and create umbrella JIRA once the proposal is
accepted.
@Fabian @JIngcheng Regarding the name, I'm fine with
https://flink.apache.org/zh/.
@Yun Tang T
Is the build-system for flink-china.org identical to flink-web?
On 28.01.2019 12:48, Jark Wu wrote:
Hi all,
In the past year, the Chinese community is working on building a Chinese
translated Flink website (http://flink.apache.org) and documents (
http://ci.apache.org/projects/flink/flink-docs-
Hi Jark,
I am glad to see your exciting email about contributing to Flink Chinese
Community. Remebering the days to solve outstanding issues in Spark
Officical Documents, the project was developped slowly, I am looking forward
to more and more contributions to Flink Chinese Community. Of
Hi Jark,
Thank you for starting this discussion.I am very willing to participate in
flink document translation.
Best,
Nicholas
--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
create a jira for the Chinese documents.
-- --
??: "fudian.fd";
: 2019??1??29??(??) 1:30
??: "dev";
: Re: [DISCUSS] Contributing Chinese website and docs to Apache Flink
Hi Jark,
Thanks a lot for startin
Keep also in mind the other direction eg a new/modified version of the Chinese
documentation needs to be reflected in the English one.
> Am 29.01.2019 um 06:35 schrieb SteNicholas :
>
> Hi Jark,
>
> Thank you for starting this discussion.I am very willing to participate in
> flink document tra
Hi Jark,
Thank you for starting this discussion.I am very willing to participate in
flink document translation.
Best,
Nicholas
--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
Hi Jark,
Thanks a lot for starting the discussion! It would be great to have an official
Flink Chinese doc. For the long term maintaining problem, I think creating a
JIRA when the English documentation is updated is a good idea. Should we add
one item such as "Does this pull request updated th
Thanks Jark starting this discussion!
Hi Fabian, very glad to hear that you like this proposal.
As far as I know， `zh` is the language, `cn` is the territory, such as:
`zh-cn` representative
Simplified Chinese (China) , `zh-tw` representative Traditional Chinese
(Taiwan), So i like the naming the
gt; > You signed out in another tab or window. Reload to refresh your session.
> > github.com
> >
> > Best
> > Yun Tang
> >
> > From: Fabian Hueske
> > Sent: Monday, January 28, 2019 21:48
> > To: dev
> > Sub
cn>
> You signed in with another tab or window. Reload to refresh your session.
> You signed out in another tab or window. Reload to refresh your session.
> github.com
>
> Best
> Yun Tang
>
> From: Fabian Hueske
> Sent: Monday, Janua
m
Best
Yun Tang
From: Fabian Hueske
Sent: Monday, January 28, 2019 21:48
To: dev
Subject: Re: [DISCUSS] Contributing Chinese website and docs to Apache Flink
Hi Jark,
Thank you for starting this discussion!
I'm very happy about the various efforts to support the Chinese Flin
Hi Jark,
Thank you for starting this discussion!
I'm very happy about the various efforts to support the Chinese Flink
community.
Offering a translated website and documentation gives Flink a lot more
reach and will help many users.
I think integrating the website and documentation as subdirector
Hi all,
In the past year, the Chinese community is working on building a Chinese
translated Flink website (http://flink.apache.org) and documents (
http://ci.apache.org/projects/flink/flink-docs-master/) in order to help
Chinese speaking users. This is http://flink-china.org and it has received
a
IMHO it would be a pity if we lost the Git history of changes made to the
Blink repository since the time that it was forked from Flink.
If the Blink repository is a true fork, i.e., branch at a certain
time/commit id, from the Flink repository, then there is no problem. The
entire Blink repositor
Thanks Stephan,
The entire plan makes sense to me.
Regarding the branch name, how about using "blink-flink-1.5" wich meant
that the branche is based on flink-1.5. If the name is "blink-1.5", some
users will think that this is the version number of the internal Blink of
alibaba, and will not asso
Exciting to see this happening!
Wrt doc, have we done a diff which can show us how much differences are
between Flink's and Blink's documentation (flink/docs)? For example, how
many pages and how much percentage of each page is different? How many new
pages (for new features) does Blink have?If we
Sure, i will do the rebase before pushing the branch.
Timo Walther 于2019年1月24日 周四18:20写道：
> Regarding the content of a `blink-1.5` branch, is it possible to rebase
> the big Blink commit on top of the current master or the last Flink
> release?
>
> I don't mean a full rebase here, but just forkin
Regarding the content of a `blink-1.5` branch, is it possible to rebase
the big Blink commit on top of the current master or the last Flink release?
I don't mean a full rebase here, but just forking the branch from
current Flink, and putting the Blink content into the repository, and
commit it
Thanks Stephan,
The plan makes sense to me.
Regarding the docs, it seems better to have a separate versioned website
because there are a lot of changes spread over the places. We can add the
banner to remind users that they are looking at the blink docs, which is
temporary and will eventually be
Thanks Stephan,
The entire plan looks good to me. WRT the "Docs for Flink", a subsection
should be good enough if we just introduce the outlines of what blink has
changed. However, we have made detailed introductions to blink based on the
framework of current release document of Flink (those introd
Nice to see this lively discussion.
*--- Branch Versus Repository ---*
Looks like this is converging towards pushing a branch.
How about naming the branch simply "blink-1.5" ? That would be in line with
the 1.5 version branch of Flink, which is simply called "release-1.5" ?
*--- SGA --- *
The S
Really excited to see Blink joining the Flink community!
My two cents regarding repo v.s. branch, I am +1 for a branch in Flink.
Among many things, what's most important at this point is probably to make
Blink code available to the developers so people can discuss the merge
strategy. Creating a br
From the ASF side Jar files do notrequire a vote/release process, this
is at the discretion of the PMC.
However, I have my doubts whether at this time we could even create a
source release of Blink given that we'd have to vet the code-base first.
Even without source release we could still dis
As far as I know it, we will not provide any binaries but only the
source code. JAR files on Apache servers would need an official
voting/release process. Interested users can build Blink themselves
using `mvn clean package`.
@Stephan: Please correct me if I'm wrong.
Regards,
Timo
Am 23.01.1
Hi Timo,
What about the jar files, will blink's jar be uploaded to apache
repository? If not, i think it will be very inconvenient for users who
wants to try blink and view the documents if they need some help from doc.
Best,
Kurt
On Wed, Jan 23, 2019 at 6:09 PM Timo Walther wrote:
> Hi Kurt,
Hi Kurt,
I would not make the Blink's documentation visible to users or search
engines via a website. Otherwise this would communicate that Blink is an
official release. I would suggest to put the Blink docs into `/docs` and
people can build it with `./docs/build.sh -pi` if there are intereste
Thanks @Stephan for this exciting announcement!
>From my point of view, i would prefer to use branch. It makes the message
"Blink is pat of Flink" more straightforward and clear.
Except for the location of blink codes, there are some other questions like
what version should should use, and where
--
From:Hequn Cheng
Send Time:2019年1月23日(星期三) 10:55
To:dev
Subject:Re: [ANNOUNCE] Contributing Alibaba's Blink
Hi all,
@Stephan Thanks a lot for driving these efforts. I think a lot of people
is already waiting for this.
+
Hi all,
@Stephan Thanks a lot for driving these efforts. I think a lot of people
is already waiting for this.
+1 for opening the blink source code.
Both a separate repository or a special branch is ok for me. Hopefully,
this will not last too long.
Best, Hequn
On Tue, Jan 22, 2019 at 11:35 PM
Great news! Looking forward to the new wave of developments.
If Blink needs to be continuously updated, fix bugs, release versions,
maybe a separate repository is a better idea.
Best,
Jark
On Tue, 22 Jan 2019 at 18:29, Dominik Wosiński wrote:
> Hey!
> I also think that creating the separate br
Hey!
I also think that creating the separate branch for Blink in Flink repo is a
better idea than creating the fork as IMHO it will allow merging changes
more easily.
Best Regards,
Dom.
wt., 22 sty 2019 o 10:09 Ufuk Celebi napisał(a):
> Hey Stephan and others,
>
> thanks for the summary. I'm ve
1 - 100 of 168 matches
Mail list logo
