jorisvandenbossche commented on a change in pull request #11677: URL: https://github.com/apache/arrow/pull/11677#discussion_r754331616
########## File path: docs/source/developers/guide/introduction.rst ########## @@ -0,0 +1,135 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +.. or more contributor license agreements. See the NOTICE file +.. distributed with this work for additional information +.. regarding copyright ownership. The ASF licenses this file +.. to you under the Apache License, Version 2.0 (the +.. "License"); you may not use this file except in compliance +.. with the License. You may obtain a copy of the License at + +.. http://www.apache.org/licenses/LICENSE-2.0 + +.. Unless required by applicable law or agreed to in writing, +.. software distributed under the License is distributed on an +.. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +.. KIND, either express or implied. See the License for the +.. specific language governing permissions and limitations +.. under the License. + +.. _introduction: + +********************** +New Contributor's Guide Review comment: I personally agree with @thisisnic and @AlenkaF as well. I think the points in @AlenkaF's comment just above is a nice summary of the goals and scope of the this new contributors guide. (and I also agree we should further improve and restructure the general contributors docs that we will be linking to from here) We should pay attention to not create too much duplication, but having a page that explains a bit more the "why" (the broader context) and not just the mechanical "how" (the steps to build pyarrow) is useful I think. @AlenkaF it might be useful to document the goals / scope of the new subsection you are adding somewhere (eg in a comment in the file, restructuredtext has syntax to add a comment which is then not rendered in the online version) -- 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]
