3 ms·
A contribution typically implies actual work, not just having talked to the person who made the actual contribution.
by isitmadeofglass 4y ago
A contribution typically implies actual work, not just having talked to the person who made the actual contribution.
- julianlam 4y agoNot according to GitHub, which — unless I'm mistaken — treats opened issues as contributions.
- soperj 4y agoNoticing a bug and filing a report on it is actual work.
- isitmadeofglass 4y agoNoticing a broken window and telling the owner about it is not actual work towards fixing it.
- soperj 4y agoIf the owner has no idea that the window is broken, then it'll never get fixed until this step happens, so yes it is.
- redditor98654 4y agoA product manager that comes up with feature ideas is doing actual work, would you not agree? Even if they themselves do not implement anything.
- just-ok 4y agoWhat? No. Writing a well-spec’d feature request with clear outcome and behavior expectations is work. Just asking, “Wouldn’t it be cool if ____?” is not actual work.
- redditor98654 4y agoIf the feature is simple enough, it is possible to illustrate it in a few sentences. I am just speculating at this point, but if the discussion went like "hey, I think in Markdown, if the users enters a code-block, we should treat everything literally and not escape anything. This way users can just copy-paste code and expect it to render exactly like the raw text". This is clearly spec'd and has clear expectations on how it should behave. No implementation details of course which you wouldn't expect from a product manager in most cases as well.