jrgemignani commented on issue #343:
URL: https://github.com/apache/age/issues/343#issuecomment-1343272432
@TropicalPenguin IMHO, I think the issue here, for all parties, is that we
are all learning this - not so well defined (yet) process, and it is messy.
As an Apache AGE PMC, I'm trying to find a way to coordinate everyone's
efforts without stepping on anyone's toes nor causing a duplication of any work
nor giving preferential treatment to anyone. And, I fully realize that some is
inevitable, no matter how hard I may try. But, I still try.
As a user, you ideally need the feature/fix, right now, A.S.A.P. and there
is nothing wrong with that position either.
We also have different perspectives for that fix. I want it to be correct
and as complete as possible. You just want an adequate solution, sooner rather
than later. Both are valid within the proper context.
In walk bounties,... I like the idea of bounties, I really do. However, in a
development environment, I see them as causing problems due to their monetary
component.
- Do I approve a bounty over another submission, or not, provided they are
equivalent? And both are submitted reasonably close.
- What happens if the bounty submission isn't approved, but the fix was
valid?
- How much support do I give to someone working on a bounty?
- What if the feature/fix requires design and implementation decisions to be
made?
- What if one of the Apache AGE PMCs were to complete a bounty?
- Should that bounty be given to whomever fixes the issue the bounty is tied
too?
Those are just some concerns of mine. But, let's try to see if we can
coordinate the bounties and iron them out along the way.
> @jrgemignani Hmm, this becomes complicated. There's a much weaker
incentive for me to create a bounty in the first place if I know that a given
item is under active development.
If I were aware you might put a bounty on the item, I might have mentioned
that the issue was already under review. Although, technically, I **sort of**
did.
> I was not aware that the SET commands implementation of the Cypher
specification was incomplete. I will look into addressing this.
Let's try to improve our communication and see if we can make these work.
john
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
