Skip to content

Update 2026 Incheon information and photo - #359

Open
miles-p wants to merge 17 commits into
mainfrom
punch/2026-robocup-photo
Open

Update 2026 Incheon information and photo#359
miles-p wants to merge 17 commits into
mainfrom
punch/2026-robocup-photo

Conversation

@miles-p

@miles-p miles-p commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Add Incheon 2026 photograph and team information :)

Preview

https://deploy-preview-359--nubook.netlify.app/team/past-members

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for celebrated-malasada-385661 ready!

Name Link
🔨 Latest commit 0b6fab2
🔍 Latest deploy log https://app.netlify.com/projects/celebrated-malasada-385661/deploys/6a6fd2527840e60008f8d70f
😎 Deploy Preview https://deploy-preview-359--celebrated-malasada-385661.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for nubook ready!

Name Link
🔨 Latest commit 0b6fab2
🔍 Latest deploy log https://app.netlify.com/projects/nubook/deploys/6a6fd252bab1420008e76124
😎 Deploy Preview https://deploy-preview-359--nubook.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@miles-p
miles-p requested a review from ysims July 22, 2026 11:11
@miles-p

miles-p commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

This could probably trigger us to go through the Current Team info and whatnot. Clean up the cobwebs, considering you recommended this just under a year ago
image

@ysims

ysims commented Jul 22, 2026

Copy link
Copy Markdown
Member

#349 I have this PR but I wasn't sure who was on the team so never got around to finishing it, maybe you could incorporate it. I put the Beijing photo in, which could go into the past team now

@miles-p

miles-p commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

#349 I have this PR but I wasn't sure who was on the team so never got around to finishing it, maybe you could incorporate it. I put the Beijing photo in, which could go into the past team now

Nothing in that list looks too bad for the team list still somewhat accurate.
Yeah I'll throw Beijing in to the team history.

@miles-p

miles-p commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

@ysims this is looking good now

Comment thread src/book/01-team/04-history/02-past-members.mdx Outdated
Co-authored-by: Ysobel Sims <35280100+ysims@users.noreply.github.com>
@miles-p

miles-p commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

Good catch @ysims. What to do about the Junior Member section? No-one is actually a junior member at the moment given we're about to do recruitment, right? That should probably get a tweak.

@ysims

ysims commented Jul 23, 2026

Copy link
Copy Markdown
Member

Good catch @ysims. What to do about the Junior Member section? No-one is actually a junior member at the moment given we're about to do recruitment, right? That should probably get a tweak.

Yeah, I agree, I was thinking the same thing. Right before recruitment you expect there's no junior members. Sometimes there are some, if they joined outside of recruiment in S1. Remove anyone who is not active, and give people who are around their own spots in the member list. There may be some on the member list who aren't around anymore, like Will and Lucy?

@miles-p

miles-p commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

Good catch @ysims. What to do about the Junior Member section? No-one is actually a junior member at the moment given we're about to do recruitment, right? That should probably get a tweak.

Yeah, I agree, I was thinking the same thing. Right before recruitment you expect there's no junior members. Sometimes there are some, if they joined outside of recruiment in S1. Remove anyone who is not active, and give people who are around their own spots in the member list. There may be some on the member list who aren't around anymore, like Will and Lucy?

I'll throw a message in Slack for any incorrect information (changed degrees, graduated - Kim, no longer active, working in a different field, name misspellings, etc)

@Claegtun Claegtun left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Will Burgin and Benjamin Hallett should go under supporting members. Kim should also technically go under that section since he graduated a few weeks ago.

The last five under "Student Members" have the correct degrees, although Ben needs to be moved to the next section; you just need to fully write out the degrees in order to be consistent with the above list.

We will likely need to update this anyway in the next few weeks as I chase up inactive members. But may as well get it merged soon.

@miles-p
miles-p requested a review from Claegtun July 23, 2026 06:41
@ysims

ysims commented Jul 23, 2026

Copy link
Copy Markdown
Member

The idea with the Junior vs Member list was that if someone had joined but not really contributed or done any work yet, they would be on the junior list since a lot of people don't stick around. I moved people in the other PR up to members because I had seen/heard of completed work from them. Having the description of what area they work in is also useful for this - if you can't really describe what area they work on, then they may not really be an active member of the team. Some members might be an unknown, and then they could stay in the Junior list until it's sorted.
But this is just how I managed it in the past, the documentation process can be changed of course.

@miles-p

miles-p commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

The idea with the Junior vs Member list was that if someone had joined but not really contributed or done any work yet, they would be on the junior list since a lot of people don't stick around. I moved people in the other PR up to members because I had seen/heard of completed work from them. Having the description of what area they work in is also useful for this - if you can't really describe what area they work on, then they may not really be an active member of the team. Some members might be an unknown, and then they could stay in the Junior list until it's sorted.
But this is just how I managed it in the past, the documentation process can be changed of course.

I'm not the one to make the comment on who is active, who is junior, who is not. With the new team leader coming in at some point, we might want to also put that in this page. While Clayton chases this up, we can leave this PR dormant and fill it up with new info in a week or so maybe.

@miles-p

miles-p commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

@ysims i've put the new team leaders in now, do we want to just remove the junior members section?

@miles-p
miles-p requested a review from ysims August 1, 2026 11:11
@ysims

ysims commented Aug 2, 2026

Copy link
Copy Markdown
Member

@miles-p in the past I've left the heading in and just put a line mentioning recruitment soon, but you could put in the person who just joined under junior members

@miles-p

miles-p commented Aug 2, 2026

Copy link
Copy Markdown
Contributor Author

@ysims Added Marvin :D

@ysims

ysims commented Aug 2, 2026

Copy link
Copy Markdown
Member

LGTM :)
what's the plan with this - is @Claegtun (or the new team leaders) still checking the names or is it good to merge?

@miles-p

miles-p commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

I've handed the list over to @sebastianbrooker2 to have a look and make some judgement calls on who is 'active' and who probably isn't anymore. i'm keen to get this in.

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