Spring cleanup and restructure - dana-dev to dev #114
Merged
Conversation
This file contains hidden or 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
Dev Merging sphinx into master to transition away from gitbook
Fixing from broken links - dev - prepping link fixes
This doesn't need to be in the repo.
no longer needed since no more gitbooks
May not be needed (if top level, that's fine). but if a page needed to create this subdir, this content should be updated with links
Includes note about what you won't see in the guide. This could be fleshed out more by others.
Add note about advocacy language; could be fleshed out more with examples, Ben's tool, etc.
Added note about avoiding sharing pump serial; added other gitter channels; added omniaps slack link
general content update. need to add link about first-PR
minor formatting tweaks
need to come back and add link to "your first PR"
adding note about making PRs and linking to list page. need to fix link later.
note about this being google-able
simplify; some stuff will get moved to phase 2
… source/docs/walkthrough/phase-1/visualization.md add why; move to phase 1
add note about setup script; link needs to be fixed though and maybe there's a better source?
…docs/walkthrough/phase-2/using-openaps-tools.md moved to phase 2; tweak title
making note about reviewing data, this could be added to in more detail later though
…e-basal.md to source/docs/walkthrough/phase-3/Understand-determine-basal.md making part of phase 3; notes about using this to decide max basal
renaming and needs to be reordered in the documentation flow
pulling out error checking to be separate
moving error checking here to it's own page
update to match new flow
…to source/docs/walkthrough/phase-4/troubleshooting-loop.md move to 4
Wip guides included
may need a better way to link to/reference guide, but just linking for now.
removing gitbook reference
formatting tweak
Contributor
|
#91 is ready to go |
Contributor
Author
|
For easier view of what the new structure looks like, you can look at the On Wednesday, March 30, 2016, CrushingT1D notifications@github.com wrote:
Dana Lewis | http://www.twitter.com/danamlewis | |
Contributor
|
👍 to merge to dev. This is definitely better than what we have now. |
Somehow #111 clobbered clean mergability. Conflicts: docs/docs/walkthrough/phase-0/index.rst docs/index.rst
Member
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this includes:
Also includes:
After this is merged:
Asking open PRs left (#91; #92; #93; #94; #95 ) to re-review their work and see if they need to update anything to re-target dev after this big one is merged.
Feel free to make any notes here in the thread about things you'd like to see adjusted, but please specify whether they're adjustments that can be made after the merge to dev so we can track those things but not necessarily hold up the merge. Ideally, this is better than dev as-is and we can make more changes in dev before submitting as a PR to master in another week or two. Give it a thumbs up when you're ready to support merging to dev.