News for hackers. Stuff that matters.
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @02:37PM (#11054398)
This "FOQ" does not come off as anything but something written by someone on a very high horse.

For a project owner to need to write a page about these common questions, why would you not instead implement these common requests?

I've often done this in some of my projects, which could be considered a microcosm of this.

I've never heard of this application, but if there is a module system, why not write a few modules for some other people? Unless your api is horrible, it shouldn't be too difficult to implement all of the "Why Didn't You Implement My Favorite Feature?" if you are familiar with the code base.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by notacoward on Sunday February 07, 2016 @02:49PM (#11054470)
> why would you not instead implement these common requests?

Because time is finite. Apparently you're one of the few developers that doesn't have 10x more feature requests than you have resources to work on them. Good for you. However, that's not the norm.

> why not write a few modules for some other people?

See above. It's a mistake to generalize from young and/or small projects to those that have become large and complex over time.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @02:56PM (#11054502)
On every project that I have worked on, developer support for projects increased with the amount of users.

I would understand if there was no one using this project and it was a one-person operation, but if you are getting so many requests that it is literally impossible to comply with the top 5% of them then you should have made friends with enough people in your community who would be suited for doing these tasks.

Don't get me wrong, I am not saying do every single request and I am definitely not saying spend most of your time doing requests. But my the developers admission, "Taskwarrior [...] is easy to programmatically convert to any other data interchange format."

If it would make that many people happy, to the point where you need to have a link handy to tell them "no", then it might be worth it just to write the feature that everyone seems to want, even if it is in an optionally usable format like a 'module'.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by xioxox on Sunday February 07, 2016 @03:27PM (#11054640)
I've haven't noticed any increase in developers with my main project, which is very user heavy. It's a multiplatform GUI application, something which attracts a lot of non programmers. If you write some sort of library, you're going to get a lot of development help. That's not the case for a GUI app lots of people can use.
[dead]
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by dang on Sunday February 07, 2016 @10:26PM (#11056202)
Please don't be personally abrasive in HN comments. This post would be fine without the snarky swipe at the beginning and the personal swipe at the end.
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by throw12121 on Sunday February 07, 2016 @03:14PM (#11054589)
Q: Why won't you spend your free time implementing my favorite feature?

If you're not paying us, you need to convince us that your feature is so great, that it's worth giving up our free time to work on.

This is open source. Scratch thine own itch.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @03:19PM (#11054611)
Not everyone knows how to program. If a programmer asks for a feature, tell a programmer to write it, if someone who is interested in programming help them write a feature, but if enough people officially request a feature it's better to just help the lot of them.
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by dalke on Sunday February 07, 2016 @04:12PM (#11054863)
I wrote a simple RSS package in 2003. I still get support emails about it. I don't even remember how the code works.

I wrote some introductory Python code 10+ years ago, for one of my classes. I put it online. I now get random college students emailing me personally to ask for help doing their homework.

I distribute some of my software for free. I've since had people demand (yes, demand) essentially hours of free support time to debug their hardware configuration for them because they don't know enough to do it themselves.

When do I get to decide what is "better" for me, rather than do things which are "better" for others?

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by ubernostrum on Monday February 08, 2016 @03:10AM (#11056914)
When I was in college (15 years ago) I did a course on ancient Hellenistic religious groups. Part of that was to either write a 20-page term paper (on a topic assigned by the professor), or produce a smaller set of Web pages on the topic.

Being lazy, I spent a weekend teaching myself HTML, and did the Web option. It was linked from the course page on the college's site.

Ten years later I was still getting random emails from people who saw it, noted the .edu domain, and assumed I was an academic expert on Hermetic cults. Thankfully, a reorganization of the college's site and course pages seems to have killed it off for good.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by dzsekijo on Tuesday February 09, 2016 @09:35AM (#11065485)
Do you (or archive.org) has that stuff archived? This sounds to be a cool thing. I'd like to read it if possible. (And I promise I won't mistake you for an academic expert ;) )
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by ben336 on Sunday February 07, 2016 @03:31PM (#11054657)
Thats equivalent to saying "if enough people have strong feelings about how you should spend your free time, you should listen to them". Would you really support that in any context that didn't involve "open source"?
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by Chris2048 on Sunday February 07, 2016 @09:11PM (#11056040)
Depends on how you interpret putting code online, and how it is done. If I started/declared a running club, there maybe expectations on how I spend my time - I initiated the expectation.
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by tptacek on Sunday February 07, 2016 @02:56PM (#11054501)
For a project owner to need to write a page about these common questions, why would you not instead implement these common requests?

The whole document is about answering each of those common questions individually.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @02:58PM (#11054513)
If it gets to the point where someone says "can you implement X, Y, and Z for me, it would make my life much better" isn't it better to just implement it and make everyone happier rather than write a web page just telling them essentially to get out?
Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by dalke on Sunday February 07, 2016 @04:04PM (#11054833)
Hey, can you rewrite your code in Visual Basic/Objective C? It would make my life so much better to be able to support Windows 95/the iPad.

Hey, can you rewrite your documentation in Swedish? It would make my life so much better?

Hey, can you implement I/O using size in English units instead of metric? It would make my life much better.

Hey, can you add a GUI for me? It would make my life much better than using the command-line.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @04:08PM (#11054845)
Come on, you know that is an absolute mischaracterization of what I am saying.

If those where the problems in this document, I would agree. However that is not the case.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by dalke on Sunday February 07, 2016 @04:17PM (#11054888)
Okay, "Can you rewrite the documentation in Markdown instead of HTML? That would be so much better for me."

"Can you switch from Atlassian to the Github issue tracker? That would be so much better for me.

"Can you switch from a custom CI solution to Travis? That would be so much better for me."

Then two years later someone comes along and says:

"Can you rewrite the documentation in reStructuredText instead of Markdown? That would be so much better for me."

"Can you switch from git to mercurial? That would be so much better for me."

And so on.

When does the madness stop?

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @04:36PM (#11054984)
See https://news.ycombinator.com/item?id=11054268.

But in the end, I am not talking about the devops around the application. The only opinion that really matters there is the one coming from the project owner.

Your obvious attempt straw-man is nothing but opaque.

What I am attempting to discuss are features for the application that the owner refuses to implement because "get out".

Had Linus said that to the first person who emailed him about building an init daemon, I don't think many people would have paid much attention to Linux.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by dalke on Sunday February 07, 2016 @05:01PM (#11055115)
You say "see ...", but I've already commented on that comment.

Your analogy with Torvalds isn't that relevant. Building an init daemon didn't conflict with the long-term goals, and the advantages are reasonably clear.

Consider the FOQ "Why is Taskwarrior written in C++ and not something hackable".

We can construct a similar question to pose to Torvalds - "Why is git written in C and not a more modern language like C++?"

We know what Torvalds thinks of C++ ("C++ is a horrible language") and of that proposal.

If he ignored or blew off the first email to suggest rewriting git in C++ then we know exactly where git would be.

This demonstrates that your argument concerning "can you implement X, Y, and Z for me, it would make my life much better" has little predictive or even explanatory power.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by gravypod on Sunday February 07, 2016 @05:54PM (#11055375)
I will again re-quote myself.

"But in the end, I am not talking about the devops around the application. The only opinion that really matters there is the one coming from the project owner. Your obvious attempt straw-man is nothing but opaque."

I am simply addressing the section about the feature requests.

You on the other hand are painting my argument as something it is not about.

Edit: By features I mean anything under "Why Didn't You Implement My Favorite Feature?"

My comments are solely on that section.

Re:FOQ – Frequently Obnoxious Questions When Doing an Open S... by tptacek on Sunday February 07, 2016 @03:00PM (#11054520)
See: https://news.ycombinator.com/item?id=11054501 and note that none of the reasoning on that page includes "so we can write this web page".