avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-341) specify avro transport in spec
Date Fri, 14 May 2010 17:42:50 GMT

    [ https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867590#action_12867590

Doug Cutting commented on AVRO-341:

We don't have a Confluence wiki yet.  Someone needs to as infrastructure to create one and
then move all of our content to it.  Volunteers welcome.

To some degree it doesn't matter where it's hosted.  We just need a clearly defined process.
 The PEP process is version-control based, which more naturally keeps it from becoming a free-for-all.
 But a wiki-based process could be defined.  We don't want folks to just add features they'd
like to see to a spec without considering implementation costs.  A proposed enhancement should
have a clear owner, a clear process for integrating changes to the proposal and a clear process
for acceptance.

If maintaining the proposal in Jira proves awkward, then we can commit an early version of
it to subversion and then folks can submit patches to it.  Or someone can propose and instigate
an alternate process.

> specify avro transport in spec
> ------------------------------
>                 Key: AVRO-341
>                 URL: https://issues.apache.org/jira/browse/AVRO-341
>             Project: Avro
>          Issue Type: Improvement
>          Components: spec
>            Reporter: Doug Cutting
>         Attachments: aep-001.txt
> We should develop a high-performance, secure, transport for Avro.  This should be named
with avro: uris.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message