pythonindia / inpycon2020-tasks

PyCon India 2020 Task and Coordination
12 stars 9 forks source link

Need content pieces for Outreach Partners #56

Closed anistark closed 4 years ago

anistark commented 4 years ago

Since last call, we can onboard outreach partners to help us spread the word about PyCon India 2020, we would a few content pieces as mentioned below to send out to them:

anistark commented 4 years ago

@vipulgupta2048 Can we get an update on this? Is someone available to take this up?

vipulgupta2048 commented 4 years ago

@anistark Let me post again if someone wants to take this up otherwise I and @sc0rpi0n101 can take care of this

Madhura12gj commented 4 years ago

@anistark Let me post again if someone wants to take this up otherwise I and @Sc0rpi0n101 can take care of this

Hey Vipul, let me know where can I help in this.

vipulgupta2048 commented 4 years ago

Thanks, @Madhura12gj for taking this up, This time around we are looking for Outreach Partners or much simpler other communities who can help us get the word out regarding PyCon India as @anistark mentioned in the issue. At the moment, we need content for an invite that can be sent to communities to become an outreach partner for PyCon India 2020. We need to mention what all it would entail + we can put the communities's logo on our PyCon India website that would be helping both parties involved. Let me know if you need any more information @anistark can help you out. Reaching us on Zulip would be faster.

anistark commented 4 years ago

Here's more info: https://github.com/pythonindia/inpycon2020-tasks/wiki/Outreach-Partners

Sc0rpi0n101 commented 4 years ago

Looks like @Madhura12gj is a little busy atm I'll work on this.

Sc0rpi0n101 commented 4 years ago

For reference,

The PR for the Outreach partners blog is https://github.com/pythonindia/inpycon-blog/pull/289 and for the Outreach partners email is https://github.com/pythonindia/pyconindia-handbook/pull/31

sayanchowdhury commented 4 years ago

This also has been done. Marking as resolved :heavy_check_mark: