Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for help maintaining parser-c! #8

Open
tcr opened this issue Jul 6, 2017 · 3 comments
Open

Looking for help maintaining parser-c! #8

tcr opened this issue Jul 6, 2017 · 3 comments

Comments

@tcr
Copy link
Owner

tcr commented Jul 6, 2017

See the blog post on the Rust User's forum for more information.

@tcr tcr added the help wanted label Jul 6, 2017
@birkenfeld
Copy link
Collaborator

I'd be interested. Is there a dedicated communication channel (IRC, gitter, slack) you want to use?

@sanxiyn
Copy link
Collaborator

sanxiyn commented Jul 7, 2017

I want to help. What would be some useful tasks for me to do?

@tcr
Copy link
Owner Author

tcr commented Jul 8, 2017

@birkenfeld @sanxiyn Thank you both! The easiest solution for me to set up was a Gitter room, so I created one and added its badge to the repo: https://gitter.im/parser-c/Lobby

@sanxiyn I'll flesh out more directed/pressing issues and share them in this thread. #3 is a very straightforward task that might be a good introduction to the codebase.

The most high-value task to tackle is analyzing language-c's "test" folder (see https://github.com/tcr/parser-c/tree/master/reference/test) and planning how we can bring this over to the Rust crate. Most of it can be reused wholesale, like the C tests, but there's some support code written in Haskell we may need to port, either with Corollary or manually.

I'll detail some other tasks here shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants