Roadmap by using milestones and issue labels

[redtide]

This is just an idea that comes to my mind, not really an issue/feature request.
I think it could be nice to mark issues with labels, for example the requested widgets with a new feature request label, then organize the ones with more priority (bugs and "must have" features) to be part of some milestone (next release).
This to have some roadmap for the project; maybe other than make explicit its progress could attract some contribution?

[tiagobonetti]

Maybe a good first issue tag would help some lurkers to become contributors.

[Xeverous]

I would also support such idea. Only accounts with the write access to the repository can edit labels, however recently GitHub added issue templates so new issues can be automatically labeled when they are created.

[djowel]

Splendid idea. At first glance when I skimmed over my inbox, I thought you wanted a Roadmap document, which I think is a good idea and will give some structure and reveal priorities, etc., not only on 'issues' here, but for my future plans as well. I know @Xeverous complained about not knowing my plans many times :-), and I've been a bit uncommunicative and even undisciplined in that area. I think it's best to start with such a Roadmap document, taking into consideration the 'issues' here. Then, we can tag the issues based on that.

[redtide]

Reading again myself it seems I wasn't clear about what I meant with milestones, for some automated task, I suppose it would work also as roadmap if tasks are made using issues?

[djowel]

Reading again myself it seems I wasn't clear about what I meant with milestones, for some automated task, I suppose it would work also as roadmap if tasks are made using issues?

Yeah, I realized that later after reading this post again. I'm doing some cleanup and inspecting the code, wanting to see where we are at a high level. I'll see what I can do, maybe we can target 0.9 after I collect the TODO list.

[redtide]

I wonder if I can close this, since there are #216 #217 and #219? There is also to consider the proposed good first issues and issue templates (@Xeverous, you mean this one, right?).

[Xeverous]

Yes, I meant exactly this feature. It has 1 significant advantage: issue templates can have preset labels but normally users who create issues (without write access to the repo) can not set labels.

[djowel]

Closing this now. I prepared #229 for this purpose. Yes. also #216 #217 and #219.