Ways to get involved

[Sealjay]

How could it be easier for folks to get involved? @danuw and a couple of other folks were suggesting easy tasks or issues, for things like including support for tools like WattTime, demos, or trying to set up projects we support.

[akshitbatra]

@Sealjay, could we also look into adding updates to very old issues or start closing them/or adding description on why they are still pending and if someone could take it up.
For example: Carbon Aware SDK has 24 currently open issues.

[Sealjay]

I love it. There are some project management changes coming, if you saw @jawache's email - but once those are in place, I definitely think the lead and principal should take an active role in closing or reviewing these.
FYI @Willmish @DanniBradu @vaughanknight

[Sealjay]

We're going to start jumping into that, and closing/bumping issues.

[Sealjay]

30 days for issues and discussions being stale - no comments or reactions.
PRs will be merged into dev after 7 days, if no objections are raised.
GH action to notify people. Chair/project lead will merge.
Chairs and convener to have discretion to move discussions to issues/vice versa. Broadly, discussions will become issues when consensus is reached.

• Issue to be created for new stale process

[Sealjay]

Implemented by #34

[Sealjay]

Do we want to consider sending out a form - typeform, MS Form, Monday.com, etc, each week; asking if leads can attend calls, and prompting them to post an update in slack if not?

[Sealjay]

• Issue to be created for a proposal/GH Action