Skip to content
New issue

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

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

Already on GitHub? # to your account

Maintenance Status #555

Open
eFrane opened this issue Aug 21, 2020 · 1 comment
Open

Maintenance Status #555

eFrane opened this issue Aug 21, 2020 · 1 comment

Comments

@eFrane
Copy link

eFrane commented Aug 21, 2020

I would like to use sassdoc for a long-living project but am a bit taken back by the lack of commits in the past few months. If there were no open issues or unmerged approved pull requests, I wouldn't worry. It does happen that stable tooling does not require many commits for longer stretches of time. This however is not the case, which begs the question:

What is the maintenance status of sassdoc? Is it actively worked on or is it more or less left to slowly rot in it's current state with minor improvements?

Last but not least: This is an awesome project and it would be sad to see it die, going the apparent route that pretty much all (S)CSS documentation tools are currently going.

@pascalduez
Copy link
Member

Hi @eFrane,

that's a legit question.
Out of a team of four I'm more or less the last one trying to maintain at the very minimum the project (security fixes, reviewing and merging PRs, etc.). But some of those tasks takes time, especially merging PRs, major dep upgrades, as we need to make sure it doesn't break things.
SassDoc 2 is pretty stable though, so it basically doesn't require a bunch of maintenance per se and can be used without worries.

I had quite some ideas for a 3 version, like using a third party parser like PostCSS or other, which would remove us this part to maintain. But time flies, life things, etc. Also not using it anymore on projects so lost a bit of motivation to be honest.

We would be very happy to see new people showing interest and investing time in it though, and would happily provide directions.
It could all start with reviews, updates, triaging, improving tests, etc.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

2 participants