Branch |GitHub Actions |
---------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------
master
| |
develop
||
alexine
||
claudio
||
frans
| |
geert
| |
richel
| |
willy
| |
master
, develop
, then topic branches alphabeticallyThe informalr
R team!
Add project description...
Ordered alphabetically on first name:
Name |Role
---------------------------------------------|-----------------
Alexine |Junior
Claudio |Medior
Frans |Junior
Geert |Junior
Jan |Teaches git
to newbies
Richel|Team leader
Willy |Medior
What | Time -------------------------|------ Doors open |18:00 Work starts [1] |18:15 Break time! |19:00 Work continues |19:15 Done! |20:00
develop
to your branch, then push your branchFor those that prefer online, we use Discord to chat.
To join, send Richel a Discord Friend Request: richelbilderbeek#9002
.
He'll add you to the informalr
server.
See CODE_OF_CONDUCT.md.
In case it is undesirable to email Richel, contact Willy.
:warning: these are only the current ideas; this is not set in stone :warning:
General ideas:
Function argument names:
action
: an action, which always has an action_type
actions
: zero, one or more actionsaction_type
: a type of action, e.g. "player_move_left"
game
: logical state of the gamegame_display
: the visualization of the game, e.g. by a Shiny app#' Do actions on a game
#' @return a game in its new state
do_actions <- function(game, actions)
# Play the game
play_game <- function() {
# Run the visualization
}
informalr
?To learn how to develop professionally in a team in an informal setting using R.
That we follow the literature, which means we will:
git
for version control, where each person has his/her own branchlintr
to check for stylecovr
to check for code coveragegoodpractice
for miscellaneous good practicesSee, for example, here for multiple videos we will follow.
That we work together. A beginner will be taught by a more experienced team member. We will be doing pair programming.
This means that:
By working on projects as a team. In practice, we will be writing packages.
First, we'll write some trivial packages to get used to the workflow. After this, the team decides on a project by majority vote.
To be precise, you will learn, in this order:
git
minimal workflow: add, clone, commit, pull, pushgit
branching: checkout, mergeThere is none.
richelbilderbeek#9002
, so he can add you to the tresinformal Discord groupinformalr
teamNote: if the Issue is closed, re-open it, assign yourself, move the Issue to 'In Progress'. Close the Issue after fixing it. Welcome to our workflow :+1:
Golden rules:
You start out as a junior and gradually move up to medior.
Do some simple Issues to get to know the project. These are labeled 'Good First Issue'. These Issues have a test that needs to be fixed.
If there are no such Issues, create an Issue for richelbilderbeek
to add these :+1:
Add here some related project...
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.