couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick North <nort...@gmail.com>
Subject Re: Process for code submissions?
Date Tue, 07 Aug 2012 13:47:53 GMT
The fault was mainly mine, as I did drop the ball for several months. My
concern this time was that maybe there was some process I should now be
following and wasn't. But all is now sorted so thanks to both of you,

Nick

On 7 August 2012 01:33, Bob Dionne <dionne@dionne-associates.com> wrote:

> Nick,
>
> You can ignore this given Bob Newson picked it up. I guess the mailing
> list took some time off, I sent this out yesterday at 11:30 am.
>
> Cheers,
>
> Bob
>
> On Aug 5, 2012, at 11:22 AM, Bob Dionne <dionne@dionne-associates.com>
> wrote:
>
> > Hi Nick,
> >
> > Sorry this is my fault for dropping the ball on this. It looks like we
> batted this around a bit, you made good progress refactoring, enhancing,
> etc.. and then we all forgot about it. I'll review the patch again in the
> next couple of days with respect to the current code and either get this
> committed or get a decision as to why not.
> >
> > I'm not sure what the "formal" process for all this is, I imagine the
> Apache site has some docs on it, but I do know committers are obligated to
> help build community, shepherd contributions, etc.. so I definitely put
> this on my TODO list.
> >
> > Cheers,
> >
> > Bob
> > On Aug 5, 2012, at 11:05 AM, Nick North <north.n@gmail.com> wrote:
> >
> >> I'm wondering if there is any process for dealing with code submissions
> >> i.e. for getting a decision that they are accepted, rejected, or
> ignored. I
> >> hope the following doesn't come across as a complaint, because I think
> >> CouchDb and the community are great, but I feel in limbo on this
> particular
> >> topic.
> >>
> >> The reason for asking is that I submitted JIRA issue
> >> COUCHDB-1373<https://issues.apache.org/jira/browse/COUCHDB-1373>a
> >> while back, then let it drop for some while before submitting pull
> >> request 28 <https://github.com/apache/couchdb/pull/28> with proposed
> code
> >> for implementing the suggestion. After some initial discussion on the
> JIRA
> >> issue, there was no response to the pull request, and I don't know if
> that
> >> means I didn't follow the right process, it has been rejected, it's been
> >> decided to ignore it, or it's gone into a queue to be considered
> eventually.
> >>
> >> There are many good reasons for not accepting submitted code: the
> >> suggestion may be bad, the code may be bad, there may not be the
> resources
> >> to deal with it, it may be undesirable creeping featurism, it may come
> from
> >> someone who hasn't demonstrated good understanding of the project etc.
> Any
> >> of those verdicts might apply in this case but, whatever the reason is,
> it
> >> would be good to be told it so that I know whether it's worth expending
> >> more effort to improve my chances of acceptance, or whether to spend
> that
> >> time on finding ways to carry on without the proposed code.
> >>
> >> If someone can help or guide me, or give an outline of how things
> operate
> >> in this area, I'd be really grateful. Many thanks,
> >>
> >> Nick North
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message