node-hdb - SAP HANA Database Client for Node
Love GitHub? You’ll enjoy Kerika
Kerika is the only task board that’s designed for distributed teams. Everyone working in the same office. Stop reading. Everyone else grok this. Kerika complements GitHub allowing directions and dialog to flow between distributed teams. Imagine your software designers and go to market teams are in Seattle and your dev team is off shore in India or Pakistan. You’ve already got GitHUb established, but so much more needs to flow with designing before and while crafting into code. What are you going to do stay up all night answering email or chatting on Google talk. Far better than burning the midnight oil use Kerika. Let the team see the collaboration happening and the designers, managers, QA can plug back in after a good nights sleep.
Kerika utilizes Google docs for its native document store and AWS for web services. So reliability is predictable and latency minimal wherever your distributed teams are working from globally.
The usability, HCI and UX in Kerika is superb, lots of attention to details, drag and drop polish as an online consumer application. User experience head and shoulders above common SDLC or project tools. Kerika does all that social collaboration stuff without marketing it as a feature, because its was specifically designed for distributed mobile and enterprise application development.
Pricing is fully functional, all the time. Start free. Move up to Professional ($10/MO). Free to academic and non-profit (I assume means free to open source).
Arun Kumar left Microsoft and took a couple of years to design and build http://kerika.com/ . After his talk at Seattle Google Developers Group and number of us working with distributed teams signed up and enjoy the product flow.
Previous research suggests that the publicity on GitHub that is making developers’ actions and interactions more visible might have an effect on how software development practices are communicated …
Tips for leaders of thriving open source projects
Just by watching how other, more senior project members behave, they learn what a good commit looks like.
Drive-by commits, make this very easy by providing clear guidelines and simple continuous integration frameworks for testing.
Low barriers seems to be very important in getting developers to test their contributions.
BigQuery Dremel analyzing millions of GitHub commits.
To help us extract the insights from the public GitHub timeline which generated hundreds of thousands of daily events, we imported the entire dataset into Google BigQuery. This makes data about tens of millions of open source commits and discussions accessible to the world for quick interactive analysis. With that, we can run our analysis:
Who are the most productive developers using GitHub? Which languages are growing in popularity and why? Which language features result in the most angst and developer pain? What makes open source developers happy?
Inside GitHub. Checkout combination of ‘web 2.0’ polyglot technologies used to cache and bring performance to the user experience.
Always an admirer of icons designed for internationalization.
GitHub describes their process in creating and using a custom
@font-facefor icons throughout the site. Beyond these spiffy new icons, the entire design at GitHub seems to get iterated and improved upon constantly.