…responsive email framework. And it's certainly been a busy month: After four patch releases, 30 closed GitHub issues, seven accepted pull requests, almost 3,000 stars and a surprisingly friendly hacker news thread later, we've learned a lot of lessons from the launch.
1. Test on Real Hardware
Even though we did a lot of testing with Litmus prior to launch, not every problem can be caught by a screen-capture tool. When we first launched, we had buttons that looked brilliant on almost …
…yourself something fancy. No sweat. But if your application is more likeor Github or the majority of applications on the web that are proud of their document-based roots, then you really should embrace SJR with open arms.
…the likelyhood of useful community contributions. With nearly 600 forks on GitHub, clean code is of paramount importance to the buildpack's future success and adoption. The new buildpack has a lighter footprint, fewer dependencies, and lots of comments .
About 3 months ago, we announced the beta version of the buildpack on the new Heroku Discussion Forum , asking node developers to try the new buildpack and give feedback. The forum …
… bundle_cache and travis_bundle_cache , implement the pattern of caching the results of bundle install to . However, both projects depend on the aws-sdk library, which in turn depends on and libraries that have native extensions to be compiled. As a result, installing the library that is supposed to speed up your build time is still slow , and this is unnacceptable.build preparation on . Two projects on GitHub,
…here's what you should do if you need help or would like to contribute:
If you need help , use Stack Overflow .
If you found a bug , use GitHub issues.
If you have an idea , use GitHub issues.
If you'd like to ask a general question , use GitHub issues.
If you want to contribute , submit a pull request.
We're looking forward to your questions on. We'll see you there!
…its own setup process and may slow down the development. We're using Boxen from GitHub to solve this problem. It works very well and allows us to have a project environment quickly set up.
But recently we have run into a problem that Boxen couldn't solve. We had a project which has multiple repositories and some of them are too large. It would take some time just to git clone their > 3GB size repos.
Our first thought was creating a tar file with gzip or lzma compression. …
…back to the canonical source code started to wane. This isn't simply altruistic behavior, though GitHub definitely encourages altruism through gamification . Contributing changes back means that the forker no longer has to maintain their own copy of the code. They can merely depend on the upstream project owner to maintain the software, with their fixes, and consume that software as an off-the-shelf component.
These are some of the reasons we encourage our customers — startups …
…future. While there are some user-visible actions that it's okay to offload to workers - forking GitHub repos, for example, happens in a worker - generally you want to keep actions that the user specifically requests in the request/response loop.
Message queues are the bonds that tie distributed …
…fans to use the forum to ask and answer questions regarding responsive design and Foundation. Unlike GitHub, the Forum is your place to start a dialog with the community. We wanted to give our fans an avenue to ask open-ended questions about a variety of topics, from design questions, installation issues, to the proper implementation of Foundation code. You can get answers from other avid users.
Using the Forum
Foundation Forum makes it easy to describe your problem using code, images, …
…introduces a lot of new interesting features that are even more compelling in the PXC/Galera world. If you want to experiment for yourself, I pushed the Vagrant environment I used to Github at: https://github.com/jayjanssen/pxc_56_features