-
Notifications
You must be signed in to change notification settings - Fork 3
Personalize repo and add calls to action #2
Comments
Thanks! Teri. |
@taoshengshi I've added a few comments to your PR with the personalization. Note that I've sent out an invitation giving you admin status on the repo so that you'll be able to merge it, but your invitation hasn't yet been accepted. Try hopping over to https://github.com/ProtoSchool/chengdu/invitations to find it. |
@terichadbourne Thanks very much for your support! I have merged the Personalize repo , please kindly review it. |
Looking good! The one issue I see is that your link to the July TBD meetup still doesn't link to anything. I'd recommend that you either create a new issue to link to or at least remove the markdown formatting I'll go ahead and close this issue. Thanks! |
uh! OK, let me fix it. |
We've provided a basic readme for you, but you should personalize it for your own
chapter's needs. You might want to:
When someone learns of your ProtoSchool chapter for the first time by visiting your repo's readme, what would you like them to do next? Providing a clear call to action is a best practice for making newcomers feel welcome and increasing community involvement.
How can your members learn about upcoming events? Will they be published at a Meetup website that you've linked to? Will they be announced in an issue in your repo (example), which means they should watch the repo to be notified?
Do you need help planning your next event, perhaps in the form of mentors or meeting space? Try opening an issue in your repo for event planning (example) and linking to it from your readme file with a friendly "Help us plan our next event!" message.
Do you need co-organizers? If so, tell them who they should reach out to (and how) to offer their help (example).
The processes you use to communicate with your members are up to you, but you should aim to make it clear from the readme how people can get involved and stay up-to-date.
The text was updated successfully, but these errors were encountered: