-
Notifications
You must be signed in to change notification settings - Fork 3
March 2017 Meetup #24
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.
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
Comments
@Rustaceans/organizers-cologne, any ideas about topics we want to cover? Lukas (at least I think it was him) asked if I want to talk a bit about Diesel, which I'd be up to. |
I generally like the idea to find pairs of talks or activities with a common overall story. Of course that's not a necessity. But a while ago we had the idea to have an arewewebyet themed evening, or even a series of events. Can we make the diesel talk be part of a larger picture somehow? Alternatively we could always throw in another openspace meetup to buy us more time to prepare something else. |
PS: Diesel would definitely be an interesting topic. Would you like to focus more on use cases, or the inner workings? |
Just a heads up: 2017-03-01 is Aschermittwoch. So most of Karneval is over by then. I'd very much like putting on the arewewebyet story. Diesel would fit right in. |
Having two talks with an overarching theme is great. I'd also focus on having that first; if there are two other talks proposed that fir together, I have no problem putting a Diesel talk off for a month or two. Luckily, there are a lot of aspects of Diesel I can talk about, though!
Do you think anyone wants to talk about rocket.rs? |
Shall we make an announcement via our mailinglist that we are looking for talks for an arewewebyet themed meetup series? |
Sound good to me.
… Am 03.02.2017 um 09:41 schrieb Colin Kiegel ***@***.***>:
Shall we make an announcement via our mailinglist that we are looking for talks for an arewewebyet themed meetup series?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@Rustaceans/organizers-cologne I drafted an email to send via our mailinglist. Please have a look and feel free to edit. I am undecided whether we should link to this ticket - or a new one. Especially if we are planning to have a series of web meetups it might be clever to pool ideas separately - what do you think?
|
PS: I added |
Nice. I'd try to ask for ideas in general, but also for talks for a specific date. Having someone commit to "talking about this in a few months" is probably not as helpful as having a second talk on March 1. Thus, I'd link to this issue. If there are too many proposal, I'll personally copy-paste them into a new one :) I adjusted your text a bit: Fellow Rustaceans,
We feel like the time is right to have a meetup around web development in Rust.
And we need your help to make it happen!
We are looking for talks and general ideas of activities that would fit that
topic. For example:
- Are you working on a web project?
- Would you like to present a cool library?
- Do you want to tell us about general architecture?
We would love it if you send us an email, comment on Meetup.com, or if you chime
in on our planning discussion on Github:
<https://github.com/Rustaceans/rust-cologne/issues/24>
Thank you!
Yours, Jan-Erik, Pascal, Florian and Colin
---
P.S.: Have you seen http://www.arewewebyet.org/ yet? |
ok, I sent both (a) our usual 'save-the-date' info and (b) the call for help announcement. I hope it makes sense this way - but meetup doesn't allow that much text in event notifications. ;-) |
Hey, I could give a talk about the current status of my Rust slack client. Don't expect anything outstanding, though. It's more like a rundown of pitfalls you might want to avoid when writing such a library. 😁 Interested? |
Sure! Added anything fancy recently? (Like the new version of
derive-builder *hint* *hint* ;))
Matthias Endler <[email protected]> schrieb am Mi. 8. Feb. 2017 um
14:55:
… Hey, I could give a talk about the current status of my Rust slack client.
Don't expect anything outstanding, though. It's more like a rundown of
pitfalls you might want to avoid when writing such a library. 😁
Interested?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABOX064OMPumQ-PqSr5w3n37QRtIGSFks5raclqgaJpZM4L1NxO>
.
|
I'll try to integrate the newest version of derive_builder until the talk. |
@Rustaceans/organizers-cologne I suggest that we send the final invitation this weekend. IMO we have two options (a) have the diesel and slack API talks or (b) wait until we have more web related talks to start a series of meetups and do something openspace like first. cc @killercup @mre I think we should hear your preferences first. ;-) Everyone else reading this, feel free to suggest other talks here, even if you would not do it in march, but later. |
@colin-kiegel both is fine with me. Even if the talks might be short I guess we won't run out of topics afterwards. There's just too many good Rust libraries out there. 😉 |
I agree, let's go with (a). We can always let the meetup turn into an openspace after the talks.
… Am 14.02.2017 um 09:24 schrieb Matthias Endler ***@***.***>:
@colin-kiegel both is fine with me. Even if the talks might be short I guess we won't run out of topics afterwards. There's just too many good Rust libraries out there. 😉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
ok @mre @killercup what's the title of your talks? :-) |
Vote for |
Let's call mine What's so hard about writing a Slack client in Rust? |
@colin-kiegel feel free to pick one from #24 (comment)! 😄 Or go with
|
@Rustaceans/organizers-cologne I updated the invitation draft - let's get it out this weekend. ;-) Do you want to add/change something? |
@Rustaceans/organizers-cologne ping :-) |
Invite LGTM but maybe @mre wants to add a short description? Or, just leave
out mine.
Colin Kiegel <[email protected]> schrieb am Sa. 18. Feb. 2017 um
21:43:
… @Rustaceans/organizers-cologne
<https://github.com/orgs/Rustaceans/teams/organizers-cologne> ping :-)
#24 (comment)
<#24 (comment)>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABOX2CoxE8KfjUnMUIyAwKHH4_1Kg1yks5rd1fYgaJpZM4L1NxO>
.
|
@killercup good idea! Here we go:
|
@killercup I sent most invitations. Do you want to do reddit again? Also the text on the website is not up-to-date. |
Thanks! Just got the invite email myself. I'll update both.
… Am 19.02.2017 um 12:49 schrieb Colin Kiegel ***@***.***>:
@killercup I sent most invitations. Do you want to do reddit again? Also the text on the website is not up-to-date.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@killercup @mre There is interest in recordings of these talks in the Rust forum. Do you want to record them? @Florob Would you like to organize the recording? |
I'm okay with recording my talk. Just as a head up: It might get pretty Q&A-y, so we'll probably need mic(s) for the audience. (But this was pretty good in the past.)
… Am 19.02.2017 um 13:45 schrieb Colin Kiegel ***@***.***>:
@killercup @mre There is interest in recordings of these talks in the Rust forum. Do you want to record them?
@Florob Would you like to organize the recording?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yup, I'm also fine with it. |
I'm happy to do recordings again. We have a hand-held microphone for Q&A, the biggest problem is usually getting people to use it consistently. |
I added a few more things under "Rust News". Feel free to expand :) |
Notes/suggestions for next meetups:
|
@mre, do you want to publish your slides? Which were brilliantly hilarious, by the way! |
@killercup yes sure. Uploaded to Speaker Deck. Feel free to move it around. |
Uh oh!
There was an error while loading. Please reload this page.
Todo
Invitation draft
News
fn<const n: usize>(input: [u8; n])
)The text was updated successfully, but these errors were encountered: