kou commented on a change in pull request #278: URL: https://github.com/apache/arrow-julia/pull/278#discussion_r787170086
########## File path: CONTRIBUTING.md ########## @@ -0,0 +1,37 @@ +# How to contribute Apache Arrow Julia + +## Did you find a bug or have an improvement? + +We recommend you first search among existing [Github issues](https://github.com/apache/arrow-julia/issues). The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue. + + +## How do you write a patch that fixes a bug or brings an improvement? +If you cannot find the same idea in the issues, you first need to write a GitHub issue (e.g. [issues in Arrow-julia](https://github.com/apache/arrow-julia/issues)) for a bug fix or planned features for the improvement. To write an issue would help the community have visibility and opportunities for collaborations before a pull request (PR) shows up. This is for the [Apache way](http://theapacheway.com/). We can use GitHub labels to identify bugs. +It should not be necessary to file an issue for some non-code changes, such as CI changes or minor documentation updates such as fixing typos. + +After writing the issue, you may want to write a code by creating [a PR](https://github.com/apache/arrow-julia/pulls). In the PR, it is preferable to refer to the issue number (e.g. `#1`) that you already created. + + +## 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://lists.apache.org/[email protected]). Review comment: I think that we can GitHub issues and/or arrow-dev mailing list. We can keep ["Open" in Apache way](http://theapacheway.com/open/) on GitHub issues like other bug reports and feature requests. @quinnj What do you think about this? ########## File path: CONTRIBUTING.md ########## @@ -0,0 +1,37 @@ +# How to contribute Apache Arrow Julia + +## Did you find a bug or have an improvement? + +We recommend you first search among existing [Github issues](https://github.com/apache/arrow-julia/issues). The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue. Review comment: ```suggestion We recommend you first search among existing [GitHub issues](https://github.com/apache/arrow-julia/issues). The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue. ``` ########## File path: CONTRIBUTING.md ########## @@ -0,0 +1,37 @@ +# How to contribute Apache Arrow Julia + +## Did you find a bug or have an improvement? + +We recommend you first search among existing [Github issues](https://github.com/apache/arrow-julia/issues). The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue. + + +## How do you write a patch that fixes a bug or brings an improvement? +If you cannot find the same idea in the issues, you first need to write a GitHub issue (e.g. [issues in Arrow-julia](https://github.com/apache/arrow-julia/issues)) for a bug fix or planned features for the improvement. To write an issue would help the community have visibility and opportunities for collaborations before a pull request (PR) shows up. This is for the [Apache way](http://theapacheway.com/). We can use GitHub labels to identify bugs. Review comment: ```suggestion If you cannot find the same idea in the issues, you first need to write a GitHub issue (e.g. [issues in apache/arrow-julia](https://github.com/apache/arrow-julia/issues)) for a bug fix or planned features for the improvement. To write an issue would help the community have visibility and opportunities for collaborations before a pull request (PR) shows up. This is for the [Apache way](http://theapacheway.com/). We can use GitHub labels to identify bugs. ``` ########## File path: CONTRIBUTING.md ########## @@ -0,0 +1,37 @@ +# How to contribute Apache Arrow Julia + +## Did you find a bug or have an improvement? + +We recommend you first search among existing [Github issues](https://github.com/apache/arrow-julia/issues). The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue. + + +## How do you write a patch that fixes a bug or brings an improvement? +If you cannot find the same idea in the issues, you first need to write a GitHub issue (e.g. [issues in Arrow-julia](https://github.com/apache/arrow-julia/issues)) for a bug fix or planned features for the improvement. To write an issue would help the community have visibility and opportunities for collaborations before a pull request (PR) shows up. This is for the [Apache way](http://theapacheway.com/). We can use GitHub labels to identify bugs. +It should not be necessary to file an issue for some non-code changes, such as CI changes or minor documentation updates such as fixing typos. + +After writing the issue, you may want to write a code by creating [a PR](https://github.com/apache/arrow-julia/pulls). In the PR, it is preferable to refer to the issue number (e.g. `#1`) that you already created. + + +## 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://lists.apache.org/[email protected]). + + +## Do you have questions about the source code, the build procedure or the development process? + +You can also ask on the mailing-list, see above. + + +## Local Development + +When developing on Arrow.jl it is recommended that you run the following to ensure that any changes to ArrowTypes.jl are immediately available to Arrow.jl without requiring a release: + +``` +julia --project -e 'using Pkg; Pkg.develop(path="src/ArrowTypes")' +``` + + +## Release cycle + +The Julia community would like an independent release cycle. Release for apache/arrow doesn't include the Julia implementation. The Julia implementation uses separated version scheme. (apache/arrow uses 6.0.0 as the next version but the next Julia implementation release doesn't use 6.0.0.) Review comment: 6.0.0 has been released. So the example may confuse. ```suggestion The Julia community would like an independent release cycle. Release for apache/arrow doesn't include the Julia implementation. The Julia implementation uses separated version scheme. ``` ########## File path: CONTRIBUTING.md ########## @@ -0,0 +1,37 @@ +# How to contribute Apache Arrow Julia + +## Did you find a bug or have an improvement? + +We recommend you first search among existing [Github issues](https://github.com/apache/arrow-julia/issues). The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue. + + +## How do you write a patch that fixes a bug or brings an improvement? +If you cannot find the same idea in the issues, you first need to write a GitHub issue (e.g. [issues in Arrow-julia](https://github.com/apache/arrow-julia/issues)) for a bug fix or planned features for the improvement. To write an issue would help the community have visibility and opportunities for collaborations before a pull request (PR) shows up. This is for the [Apache way](http://theapacheway.com/). We can use GitHub labels to identify bugs. +It should not be necessary to file an issue for some non-code changes, such as CI changes or minor documentation updates such as fixing typos. + +After writing the issue, you may want to write a code by creating [a PR](https://github.com/apache/arrow-julia/pulls). In the PR, it is preferable to refer to the issue number (e.g. `#1`) that you already created. + + +## 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://lists.apache.org/[email protected]). + + +## Do you have questions about the source code, the build procedure or the development process? + +You can also ask on the mailing-list, see above. Review comment: In addition to the arrow-dev mailing list, I think that we can use GitHub issues and/or GitHub discussions (we can enable this by `.asf.yaml`). @quinnj What do you think about this? -- 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]
