Submit final event plan to Tinkerspace

[dennyabrain]

Is your feature request related to a problem? Please describe.

What does the event with Tinkerspace look like and how it ties with our work this month on 16 days of activism and group annotation exercises.

Describe the solution you would like

The end goal(s) should align with the group annotation exercises or their end results.

Describe alternatives you've considered

No response

Addtional Context

No response

[dennyabrain]

Addressing some of the concerns flagged in the email :

Are we supposed to mandate that the students should either comment under the Github issue or emailing directly to Tattle for showing interest and clarifying doubts?

I think using the Github issues or Discussions is ideal. Some proposals don't have a dedicated issue yet, so we will create that. Then for general discussions about the event, this space can be used. Firstly its public so others can benefit from it. It also allows all tattle members to chime in. Email will be siloed and additional overhead for us to coordinate who should respond and how.

Since the students are working on sensitive topics, do we have separate processes for each issue, or will it be common?

I think we should do a common one for everyone. We COULD bifurcate the cohort into two - those who are actively dealing with slurs and other problematic content and those who are simply doing the tech tasks. Although I think since part of our goal is to expand how tech students think about this issue, This bifurcation might defeat that purpose. Any thoughts?

New Timeline :

1. Problem statement release
2. Workshop
3. Office hours

Lets discuss this over a call and see especially how it clashes or goes along with the "group annotation" exercises we have planned as part of https://github.com/tattle-made/Operations/issues/160

Additionally, the timeline we are planning to allocate for the students to work on the projects are also to be finalised. In our previous discussion, we planned one week for the same. Let us know if we are going ahead with the same.

This can stay the same. We do a workshop, give the students a week to work on, schedule office hours in between, have an end showcase day.

[dennyabrain]

Tentative timeline :
Nov 8 : Tinkerhub announces the event
Nov 13 : Tattle Workshop
Nov 14 to Nov 21 : Students work on Issues
Nov 25 to Dec 10 : Students work on proposals

[dennyabrain]

Email has been sent to tinkerhub.

[kaustubhavarma]

Followed up with the team, awaiting a response.

[dennyabrain]

We've not been able to align on timelines. The team has now gotten busy for Nov-Dec. So in the meanwhile students can particpate in 1) the ICONN task and 2) the extremely online kinds can participate in our 16 days of activism activity.

Lets do the original event around open issues and proposals in Jan because we think students would be busy in December.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.