Skip to content

Conversation

@wbamberg
Copy link
Member

@wbamberg wbamberg commented Feb 5, 2022

This PR updates the impact report to cover all of 2021, rather than stopping in September.

What's here:

I haven't replaced the "September" pie charts with "December". I could do if you like although it won't look so good, partly because December is just a weird month.

I'd encourage @Elchi3 , @estelle , and @teoli2003 to suggest improvements to my descriptions of their projects. Also tagging @robnyman and @torgo for review.

Copy link
Member

@Elchi3 Elchi3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Nice work, Will! 👍

I think this wraps up 2021 nicely. I guess we will have to work out how to make this a continued/versioned report or is the idea to start with a somewhat empty 2022 report where we add things until this December?

@teoli2003
Copy link
Member

Sounds good to me! Thanks a lot @wbamberg

@wbamberg
Copy link
Member Author

wbamberg commented Feb 7, 2022

Looks good to me. Nice work, Will! 👍

Thanks!

I think this wraps up 2021 nicely. I guess we will have to work out how to make this a continued/versioned report or is the idea to start with a somewhat empty 2022 report where we add things until this December?

I think my plan is to write something for Q1 that just talks about staffing and the work we did (metrics + projects) and either make it standalone for each quarter or build on it in each quarter. This report contains a lot of content that's not directly about the work we did (i.e. financials, marketing quotes, mission) that I would not include in a quarterly update, but that we could put into a yearly report close to the end of 2022.

(I think at that point this quarterly report ends up looking a lot like a quarterly version of the worklog, and we might want to consider what the relation between these things is.)

@Elchi3
Copy link
Member

Elchi3 commented Feb 8, 2022

I think my plan is to write something for Q1 that just talks about staffing and the work we did (metrics + projects) and either make it standalone for each quarter or build on it in each quarter. This report contains a lot of content that's not directly about the work we did (i.e. financials, marketing quotes, mission) that I would not include in a quarterly update, but that we could put into a yearly report close to the end of 2022.

That sounds very reasonable to me.

(I think at that point this quarterly report ends up looking a lot like a quarterly version of the worklog, and we might want to consider what the relation between these things is.)

My feeling is that we should then publish quarterly worklog blog posts that go hand in hand with the quarterly impact report.

However, if we believe there should be monthly updates, I would propose to change the monthly blog posts to something different. The 2021 worklog format hasn't been the most interesting. (at least that's the feedback I heard). We could challenge ourselves to publish a blog post once a month on a particular topic about doc writing or a deep dive on a project we did or want to do.

@teoli2003
Copy link
Member

teoli2003 commented Feb 8, 2022

I like the idea of publishing a monthly blog post about a subject (like Migrating to markdown, How to document events, Aria and documentation). These could (in the future) be published on the future OWD website that can then have content.

Each of these blog posts will also have a clear owner.

/me really likes this.

@wbamberg
Copy link
Member Author

wbamberg commented Feb 8, 2022

(I think at that point this quarterly report ends up looking a lot like a quarterly version of the worklog, and we might want to consider what the relation between these things is.)

My feeling is that we should then publish quarterly worklog blog posts that go hand in hand with the quarterly impact report.

However, if we believe there should be monthly updates, I would propose to change the monthly blog posts to something different. The 2021 worklog format hasn't been the most interesting. (at least that's the feedback I heard). We could challenge ourselves to publish a blog post once a month on a particular topic about doc writing or a deep dive on a project we did or want to do.

I like this plan, and would happily write something about Markdown to get started.

@Elchi3
Copy link
Member

Elchi3 commented Feb 11, 2022

Merging this for now. Let us know if there are further comments / things to improve.

@Elchi3 Elchi3 merged commit 8e6f4e2 into openwebdocs:main Feb 11, 2022
@robnyman
Copy link
Contributor

A few weeks too late, but looks great! Thanks for updating the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants