jrgemignani commented on issue #369:
URL: https://github.com/apache/age/issues/369#issuecomment-1341511955
Please don't take offense to any bolding, I did it strictly for emphasis.
This is a compilation from many sources, not just from here.
**At the risk of repeating myself, and for future contributors and
contributions -**
Bounties have **NO** connection to Apache AGE. Meaning, we neither condone,
prohibit, support monetarily or otherwise, bounties, in any way. This **may**
change in the future. So, use/do them at your own risk.
If someone wants to set a bounty, Apache AGE has **zero** obligation to
support or approve any PR derived from it. If someone hopes that their PR will
get approved, they need to, at the very least, follow our standards. Remember,
Apache AGE did not ask for any bounties, nor put them up, nor fund them.
Here is a rough guide of minimum expectations for **any** PR -
1. All bug fixes must have explanations as to why/how they address the
problem. Meaning, what was the root cause of the bug and why (how) does this PR
correct it. As I have stated above, think of it like a proof. You need to prove
to Apache AGE PMC members and committers that your work resolves the issue, not
masks it, nor generates potentially hidden issues.
2. All contributions, without exception, must conform to our coding
standards.
3. Adequate commenting in the code.
4. Adequate documentation in the PR commit log entry.
Please understand, we will not always be prompt in responding to these
requests. Apache AGE PMC and committers have a lot of work to do. However, we
will try our best.
Hopefully, this will be helpful going forward.
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]
