Settle on tools for camp planning

If it's not upsetting to others, I'm glad to see these discussions here on d.o., augmented with email for conversations that need to be private, and conference/phone calls to hash out other issues when necessary (then noted here). In general, I prefer the asynchronous tools. I'm not sure how much time I will be able to devote to this, but I generally find it easy to pop in to discussions like this to offer feedback when it's helpful.

The other big reasons for this experiment from my perspective:
1) Transparency. Can't get much more transparent than this! Anyone can come and see what we're working on and jump in to participate.
2) Credit. We've had several discussions about how to give credit to our volunteers and possibly their supportive organizations in the past. Using this issue queue is a tool other camps and initiatives have picked up to fill that need. Please be sure to set your Attribution as you'd like it when you participate in these conversations. You can choose to say you're volunteering your own time or that you're participating with the support of an organization. When we "fix" these issues you'll receive those credits on your Drupal.org profile.

In my mind, this issue is already settled. And as I was the only one to offer an alternative: having the issue planning be on Gitlab. I don't see any more opposition for moving ahead.

I liked Gitlab for personal reasons, as it seems much of the underlying architecture is moving onto Gitlab. I also like the keyboard shortcuts for creating issues.

We have talked about handling issue planning here in the last two meetings so that why this issue is settled in my mind.

We're well underway in planning and we've decided to use this issue queue for public conversations / Slack / email from conversations that need to stay private.

As a result, closing this issue.