4 ms·

The constructiveness of this is that people trying to find a solution for an already solved problem can easily take from them the solutions already implemented;

The constructiveness of this is that people trying to find a solution for an already solved problem can easily take from them the solutions already implemented; instead of struggling through making their own solution. "Stealing" is highly recommended and looked upon favourably by Perl people. And as you say, it also serves to show newer programmers that there is no need to badmouth older languages, there is only to learn.

SEMW 12y ago
> trying to find a solution for an already solved problem can easily take from them the solutions already implemented The 'solution already implemented' in this case seems to be 'Email the PAUSE admins who will deal with each case individually'. It seems kinda condescending to imply that 'have more volunteers' is something that the ruby community just hasn't thought of; as if projects short of manpower just need to learn from the wisdom of the perl community in just, y'know, having more. One of the main motivations for Benjamin to write his post seems to have been the reply in the initial thread from the Rubygems admin saying "I want these decisions to not be on my (or anyone's) shoulders. It's stressful and nerve-wracking if I get it wrong"[0]. Given that, a reply saying, essentially, 'What's the problem, just get the RubyGems admin to make the decisions' seems.... unconstructive at best. [0] https://groups.google.com/d/msg/rubygems-org/niS5ZO9DNgk/9gFq2S67npoJ https://groups.google.com/d/msg/rubygems-org/niS5ZO9DNgk/9gF...
- Mithaldu 12y ago
  He didn't post the step-for-step instructions on how to proceed, but only the first bit of that: http://www.cpan.org/misc/cpan-faq.html#How_adopt_module http://www.cpan.org/misc/cpan-faq.html#How_adopt_module In short: Make an account, email admins and cc author, then shotgun every place the author's likely to see your intent, then wait a few weeks, and if your efforts have been clear, and the author unresponsive, admins will transfer rights to you. Typically following this procedure results in the original author reacting, and if they don't, then there's nothing wrong or nerve-wracking about a transfer. CPAN has a big body of history pointing to this working just fine. Besides, if i interpret this right that the number of rubygem admins is low enough that simply handling such a simple matter would be a problem, then you have bigger fish to fry. ---- Edit: Then again, Benjamin admits that his post doesn't solve: > deal with gems whose owners are AWOL Which is the real problem, and the solution to which solves pretty much all other cases too.
kyrra 12y ago
I had a college professor for an OpenGL graduate class that regularly told us: "Don't shade your eyes, plagiarize." It meant the same thing you said. Lots of what you are trying to do has already been done, reuse it.
- to3m 12y ago
  "Only be sure always to call it please... research." http://www.youtube.com/watch?v=UQHaGhC7C2E http://www.youtube.com/watch?v=UQHaGhC7C2E

SEMW 12y ago

> trying to find a solution for an already solved problem can easily take from them the solutions already implemented The 'solution already implemented' in this case seems to be 'Email the PAUSE admins who will deal with each case individually'. It seems kinda condescending to imply that 'have more volunteers' is something that the ruby community just hasn't thought of; as if projects short of manpower just need to learn from the wisdom of the perl community in just, y'know, having more. One of the main motivations for Benjamin to write his post seems to have been the reply in the initial thread from the Rubygems admin saying "I want these decisions to not be on my (or anyone's) shoulders. It's stressful and nerve-wracking if I get it wrong"[0]. Given that, a reply saying, essentially, 'What's the problem, just get the RubyGems admin to make the decisions' seems.... unconstructive at best. [0] https://groups.google.com/d/msg/rubygems-org/niS5ZO9DNgk/9gFq2S67npoJ https://groups.google.com/d/msg/rubygems-org/niS5ZO9DNgk/9gF...

Mithaldu 12y ago
He didn't post the step-for-step instructions on how to proceed, but only the first bit of that: http://www.cpan.org/misc/cpan-faq.html#How_adopt_module http://www.cpan.org/misc/cpan-faq.html#How_adopt_module In short: Make an account, email admins and cc author, then shotgun every place the author's likely to see your intent, then wait a few weeks, and if your efforts have been clear, and the author unresponsive, admins will transfer rights to you. Typically following this procedure results in the original author reacting, and if they don't, then there's nothing wrong or nerve-wracking about a transfer. CPAN has a big body of history pointing to this working just fine. Besides, if i interpret this right that the number of rubygem admins is low enough that simply handling such a simple matter would be a problem, then you have bigger fish to fry. ---- Edit: Then again, Benjamin admits that his post doesn't solve: > deal with gems whose owners are AWOL Which is the real problem, and the solution to which solves pretty much all other cases too.

kyrra 12y ago

I had a college professor for an OpenGL graduate class that regularly told us: "Don't shade your eyes, plagiarize." It meant the same thing you said. Lots of what you are trying to do has already been done, reuse it.

to3m 12y ago
"Only be sure always to call it please... research." http://www.youtube.com/watch?v=UQHaGhC7C2E http://www.youtube.com/watch?v=UQHaGhC7C2E