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

Brainstorm name of this package #1

Open
lwjohnst86 opened this issue Feb 18, 2022 · 6 comments
Open

Brainstorm name of this package #1

lwjohnst86 opened this issue Feb 18, 2022 · 6 comments

Comments

@lwjohnst86
Copy link
Member

A key to any good package is its name... and its also one of the hardest things to do! Think of some names and use the package and function available::available() to check if that package name already exists.

@Aastedet
Copy link
Collaborator

Aastedet commented Nov 8, 2022

I set up a testing repo for the cite package, working title pubmedciteR:
https://github.com/Aastedet/pubmedciteR

I've cleared the major hurdles I think, and it's probably going to work out with a bit more work, so I should move it to the science-collective repo, right?

@lwjohnst86
Copy link
Member Author

Yea, if you'd like to! It would make it significantly easier for me to contribute

@lwjohnst86
Copy link
Member Author

Also, way to go, looks cool! Only thing we'd have to consider is that CRAN has a max 5 Mb package size. So you might have to get creative in ways to keep file size down.

@Aastedet
Copy link
Collaborator

Aastedet commented Nov 8, 2022

Copied it here as-is, so very raw/exploratory.
A lot of the comments/mind-mapping should probably be GitHub-issues rather than bloating the documents/scripts, but there's a time for that later.
Also, the package-name can be whatever, I just picked something descriptive that contained a capital R (and was available). Can you rename a repo at some point, or how does that work?
Edit: That kind of relates to the starter post. I guess we'll end up working towards more than one package in separate repos inside /science-collective/.
Feel free to clean up my GitHub-ignorant mess as you see fit by the way - I have a very loose idea of what can/should be done here 😄

@lwjohnst86
Copy link
Member Author

Yes we totally can rename the package. Alternatively, you can transfer ownership of the repository to here (go to settings, scroll down, in the Danger Zone area). I can give you access to do that on science-collective.

@Aastedet
Copy link
Collaborator

Aastedet commented Nov 9, 2022

I figured there had to be a smarter way than copy/paste 😄
Now this repo is ahead of mine by a few minor edits, so let's just continue here (and maybe set up a new template repo for others to build other packages on).
For now I'm putting it on the backburner until december, when hopefully I have more time again. You and I could perhaps sit down and discuss it some time later.

Maybe we should also schedule a meeting in the group in january/february to keep everyone updated on what's been going on in the last year?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants