[01:17] Alright, to continue the discussion from #ubuntu. mchelen2: like you said, this is completely anecdotal, but in general, whenever I look up something related to linux software, I find it easier/faster on the Arch wiki. [01:18] For example, tonight I'm trying to learn about GPUs and graphics drivers in Ubuntu. [01:18] And the last thing I was looking up is this "intel-microcode" driver that shows up in my Additional Drivers. [01:20] So I go to https://help.ubuntu.com/ and type in "microcode", and I see no official wiki pages but a bunch of links to AskUbuntu questions. [01:22] In this particular case, I was lucky enough that the second link has an answer that explains what microcode is, so I didn't have to spend too much time scrolling too unrelated questions or irrelevant answers. [01:22] On the other hand, when I search the Arch wiki for "microcode", I immediately get this page https://wiki.archlinux.org/index.php/Microcode and in two lines I have my answer. [01:23] yep they seem to have better docs than most distros, whether that applies to all distros though, is another story. [01:24] Sure [01:25] TBF, microcode isn't something that a regular user would need to bother themselves with [01:25] It was just one example... [01:25] but secondly (and more importantly in my opinion) is that you found it on the Arch wiki. Last I checked Arch uses the Linux kernel. It's not like you found it on a Microsoft wiki or an OSX blog [01:27] Mihasi: i mean i generally agree with this example, i just wouldn't try to generalize based on that [01:27] True, but the nice thing for Arch users is that apart from this background information that applies to Linux in general, they also get a up-to-date information on how to install this on their specific distro. [01:28] mchelen2, but this has been my general experience since I've started using Ubuntu. [01:28] Mihasi: I think that's where we have a difference of opinion. You keep making it sound like it's a bad thing that you found it on the Arch wiki [01:28] Mihasi: ok, but i cant really speak to your general experience [01:30] And I don't think I'm the only one with this experience. At least I've seen similar remarks mentioned multiple times. [01:31] at least when i was last involved, there seemed to be a lot of folk that had to install that microcode update along with proprietary graphics drivers for them to work (can't remember if that was just a discrete nvidia or an nvidia optimus situation though) [01:31] Mihasi: thats still super generalized and nothing i can specifically agree or disagree with [01:32] what was actually the point in bringing this up? [01:32] i can see value in discussing "how can we improve ubuntu documentation? what problems does it have that we can address?" [01:33] yes, which leads to two questions to users really [01:33] 1) do they know wikis are user editable? [01:33] There was someone in #ubuntu asking up-to-date info on how to install a (commercial) software package, and I made a remark about how I found it frustrating that the Ubuntu documentation often lacks centralized, up-to-date information (in my experience) [01:33] but a sort of generic "is wiki A better than wiki B? i heard a bunch of people say so" is not something i know how to act on [01:33] 2) if they do, why aren't they helping others with what they learn? [01:34] daftykins: personally i find wikis to have a somewhat high barrier to entry, but they still may be the best option available [01:34] yeah, bit of hassle to create an article [01:35] it would probably be handy to know if folks don't know they can help others with it, though [01:35] i sort of like discussion based help systems like ask ubuntu [01:35] i find those a nightmare because they come up in search results but they're often outdated or wrong [01:36] mchelen2, Well, all I was really saying is: I" find that wiki A is better than wiki B in general", but I agree that this is not something that can be acted on directly. [01:36] Mihasi: yeah i mean i appreciate your perspective, but i don't really know how to evaluate that objectively [01:36] And yes, same here. Always reminds me of this XKCD comic: https://xkcd.com/979/ [01:36] what made you come from arch to ubuntu? [01:36] * daftykins predicts the "what did you see!?" xkcd :D [01:37] daftykins: in this use case of finding info on microcode at least ask ubuntu has more info than the ubuntu wiki [01:37] XD [01:37] mchelen2, that is definitely true. :D [01:37] ah so you didn't use arch then move [01:37] I did use Arch for a couple of months. [01:38] what made you switch? [01:38] I started on Fedora, eventually moved to Ubuntu, then Arch, then Windows again for a loooong time. [01:38] daftykins: it would be nice if the ask ubuntu search would prioritize highly rated answers better [01:38] Am I the one one that thinks it's possibly a bad idea to copy simple things from one wiki to another [01:38] And now timing constraints made me switch back to Ubuntu. [01:38] tgm4883: yeah i agree, it contradicts DIY [01:38] err DRY [01:38] lol [01:38] "wikis are user editable" => did wiki.ubuntu.com ever stop being restricted after that spam nonsense [01:39] tgm4883: its better to link, although in a perfect world there would be transparent embed options [01:39] i'd go look but the dang thing never loads right for me [01:39] i think i had a lot of faffing to endure when i wanted to submit one of those macbook articles [01:39] !mac [01:39] For help on installing and using Ubuntu on a Mac, see: https://wiki.ubuntu.com/MactelSupportTeam/CommunityHelpPages [01:40] It used to be cool to do a CLI-based distro install, but now I prefer things to "just work", and Ubuntu is far better in that department than Arch. [01:40] can you tell which one i wrote? :) look down the LTS column from the top and look at the first release that seems to stand out... [01:40] transparent embed options only matter for the people that think they need to brand everything [01:41] I used to be like that [01:41] heh yeah masochism and ones OS should not go together [01:42] i'm not talking about branding, i'm talking about maintaining a consistent user experience [01:43] meh, the second you need to jump to the internet to find something, you aren't going to find a consistent user experience [01:43] :P [01:44] daftykins, MacBook6-1/Lucid? [01:44] and lol [01:44] it's unobtainable [01:44] nope trusty on 3,1 [01:44] hardy is like, 8.04? lucid is 10.04 and trusty is 14.04 [01:44] you find me an online resource that has a consistent user experience, and I'll find you a user that has an issue that resource doesn't have an answer for [01:48] check out this curvy board :) http://i.imgur.com/R76mL5O.jpg the very chunky scythe mugen heatsink caused that over many years [01:49] tgm4883, but isn't that the point of transparent embedding? to prevent the user from having to jump to the internet to find something, but to instead see all of the information on one site? [01:49] (as opposed to providing links that *do* make them jump) [01:50] i think all this pointless chatter would be better served writing a few articles [01:50] * daftykins coughs [01:50] At this point at night, all I'm good for is pointless chatter. :P [01:50] actual productivity is tiring [01:50] but dont let us stop you :D [01:51] Mihasi: by that definition, they would already be on the internet. Unless you are suggesting some app that exists on in a default ubuntu install. I know, we could give it some cool animal name. How about a Fox [01:51] Also, when I'm writing articles/my thesis all day, I don't have much motivation left to write more articles at night. :P [01:54] tgm4883, I'm not sure if I understand your point. What I imagine transparent embedding of wiki pages to be is: I look up "microcode" in the Ubuntu documentation, I get an Ubuntu wiki-page with the same text as on the Arch wiki, seemingly without having left the Ubuntu wiki. And maybe with some additional instructions on how to install it on Ubuntu underneath the embedded text. [01:55] but enough to come on IRC and ramble :) [01:55] Mihasi: and what if the Arch wiki doesn't have any information on microcode? [01:55] i don't mean to pick on you there, it's the same sentiment which is why most of the ubuntu docs are outdated or rubbish [01:55] daftykins: what else are we going to do while waiting for spaceships to dock? [01:56] So instead of jumping from the Ubuntu wiki to the Arch wiki, then back to the Ubuntu wiki, then to AskUbuntu for installation instructions. Instead of visiting 3 pages, I only have to visit 1. [01:56] tgm4883, then I guess there should be a transparent embedding of another wiki that does have information. :P [01:56] Mihasi: Literally the only thing that helps is in Ubuntu branding... [01:56] ... [01:57] honestly i think your argument is a bad one [01:57] Mihasi: Ok, lets take a step back [01:57] You don't see how, for a user, it's a better experience to only have to click once and visit one page than visiting 3 separate pages? [01:57] tgm4883: i think new users might totally ignore archwiki content, unless it is curated to be applicable to ubuntu [01:58] Mihasi: what you want is to be able to go to the ubuntu wiki, search for something and be able to find information on it (all on the ubuntu wiki) right? [01:58] Yup [01:58] Mihasi: ok, so in order to do that, you're going to have to have this "transparent embedding" of enough different websites so it has information for any request, right? [01:59] "any" is an overly broad scope [01:59] lets settle for "more" [02:00] mchelen2: fine, switch any with 90%. [02:00] tgm4883: 90% of all problems? [02:00] Mihasi: mchelen2 so what I described is accurate to what you want? [02:00] let me rephrase [02:00] lets say ubuntu wiki covers 1000 issues [02:00] mchelen2: "more" is vague [02:01] 2 is more than 1 [02:01] yes, that seems extremely specific to me [02:01] mchelen2: Mihasi: ok, so in order to do that, you're going to have to have this "transparent embedding" of enough different websites so it has information for most requests, right? [02:01] is that better? [02:01] Alright, for the same of argument let's say that the ultimate goal is to cover at least 90% of the issues or information that Ubuntu users want access to. [02:02] lets say ubuntu wiki covers 1000 issues. if you can transclude content for 200 more, that would be swell [02:02] tgm4883: i never used the word "most" [02:02] mchelen2: true, but you are super vague on what you actually want [02:03] tgm4883: i just gave an extremely specific example, with hypothetical numbers [02:03] mchelen2: so explain to me what you want. We can use Mihasi's example if you want [02:03] I think just had trouble with the wording "any request". [02:03] use the example i just stated [02:03] mchelen2: Mihasi ok, so using those examples. You want to be able to search all that from inside the ubuntu wiki, correct? [02:04] Alright, so the ultimate goal is to cover at least 20% of the issues. ^^ [02:04] Yes [02:04] tgm4883: yes, the wiki would search 1200 pages, instead of 1000 [02:04] Congratulations, you just invented Google Custom Search Engine [02:04] federated search is fine [02:05] it's basically one step narrower than google.com [02:05] You don't see any difference between a general search engine and a site specifically tailored towards Ubuntu? [02:05] Mihasi: you apparently don't know what google custom search engine is [02:06] Ah, I ignored the word custom. [02:06] Carry on. [02:06] :P [02:06] tgm4883: yeah the part that you are missing is we dont want to include all of the arch wiki, we want whitelisted articles or article sections which apply to ubuntu [02:06] mchelen2: ah ok, and who is going to currate that? [02:06] if you want to do that via CSE, thats fine [02:06] tgm4883: its part of the wiki.... [02:06] tgm4883, the same people who curate the wiki now, no? [02:06] Mihasi: that won't work [02:07] tgm4883: so instead of writing an article covering the microcode stuff, basically link to the arch wiki page [02:07] which then gets included in search results [02:08] Exactly [02:09] mchelen2: Mihasi That won't work. As you both have pointed out already, the Ubuntu wiki is terrible. What makes you think the currators are going to go through the trouble of linking to content when they weren't even bothered enough to write a wiki page on what you were looking for now? [02:09] because linking content is easier than writing a page from scratch? [02:10] mchelen2: But linking a page isn't what you asked for [02:10] mchelen2: you asked that it be tranparently linked. So it has to look good inside the ubuntu wiki [02:10] tgm4883: thats what an embed is... [02:10] mchelen2: it would be much simpilier for them to just copy&paste the content [02:11] mchelen2: this is all ignoring the fact that nobody has done this already [02:11] the problem there is handling updates [02:11] tgm4883: mediawiki lets you transclude content from within a wiki. i'm talking about that feature across domains [02:11] but yeah we are speaking purely theoretically [02:11] mchelen2: why don't we just have one wiki? [02:12] sarcasm? [02:12] mchelen2: no [02:12] who is "we"? [02:12] mchelen2: you're talking about some ideal solution that you want everyone to follow. I'm proposing a different ideal solution that everyone should follow [02:12] the basic issue is that a single org has to have admin control [02:12] We just have one, wiki.linux.com [02:12] fedora/ubuntu/arch all put our stuff there [02:13] tgm4883: i never said it was ideal, its just one approach [02:13] tgm4883: ok swell, thats another approach [02:15] Yes, that would also be a solution. [02:17] Although in that case, user's would have to be Linux-minded instead of distro-minded. I wonder if for example Arch users would want to be bunched together with all other Linux users. [02:17] There's another problem with that solution (as is a problem with the former solution you proposed) [02:18] You're relying on other people to do all the work [02:18] g'night folks [02:19] night daftykins [02:23] tgm4883: thats the same as right now [02:23] ofc someone has to write the article in the first place [02:23] Night night daftykins [02:24] the point is it should only have to be written once, and they be available in ways that are easy for users to find [02:24] Yes [02:24] mchelen2: no. Right now ubuntu is hosting the content. In your proposed solution, if the other wiki page goes away, the content is lost [02:25] tgm4883, How is that different from linking or from having it all on one big Linux-wiki (which can also go away)? [02:26] tgm4883: right now the ubuntu wiki is totally missing this content. so even if some of it was lost later, you would still have more than you started with [02:26] yeah also what Mihasi said [02:26] I'm glad we're all on the same page, that all of these solutions suck [02:27] everything sucks, all you can do is make things suck slightly less :D [02:28] mchelen2: I'm glad you said that. You can start here https://wiki.ubuntu.com/ let me know which articles you've fixed [02:30] So now you're saying that the only good solution is to actually have a completely separate Ubuntu-specific wiki after all? [02:30] tgm4883: last time i checked, your job title didn't include directing user contributions [02:30] mchelen2: and yours is complaining on IRC then :P [02:31] How is it complaining? We started from the question "how could we improve the Ubuntu documentation" [02:31] Mihasi: I'm saying that I haven't seen a solution posted that is objectively better [02:31] tgm4883: i'm pretty sure that's what irc was invented for. but i appreciate that you consider discussions of alternative approaches to be complaining :D [02:32] mchelen2: look, you can take shots at me all you want. I'm the only one that bothered to have this discussion with you... [02:32] Oh, so now I don't exist anymore? O.o [02:33] Mihasi: come off it, that's not what I meant at all [02:33] tgm4883: if all your input consists of pointing out that no proposed solutions are perfect, i'm honestly struggling to find the value of it [02:34] mchelen2: I'm well aware that we don't want the perfect to be the enemy of the good. I just find your approach lacks being good [02:34] wait no [02:34] thats not really a specific enough claim to be evaluated [02:35] mchelen2: your approach is good, I just don't see the need for it [02:35] ok i mean, fair enough, thats a subjective perspective you are entitled to have [02:35] mchelen2: well TBF, you have dismissed all of my objections to it [02:36] i feel that i have specifically addressed each one [02:36] at which point you added another and another to the laundry list [02:37] mchelen2: really? I said who is going to currate this and you haven't addressed that at all. You're response was "the same people who currate it now" which is laughable considering how bad you think the current situation is [02:38] tgm4883: you realize that objection is a separate one from your position that you "don't see the need" [02:39] yes... [02:39] apparently I'm limited to one objection of this idea [02:39] To add to that, I don't see how that response was laughable, considering that the current situation might be bad because the current curators don't have enough time to work on it. [02:40] And since embedding would be faster than writing new content, it might be a better solution. [02:41] i don't really want to go through a list of 10 different concerns you have. pick one [02:41] Mihasi: yeah thats basically the argument i made about why such an approach would reduce burden on curators [02:42] It would be nice if there was a page that aggregated pages about the same topic from different linux wikis and displayed them all on screen at once. [02:42] justsomeguy: just need someone to work on it.... [02:43] That actually sounds like an interesting project. *-) [02:43] tgm4883: I wish I knew enough web development stuff to implement it. [02:43] justsomeguy: well that's a common problem [02:44] "Hey guys, I've got this great idea. Why don't you build it" [02:44] So people who don't have the time or skills to contribute should not share their ideas or join in discussions? [02:45] * tgm4883 rolls eyes [02:45] I don't think that what tgm4883 was saying. [02:45] Mihasi: you can spin what I said however it makes you feel better [02:45] yeah i agree ideas are cheap, implementations are expensive [02:45] Mihasi: but I've first hand experience being on the wrong side of these types of discussions [02:46] Also, not my idea, I was just summarizing someone elses point from earlier on in this chat. [02:46] but at the same time i dont think its productive to discourage theorizing [02:46] Be the change you want to see in the world [02:47] That's the plan. I just have to learn a bunch 'o stuff first. ...damned JavaScript. [02:47] tgm4883, I don't necessarily feel better or worse, but this is you've repeated "then why don't you do it?" a number of times in the course of the discussion and I don't feel that contributes. [02:48] Mihasi: you've got to look at the other side of the argument though [02:48] i didn't have a problem with tgm4883's last comment, it was the 200 before that which bothered me [02:48] :D [02:49] Although I do agree that it is important to be realistic about what *can* be done, that doesn't mean we can't talk about what *should* be done. [02:49] mchelen2: and you are entitled to be bothered by it :) [02:49] its the difference between "i have an idea" "great! go build it" and "i have an idea" "that will never work, its pointless" [02:49] the former is totally fine [02:50] mchelen2: actually it's more "I have an idea" "That doesn't seem worth the effort over our current solution" [02:51] tgm4883: right, and i dont see the point of discouraging ppl, if they are not asking you to do it [02:52] you could just as easily say "that would be a nice feature, but its a lot of work, if you want to do it that would be great" [02:52] it costs you nothing [02:53] Yes, or "good idea, we'll take it up with the devs/contributors and see if anyone has the time to work on it" [02:53] Mihasi: well in that case you are taking on extra work [02:54] You're still asking someone do it [02:54] err, someone else [02:54] yeah in my example, nobody is being asked to do anything [02:54] True, but what is so bad about asking? [02:55] (As long as you're not forcing anyone to do it.) [02:56] asking is a form of pressure [02:56] in any case we can debate that issue, but it wasn't the example i was trying to use [02:56] in this whole convo i have literally never asked anyone to do anything [02:56] mchelen2: that is true [02:58] thats why i mean by saying, encouragement costs nothing [02:59] But asking is wrong because it is a form of pressure? [02:59] Mihasi: i mean it depends on the circumstances, but i think we can imagine cases where asking for things is not appropriate, even if nobody is forced to do anything [03:00] Mihasi: you wouldn't go to a car dealer and ask them for a free car, it would be rude [03:00] I think if you're going to ask someone to do something, you should have some "skin in the game" [03:00] Of course, but I don't think asking developers to implement some idea that you might not have the skill to implement yourself. [03:01] Mihasi: honestly, I think that's a cop out [03:01] Mihasi: consider that it takes time to evaluate a request. if a dev has to read through 10,000 requests, they can't get anything else done [03:02] Mihasi: we might imagine a situation where those requests are filtered, reviewed, and recommended by other users, then maybe the top 10 get passed along [03:03] If you put yourself forward as a voluntary software developer for Ubuntu (for example), doesn't that imply that you're willing to work on features that Ubuntu users would want? [03:03] ofc in the open source world, how we define "the devs" is a little unclear [03:03] Mihasi: no, not at all [03:03] And sure, that would be a good way of doing it. [03:03] I'm not saying every idea or request that ever pops up in IRC should go to the devs directly. [03:04] Mihasi: not necessarily, maybe you are only working on a feature you want. if other ppl benefit too, thats great [03:04] its a little weird to talk about "the devs" as a specific group of ppl [03:04] Mihasi: someone that puts themselves as a voluntary software developer for Ubuntu (for example), implies that they are willing to work on features that one Ubuntu uses wants [03:05] Hmm, okay. I hadn't considered that some people might only want to work on one specific feature that's primarily interesting for them. [03:05] i've contributed to specific bugs that affected me in ubuntu distros. once the bug is fixed, i'm done. it doesn't necessarily mean i'm interested in creating new features [03:06] That makes sense. [03:06] that doesn't apply to all devs, just trying to convey that ppl contribute for a variety of reasons, in a bunch of different ways [03:06] Yeah, I hadn't considered that. [03:07] My own view on volunteering is different. [03:09] (I'm a volunteer for the Red Cross, and in my mind I was comparing turning down ideas for features to turning away patients because "I only signed up to do CPR, I'm not interested in treating open wounds, go do it yourself".) [03:10] Didn't consider that fact that this is a completely different situation. :P [03:10] ah lol [03:11] Needless to say, I haven't contributed to big software projects yet. :P [03:11] imagine if you signed up to be a red cross volunteer in chicago [03:11] and they said you were being transferred to syria [03:12] you might be like, "i didn't sign up for this!" [03:12] Ah, but isn't that different? [03:12] nope, its 100% the same :D [03:12] I don't think so, because here I have no choice. [03:13] which one don't you have a choice in? [03:13] If they were to ask me if I would be willing to go help out in Syria, I could say no. [03:13] I wouldn't be upset that they'd ask me though, because that's part of what the organization I joined does. [03:13] i see what you are saying, but imagine if they asked you every 15 minutes [03:13] Yeah, I can imagine that's different. ^^ [03:13] Mihasi: would you go to Syria to help the red cross? [03:14] Mihasi: would you go to Iran to help the red cross? [03:14] Mihasi: would you go to Russia to help the red cross? [03:14] Mihasi: would you go to Canada to help the red cross? [03:14] lol [03:14] Mihasi: would you go to Ohio to help the red cross? [03:14] Mihasi: would you go to Columbia to help the red cross? [03:14] Mihasi: would you go to Mars to help the red cross? [03:14] oh god [03:14] yes to mars [03:14] See! [03:15] Do you have V/\_ Blood? [03:15] also acceptable: french riviera [03:15] because that is what they need on Mars [03:15] It might be annoying to get so many requests, but eventually one gets through that is super-interesting! :P [03:15] no, but i can get some [03:16] Mihasi: yeah i think the issue is really about bandwidth, how to triage feature requests and find the best bang for buck [03:16] Absolutely [03:17] But that's like you suggested: a first triage could be done by other people who have no programming skills, so only the most important or innovative ideas reach the devs. [03:17] It's a lot more appealing to hear "Hey I have this sweet idea, but I don't know how to do X. Could you help me accomplish this" rather than "Hey I have this sweet idea, can you do it for me?" [03:17] Kind if like we do the small stuff at the RC so the real doctors and nurses have more time for the serious cases. [03:18] Sure, can't argue with that. [03:18] Mihasi: do you ever learn anything from the doctors or nurses? [03:18] Yes, but not enough to do their job. [03:18] Mihasi: do you ever learn from other resources that would help you with the RC? [03:19] Mihasi: ok, not enough to do there job. That is fine. But could you assist them? [03:19] Mihasi: if they were like "take this guys blood pressure", could you do it? [03:19] Sure [03:20] Mihasi: So why is it so different then to learn something related to the task at hand with ubuntu? [03:20] It depends on what your goal is. [03:20] i don't think Mihasi said it was different [03:21] maybe i missed something [03:22] I wanted to get into the RC because I'm interested in health care, so I wanted to learn how to be healthy and how to help other people to be healthy. [03:22] But the people/patients I treat only want to become healthy themselves, they are not interested in learning about health care or in providing it for others. [03:23] I don't think every Ubuntu user that has an idea on how to improve Ubuntu wants -or should want- to also be a developer. [03:24] yeah i think thats fair [03:25] nobody said they needed to be [03:25] yeah i just took it as a general point [03:26] oh or that there should be a way for ppl to make feature requests [03:26] even when they cant do it themselves [03:26] In that case I misunderstood. I thought your argument was that it would be best if the people who suggest new features should want to implement them themselves, or should be willing to learn how to implement them. [03:27] Mihasi: no, my point was that they should contribute in some way (more than the idea itself) [03:27] Maybe they do. [03:27] Mihasi: they most likely don't, or contribute very little [03:28] Maybe they're using Ubuntu to find a cure for cancer, but they have an issue with some piece of Ubuntu software? [03:29] irrelevant [03:29] i don't think people necessarily need to contribute more to have their suggestion be valid [03:29] but their suggestion may not carry a huge amount of weight [03:30] so if 1 user makes a suggestion, it may not get much consideration, unless 10k ppl have that same suggestion [03:30] mchelen2: that was my point. Not that it's not valid, just that as a developer, I'm less inclined to want to work on your suggestion unless it sounds particularily appealing [03:30] Oh, that's completely fine. [03:30] But you're point a few minutes ago was "that they should contribute in some way (more than the idea itself)" [03:30] tgm4883: yeah and i think volunteer devs totally have discretion over their time & attention [03:31] That's what I was arguing against. [03:31] it depends if "should" means that ideally they would contribute more, or that they must contribute more for their suggestions to be valid [03:31] But of course volunteer devs should be completely free to work on what they find interesting. [03:32] Mihasi: I'm not sure where the hang up is, yes, I think if you have an idea you should contribute in some way. If you don't contribute in some way, that doens't make your idea invalid, it just makes it less appealing [03:32] In my opinion it doesn't... To go back to my extreme example: if they're working on a cure for cancer, I don't think it would be ideal for them to learn to program and contribute. [03:33] Yup, than it's clear where the hang up is: I was interpreting it as you saying those ideas are not valid/should not be considered. [03:33] Mihasi: a few things, 1) bringing up working on cancer is pointless and irrelevant to the argument unless the developer happens to have cancer. 2) one does not have to learn how to program to contribute [03:33] If you're only saying that they're less appealing, I'm not going to argue with that. [03:34] Haha, looks like we're going to have another hang-up then. [03:34] Mihasi: on which part [03:34] Mainly that my example is irrelevant and pointless. :P [03:36] Mihasi: you're trying to persuade me by tugging at my heart strings. It's childish [03:36] If you would be saying that a suggestion is less valid if the user does not contribute directly to Ubuntu in some way, my counter-argument would be that they might be working on something else that is equally (or even more) important. [03:37] No I'm not. I'm giving merely giving an example of something I think would contribute to humanity. [03:40] Mihasi: ok, so what about this example. A developer gets three completely different suggestions and can only work on one. The first is from someone working on cancer research, the second is from a business owner willing to pay the developer $50,000, the third is from the developers wife. Which suggestion should the developer choose to implement [03:40] So I do not see how that would be irrelevant. But on the other hand, as you're apparently talking about what is more appealing to you as a dev, and not about what is more valid, we don't disagree on that. [03:40] Depends. Does the developer have enough money to support himself and his family? [03:41] Sure [03:41] Then for me the 50k option is out. [03:42] The second choice is a bit more difficult. [03:42] This actually has a pretty easy answer, although it's a bit of a trick question [03:42] Does the suggestion of the cancer researcher something that would make him more effective at his work? [03:43] I assume the answer is: he should work on the one he finds most interesting. [03:44] No, he should work on whatever his wife want's him to :P [03:44] happy wife happy life [03:44] Ah, so it's a joke. :P [03:44] Mihasi: it's a joke, but it's completely valid and here's why. [03:45] Mihasi: Lets say it was just the first two options, and the developer makes the average wage for his area for a developer of his expertise. which should he choose? [03:47] Same question as before: is the suggestion made by the cancer researcher something that would improve his efficiency? [03:47] Mihasi: Sure [03:47] but remember [03:48] This time, it's your average developer spending his free time working on some project [03:48] Heh, this is intersting. [03:49] (that would be the answer ) [03:49] I would make that choice in a heartbeat myself, but I'm still thinking of whether it should apply generally. [03:50] The answer would be he should work on whatever he wants to (which is what you said) [03:50] Yeah, that was what I thought the official answer would be. [03:51] Not my personal opinion. [03:51] you'd pick cancer research? [03:51] According to my -currently utilitarian- way of thinking, the developer should work on those things that make the most people more happy (or less unhappy). [03:52] So yes, cancer research. [03:52] What if it's just a low risk low probability cancer and the business man is working to feed the homeless? [03:53] Then it becomes an even more interesting problem. :D [03:53] Mihasi: it really doesn't. The developer should work on whatever he wants [03:54] Weeeeeell, let's agree to disagree. [03:55] i can understand prioritizing bugs [03:55] Mihasi: why should he be forced to work on the one for the cancer reasearcher just because it affects more people [03:55] bugs or features [03:56] but that is part of overall development process, usually not determined by 1 user [03:56] Because -in my opinion- the world would be a better place if people valued other people's happiness the same as their own. [03:56] thats a very idealistic view of the world that i dont think matches reality unfortunately [03:57] It doesn't. But it's something worth striving for. (Again, in my opinion.) [03:57] Mihasi: let me rephrase, why should the cancer researcher get free work done for him just because he's working on cancer research [03:57] Mihasi: yeah but even if we work toward that goal, we have to be aware of the current situation [03:58] mchelen2, yes, but we're talking about "which option *should* the developer choose in this fictional situation". [03:59] from a personal perspective, if i'm trying to decide between fixing bug A and bug B, and A will affect 2 people and B affects 500 people (even indirectly) i will prioritize B [03:59] this fictional situation never existed in an ideal world, nor a vacuum [03:59] the problem is logistically, how do you determine if that is true? [03:59] tgm4883, because he's working on something that could help a lot of people suffer less. (Again, provided that the feature request is something that would make him more effective in that goal.) [03:59] * nacc_ tries to read scrollback, checks the clock, gives up [04:00] lol [04:00] Mihasi: like how does the dev know if this cancer researcher has any chance of success [04:00] Aha, that's another very interesting question. [04:00] Mihasi: I'm starting to think you'd be all about a "cancer researcher" card that they could just go to places and get free stuff. Walk into a restaurant and hand them the card, free food. Walk into a massage parlor, get a free massage [04:00] Mihasi: or maybe they are a terrible, incompetent researcher who will still fail even if their feature request is completed [04:01] i can agree if you can theoretically quantify all these things, but that is just so far removed from real world constraints [04:01] The original point I was trying to make was why you shouldn't simply shout "cancer research" to try to persuade people. [04:01] nacc_: im just running on fumes at this point :D [04:03] tgm4883, I wonder what the world would look like if people who have could solve cancer wouldn't have to worry about housing, food etc. [04:03] yeah so imho the issue is not whether to prioritize things that help people, but how do you know what will actually help people? [04:04] mchelen2, sure, but that's a different issue and I'm too tired to deal with two issues at once. :P [04:04] tgm4883: or if the people who develop software wouldn't have to worry about housing, food, etc :D [04:04] Mihasi: I wonder what the world would look like if drug companies could only charge a max of $2 per pill [04:04] Mihasi: Honestly, I think I've given up on anything you say being grounded in reality [04:05]