[ANNOUNCE] JIRA permissions changed: Only committers can assign somebody to a ticket

Hi all, The permissions for the FLINK Jira project have been changed [1], to *only allow committers and PMC members to assign somebody to a Jira ticket.* Anybody with a Jira account can be assigned to a ticket. There is no need for "Contributor" permissions. This has been discussed in this

[ANNOUNCE] Jiangjie (Becket) Qin has been added as a committer to the Flink project

Hi all, I'm excited to announce that Jiangjie (Becket) Qin just became a Flink committer! Congratulations Becket! Best, Robert (on behalf of the Flink PMC)

Re: [DISCUSS] Create a Flink ecosystem website

ebsite, we can ask Apache > infra team to prepare the VM for us, as that may also take some time. > > On Wed, Apr 24, 2019 at 11:57 PM Robert Metzger > wrote: > >> Hey all, >> >> quick update on this project: The frontend and backend code have been put >> toge

Re: [ANNOUNCE] Weekly Community Update 2019/28

As always, thank you for putting these nice summaries together! On Sun, Jul 14, 2019 at 7:34 PM Konstantin Knauf wrote: > Dear community, > > happy to share this weeks community update with Apache Flink 1.9, bylaws > for Apache Flink, Savepoints vs Checkpoints, Flink on ARM, and more. > > As

Re: [DISCUSS] Adopting a Code Style and Quality Guide

I have received one review for the PR so far. I'll merge it in the next 24 hours unless there's further feedback. On Mon, Jul 8, 2019 at 6:04 PM Robert Metzger wrote: > I've converted the google document into a markdown-based pull request > here: https://github.com/apache/flink-web/pu

Re: [DISCUSS] Create "flink-playgrounds" repository

y Schepler wrote: > Wouldn't this qualify for releasing snapshot artifacts to users? (Which, > you know, shouldn't be done?) > > On 12/07/2019 11:55, Robert Metzger wrote: > > I will request the repo now, so that you can continue working on the > > documentation (thanks f

Re: [DISCUSS] Create "flink-playgrounds" repository

The repo creation was faster than expected: https://github.com/apache/flink-playgrounds (it's not even listed here yet: https://gitbox.apache.org/repos/asf) On Fri, Jul 12, 2019 at 11:55 AM Robert Metzger wrote: > I will request the repo now, so that you can continue work

Re: [DISCUSS] Create "flink-playgrounds" repository

"docs" but under "flink-quickstart" or so? > > > > > > Would that be equally cumbersome for users? > > > > > > > > > > > > Best, > > > > > > Stephan > > > > > > > > > > > >

Re: [DISCUSS] Flink project bylaws

Thank you Becket for kicking off this discussion and creating a draft in the Wiki. I left some comments in the wiki. In my understanding this means, that a committer always needs a review and > +1 from another committer. As far as I know this is currently not always > the case (often committer

Re: [DISCUSS] Create "flink-playgrounds" repository

+1 to create a repo. On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf wrote: > Hi everyone, > > in the course of implementing FLIP-42 we are currently reworking the > Getting Started section of our documentation. As part of this, we are > adding docker-compose-based playgrounds to get started

Re: [DISCUSS] META-FLIP: Sticking (or not) to a strict FLIP voting process

Thanks for your summary Becket. Your list of items makes sense to me. I wonder if we should start working on some project Bylaws to write down how we want to work together. I really like your thoughts around "sticking to the process" to make us more efficient and approachable for new

Re: [DISCUSS] Adopting a Code Style and Quality Guide

y special > editor > > / > > >> checkstyle configs as the code formatting is part of the build itself. > > >> > > >> The one Beam uses is https://github.com/diffplug/spotless with > > >> GoogleJavaFormat, it may be worth to look into. > >

[jira] [Created] (FLINK-13125) Add note to PubSub connector documentation about beta status

Robert Metzger created FLINK-13125: -- Summary: Add note to PubSub connector documentation about beta status Key: FLINK-13125 URL: https://issues.apache.org/jira/browse/FLINK-13125 Project: Flink

Re: [DISCUSS] A more restrictive JIRA workflow

This is the Jira ticket I opened https://issues.apache.org/jira/browse/INFRA-18644 a long time ago :) On Thu, Jul 4, 2019 at 10:47 AM Chesnay Schepler wrote: > @Robert what's the state here? > > On 24/06/2019 16:16, Robert Metzger wrote: > > Hey all, > > >

Re: [ANNOUNCE] Weekly Community Update 2019/25

ks! > > On Fri, Jun 28, 2019 at 9:51 AM Robert Metzger > wrote: > > > Thank you for the update! I always enjoy reading them. > > > > Maybe we could use these threads as an input for a monthly "Community > > Update" blog post series? > > I've d

Re: [ANNOUNCE] Weekly Community Update 2019/25

Thank you for the update! I always enjoy reading them. Maybe we could use these threads as an input for a monthly "Community Update" blog post series? I've discussed this idea offline already my colleague Marta. Are you still interested? On Sun, Jun 23, 2019 at 10:18 PM Konstantin Knauf

Re: [DISCUSS] solve unstable build capacity problem on TravisCI

Do we know if using "the best" available hardware would improve the build times? Imagine we would run the build on machines with plenty of main memory to mount everything to ramdisk + the latest CPU architecture? Throwing hardware at the problem could help reduce the time of an individual build,

[ANNOUNCE] Jincheng Sun is now part of the Flink PMC

Hi all, On behalf of the Flink PMC, I'm happy to announce that Jincheng Sun is now part of the Apache Flink Project Management Committee (PMC). Jincheng has been a committer since July 2017. He has been very active on Flink's Table API / SQL component, as well as helping with releases.

Re: [DISCUSS] A more restrictive JIRA workflow

to tickets c) Every registered JIRA user is an assignable user in FLINK On Fri, May 24, 2019 at 9:18 AM Robert Metzger wrote: > Hey, > > I started working on step 1 and proposed some changes to the Flink > website: https://github.com/apache/flink-web/pull/217 > > > > O

[jira] [Created] (FLINK-12930) Update Chinese "how to contribute" pages

Robert Metzger created FLINK-12930: -- Summary: Update Chinese "how to contribute" pages Key: FLINK-12930 URL: https://issues.apache.org/jira/browse/FLINK-12930 Project: Flink

Re: [DISCUSS] Adopting a Code Style and Quality Guide

It seems that the discussion around this topic has settled. I'm going to turn the Google Doc into a markdown file (maybe also multiple, I'll try out different things) and then open a pull request for the Flink website. I'll post a link to the PR here once I'm done. On Fri, Jun 14, 2019 at 9:36

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

g > apache > mailing list. > > Best, > Kurt > > > On Thu, Jun 20, 2019 at 10:23 PM Kurt Young wrote: > > > Thanks Robert, I left a comment in the JIRA you gave and see what will > > happen. > > > > Best, > > Kurt > > > > >

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

; > > Do we know why that's the case? Do we need to educate people > more > > > on > > > > > > mailing lists? > > > > > > - They "prefer" it possibly because it's easy and fast with lower > > > cost > > > > > th

Re: [ANNOUNCEMENT] March 2019 Bay Area Apache Flink Meetup

Hey Xuefu, thanks a lot for organizing the Bay Area Flink Meetup. For others following this email thread, here is the (deep) link to the event: https://www.meetup.com/Bay-Area-Apache-Flink-Meetup/events/262216929/ I see that only 19 people have RSVPed so far. In my experience, it's possible to

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

g, announcing news and updates, broadcasting live > > streams/events, etc, and all technical discussions should be diverted to > > user-zh mailing list. > > > > I cc-ed a few organizers and drivers of the DingTalk group so that they > > can share their thoughts. >

Re: [DISCUSS] Adopting a Code Style and Quality Guide

Thanks a lot for putting this together! I'm in the process of reworking the "How to contribute" pages [1] and I'm happy to add the guide to the Flink website, once the discussion here is over. [1] https://github.com/apache/flink-web/pull/217 On Fri, Jun 14, 2019 at 3:21 AM Kurt Young wrote: >

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

Hey all, the user...@flink.apache.org is now a few months old and I wanted to hear how things are going. >From the number of people in the DingTalk group (5000 ?), I would have expected more people to use the mailing list. But I also understand that mailing lists are an outdated technology from

Re: [DISCUSS] Clean up and reorganize the JIRA components

esting anything (from time to time we have to fix something in the > benchmarking setup and also it happened couple of times, that benchmarks > have discovered some release blocker regressions in the Flink) > - Jira issue to fix some benchmark > - Jira issue to implement a missing benchmark

Re: [DISCUSS] A more restrictive JIRA workflow

Hey, I started working on step 1 and proposed some changes to the Flink website: https://github.com/apache/flink-web/pull/217 On Tue, Apr 30, 2019 at 4:08 PM Robert Metzger wrote: > Hi Fabian, > You are right, I made a mistake. I don't think it makes sense to introduce > a new p

[jira] [Created] (FLINK-12605) Describe new contribution process

Robert Metzger created FLINK-12605: -- Summary: Describe new contribution process Key: FLINK-12605 URL: https://issues.apache.org/jira/browse/FLINK-12605 Project: Flink Issue Type: Task

Re: contribute to Apache Flink

Hey guys, I'm very happy to hear that you are interested in contributing to Flink. I have checked your past activity on Jira, and I didn't see any interaction with a Flink ticket yet. The Flink community has recently discussed that we intend to change the process of giving people contributor

Re: [DISCUSS] FLIP to Restructure, Update & Rework Apache Flink's Documentation

Thanks a lot for working on this FLIP! I just read it, and it seems well written and well thought out. +1 from my side to put it into Confluence and start working on the docs :) On Mon, May 20, 2019 at 7:23 PM Konstantin Knauf wrote: > Hi all, > > following our unsuccessful application to

Re: Flink Forward Europe 2019 - Call for Presentations open until 17th May

gt; data > > from Twitter. > > I would talk about our experiences and describe how we leveraged online > > learning in conjunction with social data to determine if we are able to > > predict future currency exchange rates. I’ll point out the general > > architectur

Re: [DISCUSS] Clean up and reorganize the JIRA components

ou see in that component? > > Piotrek > > > On 20 Feb 2019, at 10:53, Robert Metzger wrote: > > > > Thanks a lot Timo! > > > > I will start a vote Chesnay! > > > > On Wed, Feb 20, 2019 at 10:11 AM Timo Walther > wrote: > > > >&

Re: [DISCUSS] Bump required Maven version to 3.1.1 (from 3.0.3)

appears that this plugin doesn't use the > > repositories as are defined in a settings.xml, but tries to setup an > > external connection (which fails, because we're behind a proxy). > > > > > > Best regards, > > > > > > Martijn > > > > >

[jira] [Created] (FLINK-12447) Bump required Maven version to 3.1.1 (from 3.0.3)

Robert Metzger created FLINK-12447: -- Summary: Bump required Maven version to 3.1.1 (from 3.0.3) Key: FLINK-12447 URL: https://issues.apache.org/jira/browse/FLINK-12447 Project: Flink Issue

Re: Flink Forward Europe 2019 - Call for Presentations open until 17th May

Thanks for announcing the Call for Presentations here! Since the deadline is approaching, I wanted to bump up this thread to remind everybody to submit talks! Please reach out to me or Fabian directly if you have any questions or if you need any support! On Thu, Apr 11, 2019 at 3:47 PM Fabian

Re: [DISCUSS] A more restrictive JIRA workflow

ds to ask for the right Jira permissions? > > Fabian > > > Am Di., 30. Apr. 2019 um 10:46 Uhr schrieb Timo Walther < > twal...@apache.org > >: > > > Hi Robert, > > > > thanks for taking care of this. +1 to your suggested steps. > > > > Rega

Re: [DISCUSS] FLIP-23 Model Serving

Hey all, I'm wondering if somebody on the list can take a look at the PR from FLIP-23: https://github.com/apache/flink/pull/7446 On Mon, Oct 1, 2018 at 6:13 PM Rong Rong wrote: > Thanks for the contribution Boris!! I've been playing around with the basic > model for a while back and loved it.

Re: [DISCUSS] A more restrictive JIRA workflow

...@ververica.com > > > > > >> > wrote: > > >> > > > >> >> @Robert thanks for pointing out and sorry for confusion. The > correct > > >> text: > > >> >> > > >> >> +1 for option 1. > > >> >> >

Re: Apply for confluence Wiki edit permission

Hey Shuiqiang, I gave you access to the Wiki. On Tue, Apr 30, 2019 at 4:29 AM Shuiqiang Chen wrote: > Hi, > > I am going to create a new FLIP for Proposal of Flink Driver. > < >

Re: 申请 JIRA Contributor 权限

Hi, I was not able to reliably identify you. The Jira Id "yd" does not exist: https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dy Is that you? https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dey (the JIRA Id is "dey" then) On Sat, Apr 27, 2019 at 3:10 AM 叶问 wrote: > Hi, >

Re: Contribute to flink

Hi, I gave you permissions. On Mon, Apr 29, 2019 at 12:22 PM jake wrote: > Hi, > > I want to contribute to Flink, Would you please give me the contributor > permission? > And my JIRA ID is ft20...@qq.com . > > thanks.

Re: Contributor Permission Request

Hi, I gave you permissions. On Mon, Apr 29, 2019 at 12:29 PM 张晨 wrote: > Hi, > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is pekingzcc >

Re: [DISCUSS] Bump required Maven version to 3.1.1 (from 3.0.3)

se the repositories as > are defined in a settings.xml, but tries to setup an external connection > (which fails, because we're behind a proxy). > > > > Best regards, > > > > Martijn > > > > -Original Message- > > From: Robert Metzger [mailto:rmetz...@apache

Re: Flink Filesystems [FLINK-12115] - Review adding Azure FS support

Hey Piyush, sorry for the delay. Some folks have started reviewing your change now. Best, Robert On Mon, Apr 22, 2019 at 5:10 PM Piyush Narang wrote: > Hi folks, > > I put up this review a couple of weeks back and after an initial set of > comments, I haven’t heard back from anyone ( >

[jira] [Created] (FLINK-12340) Cache frontend-maven-plugin npm artifacts

Robert Metzger created FLINK-12340: -- Summary: Cache frontend-maven-plugin npm artifacts Key: FLINK-12340 URL: https://issues.apache.org/jira/browse/FLINK-12340 Project: Flink Issue Type

[DISCUSS] Bump required Maven version to 3.1.1 (from 3.0.3)

Hey, I recently merged the new Flink UI [1]. After merging it, I was made aware that the frontend-maven-plugin requires at least Maven 3.1.0. There was a discussion about bumping the maven version already last year [2]. In that thread, Stephan mentions that some Linux distributions still have

Re: [DISCUSS] Create a Flink ecosystem website

for this to finish, but we are making progress :) Best, Robert On Mon, Apr 15, 2019 at 11:18 AM Robert Metzger wrote: > Hey Daryl, > > thanks a lot for posting a link to this first prototype on the mailing > list! I really like it! > > Becket: Our plan forward is that Congxian is implem

Re: Contribute to Flink

Hi, I gave you the permission. On Wed, Apr 17, 2019 at 2:58 PM QingA Li wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is moqi. >

Re: Request for JIRA Contributor Permission

Hi, I gave you the permissions. On Wed, Apr 17, 2019 at 3:18 PM DONG, Weike wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > > My JIRA ID is kyledong > > Thanks : ) >

Re: Apply for contributor permission

Hi, I gave you the permissions. On Thu, Apr 18, 2019 at 5:05 PM peng2251 wrote: > Hi, > > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is TonySu. > Thanks.

Re: Apply for contributor permission

Hi, I gave you the permission. On Sat, Apr 20, 2019 at 12:24 PM Dillon Zhang wrote: > Hi, > > I've been interested in flink for a long time and have worked on a few > internal features mainly in flink-runtime. > > I'd like to apply for contributor permission so that I could join feature >

Re: Apply for contributor permission

Hi, I gave you the permission. On Mon, Apr 22, 2019 at 12:45 PM 张军 wrote: > Hi, > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is zhangjun > Thanks.

Re: I want to apply Flink JIRA contributor

Hi, I gave you the permission. On Mon, Apr 22, 2019 at 12:57 PM Armstrong wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is Armstrongya. >

Re: contributor

Hi, I gave you the permission. On Wed, Apr 24, 2019 at 12:42 PM cc c wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is chauncy >

Re: Contributor permission Request

Hi, Welcome to the Flink community. I gave you the permissions. On Wed, Apr 24, 2019 at 2:28 PM Sean Mao wrote: > Hi, > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is seancxmao ( >

Apache Flink survey by Ververica

Hi everyone! Ververica is running a brief survey to understand Apache Flink usage and the needs of the community. We are hoping that this survey will help identify common usage patterns, as well as pinpoint what are the most needed features for Flink. We'll share a report with a summary of

Re: [REMINDER] Please add entries for newly added dependencies to NOTICE file

I will add such a feature to the bot! On Mon, Mar 25, 2019 at 7:41 PM Stephan Ewen wrote: > +1 to an enhancement to the Flink bot as a simple first step. > > The first step could be as simple as adding a red warning message as a > comment to the PR whenever a PR touches a POM file. > That needs

Re: [DISCUSS] Create a Flink ecosystem website

Hey Daryl, thanks a lot for posting a link to this first prototype on the mailing list! I really like it! Becket: Our plan forward is that Congxian is implementing the backend for the website. He has already started with the work, but needs at least one more week. [Re-sending this email

Re: [DISCUSS] Apache Flink at Season of Docs

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

Re: [DISCUSS] A more restrictive JIRA workflow

utor could > just ask the committer (who merged those contributions) about contributor > permissions. > > Best, > Andrey > > On Wed, Apr 10, 2019 at 3:58 AM Robert Metzger > wrote: > > > I'm +1 on option 1. > > > > On Tue, Apr 9, 2019 at 1:58

Re: [DISCUSS] A more restrictive JIRA workflow

uld prefer option 1 as some people also mentioned that option 2 > requires some standadized processes otherwise it would be difficult to > communicate why somebody is a contributor and some somebody is not. > > What do you think? > > Regards, > Timo > > > Am

Re: Contributor permission apply

Hey, I gave you contributor permissions. On Mon, Mar 25, 2019 at 10:36 AM huang <2440239...@qq.com> wrote: > Hi Guys, > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA ID is hyl > > > thanks

Re: [DISCUSS] Reorganizing Table-related Jira components some more

Nice! I'm happy to see that the components are evolving (this means they are used :) ) This is also a good test for my latest changes to the GitHub labeling tools. They should support label changes. On Fri, Mar 22, 2019 at 10:18 AM Aljoscha Krettek wrote: > Perfect! I re-arranged the components

Re: [REMINDER] Flink Forward San Francisco in a few days

I would like to add that the organizers of the conference have agreed to offer all Apache committers (of any Apache project) a free ticket. *To get your free ticket, use the "ASFCommitters19” promo code AND use your @apache.org email when registering.* Feel free to reach out

Re: [DISCUSS] Create a Flink ecosystem website

AM Robert Metzger wrote: > Okay, great. > > Congxian Qiu, Daryl and I have a kick-off call later today at 2pm CET, 9pm > China time about the design of the ecosystem page (see: > https://github.com/rmetzger/flink-community-tools/issues/4) > Please let me know if others want to j

Re: [DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

Hey all, Yadong has now opened a pull request with the Angular 7-based web frontend: https://github.com/apache/flink/pull/8016 The PR contains the complete dashboard, and is ready to check out, build and run locally. I believe it would be good to get some more feedback on the PR, from people

Re: [DISCUSS] Create a Flink ecosystem website

20, 2019 at 4:10 AM Becket Qin wrote: > I agree. We can start with english-only and see how it goes. The comments > and descriptions can always be multi-lingual but that is up to the package > owners. > > On Tue, Mar 19, 2019 at 6:07 PM Robert Metzger > wrote: > >> T

Re: [DISCUSS] Create a Flink ecosystem website

, Mar 19, 2019 at 2:42 AM Becket Qin wrote: > Done. The writeup looks great! > > On Mon, Mar 18, 2019 at 9:09 PM Robert Metzger > wrote: > >> Nice, really good news on the INFRA front! >> I think the hardware specs sound reasonable. And a periodic backup of the >&

Re: [DISCUSS] A more restrictive JIRA workflow

IRA issues, we can make them > > contributors. > > > > What do you think? > > > > Regards, > > Timo > > > > Am 06.03.19 um 12:33 schrieb Robert Metzger: > > > Hi Tison, > > > I also thought about this. > > > Making a person a &q

Re: [DISCUSS] Create a Flink ecosystem website

rselves. It seems we can almost say the hardware > side is also ready. > > Thanks, > > Jiangjie (Becket) Qin > > [1] https://issues.apache.org/jira/browse/INFRA-18010 > > On Fri, Mar 15, 2019 at 5:39 PM Robert Metzger > wrote: > > > Thank you for reaching

Re: [DISCUSS] Create a Flink ecosystem website

er.com/ > [2] https://github.com/emberobserver/client > > > > On Thu, Mar 14, 2019 at 1:35 AM Robert Metzger > wrote: > >> @Bowen: I agree. Confluent Hub looks nicer, but it is on their company >> website. I guess the likelihood that they give out code from their

Re: [DISCUSS] Create a Flink ecosystem website

y worth checking it out with > Kafka folks > > > > On Thu, Mar 7, 2019 at 6:06 AM Becket Qin wrote: > >> > >> Absolutely! Thanks for the pointer. I'll submit a PR to update the > >> ecosystem page and the navigation. > >> > >> Thanks, > >>

Re: [CANCEL][VOTE] Release 1.8.0, release candidate #1

t; > >> > > >> I just found https://issues.apache.org/jira/browse/FLINK-11901 > > >> > > >> According to Chesnay, this is a release blocker. > > >> > > >> Regards, > > >> Timo > > >> > > >> Am 1

Re: [VOTE] Release 1.8.0, release candidate #1

I'm wondering whether we should tweet about this release candidate, and also post on the user@ mailing list to ask for some help with testing the RC in production environments? On Tue, Mar 12, 2019 at 11:23 AM Kurt Young wrote: > +1 (non-binding) > > Checked items: > - checked checksums and

Re: [DISCUSS] Improve the flinkbot

as changed. The implementation will be a bit differently, to not run into rate limits with the JIRA or GitHub API. On Thu, Mar 7, 2019 at 2:40 PM Chesnay Schepler wrote: > How do you intend to keep the label up-to-date with whatever > modifications are made in JIRA? > > On 07.03.2019 13:40, Rober

Re: [DISCUSS] Create a Flink ecosystem website

>> I like Shaoxuan's idea to keep this a static site first. We could then >> iterate on this and make it a dynamic thing. Of course, if we have the >> resources in the community to quickly start with a dynamic site, I'm >> not apposed. >> >> – Ufuk >> >

Re: [DISCUSS] Improve the flinkbot

they may be set incorrectly (or > not at all) by the contributor. In this case we now have to update the > component both in JIRA and on GitHub, and I'm most certainly not looking > forward to that. > > On 06.03.2019 13:51, Robert Metzger wrote: > > This is the picture: > > >

Re: [DISCUSS] Create a Flink ecosystem website

;> >>> I like this idea! Let us roll this out with Flink connectors at the >>> first beginning. We can start with a static page, and upgrade it when we >>> find a better solution for dynamic one with rich functions. >>> >>> Regards, >>> Shaoxua

Re: [DISCUSS] Improve the flinkbot

y everything in the > Feature requests section) > > If we want to better distinguish new PRs I would suggest to either a) > introduce a dedicated "New" label or b) not attach any label by default, > and only attach the description label if someone has > approved/disapproved it. >

Re: [DISCUSS] Improve the flinkbot

ds like the review is in progress. > > For "review=approved ✅", it indicates the review is finished. > > So i think 3 colors is enough, it tell committers whether the review has > not started yes, or in progress, or is finished. > > What do you think? > >

Re: [DISCUSS] A more restrictive JIRA workflow

ussion. > One becomes contributor can additionally assign an issue to a person and > modify fields of any issues. > > For a more restrictive JIRA workflow, maybe we achieve it by making it a > bit more > restrictive granting contributor permission? > > Best, > tison. > > &g

Re: [DISCUSS] Create a Flink ecosystem website

Hey Becket, This is a great idea! For this to be successful, we need to make sure the page is placed prominently so that the people submitting something will get attention for their contributions. I think a dynamic site would probably be better, if we want features such as up and downvoting or

Re: [DISCUSS] Improve the flinkbot

positive feedback from other contributors, I think they see their > contributions are better received now. > > Thomas > > > > On Fri, Mar 1, 2019 at 8:38 AM Robert Metzger wrote: > > > I will update labels only based on committer's approvals (for > everything), >

Re: [DISCUSS] Improve the flinkbot

er IMO. > > On 27.02.2019 15:08, Robert Metzger wrote: > > I did not put any restrictions on who can communicate with the bot! > But since there is currently no way of overriding somebody's approval for > something, this can easily lead to such a situation. > > My thinking wa

Re: [RESULT][VOTE] Clean up and reorganize the JIRA components

@Kurt: Okay. @all: I've now creating the new components, and I've migrated almost all of the old components. We also had 200 tickets which were not assigned to any component. I've assigned them all, and I'll keep an eye on those tickets w/o a component. There's a "*chinese-translation*"

Re: [RESULT][VOTE] Clean up and reorganize the JIRA components

Best, > Kurt > > > On Thu, Feb 28, 2019 at 5:59 PM Robert Metzger > wrote: > > > Okay, I will go with "Connectors / Misc" if nobody objects. > > > > > > On Wed, Feb 27, 2019 at 4:33 PM Chesnay Schepler > > wrote: > > > > > &

Re: [RESULT][VOTE] Clean up and reorganize the JIRA components

Okay, I will go with "Connectors / Misc" if nobody objects. On Wed, Feb 27, 2019 at 4:33 PM Chesnay Schepler wrote: > "Connectors / Misc" > > On 27.02.2019 15:20, Robert Metzger wrote: > > I have now started renaming the components. > > You can track

Re: [RESULT][VOTE] Clean up and reorganize the JIRA components

FLINK-8486. On Tue, Feb 26, 2019 at 3:59 PM jincheng sun wrote: > I agree with Robert from now. > > Best, > Jincheng > > Robert Metzger 于2019年2月26日周二 下午7:03写道： > > > Thank you for the suggestion. > > > > Would this be "Runtime / State TTL" ? > &g

Re: [DISCUSS] Improve the flinkbot

the solution, but as it stands it is rather trivial to > nuke the review process of the entire project. > > On 13.02.2019 10:29, Robert Metzger wrote: > > Hey all, > > > > the flinkbot has been active for a week now, and I hope the initial > hiccups > > have been resolved

Re: [DISCUSS] A more restrictive JIRA workflow

I like this idea and I would like to try it to see if it solves the problem. I can also offer to add a functionality to the Flinkbot to automatically close pull requests which have been opened against a unassigned JIRA ticket. Being rejected by an automated system, which just applies a rule is

Re: [ANNOUNCE] Apache Flink 1.6.4 released

ger. Great job! > >> > >> On Mon, Feb 25, 2019 at 10:48 AM Fabian Hueske > wrote: > >> > >>> Thanks Jincheng for being the release manager! > >>> > >>> Am Mo., 25. Feb. 2019 um 09:49 Uhr schrieb Robert Metzger < > >>&g

Re: [RESULT][VOTE] Clean up and reorganize the JIRA components

but it might help in future. > > Thanks, > Andrey > > On Mon, Feb 25, 2019 at 8:02 PM Robert Metzger > wrote: > > > The proposal has been approved with > > > > +1 votes: > > - Timo > > - Robert > > - Jincheng > > - Shengjk1 > > - Ches

Re: to be contributer

Hi, I've added you to our JIRA! On Mon, Feb 25, 2019 at 5:26 PM kai wang wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is frank wang >

[RESULT][VOTE] Clean up and reorganize the JIRA components

11:06 AM Chesnay Schepler > wrote: > >> +1 >> >> On 25.02.2019 09:51, Robert Metzger wrote: >> > You are right. I've fixed it: >> > >> https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=103089605=7=6 >> > >

Re: [VOTE] Clean up and reorganize the JIRA components

to them. > None of the 3 components you just listed have this. > > On 21.02.2019 16:10, Robert Metzger wrote: > > Thank you for the minor issues you've found. I addressed them: > > > https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=103089605=

Re: [ANNOUNCE] Apache Flink 1.6.4 released

Thank you Jincheng for running this release! I've also tweeted about it from @ApacheFlink: https://twitter.com/ApacheFlink/status/1099954183741022208 On Mon, Feb 25, 2019 at 4:04 AM Jark Wu wrote: > Thanks for being the release manager Jingcheng. > The 1.6.4 release contains a couple of

Re: [DISCUSS] Improve the flinkbot

gt; The bot could check the diff and tag pull requests that only touch the > docs as "Documentation". Many of these are easy to review and usually > don't require a deeper understanding of Flink. > > On 13.02.2019 10:29, Robert Metzger wrote: > > Hey all, > >

Re: [DISCUSS] Releasing Flink 1.8 / Feature Freeze

ng phase. > > Cheers, > Gordon > > On Mon, Feb 18, 2019 at 4:44 PM Robert Metzger > wrote: > > > I'm not involved enough with the development to say whether end of this > > week is a realistic deadline. > > But I see that it makes sense to release 1.8 soon,

<    3   4   5   6   7   8   9   10   11   12   >