quinnj commented on a change in pull request #278: URL: https://github.com/apache/arrow-julia/pull/278#discussion_r791911674
########## 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. Review comment: ```suggestion After writing the issue, you can submit 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. ``` ########## 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: Yes, the norm in the Julia ecosystem is to use GitHub issues or the new "discussions" feature, which I find both much more easy to digest/follow than mailing list threads. Which reminds me, can we turn on the "Discussions" feature for the arrow-julia repo please? It should just be a checkbox in the repo settings. ########## 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: Yes, I'd prefer people open issues/discussions than post on the mailing list, personally. I find the repository issue/discussion list to be a good centralized place to refer to open issues/discussions rather than searching through past mailing threads. ########## 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: ```suggestion The Julia community releases independently from the main [apache/arrow](https://github.com/apache/arrow) project. Release for apache/arrow doesn't include the Julia implementation. The Julia implementation uses the more traditional version scheme typical of packages in the Julia ecosystem. The apache/arrow project does regular major version releases, like 6.0.0, whereas apache/arrow-julia will only do major version releases for breaking changes to the user-facing package API. ``` -- 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]
