You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2016/08/26 17:28:20 UTC

[jira] [Commented] (BEAM-566) Implement proposal process

    [ https://issues.apache.org/jira/browse/BEAM-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439431#comment-15439431 ] 

Kenneth Knowles commented on BEAM-566:
--------------------------------------

In the website redesign, we lost the link to misc technical document folder at https://goo.gl/ps8twC. A lot of them are proposals, so they'll be subsumed by this if/when.

> 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
>
> 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
(v6.3.4#6332)