search

ericpaulbishop / redmine_git_hosting

A ChiliProject/Redmine plugin which makes configuring your own git hosting easy.
186 stars 37 forks source link

Add tags for issues #116

Open rcross opened 13 years ago

rcross commented 13 years ago

I was trying to figure out why some of the issues I'd raised (and seen others raise) were closed out so fast and I happened to come across this comment from Eric - https://github.com/ericpaulbishop/redmine_git_hosting/issues/98#issuecomment-2312646

It basically says that he closes all feature requests unless they come with code attached. While Eric can manage things however he sees fit of course, I think it is at a minimum quite discouraging to potential contributors. Especially since there doesn't really seem to be any notes anywhere that this is the policy here and is not the expected behaviour from most active open source projects.

Since I can't speak for anyone else, I can just say that when I posted a couple issues (one I thought a legitimate concern and another reasonable feature request) and was subsequently dismissed very quickly, I felt very unwelcome even after I later posted code towards one of the issues.

Can I propose that a tag is created for "feature request" (and probably a "bug report" tag too) so that those issues can be tagged appropriately instead of just closed without regard? This would make discussion of these issues more acceptable and might encourage more code to be produced. This would also prevent a potential fork that is willing to accept feature requests to fragment the attention on this valuable project.

It might also be helpful, regardless if issues tagged or not, for there to be some message somewhere that feature requests are only considered once they have code attached. Most probably the wiki or in the readme somewhere.

rcross commented 13 years ago

I'll also add that a milestone of "Feature backlog" or "Unplanned Feature requests" could also be used as another way of marking issues in an informative way for people.