-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #153 from ACCLAB/dev
v2023.9.12 along with favicon updates
- Loading branch information
Showing
28 changed files
with
311 additions
and
80 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,3 +12,4 @@ | |
^dabestr.Rmd$ | ||
^cran-comments\.md$ | ||
^revdep$ | ||
^CRAN-SUBMISSION$ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,4 +14,5 @@ dabestr.Rmd | |
.RProfile | ||
docs | ||
inst/doc | ||
figures | ||
/figures | ||
CRAN-SUBMISSION |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -55,7 +55,7 @@ further defined and clarified by project maintainers. | |
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project team at [email protected]. All | ||
reported by contacting the project team at [email protected]. All | ||
complaints will be reviewed and investigated and will result in a response that | ||
is deemed necessary and appropriate to the circumstances. The project team is | ||
obligated to maintain confidentiality with regard to the reporter of an incident. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,18 +1,53 @@ | ||
# Contributing to dabestr | ||
|
||
## Did you find a bug? | ||
- Ensure the bug was not already reported by searching in [Issues](https://github.com/ACCLAB/dabestr/issues). Check that the bug hasn't been addressed in a closed issue. | ||
The guide is divided into three main pieces: | ||
|
||
- If the bug isn't being addressed, open a new one. Be sure to include a title and clear description, and a [minimally reproducible code sample](http://adv-r.had.co.nz/Reproducibility.html) demonstrating the expected behavior that is not occurring. | ||
1. Filing a bug in an issue. | ||
1. Filing a feature request in an issue. | ||
1. Suggesting a change via a pull request. | ||
|
||
## Did you write a patch that fixes a bug? | ||
- Open a new GitHub pull request with the patch. | ||
Please note that dabestr is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By contributing to this project, you agree to abide by its terms. | ||
|
||
- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable. | ||
## Issues | ||
|
||
## Do you intend to add a new feature or change an existing one? | ||
- Suggest your change by opening an issue, and adding an Enhancement tag. | ||
- If the maintainers and the community are in favour, create a fork and start writing code. | ||
Ensure the bug was not already reported by searching in [Issues](https://github.com/ACCLAB/dabestr/issues). Be sure to also check that the bug hasn't been addressed in a closed issue. | ||
|
||
If the bug isn't being addressed, open a new one. | ||
|
||
Be sure to include a title and clear description, and a [minimally reproducible code sample](http://adv-r.had.co.nz/Reproducibility.html) demonstrating the expected behavior that is not occurring. | ||
|
||
## Feature Requests | ||
|
||
You may suggest by opening an issue and adding an Enhancement tag. | ||
|
||
## Pull requests | ||
|
||
To contribute a change to dabestr, you follow these steps: | ||
|
||
1. Create a fork and make your changes. | ||
1. Issue a PR to the dev branch of dabestr. | ||
1. Discuss the PR. | ||
1. Iterate until either we accept the PR or decide it's not a good fit for dabestr. | ||
|
||
Each of these steps are described in more detail below. | ||
|
||
If you're not familiar with git or github, please start by reading http://r-pkgs.had.co.nz/git.html | ||
|
||
### Guidelines | ||
1. **Clarity**. Ensure PR description clearly describes the problem and the solution. Include the relevant issue number if applicable. | ||
1. **Use dabestr coding style**. dabestr is currently following the [official tidyverse style](http://style.tidyverse.org/). You may choose to do so using the `styler` package by running the following on the code before submitting: | ||
|
||
```r | ||
# install.packages("styler") | ||
styler::style_pkg() | ||
``` | ||
3. If you're adding new parameters or a new function, you'll also need to document them with [roxygen](https://github.com/klutometis/roxygen). Make sure to re-run `devtools::document()` on the code before submitting. | ||
3. If fixing a bug or adding a new feature, please add a [testthat](https://github.com/r-lib/testthat) unit test. | ||
|
||
All PRs require review and approval from at least one member of the dabestr development team before merge. | ||
|
||
Lastly, dabestr is a **community** tool for estimation statistics and analysis. We look forward to more robust and more elegant data visualizations from you all! | ||
|
||
## Attribution | ||
This Contributing guide is adapted from [ggplot2](https://ggplot2.tidyverse.org)'s [CONTRIBUTING.md](https://github.com/tidyverse/ggplot2/blob/main/CONTRIBUTING.md?plain=1). | ||
|
||
dabestr is a community tool for estimation statistics and analysis. We look forward to more robust and more elegant data visualizations from you all! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,14 +3,14 @@ Type: Package | |
Title: Data Analysis using Bootstrap-Coupled Estimation | ||
Version: 2023.9.12 | ||
Authors@R: c( | ||
person("Joses W.", "Ho", email = "[email protected]", role = "aut", | ||
comment = c(ORCID = "0000-0002-9186-6322")), | ||
person("Kah Seng", "Lian", email = "[email protected]", role = c("aut")), | ||
person("Zhuoyu", "Wang", email = "[email protected],edu", role = "aut"), | ||
person("Jun Yang", "Liao", email = "[email protected]", role = "aut"), | ||
person("Joses W.", "Ho", email = "[email protected]", role = "aut", | ||
comment = c(ORCID = "0000-0002-9186-6322")), | ||
person("Felicia", "Low", role = "aut", email = "[email protected]"), | ||
person("Tayfun", "Tumkaya", role = "aut", | ||
comment = c(ORCID = "0000-0001-8425-3360")), | ||
person("Felicia", "Low", role = "aut", email = "[email protected]"), | ||
person("Yishan", "Mai", email = "[email protected]", role = c("cre", "ctb"), | ||
comment = c(ORCID = "0000-0002-7199-380X")), | ||
person("Sangyu", "Xu", role = "ctb", | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.