robise

Joined 12 years ago

Karma
5
Submissions
9
Member since
Mar 20
A London-based Senior Ruby & Full-stack Developer working with Ruby on Rails, Sinatra, Ember.js, React.js, Swift & iOS, Docker and more.
View on Hacker News

Recent submissions

Comment · 10 years ago
Thanks for your thoughts - I appreciate it.

Yep, I take your point. This is my first time with this so still very much finding my way. :)

I'm still in very early stages, so I was after some early feedback though to make sure I'm not "writing blind" and just guessing what people what to know about.

But I think you're right... some informative blog posts are probably the way to go.

Thanks again.

Comment · 10 years ago
Hi, I'm aware of the official meaning of the acronym, but my usage was based on my belief that in everyday language, people use it to mean "vanished" or "disappeared".

I'm aware of the connotations that this has in the terms of Open-source, but was not in any way implying that the person had an obligation to continue work on this project (quite the opposite, I simply wanted their go-ahead/approval for me to maintain the project myself, before just going ahead and making changes to __their personal Github repo__). I was using the term in a way that I thought added a slight, humorous hyperbole to get people's attention on Hacker News in the hope of getting their advice.

I would certainly not have used this term to the maintainer in question, for the reasons you describe: I would not want to imply they had any obligation. I have no problem with a maintainer not wanting to continue any further work on a project they lead, I just think it would be helpful if they left instructions for how other maintainers should proceed, or at least respond to requests for clarification.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton