[ww520]

I didn't see he forgot to return the keys (owned by the company). He asked for help to transition it off. No one came, so he just shut it down.

Yes. I can see how everyone's life is a bit harder since he has stopped providing free product and service for them. Well, they had a free ride to begin with.

[soc88]

You are still missing it completely.

[bmelton]

I believe it is you missing the point. They're his keys. If I quit the company I'm working for, they can't just take all all my keys because at some point they gave me some.

This is no different than my old neighbor, Mr. Taylor. He used to let us use the pool in his backyard until one of the kids pooped in it. He stopped letting those kids come to the pool.

It's his pool, and it's his choice who can and can't use it. In this case, David Pollack has just decided nobody can use the pool, and he's put a fence around it.

You're just pissed you can't use the pool for free anymore.

[soc88]

I never used his pool.

I just think that his behavior is intended to maximize the potential damage to everyone, he is well aware of that and does it on purpose, because someone hurt his feelings.

In my opinion there are other, more constructive options available.

[ww520]

Can you prove that? I'm not familiar with the Scala drama.

Even if that innuendo is true, why don't you blame the one who hurts his feeling? Instead of blaming him. Open source developers are human, too. They have taken on far too much abuses from ungrateful users.

I don't see the need for David to be a doormat to every abusive user out there. I would snap too and say fuck it, you guys are on your own.

[soc88]

After people finally figured out that he was leaving (almost no one knew of that) they offered to take over the complete responsibility, what happens? Suddenly he wants to keep the domain, forcing everyone to pull and update their documentation, packages, artifact IDs, Maven POMs out there, because they can't use it anymore. And the promised transition of accounts to another provider just won't work for all people who entered an id of "org.scala-tools", because most other providers require that the person publishing an artifact also controls the domain name.

The whole thing is basically maximized for pain and wasted hours of transitioning, migrating and repacking.

Have a look at http://news.ycombinator.com/item?id=3495303 for the circumstances how he "told" everyone he was leaving. I visited the Lift IRC channel an hour ago and asked what their stance was on Pollak leaving Lift/Scala. They had no idea and asked for a link. So much for "nobody stepped up for maintenance". Of course nobody can step up if nobody knows.

It is not acceptable that someone who expected that he would transfer the domain to the people maintaining it insulted him, but how can this be communicated to that individual if no body knows who it was. "Somebody insulted me" doesn't help to resolve that matter.

[zak_mc_kracken]

> After people finally figured out that he was leaving (almost no one knew of that) they offered to take over the complete responsibility, what happens? Suddenly he wants to keep the domain

This is in complete contradiction with what dpp said (he asked for help a few months ago and nobody answered). So either you or dpp is lying.

Considering that his call for help is well documented, I think you are the one spreading false information.

[tbsdy]

Please, tell us the point then.