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

maintainance? #333

Open
igravious opened this issue Jul 2, 2021 · 5 comments
Open

maintainance? #333

igravious opened this issue Jul 2, 2021 · 5 comments

Comments

@igravious
Copy link

Already using Jekyll-Scholar and interested to help out? Please get in touch with us if you would like to become a maintainer!

I would like to become a maintainer.

@inukshuk
Copy link
Owner

inukshuk commented Jul 5, 2021

That's great! In general, the project has been in maintenance-only mode for some time now -- which is fine, I think, though there are some interesting feature proposals/requests scattered around the issue tracker. I'm the original author of the plugin, but I never actively used it myself, so over the years most features were either suggested or contributed by users who've also helped with maintenance tasks, answering questions and so forth.

We don't have a fixed policy around here, but we've pretty much been following the 'open open source' approach, that is you earn write permissions when you make a few useful commits to the repository. I'm always happy to help if you have any questions.

@igravious
Copy link
Author

I've started a Jekyll blog. I used to use a self-hosted Wordpress. Because I program in RoR I decided why not move to Jekyll. I have a couple of academic projects on the go. All my references are in Zotero. I use Better-BibTeX. I figure over the course of the next few years I'll be a doing a lot of scholarly blogging.

Tell me where to start and I'll go from there. The only thing is that I'm not familiar with the test-suite you use, you might bring me up to speed on that?

@inukshuk
Copy link
Owner

inukshuk commented Jul 8, 2021

The test setup is very old, based on the Cucumber tests that Jekyll itself used originally; we use it mostly to catch regressions, because it's otherwise hard to keep track of all the different features or tweaks that have accumulated over the years. If there are any issues with it, it's probably that the dependencies are outdated nowadays.

Cucumber may not be in vogue anymore, but it's a good fit for our purpose because it allows us relatively easily to turn issue reports into tests. The feature DSL should be almost self-explanatory: it's based on a handful of step definitions. It's basically just a lot of pattern matching to set up scenarios (using the 'Given' sentences) and tests (the 'Then' sentences).

@igravious
Copy link
Author

Cool. Gotcha. Okay, tell me where to start and I'll go from there.

@inukshuk
Copy link
Owner

I think the best place to start, if you want to work on something concretely, is to browse the open issues to see if there's anything that interests you.

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

No branches or pull requests

2 participants