ProcessWire "issues" labeled as "enhancement" on Github

[ceberlin]

Hi, after looking at the 300 open "issues" on Github, it turns out that a lot of them, including some of mine, are labeled "enhancement" / "feature request".

To get the increasing number of issues down there (which might give a wrong impression on how well maintained PW is), and to do sort of a cleanup I was planning to set all of my "issues" which are labeled "enhancement"/"feature request" as closed.

I am assuming that the idea was either good enough and had been recognized for an enhancement consideration and thus stored in a to-do list somewhere else, or the the idea was not good enough and did not survive.

In either case, an "issue" like this,does not need to be open forever, imho. Is closing it the best way to deal with it - or should we leave the step to Ryan (or anyone maintaining this)?

(Also there are many "fixed" / "completed" issues that could be closed eventually.)

[ryan]

I was actually thinking of converting all feature request/enhancement issues to something in the PW website (powered by PW pages). Something like the sites directory, with the ability to "like" requests, so that the most requested ones could rise to the top and get more focus. This would also get them out of GitHub, so the focus there can be on issue reports. Though I think it's good to still submit feature requests at GitHub, but I would just move them to the more dedicated system and close them out there once that's done. 

[cstevensjr]

A great idea, Ryan!

[apeisa]

https://huboard.com/ might be easy way to go?

[Pete]

@ryan - could also easily tie it in with forum user logins to prevent someone skewing the results.

@apeisa - but $24 whole dollars? That's like... 4 pints of beer Seriously, that does look cool but maybe slight overkill? I guess it's down to whether Ryan has time to code a PW solution. We could also probably do a small part of what huboard does and hook into the Github API if we wanted to go that far with it - pull in a list of issues, convert them to requests locally on the PW system and have it close them out on Github with a link to relevant item on the PW wishlist perhaps? Or that could be done easily manually too, but if there are a lot of feature requests, clicking a button that does it all for you might not be a bad idea.

Lots of options, it's just down to time and effort. The forum user login code for the dev directory is pretty simple and more or less ready to re-use for something like this too if required.

[apeisa]

Pete, it's free for public repos. It's just another way to view and organize GitHub issues.

[ceberlin]

The good thing of having it here intead of GitHub is that there could be it's own fine grained system for flagging, like in a project management system, so the people know the current status and where a voting would have an effect. 

- planned for this dev version cycle

- panned for after next mayor update

- Maybe sometimes

- Not currently planned

- Not planned (never)

- Done/Closed (hidden?)

(Maybe closed/done requests could be hidden and only shown on request)

Just thinking...

[Craig]

What about Trello instead of or as well as?

Some useful links:

• Going Public! Roadmapping With A Public Trello Board
• Software Developmentin Usage Examples

[Peter Knight]

A native PW system would be great and a great showcase too. Having used Trello in the past for MODX I wasn't convinced it brought any value.

Actually - I just tried to login to the MODX Trello account and it's been closed. 

[Beluga]

A Bugzilla clone created using PW would be nice Then there could be a true quality assurance team with permissions to manipulate report metadata & status.

I guess the advanced search and getting it to work fast with complex queries would be the most work.

Could be way better than Bugzilla, though, if PW selectors could be used to construct queries.