olpeh / meeting-price-calculator Goto Github PK

View Code? Open in Web Editor NEW

17.0 3.0 1.0 1.42 MB

Meeting Price Calculator - How expensive are meetings, really?

Home Page: https://mpc.olpe.fi/

License: MIT License

HTML 0.55% JavaScript 7.15% TypeScript 89.20% CSS 0.44% Shell 2.67%

cyclejs productivity productivity-hacks

meeting-price-calculator's Introduction

meeting-price-calculator

What?

A timer for estimating how much a meeting has cost. Simply calculating the amount of people times the average hourly rate times duration.

Why?

Because sometimes meetings are held just because having meetings is what we do. But really, this was built mainly for fun and for learning Cycle.js. Haven't really used this during any real meetings yet.

How is it built?

The project is using the following tools and technologies:

Create Cycle App as the base boilerplate
Cycle.js as the core, in addition to the following:
- @cycle/dom
- @cycle/http
- @cycle/isolate
- @cycle/run
- @cycle/storage
- @cycle/time
- cycle-onionify
- cycle-storageify
xstream as a stream library
TypeScript
Prettier for automatic code formatting
TypeStyle for CSS-in-JS
Jest for testing
HTML Looks Like for testing that the views look about right
jsverify for property based testing
Moment for date and duration formatting

Development

Install dependencies: yarn or npm install
Run tests: npm test
Run dev build: npm start

Contributing

Found a bug or have an idea? Please add an issue
PRs are welcome

License

MIT

Acknowledgements

This project is sponsored by Futurice's Open Source Sponsorship program

meeting-price-calculator's People

Contributors

Stargazers

Watchers

Forkers

bahmutov

meeting-price-calculator's Issues

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴