4 ms·

Well, at least one downvote indicates that this is not the right way to proceed. How about a little feedback to go with that? Thank you in advance.

icebraining 12y ago
Well, I didn't downvote you, but you're essentially asking for free work. If you want contributions, you need to contribute yourself first, usually by writing some code (or paying someone to write if you cannot) and publishing it. A basic version that doesn't work well yet is OK, an empty repo isn't.
- daveloyall 12y ago
  Ok, I can see that point of view. The repo isn't technically empty. :) I put a bit of work into describing the requirements of the proposed software and making suggestions how to proceed. Basically I was volunteering to tend a garden, not just suggesting that someone plant one. I've just added `remover.go` package main import "fmt" func main() { fmt.Println("Limited functionality, WIP.") //Display introduction message and prompt user if they'd like to continue. //Determine if current process has permissions to make system changes //IF yes continue //IF no initiate appropriate OS call to prompt the user to elevate // OR advise user how to quit and start over with perms. //TODO figure out if we're on Mac or Windows //IF Windows... // Look for process CCNet.exe //Criteria: it's insufficient to match the name. Checksum? Publisher name? Install path? //If found //var installLocation string = ?? //record the install location. //terminate process // Look in these directories for installation //C:\Program Files\WinSS\Book //installLocation //defined above //IF found //Delete //IF not found //Prompt user to offer a suggestion // Look in this directory for key log files //C:\Windows\WinCCNet //IF found //Prompt for delete //If not found //Prompt user to offer a suggestion // Remove the Add/remove programs entry // Remove auto-start keys //TODO Where are they? //IF Mac... // ??? } As you can see, it is a work in progress.
  - cmdrfred 12y ago
    If I wanted someone to give me requirements for software that I'm making on my own free time, I'd get paid for it.
    - daveloyall 12y ago
      So, in this case, you already know the requirements, right? Does that ease the blow of being told what to do? I mean, also I assure you that I'm not trying to tell you what to do. I presume that more or less the same items would appear on the TODO list if you told me what to do. I can and will give up on this whole idea if it's truly a bad idea. But, lets look at some alternative timelines here. Suppose that I'd immediately hunkered down and started writing an uninstaller in isolation. Note: this is not something I'd finish today. Thus: by the time I had a working or semi-working uninstaller, the world would have moved on. By starting the work in public, I hoped to avoid that eventuality not just for myself but also for anyone else who might otherwise have walked that path. (Experts who could finish the software quickly don't need the suggestion, of course.) And, by starting the work in public, I hoped to reduce the cost-of-entry for others. I mean, I don't know about you, but I'd rather start with a couple of kb of skeleton than an empty repo.
      - cmdrfred 12y ago
        I likely can make one in a few hours, if I made it I'd put it on my blog. What is your contribution to the project? Why do you even need to be involved?
        daveloyall 12y ago
        I don't need to be involved and I hereby promise to update my README to point at your blog if you do that. Well assuming that you do a good job. :) At the end of the day my goals are these: * Help those users * Educate a bunch of police depts. * Promote the EFF.
        cmdrfred 12y ago
goblin89 12y ago
(I didn't downvote.) Think why would anyone be motivated to contribute to your repository, as opposed to creating a new one from scratch under one's own username. Imagine you got a first pull-request, with a Go app. Then another, with a bunch of working Python scripts. Then yet another, providing a complete Python app packaged on PyPI but somewhat broken. What will you do? It doesn't matter: x-1 of x people have just wasted their time writing code that will end up under your GitHub username anyway. Yes, it has to do with reputation management, too. You'd have a project under your GitHub name written completely by other people. The way it works currently, people will tend to see it as your project. You'll be free to claim it in your portfolios and resumes. Meanwhile, creating a GitHub repository isn't a hard task, and your README contents is basically what normally happens in one's head as one designs and writes the software. In addition, and that's what may have actually caused the downvotes IMO, there's something not enjoyable about the idea of stumbling across a bunch of orders issued by a random person in writing to undefined audience, which you unexpectedly find yourself part of, by virtue of reading those orders. Your requirements, without any code, sure looked like such orders though. It wouldn't be a problem be there a big name or much publicity associated with your project (and the resulting network effect), but without that there's no challenge and no meaningful payoff. * * * Things would be different if your repo had a well-thought-out skeleton consisting of some (even if completely no-op) units and a (failing but thorough) test suite, tied up to Travis CI and what not. That would increase motivation as it would eliminate quite a bit of actual friction associated with starting a new project. Arguably one of the hardest parts would be already done—us lazy programmers will be able to look at the units, the tests, and figure out how to make it work. No need to even clone, just edit some files via GitHub web interface.
- daveloyall 12y ago
  > Any way, two of three people have just wasted their time writing code When I first imagined this project, I didn't picture it taking all day, from start to finish. An uninstaller doesn't do much. > The way it works currently, people will tend to see it as your project. Hm. Hold on. https://github.com/ComputerCOP-OpenRemover/ComputerCOP-OpenRemover https://github.com/ComputerCOP-OpenRemover/ComputerCOP-OpenR... Yes? > It wouldn't be a problem be there a big name or much publicity associated with that My end goal is for my local police department to pass this uninstaller out to citizens, in a similar manner to how they passed out the installer. That will never happen without the support of a big name. I'm hoping the EFF will take an interest (I've already put my name on their volunteer list some time ago). > humans don't enjoy the idea of being given orders from [random] people. Your requirements sure looked that way, though. ...I'm sorry. :( I'll look back over the README for use of the imperative voice. ...Honestly, I've heard this feedback once or twice before AFK and I wasn't sure how to change then, either. Thank you for your candid feedback, goblin89.

icebraining 12y ago

Well, I didn't downvote you, but you're essentially asking for free work. If you want contributions, you need to contribute yourself first, usually by writing some code (or paying someone to write if you cannot) and publishing it. A basic version that doesn't work well yet is OK, an empty repo isn't.

daveloyall 12y ago
Ok, I can see that point of view. The repo isn't technically empty. :) I put a bit of work into describing the requirements of the proposed software and making suggestions how to proceed. Basically I was volunteering to tend a garden, not just suggesting that someone plant one. I've just added `remover.go` package main import "fmt" func main() { fmt.Println("Limited functionality, WIP.") //Display introduction message and prompt user if they'd like to continue. //Determine if current process has permissions to make system changes //IF yes continue //IF no initiate appropriate OS call to prompt the user to elevate // OR advise user how to quit and start over with perms. //TODO figure out if we're on Mac or Windows //IF Windows... // Look for process CCNet.exe //Criteria: it's insufficient to match the name. Checksum? Publisher name? Install path? //If found //var installLocation string = ?? //record the install location. //terminate process // Look in these directories for installation //C:\Program Files\WinSS\Book //installLocation //defined above //IF found //Delete //IF not found //Prompt user to offer a suggestion // Look in this directory for key log files //C:\Windows\WinCCNet //IF found //Prompt for delete //If not found //Prompt user to offer a suggestion // Remove the Add/remove programs entry // Remove auto-start keys //TODO Where are they? //IF Mac... // ??? } As you can see, it is a work in progress.
- cmdrfred 12y ago
  If I wanted someone to give me requirements for software that I'm making on my own free time, I'd get paid for it.
  - daveloyall 12y ago
    So, in this case, you already know the requirements, right? Does that ease the blow of being told what to do? I mean, also I assure you that I'm not trying to tell you what to do. I presume that more or less the same items would appear on the TODO list if you told me what to do. I can and will give up on this whole idea if it's truly a bad idea. But, lets look at some alternative timelines here. Suppose that I'd immediately hunkered down and started writing an uninstaller in isolation. Note: this is not something I'd finish today. Thus: by the time I had a working or semi-working uninstaller, the world would have moved on. By starting the work in public, I hoped to avoid that eventuality not just for myself but also for anyone else who might otherwise have walked that path. (Experts who could finish the software quickly don't need the suggestion, of course.) And, by starting the work in public, I hoped to reduce the cost-of-entry for others. I mean, I don't know about you, but I'd rather start with a couple of kb of skeleton than an empty repo.
    - cmdrfred 12y ago
      I likely can make one in a few hours, if I made it I'd put it on my blog. What is your contribution to the project? Why do you even need to be involved?
      - daveloyall 12y ago
        I don't need to be involved and I hereby promise to update my README to point at your blog if you do that. Well assuming that you do a good job. :) At the end of the day my goals are these: * Help those users * Educate a bunch of police depts. * Promote the EFF.
        cmdrfred 12y ago

goblin89 12y ago

(I didn't downvote.) Think why would anyone be motivated to contribute to your repository, as opposed to creating a new one from scratch under one's own username. Imagine you got a first pull-request, with a Go app. Then another, with a bunch of working Python scripts. Then yet another, providing a complete Python app packaged on PyPI but somewhat broken. What will you do? It doesn't matter: x-1 of x people have just wasted their time writing code that will end up under your GitHub username anyway. Yes, it has to do with reputation management, too. You'd have a project under your GitHub name written completely by other people. The way it works currently, people will tend to see it as your project. You'll be free to claim it in your portfolios and resumes. Meanwhile, creating a GitHub repository isn't a hard task, and your README contents is basically what normally happens in one's head as one designs and writes the software. In addition, and that's what may have actually caused the downvotes IMO, there's something not enjoyable about the idea of stumbling across a bunch of orders issued by a random person in writing to undefined audience, which you unexpectedly find yourself part of, by virtue of reading those orders. Your requirements, without any code, sure looked like such orders though. It wouldn't be a problem be there a big name or much publicity associated with your project (and the resulting network effect), but without that there's no challenge and no meaningful payoff. * * * Things would be different if your repo had a well-thought-out skeleton consisting of some (even if completely no-op) units and a (failing but thorough) test suite, tied up to Travis CI and what not. That would increase motivation as it would eliminate quite a bit of actual friction associated with starting a new project. Arguably one of the hardest parts would be already done—us lazy programmers will be able to look at the units, the tests, and figure out how to make it work. No need to even clone, just edit some files via GitHub web interface.

daveloyall 12y ago
> Any way, two of three people have just wasted their time writing code When I first imagined this project, I didn't picture it taking all day, from start to finish. An uninstaller doesn't do much. > The way it works currently, people will tend to see it as your project. Hm. Hold on. https://github.com/ComputerCOP-OpenRemover/ComputerCOP-OpenRemover https://github.com/ComputerCOP-OpenRemover/ComputerCOP-OpenR... Yes? > It wouldn't be a problem be there a big name or much publicity associated with that My end goal is for my local police department to pass this uninstaller out to citizens, in a similar manner to how they passed out the installer. That will never happen without the support of a big name. I'm hoping the EFF will take an interest (I've already put my name on their volunteer list some time ago). > humans don't enjoy the idea of being given orders from [random] people. Your requirements sure looked that way, though. ...I'm sorry. :( I'll look back over the README for use of the imperative voice. ...Honestly, I've heard this feedback once or twice before AFK and I wasn't sure how to change then, either. Thank you for your candid feedback, goblin89.