Bumps glob-parent from 5.1.1 to 5.1.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/gulpjs/glob-parent/releases">glob-parent's releases</a>.</em></p> <blockquote> <h2>v5.1.2</h2> <h3>Bug Fixes</h3> <ul> <li>eliminate ReDoS (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/36">#36</a>) (<a href="https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366">f923116</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/gulpjs/glob-parent/blob/main/CHANGELOG.md">glob-parent's changelog</a>.</em></p> <blockquote> <h3><a href="https://github.com/gulpjs/glob-parent/compare/v5.1.1...v5.1.2">5.1.2</a> (2021-03-06)</h3> <h3>Bug Fixes</h3> <ul> <li>eliminate ReDoS (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/36">#36</a>) (<a href="https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366">f923116</a>)</li> </ul> <h2><a href="https://www.github.com/gulpjs/glob-parent/compare/v5.1.2...v6.0.0">6.0.0</a> (2021-05-03)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>Correct mishandled escaped path separators (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/34">#34</a>)</li> <li>upgrade scaffold, dropping node <10 support</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Correct mishandled escaped path separators (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/34">#34</a>) (<a href="https://www.github.com/gulpjs/glob-parent/commit/32f6d52663b7addac38d0dff570d8127edf03f47">32f6d52</a>), closes <a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/32">#32</a></li> </ul> <h3>Miscellaneous Chores</h3> <ul> <li>upgrade scaffold, dropping node <10 support (<a href="https://www.github.com/gulpjs/glob-parent/commit/e83d0c5a411947cf69eb58f36349db80439c606f">e83d0c5</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gulpjs/glob-parent/commit/eb2c439de448c779b450472e591a2bc9e37e9668"><code>eb2c439</code></a> chore: update changelog</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/12bcb6c45c942e2d05fc1e6ff5402e72555b54b6"><code>12bcb6c</code></a> chore: release 5.1.2</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/f9231168b0041fea3f8f954b3cceb56269fc6366"><code>f923116</code></a> fix: eliminate ReDoS (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/36">#36</a>)</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/0b014a7962789b2d8f2cf0b6311f40667aecd62c"><code>0b014a7</code></a> chore: add JSDoc returns information (<a href="https://github-redirect.dependabot.com/gulpjs/glob-parent/issues/33">#33</a>)</li> <li><a href="https://github.com/gulpjs/glob-parent/commit/2b24ebd64b2a045aa167c825376335555da139fd"><code>2b24ebd</code></a> chore: generate initial changelog</li> <li>See full diff in <a href="https://github.com/gulpjs/glob-parent/compare/v5.1.1...v5.1.2">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps normalize-url from 4.5.0 to 4.5.1. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/sindresorhus/normalize-url/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps normalize-url from 4.5.0 to 4.5.1. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/sindresorhus/normalize-url/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

About You

Your Name: Brittany Walker

Twitter handle (optional): https://twitter.com/musicalwebdev

The best way to reach out to you: Twitter or here in Github

A quick bio: Brittany Walker is a software engineer and avid musical theater fan who loves loves creating fun, quirky projects that will help others learn how to code. She is a Front End Lead for Women Who Code DC, a DC Instructor for Thinkful and Co-Founder of What the CSS?!.

Your Talk

Title: Intro to Git and Github: Make Your First Pull Request 💖

What your talk is about: In this workshop, you will learn about Git and Github, some of the most popular version control tools. We will cover the command line, commonly used Git commands and how you can utilize Git and Github to manage your own projects and to collaborate with others. You will be walked through step-by-step on how to contribute to EmojiScreen, an open-source project created specifically for those wanting more practice using Git and Github.

By the end of this event, everyone will leave with a foundational knowledge of Git and Github and will have made a contribution to a real project!

How long will your talk be?

• [ ] 5-15 minutes (lightning talk)
• [ ] 20-30 minutes
• [ ] 30-45 minutes
• [x] 60 minutes or more

Meta

Do you need help crafting your talk?

• [ ] Yes
• [x] No

About You

Your Name: Matt Schaar

Twitter handle (optional): mattschaar

The best way to reach out to you: Email! ([email protected])

A quick bio: 15+ years of experience in a variety of technical, customer-facing, and marketing roles. I've led initiatives ranging from technical design to user growth to community programs, all while building critical relationships with product users.

I spend a lot of time thinking about a few topics: How technology can be a driving force for positive social change; How to speak authentically to developer communities; And, how to run incredulous distances without getting bored.

Your Talk

Title: Product Marketing 101: how to make marketing not terrible

What your talk is about: Developers want their products to be used - it foments feedback, which foments better products, which foments happier users, and so on. But how do you connect with the humans you want to use your product? That's where product marketing comes in - and during this talk, you'll learn how to best leverage it to connect your products to the people that will benefit from them.

How long will your talk be?

• [ ] 5-15 minutes (lightning talk)
• [ ] 20-30 minutes
• [x] 30-45 minutes
• [ ] 60 minutes or more

Meta

Do you need help crafting your talk?

• [ ] Yes
• [x] No

About You

Your Name: Satvik Pendem

Twitter handle (optional): https://twitter.com/satvikpendem

The best way to reach out to you: Email at satvik dot pendem at gmail.com

A quick bio: Hi, I currently work for a large company in DC doing primarily machine learning work. I also work on the side doing web dev side projects and consulting for startups and other companies.

Your Talk

Title: Interactive SVG Animations using CSS

What your talk is about: The talk will be about how to use SVGs in your website and webapp and animate them with only CSS, no external libraries such as GSAP (which are good but can be heavy for simple animations). As well, the talk will also show how to embed interactivity within SVGs while also using pure CSS, and perhaps minimal JS.

How long will your talk be?

• [ ] 5-15 minutes (lightning talk)
• [X] 20-30 minutes
• [ ] 30-45 minutes
• [ ] 60 minutes or more

Meta

Do you need help crafting your talk?

• [X] Yes
• [ ] No

About You

Your Name: Sam Brown

Twitter handle (optional): SamuelBrownIV

The best way to reach out to you: [email protected]

A quick bio:

Sam has been working in IT software delivery for the past 17 years as a Java developer, operations manager, startup product architect and Continuous Delivery consultant. Sam is the co-founder and organizer of the DC Continuous Delivery meetup and the founder and organizer of the NOVA Kubernetes meetup. Sam’s passion is helping to optimize the software delivery process to help teams delivery high-quality software applications as quickly as possible through automation. He believes that building software should be enjoyable for the entire team and can only be achieved when a team works effectively together.

Your Talk

Title: Continuous Delivery on Kubernetes with GitOps

What your talk is about:

Will demonstrate a proven Cloud-Native Continuous Delivery approach that takes advantage of open-source tooling, and Kubernetes scalability, to build and deploy cloud-native applications. It will highlight an opinionated, yet flexible approach to integrating all the common continuous delivery tools - that you’re most likely already familiar with - to create a fast, secure and predictable continuous delivery solution for containers on Kubernetes.

• Codified build pipelines with quality ensured at all stages.
• Utilizing “GitOps” to ensure K8s cluster and source repository parity.
• Shift-left security including secure coding checks, dependency scanning and image vulnerability scanning BEFORE deployment(s).
• Scalable build workers providing on-demand pipeline execution with no queueing.

How long will your talk be?

• [ ] 5-15 minutes (lightning talk)
• [ ] 20-30 minutes
• [X] 30-45 minutes
• [X] 60 minutes or more

Meta

Do you need help crafting your talk?

• [ ] Yes
• [X] No

About You

Your Name: Sean Killeen

Twitter handle (optional): sjkilleen

The best way to reach out to you: E-mail ([email protected])

A quick bio: Originally from the Philadelphia area, Sean has 15+ years of experience solving problems as an IT professional and developer for commercial, non-profit, and federal clients. He's currently the .NET Specialty Lead at Excella Consulting -- he highly recommends you check them out. He recently served on a modernization project that industry analysts called "more complex than the moon landing". He also servers as a co-trainer for Excella's Agile Testing & Automation and Agile Engineering courses. Aside from loving his work way too much, there's a good chance he's enjoying/stressing about being a new homeowner, sipping great beer, exploring the Arlington area, or singing somewhere. You can find him on Twitter at @sjkilleen or blogging not nearly often enough at SeanKilleen.com. He doesn't bite; say hi!

Your Talk

Title: An Introduction to Graph Databases in .NET with Neo4j

What your talk is about: Modern .NET development shops are fast discovering that tables & rows aren’t the only way to store data. In this talk, I introduce .NET developers to the advantages of graph databases using Neo4j. You’ll learn how graph databases differ from traditional SQL DBs, when it makes sense to use a graph database, and what the advantages are. We’ll also work through an example project to get a feel for some of the concepts, and sprinkle in a littler Docker goodness for some added fun.

How long will your talk be?

• [ ] 5-15 minutes (lightning talk)
• [ ] 20-30 minutes
• [x] 30-45 minutes
• [x] 60 minutes or more

Meta

Do you need help crafting your talk?

• [ ] Yes
• [x] No

About You

Your Name: Sean Killeen

Twitter handle (optional): sjkilleen

The best way to reach out to you: E-mail ([email protected])

A quick bio: Originally from the Philadelphia area, Sean has 15+ years of experience solving problems as an IT professional and developer for commercial, non-profit, and federal clients. He's currently the .NET Specialty Lead at Excella Consulting -- he highly recommends you check them out. He recently served on a modernization project that industry analysts called "more complex than the moon landing". He also servers as a co-trainer for Excella's Agile Testing & Automation and Agile Engineering courses. Aside from loving his work way too much, there's a good chance he's enjoying/stressing about being a new homeowner, sipping great beer, exploring the Arlington area, or singing somewhere. You can find him on Twitter at @sjkilleen or blogging not nearly often enough at SeanKilleen.com. He doesn't bite; say hi!

Your Talk

Title: Modernizing your .NET Application – the Time is Now

What your talk is about: For too long, .NET (and its respective developers) have been seen as a place where good coding practices and modern applications go to die. Why is that? In this session, I’ll talk about the challenges to modernizing a .NET web app, techniques to begin the transformation, and how you as a developer at any place in a team can help instigate this change. We’lll talk about the benefits of modernizing your app, both for your organization and for your development team.

How long will your talk be?

• [ ] 5-15 minutes (lightning talk)
• [ ] 20-30 minutes
• [x] 30-45 minutes
• [x] 60 minutes or more

Meta

Do you need help crafting your talk?

• [ ] Yes
• [x] No

<p>Keep being awesome! 🤖✨</p>

<p>Keep being awesome! 🤖✨</p>

<p>Keep being awesome! 🤖✨</p>

<p>Keep being awesome! 🤖✨</p>

<p>Keep being awesome! 🤖✨</p>

<p>Keep being awesome! 🤖✨</p>

<p>Hi there — thanks for submitting this talk! It’s been a year since the last activity — would you mind taking a look to see if you’re still interested in presenting about this topic, and if the talk’s content is still up-to-date?</p> <p><strong>If everything’s still good,</strong> just drop a comment here and I’ll pop back into hibernation like a good little robot.</p> <p><strong>If you’re no longer interested in giving this talk,</strong> or the talk is out-of-date, feel free to close this issue.</p> <p>Should I not hear back in a week, I’ll close this issue so you needn’t feel guilty about it. ❤️</p> <p>Thanks for your contribution to the tech community in DC!</p>

Bumps django from 2.2.10 to 2.2.22. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/django/django/commit/df9fd4661e203d41c189054d8b23d256815e14fc"><code>df9fd46</code></a> [2.2.x] Bumped version for 2.2.22 release.</li> <li><a href="https://github.com/django/django/commit/d9594c4ea57b6309d93879805302cec9ae9f23ff"><code>d9594c4</code></a> [2.2.x] Fixed <a href="https://github-redirect.dependabot.com/django/django/issues/32713">#32713</a>, Fixed CVE-2021-32052 -- Prevented newlines and tabs fro...</li> <li><a href="https://github.com/django/django/commit/163700388cda2305c8dbcdb3ac1542a442f3e955"><code>1637003</code></a> [2.2.x] Refs CVE-2021-31542 -- Skipped mock AWS storage test on Windows.</li> <li><a href="https://github.com/django/django/commit/bcafd9ba848d736769870b4fc940b2ebbf87a70a"><code>bcafd9b</code></a> [2.2.x] Added CVE-2021-31542 to security archive.</li> <li><a href="https://github.com/django/django/commit/3931dc765177b2793fe806b4a02122b1a718b1c3"><code>3931dc7</code></a> [2.2.x] Post-release version bump.</li> <li><a href="https://github.com/django/django/commit/ff1385ae45d267f455b1744fb39a9ab5de688d05"><code>ff1385a</code></a> [2.2.x] Bumped version for 2.2.21 release.</li> <li><a href="https://github.com/django/django/commit/04ac1624bdc2fa737188401757cf95ced122d26d"><code>04ac162</code></a> [2.2.x] Fixed CVE-2021-31542 -- Tightened path & file name sanitation in file...</li> <li><a href="https://github.com/django/django/commit/7f1b088ab4a4342a87a11496096471703994a006"><code>7f1b088</code></a> [2.2.x] Added CVE-2021-28658 to security archive.</li> <li><a href="https://github.com/django/django/commit/e95fbb6a7653a5f199d5d8c90a282cdf9e58fc22"><code>e95fbb6</code></a> [2.2.x] Post-release version bump.</li> <li><a href="https://github.com/django/django/commit/ad9fa56a17bf9691615e9bb6e41d08d51cfe8a5d"><code>ad9fa56</code></a> [2.2.x] Bumped version for 2.2.20 release.</li> <li>Additional commits viewable in <a href="https://github.com/django/django/compare/2.2.10...2.2.22">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Superseded by #44.