###The ROSSConf project, or: helping Open Source help Open Source
Last April Saturday ROSSConf Vienna took place. Sixty registered participants, some loose canons, 5 projects, 6 maintainers, 8-ish team members, 1 baby all in one coworking space. Here's what happened.
####In the beginning October last year, at arrrrcamp, I came up with the concept for ROSSConf. Having attended 1001 tech conferences (I haven't kept count) I concluded that I'm always missing something. I found myself listening to a talk and wishing I could contribute to the project discussed but the internet connection wasn't sufficient for cloning the repo, nor was there time to hack on the project as the next talk was about to start. And, I figured, I'd need some time to get into the project and the contributing etiquette before being able to contribute.
I've been looking for the best Linux backup system, and also reading lots of HN comments.
Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.
Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.
I've been looking for the best Linux backup system, and also reading lots of HN comments.
Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.
Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.
| osascript -e 'tell application "Finder" to eject (every disk whose ejectable is true)' |
##mailinglists
##list of speakers
For ETS's SKLL project, we found out the hard way that Travis-CI's support for numpy and scipy is pretty abysmal. There are pre-installed versions of numpy for some versions of Python, but those are seriously out of date, and scipy is not there are at all. The two most popular approaches for working around this are to (1) build everything from scratch, or (2) use apt-get to install more recent (but still out of date) versions of numpy and scipy. Both of these approaches lead to longer build times, and with the second approach, you still don't have the most recent versions of anything. To circumvent these issues, we've switched to using Miniconda (Anaconda's lightweight cousin) to install everything.
A template for installing a simple Python package that relies on numpy and scipy using Miniconda is provided below. Since it's a common s
| ## How to Use: | |
| from radar import radar_graph | |
| labels = ['v1', 'v2', 'v3', 'v4', 'v5', 'v6', 'v7', 'v8', 'v9'] | |
| values = [1, 1, 2, 7, 4, 0, 3, 10, 6] | |
| optimum = [5, 3, 2, 4, 5, 7, 5, 8, 5] | |
| radar_graph(labels, values, optimum) |
