Skip to content

Further support? #25

Closed
parkr opened this Issue Nov 29, 2013 · 9 comments

3 participants

@parkr
Collaborator
parkr commented Nov 29, 2013

Ahoy! We'd like to add TOML configuration file support to Jekyll (jekyll/jekyll#1765) but we're not sure which Ruby parser to use. Is this a library you're willing to continue to support for our use? Do you need any other support to make this parser even more amazing? ❤️

@jm
Owner
jm commented Nov 29, 2013

Help would be awesome! Let me know if you'd like to be added as a collaborator; I'll gladly add whomever!

@dirk
Collaborator
dirk commented Nov 29, 2013

I'm sort of available to continue supporting this too! (Especially if you run into any parser bugs/problems.)

@jm
Owner
jm commented Nov 29, 2013

I need to figure out how to add RubyGems collaborators or owners or whatever it's called. I'll try to do that tomorrow...

@parkr
Collaborator
parkr commented Nov 29, 2013

@jm To add RubyGems collaborators, you'll need to run:

$ gem owner toml --add <rubygems_org_email_of_new_contributor>

This will allow them to push new versions, etc.

I'm not sure I'm the right guy to be responsible for this parser, but I'd be happy to help via bug reports and PRs as we encounter them in usage with Jekyll.

@jm
Owner
jm commented Dec 5, 2013

If you guys could pass your RubyGems e-mail to me (either here or via e-mail), then I'll add you right now!

@parkr
Collaborator
parkr commented Dec 5, 2013

It's the same as my GitHub email.

@jm
Owner
jm commented Dec 5, 2013

Cool, added. I'll you @dirk once you ping me with your e-mail; I tried the GMail I have for you but it no worky. 😄

@parkr
Collaborator
parkr commented Dec 16, 2013

This all shore'd up?

@jm
Owner
jm commented Dec 16, 2013

I think so. You've been added as a maintainer. I haven't heard back from @dirk but he can comment here and I'll him if he wants! 😄

@jm jm closed this Dec 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.