Kevin Krammer posted on Tue, 29 Oct 2013 15:31:46 +0100 as excerpted: >> anyway) developers do stuff not only for them. And if stuff is not >> supposed to be for "everyone", why release it to the public in the >> first place? > > Publishing makes sense even if there is only a subset of "everyone" who > has the same needs. Even if one doesn't know if there is someone else.
That's worth a requote spotlighting. =:^) Once the work is done, it's very little more trouble to publish it, especially when one is already using a (D)VCS such as git to track changes already. Even if NO one else uses it, putting it on a public server provides an additional backup in case something happens to the local copy -- as Linus says, "real men" let the internet be their backup. =:^) But the chances are pretty good that /someone/ else will find the work useful, and once /someone/ does, there's a good change a not insignificant group of "someones" will find it useful, even if there's never any measurable market share, and even if the ultimate goal never advances one whit beyond "scratching your own itch" for the original developer and no one else ever provides a patch at all. So there's certainly reason to get it "out there" even if you have no idea if even one "someone else" will find it useful. Because someone might, and even if they don't, at the very least, it's still an off-site backup. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.