Contributor Covenant Code of Conduct
@@ -123,115 +48,96 @@Contributor Covenant Code of Conduct
-Our Pledge
+Our Pledge
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-Our Standards
+Our Standards
Examples of behavior that contributes to a positive environment for our community include:
--
-
- Demonstrating empathy and kindness toward other people +
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community -
- The use of sexualized language or imagery, and sexual attention or advances of any kind +
- The use of sexualized language or imagery, and sexual attention or advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others’ private information, such as a physical or email address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting -
Examples of unacceptable behavior include:
--
-
Examples of unacceptable behavior include:
+Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
-Scope
+Scope
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
-Enforcement
+Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-Enforcement Guidelines
+Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
--1. Correction
+1. Correction
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-2. Warning
+2. Warning
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-3. Temporary Ban
+3. Temporary Ban
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-4. Permanent Ban
+4. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
-Attribution
-This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/ code_of_conduct.html.
-Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
-For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https:// www.contributor-covenant.org/translations.
+Attribution
+This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/ code_of_conduct.html.
+Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https:// www.contributor-covenant.org/translations.
Contributing to mdbr
@@ -123,40 +48,31 @@Contributing to mdbr
This outlines how to propose a change to mdbr. For more detailed info about contributing to this, and other tidyverse packages, please see the development contributing guide.
--Fixing typos
-You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the source file. This generally means you’ll need to edit roxygen2 comments in an .R, not a .Rd file. You can find the .R file that generates the .Rd by reading the comment in the first line.
This outlines how to propose a change to mdbr. For more detailed info about contributing to this, and other tidyverse packages, please see the development contributing guide.
+Fixing typos
+You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the source file. This generally means you’ll need to edit roxygen2 comments in an .R, not a .Rd file. You can find the .R file that generates the .Rd by reading the comment in the first line.
-Bigger changes
-If you want to make a bigger change, it’s a good idea to first file an issue and make sure someone from the team agrees that it’s needed. If you’ve found a bug, please file an issue that illustrates the bug with a minimal reprex (this will also help you write a unit test, if needed).
--Pull request process
--
-
Fork the package and clone onto your computer. If you haven’t done this before, we recommend using
usethis::create_from_github("", fork = TRUE).
+Fork the package and clone onto your computer. If you haven’t done this before, we recommend using
usethis::create_from_github("", fork = TRUE).Install all development dependences with
devtools::install_dev_deps(), and then make sure the package passes R CMD check by runningdevtools::check(). If R CMD check doesn’t pass cleanly, it’s a good idea to ask for help before continuing.Create a Git branch for your pull request (PR). We recommend using
usethis::pr_init("brief-description-of-change").Make your changes, commit to git, and then create a PR by running
usethis::pr_push(), and following the prompts in your browser. The title of your PR should briefly describe the change. The body of your PR should containFixes #issue-number.
-For user-facing changes, add a bullet to the top of
NEWS.md(i.e. just below the first header). Follow the style described in https://style.tidyverse.org/news.html.
-For user-facing changes, add a bullet to the top of
NEWS.md(i.e. just below the first header). Follow the style described in https://style.tidyverse.org/news.html.
+New code should follow the tidyverse style guide. You can use the styler package to apply these styles, but please don’t restyle code that has nothing to do with your PR.
+We use roxygen2, with Markdown syntax, for documentation.
+We use testthat for unit tests. Contributions with test cases included are easier to accept.
+New code should follow the tidyverse style guide. You can use the styler package to apply these styles, but please don’t restyle code that has nothing to do with your PR.
-We use roxygen2, with Markdown syntax, for documentation.
-We use testthat for unit tests. Contributions with test cases included are easier to accept.
-
Bigger changes
+If you want to make a bigger change, it’s a good idea to first file an issue and make sure someone from the team agrees that it’s needed. If you’ve found a bug, please file an issue that illustrates the bug with a minimal reprex (this will also help you write a unit test, if needed).
+Pull request process
+Code style
+-Code style
--
-
-Code of Conduct
+Code of Conduct
Please note that the mdbr project is released with a Contributor Code of Conduct. By contributing to this project you agree to abide by its terms.
GNU General Public License
@@ -123,11 +48,10 @@GNU General Public License
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
--Preamble
+Preamble
The GNU General Public License is a free, copyleft license for software and other kinds of works.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
@@ -139,12 +63,10 @@Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and modification follow.
-TERMS AND CONDITIONS
--0. Definitions
+TERMS AND CONDITIONS
+0. Definitions
“This License” refers to version 3 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
@@ -154,9 +76,8 @@To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
-1. Source Code
+1. Source Code
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
@@ -164,31 +85,26 @@The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
-2. Basic Permissions
+2. Basic Permissions
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
-3. Protecting Users’ Legal Rights From Anti-Circumvention Law
+3. Protecting Users’ Legal Rights From Anti-Circumvention Law
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures.
-4. Conveying Verbatim Copies
+4. Conveying Verbatim Copies
You may convey verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
-5. Conveying Modified Source Versions
+5. Conveying Modified Source Versions
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
--
-
-
+
- a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
- b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”. @@ -196,15 +112,12 @@
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
- d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. -
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
-6. Conveying Non-Source Forms
+6. Conveying Non-Source Forms
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
--
-
-
+
- a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
- b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. @@ -214,22 +127,19 @@
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
- e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. -
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
-7. Additional Terms
+7. Additional Terms
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
--
-
-
+
- a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
- b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or @@ -241,34 +151,29 @@
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
- f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. -
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
-8. Termination
+8. Termination
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
-9. Acceptance Not Required for Having Copies
+9. Acceptance Not Required for Having Copies
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
-10. Automatic Licensing of Downstream Recipients
+10. Automatic Licensing of Downstream Recipients
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party’s predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
-11. Patents
+11. Patents
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor’s “contributor version”.
A contributor’s “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor’s essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
@@ -278,101 +183,90 @@A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
-12. No Surrender of Others’ Freedom
+12. No Surrender of Others’ Freedom
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
-13. Use with the GNU Affero General Public License
+13. Use with the GNU Affero General Public License
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
-14. Revised Versions of this License
+14. Revised Versions of this License
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
-15. Disclaimer of Warranty
+15. Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-16. Limitation of Liability
+16. Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-17. Interpretation of Sections 15 and 16
+17. Interpretation of Sections 15 and 16
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
-How to Apply These Terms to Your New Programs
+How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
-<one line to give the program's name and a brief idea of what it does.>
-Copyright (C) 2020 Kiernan Nicholls
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation, either version 3 of the License, or
-(at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program. If not, see <http://www.gnu.org/licenses/>.<one line to give the program's name and a brief idea of what it does.>
+Copyright (C) 2020 Kiernan Nicholls
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see <http://www.gnu.org/licenses/>.Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
-mdbr Copyright (C) 2020 Kiernan Nicholls
-This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
-This is free software, and you are welcome to redistribute it
-under certain conditions; type 'show c' for details.mdbr Copyright (C) 2020 Kiernan Nicholls
+This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type 'show c' for details.The hypothetical commands show w and show c should show the appropriate parts of the General Public License. Of course, your program’s commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.
-The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
+You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.
+The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
Getting help with mdbr
@@ -124,25 +49,20 @@Getting help with mdbr
Thanks for using mdbr! Before filing an issue, there are a few places to explore and pieces to put together to make the process as smooth as possible.
--Make a reprex
-Start by making a minimal reproducible example using the reprex package. If you haven’t heard of or used reprex before, you’re in for a treat! Seriously, reprex will make all of your R-question-asking endeavors easier (which is a pretty insane ROI for the five to ten minutes it’ll take you to learn what it’s all about). For additional reprex pointers, check out the Get help! section of the tidyverse site.
+Make a reprex
+Start by making a minimal reproducible example using the reprex package. If you haven’t heard of or used reprex before, you’re in for a treat! Seriously, reprex will make all of your R-question-asking endeavors easier (which is a pretty insane ROI for the five to ten minutes it’ll take you to learn what it’s all about). For additional reprex pointers, check out the Get help! section of the tidyverse site.
-Where to ask?
-Armed with your reprex, the next step is to figure out where to ask.
--
-
If it’s a question: start with community.rstudio.com, and/or StackOverflow. There are more people there to answer questions.
-If it’s a bug: you’re in the right place, file an issue.
+If it’s a question: start with community.rstudio.com, and/or StackOverflow. There are more people there to answer questions.
+If it’s a bug: you’re in the right place, file an issue.
If you’re not sure: let the community help you figure it out! If your problem is a bug or a feature request, you can easily return here and report it.
-
Where to ask?
+Armed with your reprex, the next step is to figure out where to ask.
+Before opening a new issue, be sure to search issues and pull requests to make sure the bug hasn’t been reported and/or already fixed in the development version. By default, the search will be pre-populated with is:issue is:open. You can edit the qualifiers (e.g. is:pr, is:closed) as needed. For example, you’d simply remove is:open to search all issues in the repo, open or closed.
Before opening a new issue, be sure to search issues and pull requests to make sure the bug hasn’t been reported and/or already fixed in the development version. By default, the search will be pre-populated with is:issue is:open. You can edit the qualifiers (e.g. is:pr, is:closed) as needed. For example, you’d simply remove is:open to search all issues in the repo, open or closed.
-What happens next?
+What happens next?
To be as efficient as possible, development of tidyverse packages tends to be very bursty, so you shouldn’t worry if you don’t get an immediate response. Typically we don’t look at a repo until a sufficient quantity of issues accumulates, then there’s a burst of intense activity as we focus our efforts. That makes development more efficient because it avoids expensive context switching between problems, at the cost of taking longer to get back to you. This process makes a good reprex particularly important because it might be multiple months between your initial report and when we start working on it. If we can’t reproduce the bug, we can’t fix it!
Authors
+ +Citation
+ Source:DESCRIPTION
+ -
-
-
-
Kiernan Nicholls. Author, maintainer. -
-
-
Nicholls K (2022). +mdbr: Work with Microsoft Access Files. +R package version 0.2.0, https://github.com/kiernann/mdbr. +
+@Manual{,
+ title = {mdbr: Work with Microsoft Access Files},
+ author = {Kiernan Nicholls},
+ year = {2022},
+ note = {R package version 0.2.0},
+ url = {https://github.com/kiernann/mdbr},
+}
Authors
--
-
+
@@ -79,108 +75,107 @@
@@ -189,56 +184,67 @@--
-mdbr
++ --The goal of mdbr is to easily access the open source MDB Tools written by Brian Bruns. The MDB Tools command line utilities take proprietary Microsoft Access files and convert them to standard text files. This package is experimental and has only been tested on simple MDB databases.
--+-Installation
-You can install the release version of mdbr from CRAN.
+The goal of mdbr is to easily access the open source MDB Tools written by Brian Bruns. The MDB Tools command line utilities take proprietary Microsoft Access files and convert them to standard text files. This package is experimental and has only been tested on simple MDB databases.
+++Installation +
+You can install the release version of mdbr from CRAN.
--
install.packages("mdbr")The development version can be installed from GitHub.
+install.packages("mdbr")The development version can be installed from GitHub.
--
# install.packages("remotes") -remotes::install_github("kiernann/mdbr")The user must install MDB Tools separately. Users on Debian systems can install the tools from the apt repository.
- -More installation methods can be found on the package’s README.
+# install.packages("remotes") +remotes::install_github("kiernann/mdbr")The user must install MDB Tools separately. Users on Debian systems can install the tools from the apt repository.
++sudo apt install mdbtoolsMore installation methods can be found on the package’s README.
--Example
+++Example +
-The package comes with a version of the nycflights13 relational database found with
+mdb_examples().library(mdbr) +library(readr)The package comes with a version of the nycflights13 relational database found with
mdb_examples().The tables in a database can be listed with
mdb_tables().+-
mdb_tables(ex <- mdb_example()) -#> [1] "Airlines" "Airports" "Flights" "Planes"mdb_tables(ex <- mdb_example()) +#> [1] "Airlines" "Airports" "Flights" "Planes"These tables can be exported as a delimited string or file.
+-
string <- export_mdb(ex, "Airlines", output = TRUE, delim = "|", quote = "'") -cat(string) -#> carrier|name -#> '9E'|'Endeavor Air Inc.' -#> 'AA'|'American Airlines Inc.' -#> 'AS'|'Alaska Airlines Inc.' -#> 'B6'|'JetBlue Airways' -#> 'DL'|'Delta Air Lines Inc.' -#> 'EV'|'ExpressJet Airlines Inc.' -#> 'F9'|'Frontier Airlines Inc.' -#> 'FL'|'AirTran Airways Corporation' -#> 'HA'|'Hawaiian Airlines Inc.' -#> 'MQ'|'Envoy Air' -#> 'OO'|'SkyWest Airlines Inc.' -#> 'UA'|'United Air Lines Inc.' -#> 'US'|'US Airways Inc.' -#> 'VX'|'Virgin America' -#> 'WN'|'Southwest Airlines Co.' -#> 'YV'|'Mesa Airlines Inc.'string <- export_mdb(ex, "Airlines", output = TRUE, delim = "|", quote = "'") +cat(string) +#> carrier|name +#> '9E'|'Endeavor Air Inc.' +#> 'AA'|'American Airlines Inc.' +#> 'AS'|'Alaska Airlines Inc.' +#> 'B6'|'JetBlue Airways' +#> 'DL'|'Delta Air Lines Inc.' +#> 'EV'|'ExpressJet Airlines Inc.' +#> 'F9'|'Frontier Airlines Inc.' +#> 'FL'|'AirTran Airways Corporation' +#> 'HA'|'Hawaiian Airlines Inc.' +#> 'MQ'|'Envoy Air' +#> 'OO'|'SkyWest Airlines Inc.' +#> 'UA'|'United Air Lines Inc.' +#> 'US'|'US Airways Inc.' +#> 'VX'|'Virgin America' +#> 'WN'|'Southwest Airlines Co.' +#> 'YV'|'Mesa Airlines Inc.'Tables can be easily converted to a temporary file and read immediately.
+-
read_mdb(ex, "Airports") -#> # A tibble: 1,458 x 8 -#> faa name lat lon alt tz dst tzone -#> <chr> <chr> <dbl> <dbl> <dbl> <dbl> <chr> <chr> -#> 1 04G Lansdowne Airport 41.1 -80.6 1044 -5 A America/New_York -#> 2 06A Moton Field Municipal Airport 32.5 -85.7 264 -6 A America/Chicago -#> 3 06C Schaumburg Regional 42.0 -88.1 801 -6 A America/Chicago -#> 4 06N Randall Airport 41.4 -74.4 523 -5 A America/New_York -#> 5 09J Jekyll Island Airport 31.1 -81.4 11 -5 A America/New_York -#> 6 0A9 Elizabethton Municipal Airport 36.4 -82.2 1593 -5 A America/New_York -#> 7 0G6 Williams County Airport 41.5 -84.5 730 -5 A America/New_York -#> 8 0G7 Finger Lakes Regional Airport 42.9 -76.8 492 -5 A America/New_York -#> 9 0P2 Shoestring Aviation Airfield 39.8 -76.6 1000 -5 U America/New_York -#> 10 0S9 Jefferson County Intl 48.1 -123. 108 -8 A America/Los_Angeles -#> # … with 1,448 more rowsread_mdb(ex, "Airports") +#> # A tibble: 1,458 x 8 +#> faa name lat lon alt tz dst tzone +#> <chr> <chr> <dbl> <dbl> <dbl> <dbl> <chr> <chr> +#> 1 04G Lansdowne Airport 41.1 -80.6 1044 -5 A America/New_York +#> 2 06A Moton Field Municipal Airport 32.5 -85.7 264 -6 A America/Chicago +#> 3 06C Schaumburg Regional 42.0 -88.1 801 -6 A America/Chicago +#> 4 06N Randall Airport 41.4 -74.4 523 -5 A America/New_York +#> 5 09J Jekyll Island Airport 31.1 -81.4 11 -5 A America/New_York +#> 6 0A9 Elizabethton Municipal Airport 36.4 -82.2 1593 -5 A America/New_York +#> 7 0G6 Williams County Airport 41.5 -84.5 730 -5 A America/New_York +#> 8 0G7 Finger Lakes Regional Airport 42.9 -76.8 492 -5 A America/New_York +#> 9 0P2 Shoestring Aviation Airfield 39.8 -76.6 1000 -5 U America/New_York +#> 10 0S9 Jefferson County Intl 48.1 -123. 108 -8 A America/Los_Angeles +#> # … with 1,448 more rowsWhen reading a converted table, you might need to know what types of data to expect from each column.
The schema of database tables describes the column types.
--mdb-schema -T Airports nycflights13.mdb -#> -- ---------------------------------------------------------- -#> -- MDB Tools - A library for reading MS Access database files -#> -- Copyright (C) 2000-2011 Brian Bruns and others. -#> -- Files in libmdb are licensed under LGPL and the utilities under -#> -- the GPL, see COPYING.LIB and COPYING files respectively. -#> -- Check out http://mdbtools.sourceforge.net -#> -- ---------------------------------------------------------- -#> -#> CREATE TABLE [Airports] -#> ( -#> [faa] Text (510), -#> [name] Text (510), -#> [lat] Double, -#> [lon] Double, -#> [alt] Long Integer, -#> [tz] Integer, -#> [dst] Text (510), -#> [tzone] Text (510) -#> );This information can be interpreted as a readr spec object, which is used to accurately parse columns of a converted text file.
++mdb-schema -T Airports nycflights13.mdb +#> -- ---------------------------------------------------------- +#> -- MDB Tools - A library for reading MS Access database files +#> -- Copyright (C) 2000-2011 Brian Bruns and others. +#> -- Files in libmdb are licensed under LGPL and the utilities under +#> -- the GPL, see COPYING.LIB and COPYING files respectively. +#> -- Check out http://mdbtools.sourceforge.net +#> -- ---------------------------------------------------------- +#> +#> CREATE TABLE [Airports] +#> ( +#> [faa] Text (510), +#> [name] Text (510), +#> [lat] Double, +#> [lon] Double, +#> [alt] Long Integer, +#> [tz] Integer, +#> [dst] Text (510), +#> [tzone] Text (510) +#> );This information can be interpreted as a readr spec object, which is used to accurately parse columns of a converted text file.
+-
mdb_schema(ex, "Airports", condense = TRUE) -#> cols( -#> .default = col_character(), -#> lat = col_double(), -#> lon = col_double(), -#> alt = col_integer(), -#> tz = col_integer() -#> )mdb_schema(ex, "Airports", condense = TRUE) +#> cols( +#> .default = col_character(), +#> lat = col_double(), +#> lon = col_double(), +#> alt = col_integer(), +#> tz = col_integer() +#> )
Dev status
+ + diff --git a/news/index.html b/news/index.html index ba89baf..aeefc99 100644 --- a/news/index.html +++ b/news/index.html @@ -1,74 +1,12 @@ - - - - - - - --mdbr 0.1.1 Unreleased -
--
+
- Functions now quote their input files with
shQuote(). (#7) -
-
read_mdb()now hasstdout()which can takeTRUEor a file path.
+ - Remove all formatting arguments for
read_mdb()(with smart hidden defaults).
+ - Add more schema types with readr equivalents. +
- Write schema to a matrix in-memory rather than a temporary file. +
- Always read data from a temporary file instead of
stdoutoption.
+ - Add better checking if mdbtools is installed. +
-
+
read_mdb()now hasstdout()which can takeTRUEor a file path. - Examples and tests don’t run on CRAN. -
mdbr 0.2.0
+export_mdb() now mirrors readr::format_csv() with arguments, etc.
+mdbr 0.1.1
+Export an Access database table as a text file
- Source:R/export.R
+ Source: R/export.R
export_mdb.RdExport an Access database table as a text file
it easy to read tables into R or a spreadsheet.export_mdb( - file, - table, - output = TRUE, - delim = ",", - quote = "\"", - quote_escape = "double", - col_names = TRUE, - eol = "\n", - date_format = "%Y-%m-%d %H:%M:%S" -)- -
Arguments
-| file | -Path to the Microsoft Access file. |
-
|---|---|
| table | -Name of the table, list with |
-
| output | -Path or connection to write to. Passed to the
+
+
+
+ Arguments+
|
-
| delim | -Delimiter used to separate values. |
-
| quote | -Single character used to quote strings. Defaults to |
-
| quote_escape | -The type of escaping to use for quoted values, one of +character vector) or a character string naming a file. + + +Delimiter used to separate values. Single character used to quote strings. Defaults to The type of escaping to use for quoted values, one of
|
-
| col_names | -If |
-
| eol | -The end of line character to use. Most commonly either |
-
| date_format | -The format in which date columns are converted. MDB Tools
-uses the |
-
Value
- -Character string, invisible if path to file.
- -Examples
-+for Excel. + + +
If FALSE, column names will not be included at the top of
+the file. If TRUE, column names will be included.
The end of line character to use. Most commonly either "\n" for
+Unix style newlines, or "\r\n" for Windows style newlines.
The format in which date columns are converted. MDB Tools
+uses the strftime(3) format, similar to readr::parse_date(). No need to
+specify whole string. Defaults to ISO8601.
Value
+ + +Character string, invisible if path to file.
+Examples
+if (FALSE) {
+export_mdb(mdb_example(), "Airlines", output = TRUE)
+}
+