Lowering the pile of issues on github - Call for Volunteers

[vrms]

@James_Robertson

Would it also not be a good idea to tag/label new features and localization issues as enhancements along with the module? Would make it easier to find them that way when we want to target a release based on a module and enhancements only as an example. Thoughts?

my personal take on this would be:

1. let’s try to stick with the right terms generally (which is 'label', not ‘tag’).
   Why? it’s just crystal clear that way. One of our goals as a Community is to get more people engaged and that includes to educate the inexperienced who can start contributing with simple things and likewise enable coders to focus on more complex tasks. Whether we talk in wrong terms with anyone mistakes are likely to happen and communication will have much more back and forth then necessary (aka: waste of time). I’ll keep mentioning this

2. Let’s keep that labels as defined here for this round (which is already underway since almost a week)

3. Let’s start a separate discussion whether github issues are a good a tool to steer the development process of ERPNExt in general and (if so) how we could make use of githubs labels, milestones & projects to organize that