emkornfield commented on code in PR #258:
URL: https://github.com/apache/parquet-format/pull/258#discussion_r1676184978


##########
CONTRIBUTING.md:
##########
@@ -29,3 +29,142 @@ Recommendations and requirements for how to best contribute 
to Parquet. We striv
 ### License
 By contributing your code, you agree to license your contribution under the 
terms of the APLv2:
 https://github.com/apache/parquet-format/blob/master/LICENSE
+
+### Additions/Changes to the Format
+
+Note: This section applies to actual functional changes to the specification.
+Fixing typos, grammar, and clarifying concepts that would not change the
+semantics of the specification can be done as long as a committer feels 
comfortable
+to merge them. When in doubt starting a discussion on the dev mailing list is
+encouraged.
+
+The general steps for adding features to the format are as follows:
+
+1. Discuss changes on the developer mailing list ([email protected]).
+   Often times it is helpful to link to a draft pull request to make the
+   discussion concrete. This step is complete when there is lazy consensus. 
Part
+   of the consensus is whether it is sufficient to provide two working
+   implementations as outlined in step 2, or if demonstration of the feature 
with
+   a downstream query engine is necessary to justify the feature (e.g.
+   demonstrate performance improvements in the Apache Arrow C++ Dataset 
library,
+   the Apache DataFusion query engine, or any other open source engine).

Review Comment:
   I tried to address this with additional language, please let me know if I 
covered your intent.



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to