While preparing last year's badge I noticed a few graphical errors in the logo that make it difficult to work with—e.g. horizontal asymmetry of the ribbon makes centering nontrivial, vertical asymmetry makes alignment with page design elements impossible, etc.—and in correcting those I was lured into thinking about other adjustments as well.
I'd like to propose a few revisions to the logo that should be subtle enough to not feel like a redesign.
Current
Variant A
Changes
Expected results:
The seagull is more emphasized.
Graphical elements are cleaner and more balanced.
The logo fits better in a square bound.
The seagull's face looks less human.
Edits:
Decrease the size of the ribbon.
Increase the size of the seagull.
Reshape the seagull's head and beak.
Add a red spot on the seagull's beak.
Reshape the horizon from an oval segment to an arc.
Decrease the range of text weights.
Match line thicknesses to text weights.
Decrease the length of the ribbon's folds.
Decrease the depth of the ribbon's end cuts.
Correct the asymmetry of the ribbon.
Remove the discontinuity at the edge of the background.
Some folks proposed a lot of talks this year (which is good). We only accept one talk per speaker, which means some folks received a wall of rejection emails, one per declined proposal.
If we're still using OSEM next year, there's no way to consolidate emails using that system. But, with a bit of massaging in a spreadsheet, it's possible to do it via MailChimp.
Consider doing this next year (2019) to minimize the Wall Of Rejection effect in people's inboxes.
if you haven't yet, everyone is encouraged to make TeaGL toast video, send to Romeo, can be wearing mask [mug to camera -> pull away and sip -> return mug to camera]
The meeting SeaGL/staff#24 will begin by going over the responses from SeaGL 2020's retrospective. Please review the following documents, paying extra attention to your committee(s). Gather three positives from the retrospective along with one area to improve upon for this year. Bring your list to the meeting and/or comment here.
individual teams may use other tooling within themselves, but things need to be stored in a way that everyone can access them if communication channels are down
Google Drive has been alright, but we are moving more things away from proprietary lock-in
NextCloud worked okay, but has some rough edges, also it would be nice to minimize the number of services people have to signup for
Downsides of using git? Filesize and binary diffs are two that come to mind, but are those bad enough to avoid this?
Does GH have a ToS question about being a file host?
Easiest/simplest solution is to have our own NextCloud
Start with most common use cases
All for consolidating access, need to agree on the place and who holds the keys and how to reach them
Additional check-in step can be beneficial (e.g. pull requests)
What are the problems we are trying to solve? What are our pain points? This list would be good to have in an issue in the infrastructure repo
OSEM now supports custom questions at CFP time (though we'd need to sync with upstream to get this). This issue is for tracking the questions we should include.
Member of a group under-represented in tech? (yes/no)
First time presenter? (yes/no)
Twitter handle (text)
What pronouns do you use? (text)
If more come up between now and next year, add them to the list above rather than in comments so we can keep the entire list together and not miss anything when we create the form.