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.

Sign up for GitHub

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

Jump to bottom

Contributor Setup #33

Closed
burdged opened this issue Jun 7, 2018 · 0 comments
Closed

Contributor Setup #33

burdged opened this issue Jun 7, 2018 · 0 comments

Comments

@burdged
Copy link
Collaborator

burdged commented Jun 7, 2018

Contributor Setup

For #3 you have:
Repeat this section for each team member, one at a time, including the team member who was initial assigned maintainer.
Suggested change:
Repeat this section for each team member, one at a time, including the team member who was initially assigned the roll of maintainer.
StoneyJackson added a commit that referenced this issue Jun 7, 2018
@StoneyJackson
Fix grammar
5b99215 
Closes #33
@StoneyJackson StoneyJackson mentioned this issue Jun 7, 2018
Merged
11 tasks
StoneyJackson added a commit that referenced this issue Jun 8, 2018
@StoneyJackson
Merge pull request #27 from StoneyJackson/rewrite2
23cd688 
# Version 2.0.0

## Goals

- Avoid unsafe operations (e.g., `git rebase`).
- Introduce some additional best practices (e.g., `git commit -v`; checking what files will be committed before committing, and modifying .gitignore if it's wrong.).
- Reduce the number of different commands required to learn, but possibly require more commands to be issued (e.g., `git branch feature; git checkout feature` instead of `git checkout -b feature`; it might seem like the latter is easier, but then you must know the purpose of -b, and when to leave it off).
- Rely on more external resources for instructions and provide more links to other resources.

## To-do

- [x] Create contributor guide
- [x] Create maintainer guide
- [x] Delete old reference
- [x] Rewrite activity
- [x] Link activity to steps in contributor guide.
- [x] Link activity to steps in maintainer guide.
- [x] Rewrite presentation.pptx
- [x] Update README
- [x] Add license to each file
- [x] Address feedback
- [x] Tag master as v1.0.0

## Issues

- Closes #25 because they are now asked to add a license
- Closes #22 because reflection subsections are added to each section
- Closes #21 because there are now different guides for different roles
- Closes #24 because <MY_URL> and <THEIR_URL> are gone; although folks could still get confused by all caps placeholders even though they are explained at the beginning of the guide.
- Closes #18 because no paths are given
- Closes #20 because I gave a new guess to the time requirements.
- Closes #23 because there are now each section ends with reflection questions which are times for group discussions.
- Closes #31 
- Closes #30 
- Closes #29
- Closes #32
- Closes #33 
- Closes #34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@burdged