Setup an issue list for contributers

[jaytaph]

For (new) contributors, it would be helpful if there was a list of work that needs to be done. We should add labels to them to give them a sense in how complex and in what area the issue is.

[TheFanatr]

What could be an interesting technique, that I'm fairly certain I've seen used similarly elsewhere, is to just use issue labels in GitHub, and have a link in the project description to a filtered view of them; maybe even set up a board? Not super sure how the former would work on mobile, through the app, though.

[jaytaph]

I think there must be some overview page which shows the current status. Right now, the system consists of a tokenizer that turns a stream of html into tokens, and a parser that will turn those tokens into a node-tree that resembles a DOM tree. The tokenizer seems to function correctly according to the html5 lib tests we can run (there are some issues though, as the tests show). But the parser is a lot more work to finish. I'm currently busy trying to get it running properly so most of the tests will pass (i'm so happy with html5lib-tests!), but since the amount of code and the complexity of the parsing, it takes a long time to get it running properly.

I think that contributers want to get their hands dirty instead of waiting for me to complete this in order to do something, so we might figure out which components we will be needing, and see if we can build those independent from the parser. I'm not sure if this would work as this would need some thinking about architecture of the project, which I currently do not know (yet).

I think one of the main things that I want, is to have a separate gosub-engine which can render dom-tree's to different user agents. Those would be graphical, but could also be textmode (like lynx/elinks). The last one actually might be easier to implement (famous last words).

I can setup some issues I found on the tokenizer, so people can take a look at them. And in the meantime, don't try to laugh too much at the current rust code, as i'm new to this.. so any help in refactoring things are always appreciated.