HNHacker News
TopNewBestAskShowJobs

sandal

723 karma · joined August 3, 2008

submissionscomments
sandal··on [dead]
This may explain why they don't want people touching the river (from 6/13):

"OFFSITE NOTIFICATION DUE TO SEWAGE SYSTEM RELEASE

"At 0500 CDT, the lift station #4 sewage system, South of the Fort Calhoun Station Administration building, was released to the Missouri River. The release was a mixture of ground water and sewage; samples were taken by chemistry but dilution concentration is unknown. Approximately 105 gpm release started around 0500 on 6/13/2011. This condition is being reported pursuant to 10 CFR 50.72(b)(2)(xi) for an event related to the protection of the environment for which a notification of governmental agencies is required. Applicable governmental agencies have been notified per plant procedures."

The licensee notified the State of Nebraska at 1200 CDT. The licensee also notified the NRC Resident Inspector."

http://www.nrc.gov/reading-rm/doc-collections/event-status/e...

sandal··on LulzSec Exposed
The phrase you're looking for is "good chance"
sandal··on Why RubyGems Needs Loren Segal
Some folks are trying to do this (including me). Here's the issues we've found so far and fixed:

http://blog.majesticseacreature.com/summary-of-rubygems-18-b...

sandal··on Why RubyGems Needs Loren Segal
Remains to be seen, I don't think evan has made a permanent commitment. But I believe that if anyone is best to handle whatever transition period is to come, it'd be him.
sandal··on Why RubyGems Needs Loren Segal
I've been giving slimgems grief but not Loren, I've actually been in regular, productive dialogue with Loren since this started. But actually, you're right, my public presence may not reflect that and it's time for me to change strategies. Here's what I plan to do instead now: http://blog.majesticseacreature.com/rubygems-peace-rally-vs-...

Sorry if I don't reply to this comment, but I just wanted to make sure that folks here see that I've heard their thoughts and decided to act on them.

sandal··on Why RubyGems Needs Loren Segal
We're working on ways to solve this problem. Did you check out the new release policies?
sandal··on Why RubyGems Needs Loren Segal
You missed the point. It's not about seniority at all. It's about knowledge of a very complex system. I don't want to see that fly out the window so that we can spend another couple years learning what Eric has. Rescue projects suck, and this doesn't have to be one.
sandal··on Why RubyGems Needs Loren Segal
As a mediator, I never intended to cast myself as non-biased about SlimGems. I started my involvement by specifically calling SlimGems a really bad idea, and I still stand by that point. Here's my first post:

http://blog.majesticseacreature.com/rubygems-nerd-rage-is-op...

What I said is that I'd collect the concerns of the Ruby community and present them to the maintainers and try to get changes made on their behalf. I've done that, and will keep doing that.

As for no longer being a mediator, I also already made it clear that I can't be unbiased about this, because after investigating, I've seen enough to form some strong opinions:

http://blog.majesticseacreature.com/the-rubygems-drama-conti...

In the end, I'm not worried about how this makes people who think a hostile fork is a good idea feel about me. I've received more thanks than criticism, but most of it was quiet and private, rather than loud and public. I believe in the work I'm doing, and will keep it up, but hopefully through more code and less talking.

sandal··on Why RubyGems Needs Loren Segal
To qualify my friendship with Ryan and Eric, it consists of meeting them at conferences once in a while and having some positive conversations with them. That said, I am absolutely biased here, I like them despite their flaws in the way they manage projects and their tendency to easily get embroiled in unnecessary personal conflicts.

I left a more detailed comment on your blog, but I don't think we need to have a meta-personal conflict, so I'll leave this rest here.

sandal··on Why RubyGems Needs Loren Segal
James makes a great appeal for Loren in this post, and there's no denying that SlimGems has made us all think, and brought many interesting issues to light. However, it's hard to realistically expect one to go from being the maintainer of a hostile fork to the maintainer of the project they forked overnight.

But that having been said, Loren is one of the few people qualified to really speak on these issues. He's studied the internals of RubyGems, he is aware of many of the problems with the previous ways of doing things. In particular, he's a proponent for stable APIs so that breakage becomes a thing of the past. I've spoken with literally hundreds of people over the last two weeks about this issue, and I'll be the first to admit it's one that needs to be solved. The question now is not whether it must be done, but when and how the changes need to be introduced.

These are questions that I feel I must at least strongly consider the opinions of the current maintainers of RubyGems on, because for example, Eric Hodel has been the core team for 4 years and knows more about RubyGems than anyone on the planet. There is no denying that Eric+Ryan have had personal conflicts with Loren, which would make an immediate appointment of Loren on the core team unrealistic.

However, Evan Phoenix (another of RubyGems maintainers) and I are trying to see if we can find a way to solve this problem outside of RubyGems first through a compatibility gem, in a minimally invasive way to users. We have already talked with Loren some, but I hope that dialogue continues so that he can possibly help us with our ideas and build something that everyone can be happy with. This to me would be much better than the division that would be caused by a fork, and is something I think we should at least try before we make any sweeping changes in leadership.

I've promised to back off the diplomacy and start hacking to solve the problem, and that's what I'll do in the coming weeks. But I felt it was necessary to share my thoughts here simply because I've been listening to so many people about what their concerns are with RubyGems, and that makes me really want to find a solution that works. If Loren can be part of that solution, I'd love to see him working for RubyGems rather than against it, for sure.

sandal··on SlimGems, a drop-in replacement for RubyGems -- now available
What Bundler does is run CI against RubyGems so they get automatically notified of issues. It seems like Rails should possibly consider doing that as well. However, there seems like there will be more communications between Rails<->RubyGems members in the future.
sandal··on SlimGems, a drop-in replacement for RubyGems -- now available
There have been personal conflicts abound in this drama around RubyGems, and that's a big part of the problem. The solution that I've come up with in my talks with the RubyGems maintainers is that anyone who feels that they can't work with Eric and Ryan (or vice versa) will be able to talk to Evan, who has less of a track record of difficult interactions with users.

No, that's not a great solution. But neither is supporting a fork by someone who's been working on this for three weeks when the current RubyGems core team has members on it with over 4 years of experience with the codebase. At the very least, this needs to stop being emotional and the technical points need to be laid out cleanly on white paper.

sandal··on SlimGems, a drop-in replacement for RubyGems -- now available
I agree, in fact, it's not even a problem that isn't already being worked on. Here are the new release policies from the RubyGems team:

http://blog.majesticseacreature.com/establishing-release-man...

sandal··on SlimGems, a drop-in replacement for RubyGems -- now available
Before you make a decision for or against SlimGems, please be sure to check out my series on RubyGems, in particular note the following things that happened in the last week:

* RubyGems now promises to stay API compatible with whatever version of gems ships with the latest point release of Ruby 1.9. That means if RubyGems 1.8 ships with Ruby 1.9.3, the RubyGems 1.8 API will be preserved at a minimum until Ruby 1.9.4 comes out, which will be no sooner than 6-18 months from now.

* RubyGems has removed two deprecation warnings in 1.8.4 and 1.8.5 that account for virtually all deprecation warnings that were frustrating users.

* Bundler works out of the box on RubyGems 1.8, as does Rails 3. The next point release of Rails 2.3 will also support RubyGems 1.8. Evan Phoenix is a maintainer of both RubyGems and Bundler, and is taking the responsibility of cutting stable releases of RubyGems for the time being, which nearly guarantees there will be no further Bundler issues.

* Frequent point releases of RubyGems should hopefully be a thing of the past, because starting with RubyGems 1.9, there will be beta and release candidates running for a month long cycle before they get shipped as stable releases that get installed by gem update --system

You can find additional information here: http://blog.majesticseacreature.com/tag/rubygems

sandal··on MadeForHackers.com - Kick ass landing pages for kick ass hackers
Ninja and hacker are two very different words, hacker actually has some rich history and meaning to it. But it's true that it hardly means anything without a whole lot of context now that it seems to just mean 'programmer who doesn't wear a suit to work'
sandal··on Establishing release management policies for RubyGems
The Debian situation has always seemed a bit unreasonable to me because RubyGems is designed to be a tool for Rubyists, not sysadmins. The overhead of doing operating system level integration to respect various package systems and the way they work would be way too much for the RubyGems team.

However, if changes need to be made to allow third party packagers (such as Debian) to use RubyGems in the way they want, those issues should be revisited. It's not reasonable to expect RubyGems to change its core focus or support lots of Debian specific functionality, but it is reasonable to think that if all that is needed is some extension points or something like that, the issues should be dealt with.

Please ask the Debian folks to file tickets against RubyGems, or to re-raise discussions on the rubygems-developers mailing list.

sandal··on Establishing release management policies for RubyGems
There are certain parts of Bundler that can (and perhaps should) be merged into RubyGems. Now is not the time to work on that, but after Ruby 1.9.3 is out, consider raising this question with Evan, as there is some potential there.
sandal··on RubyGems is not a Battlefield, Part I (5/25 meeting w. Eric+Ryan)
Unless this is something that has been known to be ignored or rejected otherwise, or unless you feel you can't approach them, I'd just recommend filing a support request or asking on the rubygems-developers mailing list or #rubygems on Freenode.

My main focus is on conflict points right now.

sandal··on RubyGems is not a Battlefield, Part I (5/25 meeting w. Eric+Ryan)
The --no-rodc --no-ri issue is one I want to reopen for discussion at some point, but I don't think it's as important as many of the other issues that need to be discussed, nor is it urgent.

I agree with you that like many other things, this wasn't handled especially well. I also think that a pull request with hundreds of +1's looks and feels like a riot. That can't be the best way to draw someone's best emotions out of them.

Please send me your thoughts, even if they don't lead to change in the current atmosphere, they will be documented and shared so that if anything does change, there will be a place to find them. Also, you'd be surprised how much of the shutdown comes from these personally charged conflicts. Ryan and Eric have given me an open ear. They should be turning that ear to their whole userbase, but this is a start.

sandal··on RubyGems is not a Battlefield, Part I (5/25 meeting w. Eric+Ryan)
Here's how you (and others) can reach me to share your thoughts: http://blog.majesticseacreature.com/mending-the-rubygems-fen...
sandal··on RubyGems is not a Battlefield, Part I (5/25 meeting w. Eric+Ryan)
This is exactly the sort of unhelpful comment that is making the situation worse, not better. There has been a lot of discussion about why RubyGems doesn't support this, and perhaps that discussion got lost in the circus of +1's and tensions. Would you like me to try to get Ryan and Eric to write up something explaining their stance so that you can understand it better?

If you already understand it, would you mind writing a reasoned, well thought out explanation of why you think this is important and then submit a real pull request or discuss this on the rubygems-developers mailing list?

If the answer to those two things is no, then you are not actually contributing, you're stating a preference with no explanation, and no sensitivity to the fact that your personal preference isn't necessarily what's best for Rubygems.

The good news is, RubyGems does has a configuration file which you can set once and solve this problem for yourself. Add this line to your ~/.gemrc:

    gem: --no-ri --no-rdoc
Hopefully this has come across as helpful and not rude. I'm trying the best I can to get both sides of this situation to cool down a bit, and we can help that happen as users and contributors by being a bit more mature about the way we interact with this project.
sandal··on Mending the RubyGems Fences
This is not actually a dead link, but posterous is intermittently 404ing sometimes. Reload a couple times if that happens, sorry. :-/
sandal··on RubyGems: Nerd rage is optional (and discouraged)
It really depends on what projects and groups of people you're interacting with. We have a wonderful community around Ruby Mendicant University, but it's because the folks there really care about teaching and learning as a primary goal, so they self-select towards being friendly.

Ruby isn't really a community anymore, it's an ecosystem. So if the current neighborhoods you're hanging out in don't seem too friendly, look for other ones. Different projects and organizations have different culture, and even if the union of all of those distinct groups is on a downward trend, there are still new and old groups that are going strong who are nice and helpful.

sandal··on RubyGems: Nerd rage is optional (and discouraged)
You're absolutely right. And to clarify, my article is not in any way meant to claim that the way that the RubyGems maintainers are acting is justified. Instead, I'm just trying to make the point that their experience with end users is not exactly full of ponies and rainbows, and if you act like a jerk to a maintainer, you should not expect civility in response.

Users of RubyGems who proactively act rudely to the maintainers in the expectation that they will be treated rudely are only making things worse. I think in the very worst case, that the idea that RubyGems is under some sort of tyrannical rule would seem less incredulous if contributors and users would at least try being civil first. Those that don't are simply poking at a sore wound.

sandal··on RubyGems: Nerd rage is optional (and discouraged)
That was a long time ago.
sandal··on FSF announces publication of two new books by Richard Stallman
That's true (I'm actually working on an ebook generation library that does PDF, ePUB, and MOBI), but most books that most people will read on the Kindle do have that DRM. That's what I meant by DRM restrictions on the Kindle.

If it sounded like I was saying that the device itself forces DRM, that's not what I meant.

sandal··on FSF announces publication of two new books by Richard Stallman
PDF is an ISO standard. The issue is more the DRM restrictions on the Kindle than it is the MOBI format itself.
sandal··on FSF announces publication of two new books by Richard Stallman
I dug around for a while looking for this as well, since it was absent from the main announcement. But the ordering page for both books allows you to download a PDF immediately, without charge.

It looks like Free as in Freedom 2.0 is under the GNU Free Documentation License 1.3, and Free Software, Free Society allows verbatim copying by anyone, and translation by those who have been approved by the FSF (i.e. it is not a free documentation license)

Not sure how you get at the actual manuscripts, you may need to contact FSF for that.

EDIT: Here are the links to the PDFs

http://www.gnu.org/doc/fsfs-ii-2.pdf http://static.fsf.org/nosvn/faif-2.0.pdf

sandal··on Supporting the Ruby Mendicant experiment
Once we get a non-profit set up there will certainly be that option for support RbMU at least. But if you do want to make a one time payment, here you go: http://pledgie.com/campaigns/13580 (The campaign is for RbMU but it all goes to the same place)

The reason I'm going with subscribers and not advertising the other option just yet is for the reason jonsmock mentioned.

Nonetheless, thanks for the comment because it confirmed my guess that people might want that option...

sandal··on Should every child be made to play chess?
As an occasional Go player, I mainly clicked through to see if the very first comment on the page would be someone mentioning that Go is a better choice than chess. The internets do not disappoint, regardless of whether that's a true statement or not.
← PreviousPage 3 of 7Next →