I'm new to Tidepool and wanted to learn more about the current state of discussion from the IRC channel. Looks like there's no bot to record history though. Also, when I log back in after an absence, I will have missed the interim discussions (unless I set up a bouncer such as ZNC on a VPS, which is overkill for many users).

Gitter is a modern and very popular free chat system for open-source GitHub projects, with full history tracking and search, support for Markdown, pasting images from clipboard (great for screenshots). Many JavaScript projects use it - https://gitter.im/explore/tags/javascript. It has native Mac/Linux/Windows apps and an IRC bridge as well, so it shouldn't pose any migration problem. Gitter also integrates with Trello and Travis CI.

I cannot scroll the nav bad on the left side of the component list which means that if I'm stuck on a small screen, I can't actually see the whole thing.

Right now, the component data is all in this repository. That's basically a duplication. If we can distribute that in a way that allows some task to automatically update this documentation site (Travis, perhaps) it might be worth it. But this is a someday task, not urgent.

I just left it out.

I'm putting things here as I discover them, so I don't forget.

Resources we can use to update this documentation:

• https://github.com/tidepool-org/hydrophone/blob/master/api/hydrophoneApi.go
• https://github.com/tidepool-org/platform-client/blob/master/index.js

Updates needed:

• Match all URLs formats with the ones implemented
• Accepting and dismissing an invitation requires a body with a {key: <invitationKey>} payload
• Switch invitedBy to creatorId

In " tidepool-org.github.io/_docs/platform-roadmap.md", line 32:
Items marked with @@ are lower priority given our current company priorities. Some of these (at least the ones not tied to Tidepool's deployment) might be good candidates for third party contributors to consider working on, as it's less likely that Tidepool's developers will be working on them soon. These items are marked with @@3.

What does 'These' refer to? Are items marked with @@3 ones that Tidepool devs are likely already doing?

Hi there,

I've had some trouble getting everything up and running on my local machine due to my MongoDB setup not working as expected. Blip runs but shows a Blip is stuck and isn't doing what you want it to do. We're sorry for the trouble. Blip will attempts to send the details to our server error when setting up a new user.

While get_current_tidepool_repos.sh does a good job if checking if all the prerequisites are installed, there are some additional setup instructions for a new MongoDB installation that could be included as part of the Getting Started manual?

Basically, after you've installed MongoDB with brew install mongodb, you still need to do the following:

• Run sudo mkdir -p /data/db
• Set permissions for /data/db to local user using sudo chown <your username> /data/db

Navigating back to the 'Basics' tab in the blip web interface can cause the site to log you out, putting you back at a login screen.

Reproduction:

1. Populate an account with cgm data (no pump data or finger sticks)
2. Log in, navigate to the Weekly or Trends tabs. (I have not checked 'remember me', I could see that causing some confusion here or making the bug irreproducible.)
3. Click on 'Basics'.

After clicking on 'Basics' you are immediately returned to the login screen.

Step (1) may be a red herring; I still need to upload some data from my pump -- I should be able to do that later today and report back. Edit for clarity: Step (1) is necessary to reproduce the problem.

We have a bunch of user stories -- organize them and aggregate them into a page.

Similar to tidepool-org/blip#216

It was hand-coded quickly as CSS only; probably need to figure out how to use a more responsive system for this.

There are a few enhancements I'd like to bring to this repo, but this one (if accepted) is more urgent as it gets harder to do later on...

Basically, instead of having URLs like:

• http://tidepool-org.github.io/TidepoolComponents.html
• http://tidepool-org.github.io/data-model/v1.html
• http://tidepool-org.github.io/TidepoolVCLA.pdf

You would have URLs like:

• http://tidepool-org.github.io/tidepool-components
• http://tidepool-org.github.io/data-model/v1
• http://tidepool-org.github.io/tidepool-vcla.pdf

(Notice that everything is lower-case-hyphens and there is no .html extension.)

This is just something I see as pretty standard around the web. Jekyll provides something to generate these easily. Hardest part will be checking all links we already have and updating them, but I don't mind doing it.

@kentquirk thoughts?

On the page http://tidepool-org.github.io/TidepoolComponents.html, the second big heading is for the "Application Server" and contains one repository, "Blip Data API." This repository appears to not exist any more, and the link to https://github.com/tidepool-org/blip-data-api is broken.

tidepool-org/central#77

At http://developer.tidepool.io/platform-roadmap/:

Our very aggressive goal is to submit the appropriate application to the FDA by the end of 2014.

I tried to add the tidepool favicon and it doesn't seem to have worked. No time to figure it out right now.

Under "Your Applications" in https://github.com/tidepool-org/tidepool-org.github.io/blob/master/index.md#getting-started-as-a-contributor, it says that Tidepool Mobile will replace Blip Notes. It says it's under development in the Nutshell repo, but the Nutshell repo says
"[DEPRECATED] refer to https://github.com/tidepool-org/mobile-ios".

Where is development of the Android replacement happening, and could this be made more clear?

I'm trying to build tidepool from the documentation at http://developer.tidepool.io/starting-up-services/.
I get 3 failures.

During the tools folder get_current_tidepool_repos.sh, I get an error about the versions of node and npm;
During the . tools/runservers I get errors building Blip about packages not found and a legacy binary of node.

This is my 3rd unsuccessful attempt to build Tidepool in a VM. I've found a few things along the way (like npm proxy settings need to be done with the -g flag), but I'm stumped at this point. The last time I got to a set of Blip build errors, I seemed to find myself hand-installing a set of npm dependencies that seemed more and more incorrect, with no success.

Originally I tried installing nodejs instead of nodejs-legacy, which generated other failures about not being able to find node. I went with nodejs-legacy after reading notes about how that package is meant to deal with name issues on Debian systems such as Ubuntu (that on Debian, node is named nodejs).

Any idea what I'm doing wrong? Below are the error messages, and a list of the steps I've done so far. Note: I'm a total newbie on many of the technologies (node, go, npm), so I may be making some newbie mistake.

Thanks,
Brad Needham
Intel Corporation
---------------- errors from running get_current_tidepool_repos.sh
https://registry.npmjs.org/tideline/-/tideline-0.1.22.tgz
npm ERR! 404 'blip-mock-data' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Linux 3.16.0-40-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/brad/Documents/tidepool/blip
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! code E404
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/brad/Documents/tidepool/blip/npm-debug.log
npm ERR! not ok code 0

---------- errors from . tools/runservers
Building Blip...

module.js:340
throw err;
^
Error: Cannot find module 'shelljs/global'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/brad/Documents/tidepool/blip/buildapp.js:2:1)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
npm ERR! weird error 8
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! not ok code 0
npm ERR! weird error 1
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! not ok code 0
Starting blip
Started blip, pid 15107

module.js:340
throw err;
^
Error: Cannot find module 'connect'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/brad/Documents/tidepool/blip/server.js:4:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
[13]+ Exit 8 node $2 2>&1 >> ../server.log
------------------------------ my script for creating the vm and installing Tidepool on it.
Create a VM

1. Download the Ubuntu 14.04 64-bit desktop .iso file:
   o Browse to http://www.ubuntu.com/download/desktop
   o Select the 64-bit version and click Download.
2. Use VirtualBox (or another VM manager) to create a VM with 2GB Ram, 20GB disk, and 64-bit Ubuntu 14.04 installed.
3. Start that VM
4. Select the downloaded Ubuntu .iso file to boot from.
5. Wait for ubuntu to start.
6. Click Install Ubuntu
7. Select “install this third-party software”, but do not select “Download updates while installing”, because the proxy isn’t set up yet.
8. Continue through the rest of the setup.
9. Once it stops, waiting, press Enter (it’s waiting for you to “remove” the install disk.
   o Once the VM is restarted and up…
10. (VirtualBox only) In the VM border select Devices / Insert guest additions CD image…. This will enable your VM screen to enlarge to something useful. Without this, you won’t be able to set the proxy, or do many other things, because the icons would be off-screen.
11. When “Press return to close this window” appears, press Enter
12. Scroll down to on the left menu bar to the CD icon, right click on it, and select Eject.
13. Try to resize the window by dragging the corner. If the Ubuntu window doesn’t resize, reboot the VM and try again.
14. Set the proxies:
    o In the system menu (top-right gear icon), select System Settings…
    o In the resultant window, click on Network.
    o Click Network proxy
    o Select Method: Manual and fill in the following proxies:
     HTTP: proxy-jf-intel.com port 911
     HTTPS same as HTTP
     FTP same as HTTP
     Socks Host – leave blank for now. XXX find our Socks5 proxy.
    o Click Apply system wide
    o Test by opening Firefox: it should show Google.
15. (VirtualBox only) Turn on VM Client copy/past with the host: select Devices /shared clipboard / bidirectional XXXX that doesn’t seem to work; at least trying to paste into Terminal or Libre Office doesn’t. Wound up using a USB drive to transfer files between host and the VM.
16. Because you will need it often, pin a terminal session to the left bar:
    o Click the “search your computer…” icon – the top icon in the left bar
    o Type terminal
    o Drag the resulting Terminal icon to the left bar
17. Update the Ubuntu software
    o Click the “search your computer…” icon – the top icon in the left bar
    o Type Software Updater
    o Click on the resulting A-in-a-circle Icon, labeled Software Updater.
    o When it offers updates, Click Install Now
    o Wait for the update to complete
    o Restart as requested.
    o In a terminal window, type sudo apt-get update (this updates the package manager’s idea of what packages are where).

Install the Tidepool prerequisites

1. Git. In a terminal, type sudo apt-get install git
2. (skip for now – haven’t found where it’s needed) Mercurial. In a terminal, type sudo apt-get install mercurial
3. Bazaar. In a terminal, type sudo apt-get install bzr
4. Node. Open a Terminal. Type sudo apt-get install nodejs-legacy (“legacy” because Ubuntu installs NodeJs under a name other than the standard name, “node”. This package is supposed to fix that issue.)
5. Npm. A Javascript (Node) package manager. In a terminal, type sudo apt-get install npm
   a. Configure the npm proxy See http://jjasonclark.com/how-to-setup-node-behind-web-proxy/. Type in a terminal:
   i. sudo npm config set –g proxy http://proxy-jf.intel.com:911
   ii. sudo npm config set –g https-proxy http://proxy-jf.intel.com:911
6. Gulp. A streaming build system: sudo npm install --global gulp
7. Mocha, a testing framework. Open a terminal. Type sudo npm install –g mocha
8. Mongod. The Mongo DB server (daemon). With one exception, follow the instructions at http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/#install-mongodb
   • Exception: The first command needs the proxy argument: --keyserver-options http-proxy=http://proxy-jf.intel.com:911
9. The Go language. In a terminal window, type sudo apt-get install golang
   Pull the source
10. Open a terminal window
11. Create a home directory for the source and cd to it
12. git clone https://github.com/tidepool-org/tools.git (from https://github.com/tidepool-org/tools)
13. cd into the resultant tools folder and type: ./get_current_tidepool_repos.sh >~/tidelog 2>&1
14. Wait a few minutes until the command completes, then look for errors in the log file (~/tidelog)
    a. Got npm ERR! ‘blip-mock-data’ is not in the npm registry. You should but the autor to publish it.
    b. Got npm ERR! Node –v v0.10.25; npm ERR! Npm –v 1.3.10
    i. Additional logging details can be found in: tidepool/blip/npm-debug.log
    Start the server the first time
15. In a terminal window,
    a. Cd to the folder you created for the Git repos.
    b. type (without quotes) “. tools/runservers >mylog.log 2>&1”
16. The first run performs a lot of installation, taking about 10 minutes.
    a. Building Blip failed.
    i. Got an error about missing 'shelljs/global'. The last time I went down this path, I got to a webpack module that seemed to want to be installed both locally and globally.