I surmise part of the reason they did this is to protect revenue from "authorized" partners. I'm sure these partners are not happy paying money to Chamberlain so their customers have access to myQ while other unauthorized partners get free access.
We build “You Need a Budget” the best budgeting software around. (But people in the know call us YNAB, which is pronounced “why-nab”). For more than a decade, people have been buying YNAB and then telling their friends what a difference it has made in their lives. Google us, or read some of our reviews on the app store, and you’ll see what we mean. We love building something that has a huge positive impact on people’s lives.
You’re a Full Stack developer with at least 5 years of experience shipping, monitoring, and maintaining SaaS apps at scale (not just websites). You’re an expert in at least one modern server-side framework (Rails, ASP.NET, Express, Django, etc).
You’re not necessarily the “Ops” person where you work, but you certainly understand the infrastructure well enough to aid in architecting and maintaining scalable solutions. We host on Heroku, so experience there is a bonus, but experience with AWS or other popular IAAS/PAAS is just fine.
Some client-side experience is required as well, meaning you know enough HTML/CSS/some-client-side-framework to get stuff on the screen matching a designer’s spec. We work in small, cross-functional teams where you will likely find yourself responsible for implementation on both the back-end (Rails and Postgres), as well as the front-end (using Ember or Vue and written in TypeScript).
You’ll help vet and improve our server-side layer, implement new features, integrate with third party API’s, and shepherd our application.
You Need a Budget (YNAB) | Full Stack Developer | Remote
At YNAB, we build the world’s best budgeting software. But we’re even prouder of teaching people how to align their money and their priorities, and in turn changing their lives.
Our web app is cutting edge. Our API, written in Rails/PostgreSQL, takes care of the hard stuff, like synchronizing data between offline-able clients. Our client apps use a TypeScript library we developed that makes talking to our API a piece of cake. You’d be helping us develop and maintain the server-side of things.
When we say Full Stack, we mean that you’re a programmer at heart, are comfortable at various levels of the web stack.
This is a pattern I've seen in teams to enforce review of code before it's merged. You can make the main repo read-only for most of the team and require PRs be submitted from their own forks. Then, someone with write access on main repo can review and merge the PR. I think this is overkill, personally, but just want to point out that maybe this team was employing this process, rather than them not knowing how to create PRs from a branch.