kou commented on code in PR #162: URL: https://github.com/apache/arrow-go/pull/162#discussion_r1805376670
########## CONTRIBUTING.md: ########## @@ -0,0 +1,69 @@ +<!--- + 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. +--> + +# How to contribute to Apache Arrow Go + +## Did you find a bug? + +The Arrow project uses GitHub as a bug tracker. To report a bug, sign in to +your GitHub account, navigate to [GitHub issues](https://github.com/apache/arrow-go/issues) +and click on **New issue** . + +To be assigned to an issue, add a comment "take" to that issue. Review Comment: We don't have this feature in apache/arrow-go. Do we need this? If we need this, we need to port https://github.com/apache/arrow/blob/0c3206772051c52fe2e648623daaca2c4e71cb72/.github/workflows/comment_bot.yml#L178-L194 to apache/arrow-go. ########## CONTRIBUTING.md: ########## @@ -0,0 +1,69 @@ +<!--- + 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. +--> + +# How to contribute to Apache Arrow Go + +## Did you find a bug? + +The Arrow project uses GitHub as a bug tracker. To report a bug, sign in to +your GitHub account, navigate to [GitHub issues](https://github.com/apache/arrow-go/issues) +and click on **New issue** . + +To be assigned to an issue, add a comment "take" to that issue. + +Before you create a new bug entry, we recommend you first search among existing +Arrow issues in [GitHub](https://github.com/apache/arrow-go/issues). + +We conventionally prefix the issue title with the component +name in brackets, such as "[Parquet] Fix panic in record read", +so as to make lists more easy to navigate, and +we'd be grateful if you did the same. + +## Did you write a patch that fixes a bug or brings an improvement? + +First create a GitHub issue as described above, selecting **Bug Report** or +**Enhancement Request**. Then, submit your changes as a GitHub Pull Request. +We'll ask you to prefix the pull request title with the GitHub issue number +and the component name in brackets. (for example: "GH-100: [Parquet] +fix panic in record read"). Respecting this convention +makes it easier for us to process the backlog of submitted Pull Requests. + +### Minor Fixes + +Any functionality change should have a GitHub issue opened. For minor changes that +affect documentation, you do not need to open up a GitHub issue. Instead you can +prefix the title of your PR with "MINOR: " if meets one of the following: + +* Grammar, usage and spelling fixes that affect no more than 2 files +* Documentation updates affecting no more than 2 files and not more + than 500 words. + +## Do you want to propose a significant new feature or an important refactoring? + +We ask that all discussions about major changes in the codebase happen +publicly on the [arrow-dev mailing-list](https://mail-archives.apache.org/mod_mbox/arrow-dev/). Review Comment: https://arrow.apache.org/community/#mailing-lists may be better because it has a bit more description. ########## CONTRIBUTING.md: ########## @@ -0,0 +1,69 @@ +<!--- + 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. +--> + +# How to contribute to Apache Arrow Go + +## Did you find a bug? + +The Arrow project uses GitHub as a bug tracker. To report a bug, sign in to +your GitHub account, navigate to [GitHub issues](https://github.com/apache/arrow-go/issues) +and click on **New issue** . + +To be assigned to an issue, add a comment "take" to that issue. + +Before you create a new bug entry, we recommend you first search among existing +Arrow issues in [GitHub](https://github.com/apache/arrow-go/issues). + +We conventionally prefix the issue title with the component +name in brackets, such as "[Parquet] Fix panic in record read", +so as to make lists more easy to navigate, and +we'd be grateful if you did the same. + +## Did you write a patch that fixes a bug or brings an improvement? + +First create a GitHub issue as described above, selecting **Bug Report** or +**Enhancement Request**. Then, submit your changes as a GitHub Pull Request. Review Comment: We don't have issue templates. If we need them, we need to port https://github.com/apache/arrow/tree/main/.github/ISSUE_TEMPLATE to apache/arrow-go. ########## CONTRIBUTING.md: ########## @@ -0,0 +1,69 @@ +<!--- + 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. +--> + +# How to contribute to Apache Arrow Go + +## Did you find a bug? + +The Arrow project uses GitHub as a bug tracker. To report a bug, sign in to +your GitHub account, navigate to [GitHub issues](https://github.com/apache/arrow-go/issues) +and click on **New issue** . + +To be assigned to an issue, add a comment "take" to that issue. + +Before you create a new bug entry, we recommend you first search among existing +Arrow issues in [GitHub](https://github.com/apache/arrow-go/issues). + +We conventionally prefix the issue title with the component +name in brackets, such as "[Parquet] Fix panic in record read", +so as to make lists more easy to navigate, and +we'd be grateful if you did the same. + +## Did you write a patch that fixes a bug or brings an improvement? + +First create a GitHub issue as described above, selecting **Bug Report** or +**Enhancement Request**. Then, submit your changes as a GitHub Pull Request. +We'll ask you to prefix the pull request title with the GitHub issue number +and the component name in brackets. (for example: "GH-100: [Parquet] +fix panic in record read"). Respecting this convention +makes it easier for us to process the backlog of submitted Pull Requests. Review Comment: We can stop this convention if we want. I think that this convention is to associate Jira issue easily. We can use `Fixes #XXX` PR description in GitHub instead. -- 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]
