This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
Note the Sprint Planning format #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We've had pretty good success with the Sprint Planning format suggested in ipfs/community#28 so this commit adds a rough description of it to this repo. Note: the sprint discussion times are quite late for people in GMT+2 to join. I suggest we move up the discussion up by 2 hours for the future (next week). I'll poll the group today and see what is best for everyone.
|
To be clear, the times for this week are the same as last week. |
jbenet
added a commit
that referenced
this pull request
Jun 22, 2015
Note the Sprint Planning format
|
up means back? 17:00? |
|
@krl yeah 17:00 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've had pretty good success with the Sprint Planning format
suggested in ipfs/community#28 so this
commit adds a rough description of it to this repo.
Note: move sprint planning up by 2hrs?
The sprint discussion times are quite late for people in
GMT+2 to join. I suggest we move up the discussion up by 2 hours
for the future (following week, not this one). I'll poll the group today
and see what is best for everyone.