Looks like you can export any board as JSON by going to Board Menu > More > Print and Export (from http://help.trello.com/article/747-exporting-data-from-trell...).

There's also a Chrome extension to export a board to a spreadsheet: https://chrome.google.com/webstore/detail/export-for-trello/....

Great feedback. Thanks for sharing.

Also, FTR there is no intent to boast here, merely sharing an idea and trying to elicit discussion about a problem which I admittedly do not fully understand.

I had hoped that starting with an admission of plausible fallacy would deter such judgements, but I guess you never can underestimate the power of HN to bring out the moral superiority of others.

Git has a very scalable solution for a large volume of changes and establishing change set as current (via SHA). What is different about the DNS registry than any other codebase that Git could not handle?

HospitalRun (http://hospitalrun.io/)

HospitalRun is an offline first, Ember based, Hospital Information System for charitable hospitals in developing countries.

> What do you hope to build this month? We are focused on ongoing work toward reaching the 1.0. For a list of outstanding issues, see this GitHub milestone on the frontend app: https://github.com/hospitalrun/hospitalrun-frontend/mileston...

We're in need of folks with the following skills: Ember JS experience for general app development; internationalization and localization; New Relic instrumentation experience; automating deployments from GitHub; HL7 experience; product and UI design for lots of CSS and UI cleanup (https://github.com/hospitalRun/design); design systems experience for working on a styleguide and pattern library; docs writing for app documentation; web and marketing design for the hospitalrun.io site (http://github.com/hospitalRun/hospitalrun.github.io)

To contribute, check out our CONTRIBUTING.md file on GitHub (https://github.com/hospitalrun/hospitalrun-frontend/blob/mas...) and join our Slack team.

HospitalRun is open source under the GNU general public license.

That looks very interesting. I used to work as a paramedic and I'm currently working for a client that offers EMR systems so I know a bit about the challenges in that industry (albeit from a first-world point of view).

Anyway, I joined your Slack channel.

HospitalRun loads really fast; I'm impressed.

Thanks! The demo has a relatively small data set, but keeping it fast as production data grows is one of the challenges we're working on right now.

Are you using FastBoot?

This project is non-profit correct? Wondering if any of the engineers on it are being compensated.

hey, the milestone and contributing.md links are broken.

Thanks for the heads up!!

joined the slack group, looks interesting

Very unlikely. We hope that Projects will be the best place for people to coordinate work on a GitHub repository, but that doesn't really limit Trello's value much. They'll continue to offer lots of value as a great way to coordinate work for many contexts outside GitHub repositories.

This all applies to github.com the website, and will ship separately in upcoming Enterprise releases per our normal Enterprise release schedule.

What is the Enterprise release schedule, is that available somewhere to view?

Great idea. Thanks!

While I have your attention. A few thoughts on code reviews. It's be nice if 1) approvals somehow show up on the pull requests index page, 2) create a notification within GH, 3) send an email. Right now you have to go to the PR page itself to see approvals.

Edit: I saw an approval email notification on one PR, but not another.

Thanks!

+1 for seeing approvals visually on the pull request index page. I currently use a "Reviewed" label with my team, and unfortunately we still have to even with this feature.

All reviews definitely generate notifications.

We definitely want to get some way to surface reviews better across all PR's and/or projects. I've been bothered by that myself while we were building this. :)

>projects. replaces trello, waffle.io, zenhub and many other similar services.

This is really not about replacing those services, it's more about building a better foundation for integrators like Waffle and ZenHub to build on.

At ZenHub, we have already starting working on some integrations with this functionality which you can read more about here - https://www.zenhub.com/blog/dispatches-from-github-universe/

Our focus is going to remain on how to integrate a full-featured project management suite within the GitHub eco-system. The GitHub projects release will make a great foundation, and ZenHub will be there to provide the more advanced features like issue hierarchy (epics), time estimation and reporting. Lots of exciting releases coming soon for ZenHub users :)

At Waffle.io, we're all about making project management better for engineers. We believe it's awesome that GitHub is investing in this too, and we'll continue to make GitHub delicious :). More here: http://blog.waffle.io/say-hello-to-wafflebot/

I'm looking at https://www.zenhub.com/product, and while it does have some extra features (filters on priority, labels), but for most people the base set provided by github is gonna be sufficient.

Sure, it won't completely replace them, but GitHub building this as a platform counts as competition.

Using ZenHub also provides additional features like time estimation, burndown charts and Epics (for issue hierarchy) - we find that for larger teams, these are must-have features to work inside GitHub.

Founder of Zube here. GitHub Projects seems like a nice solution for very small teams, side projects and open source projects. However, serious teams need more powerful features like a well thought out workflow, support for multiple repos and burndown charts.

Shameless plug: Zube has all these things and more - https://zube.io :)

Except all those services have already built a foundation ...

This will inevitably force out GH's integration partners once users start to complain how feature-deficient projects are in their current state.

HospitalRun (http://hospitalrun.io/)

HospitalRun is an offline first, Ember based, Hospital Information System for charitable hospitals in developing countries.

> What do you hope to build this month? We are focused on ongoing work toward reaching the 1.0. For a list of outstanding issues, see this GitHub milestone on the frontend app: https://github.com/HospitalRun/hospitalrun-frontend/mileston...

We're in need of folks with the following skills: Ember JS experience for general app development; internationalization and localization; New Relic instrumentation experience; automating deployments from GitHub; HL7 experience; product and UI design for lots of CSS and UI cleanup (https://github.com/hospitalRun/design); design systems experience for working on a styleguide and pattern library; docs writing for app documentation; web and marketing design for the hospitalrun.io site (http://github.com/hospitalRun/hospitalrun.github.io)

To contribute, check out our CONTRIBUTING.md file on GitHub (https://github.com/hospitalrun/hospitalrun-frontend/blob/mas...) and join our Slack team.

HospitalRun is open source under the GNU general public license.

NOTE: We are hosting a two day hackathon at GitHub HQ in San Francisco on September 23 & 24th. Apply here if you are interested to join us: https://docs.google.com/forms/d/e/1FAIpQLScY8IzsHNXuSnwJamdO...

Interesting project. Any sub-Saharan African countries using this?

Yes. Several of the CURE International (https://cure.org/) charitable hospitals (including a few in sub-saharan Africa) are already running it.