Skip to content

/ software-review

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

submission: ess #201

Closed
cimentadaj opened this issue Mar 4, 2018 · 45 comments
Closed

submission: ess #201

cimentadaj opened this issue Mar 4, 2018 · 45 comments
Assignees
@maelle
Labels
6/approved topic:data-access

Comments

@cimentadaj
Copy link

@cimentadaj cimentadaj commented Mar 4, 2018 •
edited

Summary

  • What does this package do? (explain in 50 words or less):

It allows users to download and explore data from the European Social Survey directly into R. Broadly speaking, it has two family of functions. The ess_* family, which downloads data from specific waves and countries and the show_* functions which allows the users to check which waves/countries are available.

  • Paste the full DESCRIPTION file inside a code block below:
Package: ess
Title: Download Data from the European Social Survey on the Fly
Version: 0.1.1
Authors@R: person("Jorge", "Cimentada", email = "cimentadaj@gmail.com", role = c("aut", "cre"))
BugReports: https://github.com/cimentadaj/ess/issues
Description: Download data from the European Social Survey directly from their website <http://www.europeansocialsurvey.org/>. There are two family of functions that allow you to download and interactively check all countries and rounds available.
Depends: R (>= 3.4.0)
License: MIT + file LICENSE
URL: https://github.com/cimentadaj/ess
Encoding: UTF-8
LazyData: true
RoxygenNote: 6.0.1
Imports: 
    xml2,
    httr,
    stringr,
    haven,
    rvest,
    tibble
Suggests: 
    testthat,
    knitr,
    rmarkdown,
    covr
VignetteBuilder: knitr
Note: The ess package is named to match the European Social Survey (ESS) hosted at http://www.europeansocialsurvey.org/. It is unrelated to the Emacs Speaks Statistics (ESS) project, an emacs-based Integrated Development Environment hosted at https://ess.r-project.org

  • URL for the package (the development repository, not a stylized html page):
    https://github.com/cimentadaj/ess

  • Please indicate which category or categories from our package fit policies this package falls under *and why(? (e.g., data retrieval, reproducibility. If you are unsure, we suggest you make a pre-submission inquiry.):

[e.g., "data extraction, because the package parses a scientific data file format"]

data retrieval, because the main objective of the package is to download a set of datasets widely used in the social sciences.

  •   Who is the target audience and what are scientific applications of this package?  

Mainly academics working in disciplines such as Economics, Demography, Psychology, Political Science and Sociologists. Hundreds of papers have been written using the European Social Survey, a survey carried over in over 30 countries for over 15 years that asks citizens everything from their health status to their political preferences. This package will allow full reproducibility for many of the academics using the survey and equally important, will remove the burden of manually exploring/downloading the datasets from the ESS website.

The lodown package (not on CRAN) has one function for downloading the data as 'Stata' or 'SPSS' files for only specific waves. The package is not intended specifically for the ESS data. This package differs because it allows the user to download the files directly into R selecting different wave/country combinations. It also supports downloading the files in 'Stata', 'SPSS' and in 'SAS' and offers a range of functions for exploring the available countries/waves directly from R.

  •   If you made a pre-submission enquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted.

Requirements

Confirm each of the following by checking the box. This package:

  • does not violate the Terms of Service of any service it interacts with.
  • has a CRAN and OSI accepted license.
  • contains a README with instructions for installing the development version.
  • includes documentation with examples for all functions.
  • contains a vignette with examples of its essential functions and uses.
  • has a test suite.
  • has continuous integration, including reporting of test coverage, using services such as Travis CI, Coveralls and/or CodeCov.
  • I agree to abide by ROpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

Publication options

  • Do you intend for this package to go on CRAN?
  • Do you wish to automatically submit to the Journal of Open Source Software? If so:
    • The package has an obvious research application according to JOSS's definition.
    • The package contains a paper.md matching JOSS's requirements with a high-level description in the package root or in inst/.
    • The package is deposited in a long-term repository with the DOI:
    • (Do not submit your package separately to JOSS)
  • Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution? If so:
    • The package is novel and will be of interest to the broad readership of the journal.
    • The manuscript describing the package is no longer than 3000 words.
    • You intend to archive the code for the package in a long-term repository which meets the requirements of the journal (see MEE's Policy on Publishing Code)
    • (Scope: Do consider MEE's Aims and Scope for your manuscript. We make no gaurantee that your manuscript willl be within MEE scope.)
    • (Although not required, we strongly recommend having a full manuscript prepared when you submit here.)
    • (Please do not submit your package separately to Methods in Ecology and Evolution)

Detail

  • Does R CMD check (or devtools::check()) succeed? Paste and describe any errors or warnings:
    It succeeds with no errors/warnings.

  • Does the package conform to rOpenSci packaging guidelines? Please describe any exceptions:

It conforms.

  • If this is a resubmission following rejection, please explain the change in circumstances:

  • If possible, please provide recommendations of reviewers - those with experience with similar packages and/or likely users of your package - and their GitHub user names:

I don't know anyone who has experience with this type of packages but I assume anyone with relevant experience in web scraping is adequate. The workhorse of the package is scraping the ESS website, reading it with the haven package and putting the data in a suitable format for R.
@cimentadaj cimentadaj changed the title Submission of the ess package submission: ess Mar 4, 2018
@maelle
Copy link
Member

@maelle maelle commented Mar 8, 2018

@cimentadaj thanks for your submission! I'm doing the editor checks right now and... the tests take a very long time, right?
@maelle
Copy link
Member

@maelle maelle commented Mar 8, 2018 •
edited

Editor checks:

  • Fit: The package meets criteria for fit and overlap
  • Automated tests: Package has a testing suite and is tested via Travis-CI or another CI service.
  • License: The package has a CRAN or OSI accepted license
  • Repository: The repository link resolves correctly
  • Archive (JOSS only, may be post-review): The repository DOI resolves correctly
  • Version (JOSS only, may be post-review): Does the release version given match the GitHub release (v1.0.0)?

Editor comments

Thanks for your submission @cimentadaj! 😸 The tests are now finished. 😌 I'm currently looking for a second reviewer (thanks @leeper for accepting to review!).

Please add this badge to ess README

[![](https://badges.ropensci.org/201_status.svg)](https://github.com/ropensci/onboarding/issues/201)

Here are a few comments/questions.

  • Just curious, why is there a note about the package name in DESCRIPTION, was that demanded by CRAN?

  • The link from the pkgdown website is missing from the repo description.

  • goodpractice::gp indicates a few long code lines. It seems that they are error messages so it is fine. You can escape them with # nolint cf https://github.com/jimhester/lintr#project-configuration

  • Please document the fact that one needs to set "your_email" as an environment variable. I moreover think its name is a bit confusing, it is my email 😉 maybe it should be "ess_account_email"?

  • I'd recommend you to look for the email by default like what is done in this package

Reviewers: @leeper @nujcharee
Due date: 2018-03-29
@leeper
Copy link
Member

@leeper leeper commented Mar 9, 2018 •
edited

Package Review

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide

  • As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Documentation

The package includes all the following forms of documentation:

  • A statement of need clearly stating problems the software is designed to solve and its target audience in README
  • Installation instructions: for the development version of package and any non-standard dependencies in README
  • Vignette(s) demonstrating major functionality that runs successfully locally
  • Function Documentation: for all exported functions in R help
  • Examples for all exported functions in R Help that run successfully locally
  • Community guidelines including contribution guidelines in the README or CONTRIBUTING, and DESCRIPTION with URL, BugReports and Maintainer (which may be autogenerated via Authors@R).
For packages co-submitting to JOSS

The package contains a paper.md matching JOSS's requirements with:

  • A short summary describing the high-level functionality of the software
  • Authors: A list of authors with their affiliations
  • A statement of need clearly stating problems the software is designed to solve and its target audience.
  • References: with DOIs for all those that have one (e.g. papers, datasets, software).

Functionality

  • Installation: Installation succeeds as documented.
  • Functionality: Any functional claims of the software been confirmed.
  • Performance: Any performance claims of the software been confirmed.
  • Automated tests: Unit tests cover essential functions of the package
    and a reasonable range of inputs and conditions. All tests pass on the local machine.
  • Packaging guidelines: The package conforms to the rOpenSci packaging guidelines

Final approval (post-review)

  • The author has responded to my review and made changes to my satisfaction. I recommend approving this package.

Estimated hours spent reviewing: 0.5

Review Comments

This package is a very easy-to-use tool for download ESS data. It will be of great benefit to ESS users in both a teaching and research context. In the latter case, it will no doubt help considerably with reproducibility of analyses using the ESS. The code is generally well-written and the documentation is mostly excellent. Both the README and vignette provide useful introductions to the package and explain all functionality.

I have flagged seven issues I would like to see responses to:

These are all suggestions for improvement rather than obvious bugs or problems with the package. The only other suggestion I would have is that this package may significantly increase interest in the ESS among R users and therefore it may be valuable to expand the examples in the README or add an additional vignette that showcases some of the really interesting substantive data available in the datasets. It would be great to see a few tables or graphs showing some interesting patterns. Not necessary, of course, but that might help sell R users on the ESS in the way that the package is already helping sell ESS users on R.

Great package.
@maelle
Copy link
Member

@maelle maelle commented Mar 9, 2018

Wow thanks a lot for your extremely rapid and good review @leeper 😮 👏

Could you please fill and add the review template to your comment? Thanks in advance.
@maelle
Copy link
Member

@maelle maelle commented Mar 9, 2018

Just a suggestion as a reaction to @leeper's excellent suggestion to add examples, I tend to think minimal READMEs make more sense with a pkgdown website (especially if the README has links to articles/vignettes), so adding a vignette or several ones might be better than expanding the README.
@maelle
Copy link
Member

@maelle maelle commented Mar 9, 2018

@cimentadaj also note that I'll expect you to answer to/comment on @leeper's issues in this thread as well to make all information about your changes available here as well. 😺
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 9, 2018 •
edited

@maelle
Copy link
Member

@maelle maelle commented Mar 9, 2018 •
edited

Thanks for agreeing to review this package @nujcharee! 😸 Your review is due on 2018-03-30.

As a reminder here are links to the recently updated reviewing and packaging guides and to the review template.

@cimentadaj you can wait for @nujcharee's review before responding if you wish.
@nujcharee
Copy link

@nujcharee nujcharee commented Mar 11, 2018 •
edited

Package Review

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide

  • As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Documentation

The package includes all the following forms of documentation:

  • A statement of need clearly stating problems the software is designed to solve and its target audience in README
  • Installation instructions: for the development version of package and any non-standard dependencies in README
  • Vignette(s) demonstrating major functionality that runs successfully locally
  • Function Documentation: for all exported functions in R help
  • Examples for all exported functions in R Help that run successfully locally
  • Community guidelines including contribution guidelines in the README or CONTRIBUTING, and DESCRIPTION with URL, BugReports and Maintainer (which may be autogenerated via Authors@R).
For packages co-submitting to JOSS

The package contains a paper.md matching JOSS's requirements with:

  • A short summary describing the high-level functionality of the software
  • Authors: A list of authors with their affiliations
  • A statement of need clearly stating problems the software is designed to solve and its target audience.
  • References: with DOIs for all those that have one (e.g. papers, datasets, software).

Functionality

  • Installation: Installation succeeds as documented.
  • Functionality: Any functional claims of the software been confirmed.
  • Performance: Any performance claims of the software been confirmed.
  • Automated tests: Unit tests cover essential functions of the package
    and a reasonable range of inputs and conditions. All tests pass on the local machine.
  • Packaging guidelines: The package conforms to the rOpenSci packaging guidelines

Final approval (post-review)

  • The author has responded to my review and made changes to my satisfaction. I recommend approving this package.

Estimated hours spent reviewing: 6

Review Comments

The ESS package provides programmatic access to European Social Survey published on http://www.europeansocialsurvey.org/downloadwizard/. Users can directly download the surveys from the website in 3 different formats: SPSS, STATA and CSV. The ESS package is compact and easy to use with 2 main family functions: show_* and ess_*. It also offers functions that handle missing values.

There are a few functions that use external packages such as library(rvest), library(xml2). At the installation these packages weren't installed as they were already installed on my local machine.

The vignettes gives an introduction of what ESS is and contains a link to the website. It also demonstrates common usage and are easy to follow.

I installed and ran it successfully on Windows 7 (R-3.4.2) and Mac OS X (R-3.3.2)
I used test_package("ess") and received the following message OK: 38 SKIPPED: 23 FAILED: 0

Possibilities for improvement

library(tidyverse)
one_round <-
  ess_rounds(1, "your_email@email.com") %>%
  recode_missings()
  • In my opinion, for those you aren't familiar with Social Survey, they might be really beneficial from a brief description of what the term "round" mean and how this is used in the context of social survey.
  • Opportunities to apply global variables for "email address"
  • Opportunities to merge functions "ess_all_rounds()" and "ess_rounds()" where "all" is default if country variables aren't passed.
  • Making the country_name argument case insensitive is a potential improvement.

Final note

Great package, I can see the potential for it to become very popular among social science professionals.
@nujcharee
Copy link

@nujcharee nujcharee commented Mar 12, 2018

@maelle I hope this is useful. Let me know if I can assist you further :)
@maelle
Copy link
Member

@maelle maelle commented Mar 12, 2018

Thanks a lot @nujcharee for your great review! 😺 👌

@leeper could you please add the review template to yours? 🙏

@cimentadaj both reviews are now in! 😀
@leeper
Copy link
Member

@leeper leeper commented Mar 12, 2018

@maelle done
@maelle
Copy link
Member

@maelle maelle commented Mar 12, 2018

Thanks @leeper!
@jimhester
Copy link

@jimhester jimhester commented Mar 12, 2018

I have no background in social sciences so have no idea how ubiquitous the acronym ESS for European Social Survey is, but in the R / S community there is long precedent for ESS standing for Emacs Speaks Statistics, dating back to at least 1994, before R existed. Emacs Speaks Statistics is also quite popular for emacs R users, so this is not a niche issue.

I am actually astonished that this package was allowed on CRAN with this name and would really encourage considering changing the name to something more descriptive; maybe essurvey would suffice, you could retain the ess_ shorthand for the internal functions.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 14, 2018 •
edited

Everyone, thanks for the suggestions/comments. I will go one by one. @maelle

  • Just curious, why is there a note about the package name in DESCRIPTION, was that demanded by CRAN?

This is because it has conflicts with Emacs Speaks Statistics and the Emacs authors suggested that I add it as a note and they will add it as well to their R package. In fact, the point raised by @jimhester has been raised by several other R users in this email thread. Among social scientists the ESS acronym is widely known and would be the first thing that comes to mind, yet not many of these scientists are R users, whereas Emacs Speaks Statistics is widely used/known in the R community. I've decided that it is best for the package to be renamed and rereleased in the future. In fact, I was thinking of using the same name @jimhester suggested, essurvey. I don't know how this affects the rOpensci submission, let me know if something needs to be changed. I will make the name change effective when I have time, somewhere in the next few weeks.

  • The link from the pkgdown website is missing from the repo description.

Done 👍

Done 👍

Please document the fact that one needs to set "your_email" as an environment variable. I moreover think its name is a bit confusing, it is my email 😉 maybe it should be "ess_account_email"? I'd recommend you to look for the email by default like what is done in this package

Currently your_email is not an environment variable but purely an argument. Following the comments of @leeper I think a better approach would be set it as environment/option variables but also allow the email as an argument (for backward dependency), encouraging the user not to use the email as an argument; this would be explained in detail in the vignette, which might cause confusion for ESS users not familiar with R. The approach would be similar but slightly different from the package you suggested.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 14, 2018 •
edited

Thanks @leeper! I will review your suggestions in the coming days. I think that making a more 'practical' vignette is also a good idea. I will work on it.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 14, 2018

@nujcharee thank you very much for your comments! I agree with your suggestions and will implement them soon. In fact, I think you also raised some common points that overlap with what @leeper suggested. Thanks!
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 14, 2018 •
edited

EDIT:
I will post all of @leeper 's answers here:

Issue https://github.com/cimentadaj/ess/issues/20 asked for package documentation. Closed it with cimentadaj/ESS@ed0df5c

Issue https://github.com/cimentadaj/ess/issues/21 suggested that the package should have a better documentation for show_rounds_country(). The function accepts a numeric vector of rounds (currently from 1:8) and returns the countries that participated in all of these rounds (that is, AND rather than OR). The issue suggested either improving documentation to make this clear or adding a separate function for AND and for OR.

See cimentadaj/ESS@76007c5 where I improved documentation as to make it clear with some examples. Adding a OR type of function could be handy, and something that I will add for next releases yet I don't think it's urgent. Users can find a work around around along theses lines purrr::map(ess::show_rounds(), ess::show_rounds_country).

Issue https://github.com/cimentadaj/ess/issues/22 suggests to break the ess_* functions into two: an import_* and download_* function. This is the case because all ess_* functions have the functionality to import data into R or download data into a directory without returning anything in R. This change makes a lot of sense and I think is the right way to approach this. In fact, the implementation should be straight forward. However, I'm concerned about backward compatibility and the fact that I plan to change the name of the package to essurvey in the near future.

My main concern is having both the breaking compatibility change in the ess package and then changing the name of the package in a short period of time. I would want to give some time to users to communicate the API changes and let them know that the functions will be deprecated without also swamping them with a new package name (let's remember that the users of this package are not necessarily R users but people who come to R for specific things). I've thought a lot about this and I think this could be one solution:

  • Release the package with all the changes from the rOpensci (including this change) review as the new package name essurvey.

  • This new release will contain the import_* and download_* functions respectively and provide a deprecated message for all ess_* functions. This specifies that the functions will be removed from the package altogether in the next release (3 months, more or less)

  • Publicising the package

  • Remove ess_* functions 3-4 months later.

I'm really hesitant on this step so I'd like to hear your comments. Perhaps it's not the best idea to apply these changes in the first place because the breaking changes are not extremely necessary.

I'd really like to hear your feedback on this particular point.

https://github.com/cimentadaj/ess/issues/23 gave a very reasonable suggestion to set the your_email argument as an environment variable rather than using it in every ess_* function call. I think this is very useful feedback! I implemented this in cimentadaj/ESS@11fcf11

A summary of the changes:

  • Add `set_email("email@email.com") function
  • Change the examples/vignette/READMe to a workflow using set_email rather than showing the email.
  • Change the your_email argument name to ess_email in all ess_* functions.

All tests pass, so it should be good to do. (Again, very sorry that the commits seem to rewrite whole documents. Something weird is happening when making changes using the Ubuntu terminal in Windows 10.)

Issue https://github.com/cimentadaj/ess/issues/24 suggested that every request made to the ESS website should be made over HTTPS rather than HTTP for security reasons.

See cimentadaj/ESS@57656ff for the implementation.

Good suggestion, I had no idea of the difference between HTTPS and HTTP. Let me know if this is fine, to close the issue.

Issue https://github.com/cimentadaj/ess/issues/25 was about using match.arg to match the format argument in all of the ess_ functions instead of creating custom checks.

I hadn't thought about it! Thanks. I'm applying it to the case of matching the format argument through out the package. However, in the other cases prefer to have a separate stop message, like here. This is because it checks whether the supplied country name is available in the ESS website and instead of match.arg returning all the country names (long) I stop with a clear message suggesting the user to check show_countries() for the correct country name. Applies to rounds (and themes), with an even more explicit error.

There are other instances where it make sense such as here but it doesn't work as expect because it needs to match every code and throw an error if it doesn't. For example match.arg(c("123", "Refusal"), c("Don't Know", "Refusal"), TRUE) only returns Refusal but doesn't raise an error. So in these other cases I also think the error message is more strict. See cimentadaj/ESS@0336d37. Let me know if it addresses your concern so I close that issue.

Issue https://github.com/cimentadaj/ess/issues/26 suggested to add documentation about using weights for analyzing the ESS data. More specifically it advised either writing a second vignette showing examples or warn the user that it should use weights in the README, vignette and package documentation. I closed this via cimentadaj/ESS@d83f728 by including comments and notes on the weights on the three sources of documentation. Implementing a second vigenette, together with more general examples using the weighted ESS data is something I have on my to-do list. In fact, I haven't created these examples because I'm currently working on developing a package to analyze the ESS. Once I have that done I'll create more vignettes for both packages.

PS: Sorry for the whole document rewrite in the commit. I'm getting these weird bugs using the Ubuntu terminal in Windows 10.
@jimhester
Copy link

@jimhester jimhester commented Mar 14, 2018 •
edited

In terms of the particulars of renaming the package, I think the best way to do it is to submit the package to CRAN with the new name, and in your comments to CRAN in the submission say you want to rename the package and archive the old name along with the reasons for doing so.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 24, 2018

@maelle, my answer's to @leeper and @nujcharee are in.
@leeper
Copy link
Member

@leeper leeper commented Mar 24, 2018

I'm happy with all of the responses to my comments.
@maelle
Copy link
Member

@maelle maelle commented Mar 24, 2018

@nujcharee are you happy with @cimentadaj's answer?
@cimentadaj cimentadaj mentioned this issue Mar 24, 2018
Closed
@nujcharee
Copy link

@nujcharee nujcharee commented Mar 25, 2018

@maelle @cimentadaj I am also happy yes ;)
@nujcharee
Copy link

@nujcharee nujcharee commented Mar 25, 2018

I think in terms of the function “all” I think personally that “all” function can be obselete if it can be embedded in ess_round function when countries aren’t specified.

I made a suggestion as a recommendation. Looking forward to seeing this on CRAN soon good luck.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 25, 2018

Thanks a lot @nujcharee! @maelle, if the package gets accepted we need to sort out the issue with name of the package. Right now the name of the package is ess both in CRAN and on Github. During this week I'm going to finish all of the changes from the review and change the Github package name to essurvey and resubmit to CRAN in the next weeks. Perhaps the package can be essurvey in rOpensci while I resubmit it to CRAN with that name.
@maelle
Copy link
Member

@maelle maelle commented Mar 25, 2018

Thanks @nujcharee and thanks @cimentadaj!

I still need to perform the last editor checks (should lead to minor comments only). Maybe it's best to have waited for you to have finished all review changes before I have a last look anyway, so ping me when it's done if that's ok with you?

We could transfer even before the name change, I think redirections from the old account/reponame would still work if it is newaccount/newreponame. But I haven't checked that yet.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 25, 2018 •
edited

Ok @maelle , the changes are in and the package has be renamed. I switched it to essurvey on Github and everything on the package has been renamed to essurvey over ess. All tests pass so I'm just waiting for the badge update. I will submit to CRAN once this review process is over to make the process much smoother.
@maelle
Copy link
Member

@maelle maelle commented Mar 25, 2018

Approved! Great work @cimentadaj and great reviewer work @leeper & @nujcharee ! A few last comments/questions from me

  • Have you checked whether it's ok to use the ESS logo?

  • Only a suggestion, you could choose to add the reviewers to DESCRIPTION as "rev", with their permission. See this recent blog post

  • the install.packages instruction is currently wrong, maybe you should remove it and add it back when the package is on CRAN?

  • Add the pkgdown link to the repo URL field and also to DESCRIPTION (after a comma)

Now here is the list of things you have to do before I close this issue 😉

  • [] Transfer the repo to the rOpenSci organization under "Settings" in your repo. I have invited you to a team that should allow you to do so. I'll make you an admin once you do.
  • [] Fix any links in badges for CI and coverage to point to the ropensci URL
  • [] add rOpenSci footer to README
    [![ropensci_footer](https://ropensci.org/public_images/ropensci_footer.png)](https://ropensci.org)
  • [] In your .github dir can you also add a CONTRIBUTING.md and a PR template, see https://github.com/ropensci/dotgithubfiles/ for examples
  • [] We're starting to roll out software metadata files to all ropensci packages via the Codemeta initiative, see https://github.com/ropensci/codemetar/#codemetar for how to include it in your package, after installing the package - should be easy as running codemetar::write_codemeta() in the root of your package

Welcome aboard! We'd also love a blog post about your package, either a short-form intro to it (https://ropensci.org/tech-notes/) or long-form post with more narrative about its development. ((https://ropensci.org/blog/). If you are, @stefaniebutland will be in touch about content and timing.
@maelle
Copy link
Member

@maelle maelle commented Mar 25, 2018

And thanks again @jimhester for chiming in! 👌
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 26, 2018 •
edited

@maelle thank you very much for the review. Thanks as well to@leeper and @nujcharee for some great reviews. essurvey benefited a lot from your comments.

Answer's to @maelle's comments below:

Have you checked whether it's ok to use the ESS logo?
Hmm, I'm not entirely sure but the communications office of the ESS has been retweeting the package constantly in their official account, so I'm guessing there shouldn't be a problem. Here's one example but there's plenty more.

Only a suggestion, you could choose to add the reviewers to DESCRIPTION as "rev", with their permission. Done! @leeper and @nujcharee would you like to be listed as reviewers? @nujcharee is your complete name Nujcharee Haswell?

the install.packages instruction is currently wrong, maybe you should remove it and add it back when the package is on CRAN? Yeah, I forgot, thanks!

Add the pkgdown link to the repo URL field and also to DESCRIPTION (after a comma)
I added the pkg website to DESCRIPTION for I can't seem to find a URL field in the repository. What do you mean exactly?
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 26, 2018

@maelle, finalized all changes to close the issue. You can check out the repo at https://github.com/ropensci/essurvey

Thank you all for this experience! I learned a lot from it and I'd love to write an extended blog post on the review process and how to use the package @stefaniebutland.
@maelle
Copy link
Member

@maelle maelle commented Mar 26, 2018

@cimentadaj you couldn't see the repo description "edit" button because you were not an admin yet. Now I've made you admin, and I've added the pkgdown URL in the description at the same time, hope that's ok.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 26, 2018

@maelle yes, that's fine! Thanks.
@nujcharee
Copy link

@nujcharee nujcharee commented Mar 26, 2018

@cimentadaj Hi there yes thats my name Nujcharee Haswell. :)
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 27, 2018

@leeper would you also like to be listed as a reviewer in the CRAN submission?
@stefaniebutland
Copy link

@stefaniebutland stefaniebutland commented Mar 27, 2018

Glad to hear you're interested it writing a post @cimentadaj. Here are some technical and editorial guidelines: https://github.com/ropensci/roweb2#contributing-a-blog-post

We ask that you submit a draft via pull request at least one week before the planned publication date. At this point I have posts scheduled through April so perhaps best for you to suggest a deadline by which you would like to submit a draft.
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Mar 27, 2018

Thanks @stefaniebutland! I could send a pull request the somewhere between the 20th and 30th of April for review where the post would land perfectly for sometime in May. Let me know if this is alright.
@stefaniebutland
Copy link

@stefaniebutland stefaniebutland commented Mar 27, 2018

Sounds good. I will ping you around April 17th to make sure your draft is still on track for submission between 20th and 30th.
@maelle
Copy link
Member

@maelle maelle commented Mar 27, 2018

Closing this now that the package has been onboarded. @leeper can still answer about being listed as "rev" in DESCRIPTION ☺
@maelle maelle closed this Mar 27, 2018
@cimentadaj
Copy link
Author

@cimentadaj cimentadaj commented Apr 3, 2018

Hi @leeper, just a reminder, would you like to be listed a reviewer when I submit the package to CRAN?
@leeper
Copy link
Member

@leeper leeper commented Apr 3, 2018

Sure. Happy to be.
@rufuspollock rufuspollock mentioned this issue Dec 15, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maelle maelle

Labels
6/approved topic:data-access
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
@jimhester @leeper @cimentadaj @maelle @nujcharee @stefaniebutland
You can’t perform that action at this time.