-
Notifications
You must be signed in to change notification settings - Fork 21
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
R Core developers #14
Conversation
rebasing main branch
rebase main branch with forwards/rdevguide main branch
rebase core-developers branch with forwards/rdevguide master branch
The chapter number will be provided later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good ☀️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
☀️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would separate current and previous R core members but perhaps because I'm more used to the Contributors site.
It would be nice to have some breakdown of areas of R code they are involved with and topics outside R code each member is involved.
A small list of R cores activities outside changing R code are:
- CRAN
- bugzilla
- svn servers
- websites
- R journal
- Blog
- others?
-- Have included the names of Core developers (former and current) in alphabetical order. -- I am not sure if we want to explicitly state the expertise/role of each member. |
However, let us see what other suggestions are made on this topic. |
We've left it up to the individual core developers to list areas of expertise (or things they are willing to maintain) if they wish. |
I agree that they are the best to write this, but I think an "educated guess" can be done and start filling some members and some areas. This will help the R core members to fill and correct the remaining details. Otherwise it is unclear how R core works making it harder getting involved for some R users. An example: for something about bugzilla I got in touch with a generic email, later I hear back from the R core that 3 people were interested/had concerns about what I was trying to do. We exchanged 5 emails with them (only one of them replied), but until I specifically emailed one member on the exchange and exchanged another 5 emails the matter wasn't resolved. I appreciate all the time and interest my question raised but sincerely I'd hoped that I hadn't even need to bother the R core for my request. If there is a way to know who to direct some requests when the community can't provide help, we, normal uninformed users, will bother less other R core members (making it easier for all). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change hypertext to be more informative and accessible.
rebase lifecycle-patch branch with forwards/rdevguide main branch
This chapter provides info about the people involved in the development of R Core.