this is just a dev running into the issue of managing project expectations. it doesnt sound like his project has any sort of roadmap, and hes upset that people are curious if he cares to keep extending his work.
how dare they. just manage those expectations in your documentation, its really that simple. you can then point to it at any yocal failing to read it.
Also, you don’t need to put every fun little programming thing you decided to do out into public. The open source space is cluttered with half-assed, unfinished, and abandoned projects. If you’re not serious about maintaining it, just keep it to yourself so we have less chaff to wade through when looking for a given type of program.
this is just a dev running into the issue of managing project expectations. it doesnt sound like his project has any sort of roadmap, and hes upset that people are curious if he cares to keep extending his work.
how dare they. just manage those expectations in your documentation, its really that simple. you can then point to it at any yocal failing to read it.
Also, you don’t need to put every fun little programming thing you decided to do out into public. The open source space is cluttered with half-assed, unfinished, and abandoned projects. If you’re not serious about maintaining it, just keep it to yourself so we have less chaff to wade through when looking for a given type of program.
I disagree. Even unfinished or abandoned projects can be helpful to others.
Just mark it as “WIP”, “unfinished” or “abandoned” (depending on whether you consoder coming back to it), but let the code still be available.
If someone (like you) searches for actively maintained, fully-featured projects, they can dismiss your project the moment they see that term.