Skip to content

Home

Jump to bottom
Rebecca Woodbury edited this page Oct 14, 2024 · 21 revisions

Welcome {#welcome}

Welcome to the Proudly Serving wiki. This serves as documentation for how we work.

Communications {#communications}

  • Slack
    • #ops channel for maintainers
    • #chapter-title for contributor communications
    • #general for announcements
  • Email
    • Intake form
    • Contributor communications

Style guide {#style-guide}

Manuscript {#manuscript}

Roles {#roles}

Proudly Serving is an open source project with maintainers and contributors.

Maintainers {#maintainers}

Responsibilities:

  • Lead product development.
  • Participate in recurring project check-ins.
  • Own designated issues/tasks and follow through on their completion.
  • Support other maintainers and contributors.
  • Recruit project contributors and maintainers (when needed).
  • Evangelize the project.

Contributors {#contributors}

Responsibilities:

  • Contribute chapter.
  • Editorial support.
  • Chapter feedback.
  • Follow team agreement and code of conduct.

Team agreement {#team-agreement}

Contributor agreement {#contributor-agreement}

I, [YOUR NAME], as a Proudly Serving contributor, earnestly swear that I will:

  • Meet my deadlines
  • Share my blockers
  • Communicate often
  • Not be afraid to ask for help

Maintainer agreement {#maintainer-agreement}

Respect/communication:

  • We will treat each other with respect, courtesy and professionalism.
  • We will actively listen to each other and value diverse perspectives.
  • We will communicate openly and honestly, providing constructive feedback.

Timeliness/attendance:

  • We will arrive on time for meetings and complete assigned tasks by agreed-upon deadlines.
  • We will notify the team in advance if we are unable to attend a meeting or fulfill a commitment.

Collaboration/accountability:

  • We will work collaboratively, sharing knowledge, ideas and resources.
  • We will take ownership of our tasks and be accountable for their completion.
  • We will support each other and offer assistance when needed.

Confidentiality/privacy:

  • We will maintain the confidentiality of sensitive information shared within the team.
  • We will respect the privacy of team members and refrain from sharing personal information without consent.

Decision-making:

  • We will strive for consensus in decision-making, actively involving all team members.
  • In cases where consensus is not possible, we will follow an agreed-upon method for resolving conflicts or making final decisions.

Work processes:

  • We will establish clear goals, objectives and milestones for our project.
  • We will establish effective communication channels and response times.
  • We will document and share project-related information and updates regularly.

Continuous Improvement:

  • We will regularly review and assess our team’s performance, identifying areas for improvement.
  • We will provide constructive feedback and support each other’s professional development.

Onboarding {#onboarding}

Maintainers {#maintainers-1}

Contributors {#contributors-1}

Email templates {#email-templates}

Welcome contributors {#welcome-contributors}

Thanks for your interest in becoming a Proudly Serving contributor!

The next step is the contributor kick-off where we’ll discuss:

  • Editorial process
  • Topic you want to write about
  • Chapter template

Schedule kick-off meeting.

Before we meet, here are two things you can do to get started:

See you soon!

Kick-off follow-up {#kick-off-follow-up}

We’re excited to work with you on your chapter contribution!

Here is the reference doc we’ll work from: Chapter doc [LINK]

Next steps:

For your reference, here's the team agreement.

If you have any questions, just ask in the document or chapter Slack channel.

Welcome!

Chapter status deadline nudge {#chapter-status-deadline-nudge}

Hi [NAME], 👋

We're writing to check in on the status of your Proudly Serving chapter. We're excited to have you as a contributor, but we also need to keep the momentum going with both the chapter and the overall project.

Questions for you:

  • Are you able to complete your chapter by Wednesday?
  • If yes, how can we support you?
  • Do you need to schedule a call or discuss via Slack?

If not, that's completely understandable. We'll just need to move your chapter to the backlog and promote the topic to others.

Thank you again for taking an interest in this!

Share your Proudly Serving draft chapter on social {#share-your-proudly-serving-draft-chapter-on-social}

Your chapter for Proudly Serving is ready for public feedback. Help us promote this by sharing it on social media.

  • LinkedIn [LINK]
  • Twitter [LINK]

Final review done for your Proudly Serving chapter {#final-review-done-for-your-proudly-serving-chapter}

Hello [NAME],

We’ve completed the final review of your Proudly Serving chapter [CHAPTER NAME].

  • Review and confirm edits [LINK TO MANUSCRIPT DOC]
  • Add names to the Acknowledgments section
  • Tag us in the doc to let us know when you’re done with your review

Please finish your review by [DATE - ONE WEEK LATER].

Chapter published in the final manuscript {#chapter-published-in-the-final-manuscript}

The final review tasks are complete. Your chapter is now published in the Proudly Serving manuscript.

We'll keep you posted on next steps as we continue to finish the project.

Thank you again for your chapter contribution! If you aren’t already, please:

Thank you {#thank-you}

Thank you for writing [TITLE].

Help us share on social:

  • LinkedIn [LINK]
  • Twitter [LINK]

Please stay engaged with Proudly Serving by providing feedback on future chapters and sharing the book with your network.

If you haven’t already, you can add Proudly Serving to your LinkedIn profile.
We appreciate you sharing your time and expertise with the government community.

Outreach {#outreach}

Goals {#goals}

  • Promote chapters.
  • Recruit contributors for remaining chapters.
  • Promote the book.

Chapter promotion {#chapter-promotion}

Feedback {#feedback}

LinkedIn {#linkedin}

A new Proudly Serving chapter titled '[CHAPTER TITLE]' is ready for public review and feedback. This chapter was written by [NAME]. 🙌

[LINK]

X/Twitter {#x/twitter}

A new @Proudly_Serving chapter titled '[CHAPTER TITLE]' is ready for public review and feedback. 🙌

This chapter was written by [NAME].

[LINK]

Slack {#slack}

Go @[Slack handle]! 🎉

Shared on socials here:

  • LinkedIn
  • Twitter

[LINK]

Substack/news post {#substack/news-post}

Request for Proudly Serving feedback: [TITLE] {#request-for-proudly-serving-feedback:-[title]}

[DATE]

A new Proudly Serving chapter titled [#TITLE] is ready for public review and feedback. This chapter was written by [#NAME].

We welcome your suggestions and ideas.

Share {#share}

Share [#this chapter] with other subject matter experts in your network. The more feedback, the better the chapter will be.

Feedback {#feedback-1}

Feedback is due [DATE].

Once we’ve incorporated the feedback, the chapter will be added to the Proudly Serving manuscript.

Published {#published}

LinkedIn {#linkedin-1}

A new @Proudly Serving chapter titled '[TITLE]' by [@NAME] has been published! 🎉 [LINK]

#DigitalGov #Government

Twitter {#twitter}

A new @Proudly_Serving chapter titled '[CHAPTER TITLE]' by @[TWITTER HANDLE] has been published! 🎉

[LINK]

#DigitalGov #Government

Slack {#slack-1}

Go @[Slack handle]! 🎉

Shared on socials here:

  • LinkedIn
  • Twitter

[LINK]

Substack/news post {#substack/news-post-1}

New Proudly Serving chapter: [TITLE] {#new-proudly-serving-chapter:-[title]}

[DATE]

New chapter {#new-chapter}

[#TITLE] is now published in Proudly Serving.

Thank you {#thank-you-1}

Thank you [#NAME] for contributing your wisdom to this chapter!

Media {#media}

Web/print {#web/print}

Podcasts {#podcasts}

Organizations {#organizations}

  • ELGL
  • Institute for Local Government
  • ICMA
  • National League of Cities
  • National Association of Counties
  • National Association of State Chief Information Officers
  • Technologists for the Public Good

Collateral {#collateral}

Security {#security}

  • Strong passwords managed via password manager
  • Two-factor authentication whenever possible

Connect {#connect}

Contact {#contact}

Proudly Serving

Clone this wiki locally