Skip to content

To address the entire 2021 backlog of CCG minutes#71

Open
bumblefudge wants to merge 8 commits into
w3c-ccg:mainfrom
bumblefudge:bumblefudge/meetings2
Open

To address the entire 2021 backlog of CCG minutes#71
bumblefudge wants to merge 8 commits into
w3c-ccg:mainfrom
bumblefudge:bumblefudge/meetings2

Conversation

@bumblefudge

Copy link
Copy Markdown
Contributor

No description provided.

@bumblefudge bumblefudge changed the title To address the entire Spruce Systems 2021 backlog of CCG minutes To address the entire 2021 backlog of CCG minutes Aug 30, 2021
@vsnt

vsnt commented Oct 29, 2021

Copy link
Copy Markdown
Contributor

Hey @bumblefudge can you resolve the people.json file conflicts? Thanks!

@bumblefudge

Copy link
Copy Markdown
Contributor Author

Very embarassing, just saw this now!

@bumblefudge

Copy link
Copy Markdown
Contributor Author

... and added yesterday's minutes as well because I can't seem to manage multiple branches at once 🤦‍♀️

@bumblefudge

Copy link
Copy Markdown
Contributor Author

No description provided.

@bumblefudge

bumblefudge commented Dec 14, 2021

Copy link
Copy Markdown
Contributor Author

Today's minutes are almost ready to go as well, but for some reason, the audio from the meeting (which ended 45min ago) never popped up in its usual place ? Otherwise ready to go, feel free to ping me here (or just add in the commit yourselves!) when the OGG materializes.

@BigBlueHat

Copy link
Copy Markdown
Member

@bumblefudge I'm cleaning house in this repo, and would be happy to get this merged. The conflicts look easy to resolve except the one that removes the Agenda: line. Do you recall why that was removed? The others all seem like text corrections which you've done on your branch (thank you!).

Let me know if we should keep or remove that Agenda: line, and I'll merge accordingly.

Cheers!
🎩

@bumblefudge

Copy link
Copy Markdown
Contributor Author

no idea about that agenda line-- i kept it when merging all the other conflicts, but feel free to take it out again if there's any reason to. maybe the automation injects it automatically making this in-line link redundant? whatever the case, thanks for cleaning it up!

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.

3 participants