process, organization stuff

[bewest]

Howdy, I plan on mentioning chrome-uploader in our ongoing work with the FDA.
We're working on a joint set of documents to describe to potential contributors, and group members, how we work on code, and how we like to get feedback on issues and feature requests.

Most of the projects are using git flow, using topical branches to create discussion in pull requests. For cgm-remote-monitor, we also tag releases. I wanted to touch base and ask some questions about how certain things happen with the chrome-uploader.

For example, are updates tracked, are their any usage stats?

[altintx]

Describes the way things are. Changes always possible:

are updates tracked

Chrome auto-updates users with no facility I'm aware of to opt out.

are their any usage stats

I haven't set up Google Analytics, so all I've got are "users within the last week", "downloads on a particular day" and "impressions on a particular day." Those are each metrics the store UI exposes.

I've started tagging releases but its hardly complete. Could probably work it out retroactively with git log | grep "version bump".

Branches and issues for bigger things but not for everything.