News for hackers. Stuff that matters.

robise

Re:Feedback wanted: Docker for Rails Developers book on Thursday July 14, 2016 @11:25AM (#12094627)
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.

Feedback wanted: Docker for Rails Developers book

I’d love to get some help. I’m working on a new book: “Docker for Rails Developers”, but I want to make sure I’m covering the things that people really want to know.If you’ve heard of Docker, or even dabbled with it, but aren’t using it regularly, I’d love to get your thoughts. I’ve written a tiny survey (only 1 question and should take seconds). I’d really appreciate it if you’d share your...

( Read More... | 4 comments | 2 points | on HN )
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.

Ask HN: Help Main open-source maintainer gone AWOL. What do I do?

The main maintainer of a popular Ruby gem, hosted on Github, is not responding to mentions in Issues (I have no other means of getting hold of them.) It's been over 8 months since I've heard from them.I am another maintainer, but was given maintainer rights specifically to support a new feature that I added.What should I do? People are still raising new issues and Pull Requests, but I’ve been...

( Read More... | 4 comments | 2 points | on HN )