by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Nicholas C. Zakas
    @nzakas
    This is less of a question/actionable item and more just a PSA, but with the planned release of ESLint v7.0.0 this coming Friday, I wanted to touch base about also merging eslint/espree#429 and running an Espree release.
    Kai Cataldo
    @kaicataldo
    Just wanted to touch base since we hadn't discussed it
    The PR in question drops support for Node 8 in Espree
    Nicholas C. Zakas
    @nzakas
    I'm :+1: for that. I'd rather merge and release it today so tests tomorrow are run against the new version
    Brandon Mills
    @btmills
    I'll put it in the notes as a PSA and note that @kaicataldo opened the PR and the other three of us have all approved it
    Nicholas C. Zakas
    @nzakas
    Sounds good
    Next item:
    (from me)
    I’d like to discuss how we can support some of our dependencies that have Open Collective pages.
    I forwarded the email about Ajv looking for sponsorship
    I'd love to start giving back to some of our first-level dependencies if they are seeking funding. Obviously we don't have enough money to be providing big grants, but I think supporting packages like Ajv with some nominal amount would be good.
    Thoughts?
    Toru Nagashima
    @mysticatea
    :+1:
    Brandon Mills
    @btmills
    This seems compatible with our sponsors' desire to support ESLint's development - the dependencies are part of what makes ESLint possible
    Kai Cataldo
    @kaicataldo
    I'm all for figuring how to do this, even if we're not able to give much. As part of our dedication to sustainable open source practices, it would be great to set an example for other projects to follow.
    Nicholas C. Zakas
    @nzakas
    Here's what I'd like to suggest: can we start off by donating $100/month to Ajv and then look for which other of our dependencies are looking for funding? Assuming we find more and donate to them, we can then do a blog post about it.
    Kai Cataldo
    @kaicataldo
    Could we budget a certain amount that we dedicate to sponsoring dependencies with? We could start with a budget of $100.
    In practice it's the same thing, but I think it's a bit of a different take in that it's not budgeted for a specific project.
    Brandon Mills
    @btmills
    I just tried npm fund on the repository to see who else is looking for funding, but it's almost empty so won't be much help
    Nicholas C. Zakas
    @nzakas
    We can do that. I'd suggest we start with a budget of $500/month, though, until we know how many dependencies we want to support.
    No sense in doing what Congress does and just keep increasing the budget every time we find something to spend money on :)
    Kai Cataldo
    @kaicataldo
    :laughing:
    That seems like a good starting point to me.
    Brandon Mills
    @btmills
    Ha. $500/mo seems like a decent starting point
    Nicholas C. Zakas
    @nzakas
    FWIW, here are our dependencies that are seeking funding: https://backyourstack.com/eslint
    @mysticatea are you good with a $500/month budget for supporting our dependencies?
    Toru Nagashima
    @mysticatea
    Sounds good to me
    Nicholas C. Zakas
    @nzakas
    Okay, we've resolved to setup a budget item of $500 for sponsoring other open source projects, starting with Ajv at $100/month.
    Here's the budget item: eslint/finances#9
    Last and certainly not least, we're planning on releasing v7.0.0 tomorrow. Any blockers or concerns?
    Brandon Mills
    @btmills
    I've been using it and haven't come across any issues since the rc :+1:
    Kai Cataldo
    @kaicataldo
    None from me. I'll plan to merge that Espree PR and run a release after this meeting. I'm also coordinating with the OpenJS Foundation for a marketing blast
    I'll share the Google Doc privately if any of you would like to see what they're planning.
    Toru Nagashima
    @mysticatea
    I don't have concerns.
    Nicholas C. Zakas
    @nzakas
    Just to confirm: @kaicataldo you're planning on putting together the blog post with all of the changes since the first alpha of v7.0.0?
    Kai Cataldo
    @kaicataldo
    Yes, I was planning to manually do it. Anyone have any better ideas for accomplishing this?
    For future releases, I'd like to update the release job
    Nicholas C. Zakas
    @nzakas
    Nope. I used to do it manually, too.
    Kai Cataldo
    @kaicataldo
    Cool :+1:
    Nicholas C. Zakas
    @nzakas
    I'd like to completely rethink how we do major releases in the future. This was too painful to repeat. :)
    But that's a topic for another day
    Brandon Mills
    @btmills
    There might be a way to modify the release script. I'll take a look after the meeting and PR eslint-release if I find anything
    Nicholas C. Zakas
    @nzakas
    Are there any other topics anyone would like to discuss?
    Kai Cataldo
    @kaicataldo
    None from me, but looking forward to getting v7 out the door so we can start prioritizing some other things! And appreciate all the hard work from everyone to help get this out the door.
    Nicholas C. Zakas
    @nzakas
    Okay, then I think we can adjourn early. Thanks everyone!
    Kai Cataldo
    @kaicataldo
    Thank you :wave:
    Brandon Mills
    @btmills
    :wave: Looking forward to release tomorrow!
    Toru Nagashima
    @mysticatea
    Thank you :wave:
    Brandon Mills
    @btmills
    Meeting notes: eslint/tsc-meetings#176
    Nicholas C. Zakas
    @nzakas
    Reminder: We've moved everything to Discord. Please use the tsc-meetings channel in Discord going forward