[
https://issues.apache.org/jira/browse/BEAM-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132512#comment-17132512
]
Beam JIRA Bot commented on BEAM-566:
------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Implement proposal process
> --------------------------
>
> Key: BEAM-566
> URL: https://issues.apache.org/jira/browse/BEAM-566
> Project: Beam
> Issue Type: Bug
> Components: website
> Reporter: Frances Perry
> Assignee: Frances Perry
> Priority: P2
> Labels: stale-assigned
>
> As discussed on the dev list...
> - Update contribution guide to explain what the design doc / proposal should
> include (like is done in
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals)
> - Clearly track the open proposals (potentially in JIRA with a known label
> and incrementing proposal IDs).
> - Set expectations around the timelines for proposals -- both to ensure
> enough feedback is gathered and perhaps inactive proposals are archived.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
