TropicalPenguin commented on issue #343: URL: https://github.com/apache/age/issues/343#issuecomment-1343166431
@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. For what it's worth, now that one is already submitted in this case, I'm happy to still honor it, assuming that doing so doesn't contravene the [note you made](https://github.com/apache/age/issues/369#issuecomment-1341511955) about Apache AGE not officially "support[ing bounties] monetarily _or otherwise_" (emphasis mine). This wouldn't seem to require being privy to such private channels, if, for example, project views like https://github.com/orgs/apache/projects/96/views/1 were in sync with such ongoing work. Given that they're already partly filled in, I assume there's no particular confidentiality issue here, just a logistical one. > We don't want the bounties to start causing issues or too much noise so, let's try to find a happy medium. I certainly don't mean to stir up noise. What makes it tricky is those (seemingly rare, fortunately) cases where my own development goals & their desired time-frames have dependencies like this. In such a situation, often even an imperfect - and quite possibly expected to be temporary - solution is better than no solution. I would hope that if I do find a need to support such work independent of AGE (whether remaining in this project's issue tracker, or - if it would usefully avert such noise - through a currently-hypothetical fork for such likely-temporary feature development), that it can feed back positively in _some_ way into the (more general) community project. I hope there can be a happy medium. -- 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]
