Anybody want to be a project maintainer?
Closed this issue · 23 comments
I haven't been using Sass for a little while so my attention to this library has diminished. I am looking for at least one other person to help maintain it -- preferably an active user of it.
Does anybody want to join in?
I'm happy to pitch in helping out however I don't have availability to maintain this package full time.
Cool! I added you as a collaborator. If you (or any one else) have any ideas about improving the way things are built, releases are done, documentation is made, etc., that would make it easier for someone-other-than-me to do that stuff, feel free to toss out ideas and PRs!
Will do. I'm tend to automate those kinds of tasks. I'll throw together an npm script this weekend to handle releases.
Hey David, I've been using Scut for a few years, and while I'm not sure I would be the best person to judge what goes in / gets modified I can definitely help with updating the docs.
@jonscottclark Thanks!
The library itself has been very stable for quite a while now. So the most useful changes to the repo would be to make it easier to do small, quick deploys to fix bugs and incorporate new features, so the occasional little issue that does pop up can be handled swiftly. Any ideas or PRs around that would be fantastic.
And of course handling those little bug fix and new feature issues when they pop up, if/when you have time.
@davidtheclark: I would be happy to pitch in as well. I am actively using Scut on several large projects and have been evangelizing it to the rest of my team for a long time now. 😄
Cool, @jmmcduffie. I will add you.
So I tried to do a quick v1.3.1 release today following the release checklist. It we relatively smoothly. There were however a couple speed bumps. As collaborators we cannot:
- publish to npm
- publish the gem
- update codepen (I think, the process is undocumented)
@xzyfer: Oh, I'm glad it went relatively smoothly ---- the build is not especially simple, and I set it up a while ago and haven't updated it. Of course anywhere you all want to take the build/site to make it easier, I'm open to ideas.
- I can add one or all of you as npm owners, please just provide your npm usernames!
- I can add one or all of you as gem owners, too. Looks like rubygems want email address!
- I don't think it's possible to add multiple collaborators on a codepen without having PRO status. If one of you wants to be in charge of the codepen library, maybe you can create the library pen and I can update all the others to use it? Or maybe the best way would be if one of you just copied the code into your own account and changed the links in the docs?
@davidtheclark a large part of my job is build tooling an infrastructure so I'm happy to take a look at streamlining things if releases become more frequent.
You can add me as collaborator on this with my GH handle. Email address is my GH handle at gmail.
I don't know much about codepen. I'll look into it.
@davidtheclark: My npm handle is the same as GH, and my email is jmmcduffie (a) me dot com.
I'm not sure what the best course of action is for CodePen. I see that the playground pen is including another pen which actually contains the source. Could that instead point to a file hosted on the GitHub page for this repo?
+1 to @xzyfer on automation.
Hmm. It looks like something may have gone wrong with the build, @xzyfer. The GH page for this repo is broken right now.
Ok I have added both of you as npm and gem owners.
@davidtheclark I don't appear to have access to scut on npm.
Nice catch @jmmcduffie. Fixed.
Oops, I added you to the wrong project! Bonehead. I'll fix it now.
Ok, I see you as collaborators now: https://www.npmjs.com/package/scut
Confirmed. Published 1.3.1 to npm.
Published 1.3.1 to RubyGems 👍
Thanks, @xzyfer!
@davidtheclark, do you think we have enough maintainers to call this issue closed?
Yes. Thanks so much for pitching in!