Infrastructure Sprint

[stpaultim]

Creating this new issue to outline goals and structure for this week. This issue is a more detailed version of #494

Motivation:

We have been seeing an increase in activity in both the forums and Gitter with new users experimenting with Backdrop CMS and seeking help through our various channels of communication.

These new users have exposed some known and some unknown issues with our infrastructure. Fixing infrastructure issues is often feels less exciting or interesting than focusing on core/contrib issues.

Hopefully, we can resolve at least some of the low hanging fruit in our infrastructure issues queues and possibly engage some new folks in contributing to the support and maintenance of these infrastructure sites.

Goals:

1. To encourage a few people (or as many as possible) to focus attention on issues in the various issue queues for Backdrop CMS infrastructure sites over the course of a nine day stretch. Certainly, work can and will continue after this sprint week.

2. To make it easier for contributors to help support and maintain our various infrastructure sites.

Sites/Tools in Question:

• http://www.backdropcms.org
• http://forum.backdropcms.org
• http://api.backdropcms.org
• Gitter

Events/Schedule

This was originally intended to be very LOW key. Just a week for folks to voluntarily focus their efforts on issues that don't always get the attention they deserve. However, we've decided to schedule at least two virtual online sprints where we can collaborate. Also, we have our weekly meeting where we can talk about progress.

Nov 17th - Virtual sprint time (possible hangout or virtual meeting space)
12:00 - 4:00pm Central Time USA - other time zones => https://bit.ly/2CJz0ib
https://gitter.im/backdrop/backdropcms.org

Nov 21st - Weekly Design/UI meeting. Opportunity to talk about work being done and how to get involved. 2:00 - 3:00pm Central Time USA - other time zones => https://bit.ly/32X5pw5

Nov 24th - Virtual sprint time (possible hangout or virtual meeting space)
12:00 - 4:00pm Central Time USA - other time zones => https://bit.ly/352Z04b
https://gitter.im/backdrop/backdropcms.org

How to participate:

As usual, anyone should participate in whatever way interests them or motivates them. For anyone looking for more guidance, here are a few tips:

1. If you have noticed any problems, bugs, or opportunities for improvement on any of our infrastructure sites, please look for existing issues in the appropriate issue queue and comment on them OR create a new issue if necessary.

• BackdropCMS.org => https://github.com/backdrop-ops/backdropcms.org/issues
• Backdrop Forum => https://github.com/backdrop-ops/forum.backdropcms.org/issues
• Backdrop API Site => https://github.com/backdrop-ops/api.backdropcms.org/issues

2. If you are unable to create Pull Requests or edit the sites in question, please read through existing open issues and offer feedback/comments. Especially if you are new to the Backdrop CMS community, we could really use your input on how to improve these tools and resources.

• backdropcms.org issues that "need feedback"
• forum.backdropcms.org issues that "need feedback" or are a "question"

3. If you are able to help solve an issue, jump in and start helping. If you want to help, but need assistance getting started, post a comment here - or find us in Gitter and let us know. We want to help you contribute to Backdrop CMS.

4. Here is a Github Project we can use with this SPRINT - I will add a few issues to this project that I think are important, I would suggest that anyone should feel free to add 3-4 issues to this project that they think are important (anyone can work on any issue regardless of whether or not it's on this list). You should be able to add issues from other issue queues to this project:

• https://github.com/backdrop-ops/backdropcms.org/projects/2

5. To actually contribute code or changes to any of the Backdrop CMS sites you can download the code from their respective repositories at https://github.com/backdrop-ops and come to gitter to request access to a sanitized copy of the database. Each repo comes with a .lando.yml file for Lando development.

Promoting this sprint:

Current plans are to casually tweet out information about this sprint, especially if we are looking for broader community input on any issues. I am sure that there will be ongoing discussion about this sprint in Gitter. Maybe we should make use of the backdropcms.org channel which seldom gets used.

• https://gitter.im/backdrop/backdropcms.org

If you think we should do more, please comment here or in Gitter.

[stpaultim]

I'm going to close this ticket, because this sprint is over and was pretty successful. We got a number of good things done during the sprint.

Future sprints might have their own issues.

[stpaultim]

I'm going to reopen this for now, because I think we should do it again. We can create a new issue for the new sprint and then close this one. But, until then, let's keep this one open.