Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating first timer issues and outreach for moja global #78

Open
Tlazypanda opened this issue Jul 23, 2020 · 8 comments
Open

Creating first timer issues and outreach for moja global #78

Tlazypanda opened this issue Jul 23, 2020 · 8 comments
Labels
Documentation Issue / feature refers to docs not code Need clarification Propose a way to better communicate a feature P0 High priority issue

Comments

@Tlazypanda
Copy link
Collaborator

Describe how we are communicating and why it is not optimal.
As discussed in the last meeting moja global would love to have an active community of opensource developers and new contributors. Let's discuss some ways we as an organisation can drive more new contributors. Please feel free to add suggestions below or provide feedback.

Describe the solution you'd like

@Tlazypanda
Copy link
Collaborator Author

Tlazypanda commented Jul 23, 2020

Please have a look @Patamap @gmajan Thanks ✌️ (created as per meeting discussion)

@Tlazypanda Tlazypanda added Need clarification Propose a way to better communicate a feature Documentation Issue / feature refers to docs not code Cat = Feedback labels Jul 24, 2020
@Tlazypanda
Copy link
Collaborator Author

Hey @sulays @abhineet97 @abhi211199 @parth-gr Inviting you all to brainstorm on this and hopefully get new contributors to contribute 🎉

@abhineet97
Copy link
Contributor

An Open Source Guide published by GitHub has some great suggestions on how we can attract more contributors. After reading it, I realized that we can benefit a lot by improving FLINT's README. I have some ideas, I'll try to suggest them in a PR later.

Apart from that, we should also consider promoting FLINT on platforms like reddit and Hacker News. These platforms love OSS. Even if we don't receive code contributions from them, we'll most likely receive a lot of great feedback.

On my end, I'll try my best to get contributors from my network (which is rather small 😄)

Thanks for the invite, hope this helps.

@abhi211199
Copy link
Member

The suggestions put forward by @Tlazypanda and @abhineet97 are really appealing 🚀🚀, social media can help us to get new contributors. Students approaching GSoCers, GSoDers, Outreachy alumnus for guidance is a common thing, and we can redirect them to the good-first-issues for a smooth start to the contribution process.

Talking about creating the issues for current projects, I think, they can be created after a month, when we have a clear idea about the path to whch the project can be scaled up to, or the features which can be improved further 🙂.

@parth-gr
Copy link
Member

Hy thanks for inviting me too, I like all the above suggestions.
And from my side, I can attract a large group of good developers that are in my connection.

And into the contribution part, What we can give them to start is:

  1. From our project, we can suggest small work from it to them as their first contribution.
  2. Documentation work, like @abhineet97, said to improve the readme.
    This can be divided into two aspects i.)How things/software work includes all the technical stuff. ii.) Non-technical stuff
    including what all software do.
  3. Features that can be Improved by @abhi211199 .

Even for social media, we can look for people to promote it so more people would get to know about our community.

@Patamap
Copy link
Contributor

Patamap commented Jul 28, 2020

@saloni-garg @yjko2 @juliancabezas, Inviting you all to brainstorm on this and hopefully get new contributors to contribute 🎉 See the thread please.

@Patamap
Copy link
Contributor

Patamap commented Aug 29, 2020

Thank you very much for all the great idea and suggestions, everyone. So all are recorded and started to knick off.

Here is a Moja global communication channels link,
https://docs.google.com/document/d/1gsWZPvh76vLTh3cNq3eH6fhaYplAiHIioI2_OSzmsUE/edit

All suggestions/comments are very welcome!!!

@shubhamkarande13
Copy link
Member

shubhamkarande13 commented Aug 29, 2020

We can use @yourfirstpr twitter.com/yourfirstpr and @first_tmrs_only twitter.com/first_tmrs_only on Twitter to attract new contributors.

We can also try for Hacktoberfest 2020 which a good way of getting motivated new contributors, as after merging 4 pull requests they'll receive a free T-shirt from Digital Ocean hacktoberfest.digitalocean.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Issue / feature refers to docs not code Need clarification Propose a way to better communicate a feature P0 High priority issue
Projects
None yet
Development

No branches or pull requests