Skip to content
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

Increase the visibility of the pkg #32

Open
2 of 4 tasks
BatoolMM opened this issue Dec 20, 2023 · 4 comments
Open
2 of 4 tasks

Increase the visibility of the pkg #32

BatoolMM opened this issue Dec 20, 2023 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement Feature improvement or addition pause Pause progress on this for now

Comments

@BatoolMM
Copy link
Member

BatoolMM commented Dec 20, 2023

In order to increase the visibility of the pkg, after making it citable, we can do the following:

  • Add a CFF file
  • Linking the repo with Zenodo to produce DOI referenced in the README
  • Featuring it in the RWeekly newsletter and AIM Newsletter
  • (Maybe) Submitting it to rOpenSci
@BatoolMM BatoolMM self-assigned this Dec 20, 2023
@BatoolMM BatoolMM mentioned this issue Dec 20, 2023
3 tasks
@BatoolMM BatoolMM added enhancement Feature improvement or addition documentation Improvements or additions to documentation labels Dec 24, 2023
@RayStick RayStick added the pause Pause progress on this for now label Apr 4, 2024
@RayStick
Copy link
Member

@BatoolMM from recent discussions, I like the idea of trying to submit it to rOpenSci

It seems that there is scope to then go on to consider JOSS - I need to read the guidelines on that

@BatoolMM
Copy link
Member Author

Yes, let's do that!

@BatoolMM
Copy link
Member Author

I will create a new issue for rOpenSci Submission - when do you want me to start the submission?

@RayStick
Copy link
Member

RayStick commented May 31, 2024

I will create a new issue for rOpenSci Submission - when do you want me to start the submission?

Thank you for the help! I think I need to start by reviewing their guidelines to check that the code, docs and general structure of the package matches their guidelines/rules, and take it from there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement Feature improvement or addition pause Pause progress on this for now
Projects
None yet
Development

No branches or pull requests

2 participants