[
https://issues.apache.org/jira/browse/FLINK-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6771:
----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Create committer guide
> ----------------------
>
> Key: FLINK-6771
> URL: https://issues.apache.org/jira/browse/FLINK-6771
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.4.0
> Reporter: Till Rohrmann
> Priority: Major
> Labels: stale-major
>
> The Flink project currently has no dedicated committer guide. I think it
> would be helpful for new committers to have such a document. The document
> should explain how the most important processes work within the Flink
> community (those not clearly stated in [1]). For example, we should outline
> how to close PRs and what information to add to a JIRA issue when closing it.
> We could use as a starting point [2].
> [1] https://www.apache.org/dev/new-committers-guide.html
> [2] http://flink.apache.org/contribute-code.html#how-to-use-git-as-a-committer
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
