$12256 / $11500
I noticed you have added in a few labels for the GitHub issues. Currently you have "Bug" (which is self-explanatory), "Feature" and "Brainstorming."
I classified the only bug in the issue list as such. But I was wondering what you consider features and what you consider brainstorming. I assume "Feature" is an engine feature and "Brainstorming" is a gameplay feature?
Perhaps adding the label "Engine" or "Core" would be good. Then you could separate it out this way: Bug (code that doesn't work properly), Engine (coding that applies toward making/cleaning up the flare engine), Feature (coding that adds additional gameplay or configuration options), and Brainstorming (ideas that can be considered for later implementation).
Or maybe I'm thinking of things too hard and you meant the labels used a different way.
This website's content is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
I haven't really messed with the labels. No current plans for them. Maybe one of the other project contributors edited them?
If most of the entries will be programming tasks, then maybe it just makes sense to mark those that are different, e.g. Bugs. Maybe I can add an Art tag too for people who want to help there.
Hrm... maybe I just noticed it for the first time recently. (I grow increasingly impressed with GitHub!) It would be kind of nice to distinguish non-standard tasks, such as art or bugfixes from the rest, however.
I added these labels Saturday or Monday, to try them and because I want to add a bug report (but I don't had the time).
I've found the idea on the lendrick/Last-Escape issues list.
Of course, the list was just a first try. By the way, I had to stop while searching the right word for rewriting or reengeenering part of code. "Rewrite" is understandable?
I think "Refactor" is the term you want. That would be a good tag, as right now it's a common task.
Yes, it was the one I was searching! :)