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.

Sign up for GitHub

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

Jump to bottom

Blog post: 2i2c quarterly update Q3 #235

Closed
4 tasks done
choldgraf opened this issue Sep 4, 2021 · 7 comments · Fixed by 2i2c-org/2i2c-org.github.io#77
Closed
4 tasks done

Blog post: 2i2c quarterly update Q3 #235

choldgraf opened this issue Sep 4, 2021 · 7 comments · Fixed by 2i2c-org/2i2c-org.github.io#77
Assignees
@choldgraf

Comments

@choldgraf
Copy link
Member

choldgraf commented Sep 4, 2021 •
edited
Loading

Description

At the end of last May, we wrote up a short overview of what 2i2c has been up to. We should extend this practice to cover the next few months of development. Moreover, I think that a nice cadence for these meta updates would be quarterly, so I'll scope this post to Q3 2021 (July, August, and September and we can include June in there this time as well).

I'll try to collect major updates and themes from 2i2c over the last few months, and give an idea of where I think we are headed next. This may also be a good opportunity for us to bake this in to our regular strategic planning.

Value / benefit

Providing organization-wide heartbeats is an important way to provide transparency to others about what we have been up to, and where we are going. It's a way to show some dyanamism for people who are not paying close attention to our repositories, and is also a signal-boost that others can follow.

Implementation details

I think we should just collect links and references in this issue, and then in October 2021 write up a summary blog post that compiles them together.

Tasks to complete

  • Until October 1st 2021, collect major updates from 2i2c here. Paste or cross-link below.
  • Write up a blog post draft (see link below)
  • Feedback on draft
  • Post on Thursday October 14th unless there are objections

Updates

  • 2021-10-11

    I've put together a draft for a "Community update". It includes a few major highlights, challenges, and next
    steps for what we've been up to. I'd love any comments or edits!

    https://hackmd.io/uQGx-x6sReG5JbuR7pqHuw

    If there are no major objections, I hope to post this on our blog on Thursday.
@choldgraf
Copy link
Member Author

choldgraf commented Sep 4, 2021 •
edited
Loading

As a first step to keeping track of our updates, I added some quarterly tags for the team compass repository. This makes it easy to compare what has changed in team-compass between major chunks of time quite easily.

For example, here's the changes to this repo since Q2 ended:

2021.07.01...main

And here's the changes we made during Q2 2021:

2021.04.01...2021.07.01

this might be a nice way for us to track our infrastructure changes as well...since we don't follow any kind of "versioning" convention, doing so by quarter (or month) seems like a reasonable approach? Let's see how it works here first though :-)

@choldgraf
Copy link
Member Author

choldgraf commented Sep 4, 2021 •
edited
Loading

Another thought here is that we could use github-activity. So for example one could do:

github-activity -s 2021-07-01 and the result today would be:

master@{2021-07-01}...master@{2021-09-04}

(full changelog)

Merged PRs

Contributors to this release

(GitHub contributors page for this release)

@choldgraf | @consideRatio | @damianavila | @GeorgianaElena | @sean-morris | @sgibson91 | @yuvipanda

And the same command run on pilot-hubs results in:

master@{2021-07-01}...master@{2021-09-04}

(full changelog)

Merged PRs

Contributors to this release

(GitHub contributors page for this release)

@abkfenris | @choldgraf | @consideRatio | @damianavila | @GeorgianaElena | @ianabc | @jbusecke | @jhamman | @JILPulvino | @jules32 | @ocefpaf | @orianac | @paigem | @rabernat | @roxyboy | @sean-morris | @sgibson91 | @yuvipanda

Or we can even grab all activity across 2i2c-org and display it with github-activity -t 2i2c-org -s 2021-07-01

master@{2021-07-01}...master@{2021-09-04}

(full changelog)

Merged PRs

Contributors to this release

(GitHub contributors page for this release)

@abkfenris | @betolink | @choldgraf | @colliand | @consideRatio | @damianavila | @GeorgianaElena | @github-actions | @ianabc | @jbusecke | @jhamman | @JILPulvino | @jules32 | @ocefpaf | @orianac | @paigem | @rabernat | @roxyboy | @sawula | @sean-morris | @sgibson91 | @yuvipanda

As an aside: wow we have been busy!

@damianavila
Copy link
Contributor

Contributors to this release

The last one (I think it is automatically generated?) is building failed URLs (taking my handle as one example but it fails with all the handles):

https://github.com/search?q=repo%3A2i2c-org%2FNone+involves%3Adamianavila+updated%3A2021-07-01..2021-09-04&type=Issues

It should be (pointing to the org instead of the repo):
https://github.com/search?q=org%3A2i2c-org+involves%3Adamianavila+updated%3A2021-07-01..2021-09-04&type=Issues

Btw, quick question, how do we capture stuff not represented on GitHub?

@choldgraf
Copy link
Member Author

I'm starting to work on a blog post about this here:

https://hackmd.io/uQGx-x6sReG5JbuR7pqHuw

I need to keep iterating on it a bit to figure out how to prevent it from being super long and complex. It is roughly broken up into these 4 main sections, corresponding to 4 ways that 2i2c wishes to have impact on our communities:

  1. Organizational updates
  2. Hub service updates
  3. Projects / collaborations updates
  4. Open source upstreams / support

I'm not sure that the draft is ready for 👀 yet but if others are curious to check it out, you're more than welcome!

@choldgraf choldgraf self-assigned this Oct 10, 2021
@choldgraf
Copy link
Member Author

2021-10-11

I've put together a draft for a "Community update". It includes a few major highlights, challenges, and next steps for what we've been up to. I'd love any comments or edits!

https://hackmd.io/uQGx-x6sReG5JbuR7pqHuw

If there are no major objections, I hope to post this on our blog on Thursday.

@choldgraf choldgraf mentioned this issue Oct 12, 2021
Closed
@choldgraf choldgraf moved this to Needs input 🙌 in Sprint Board Oct 12, 2021
@sgibson91
Copy link
Member

I think it's great! Thanks for putting it together! 🚀

@choldgraf choldgraf mentioned this issue Oct 13, 2021
Merged
@damianavila
Copy link
Contributor

As I said in the meeting, in general, I really like it!
I will add specific comments on the linked PR.

Repository owner moved this from Needs input 🙌 to Done 🎉 in Sprint Board Oct 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@choldgraf choldgraf

Labels
None yet
Projects
No open projects
Sprint Board
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Blog post: Q3 update 2i2c-org/2i2c-org.github.io
3 participants
@damianavila @choldgraf @sgibson91