You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created this repo to contain the contents for the main page of r-hyperspec organization's website. When a new package is created in r-hyperspec, the contents of this webpage should be updated with the link to the webpage of that package.
Took a template I'm using for my other project, so It could be changed in the future if you do not like this and want to improve it.
The issues directly related to the contents of the first webpage must go to this repo.
I think, that the issues, that are common for the whole r-hyperspec organization (or at least several packages) and the most appropriate repo for the issues is not obvious, should go to the issues of this repo too.
bryanhanson
changed the title
Place for common r-hyperspec issues & r-hyperspec team
Use this repo for issues common to all r-hyperspec repos & the team
Aug 17, 2020
I created this repo to contain the contents for the main page of
r-hyperspec
organization's website. When a new package is created in r-hyperspec, the contents of this webpage should be updated with the link to the webpage of that package.Took a template I'm using for my other project, so It could be changed in the future if you do not like this and want to improve it.
The issues directly related to the contents of the first webpage must go to this repo.
I think, that the issues, that are common for the whole r-hyperspec organization (or at least several packages) and the most appropriate repo for the issues is not obvious, should go to the issues of this repo too.
I also created @r-hyperspec/r-hyperspec GitHub team (https://github.com/orgs/r-hyperspec/teams/r-hyperspec) to make it easier to reference to all main members who contribute to r-hyperspec and to grant permissions (e.g., write access) to the whole team at once. Currently, the team consists of @cbeleites, @bryanhanson, @ximeg, @eoduniyi, and @GegznaV.
The text was updated successfully, but these errors were encountered: