-
Notifications
You must be signed in to change notification settings - Fork 3
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
August 2017 #35
Comments
Ok, here we go. August is approaching! At the last meetup we asked what everyone would be interested in for future meetups. We got these responses:
Right now I don't know of anyone, who would be interested in giving a talk. Because of the limited time for preparation, I would suggest one of the following
@Rustaceans/organizers-cologne I'll not be around in the first week of August, but I can help a little with the usual stuff like sending out the invitations and brainstorming. What do you guys want to do in August? |
Thanks for the great summary, @colin-kiegel! To collect ideas for talks/topics outside of these event-focused issues I've created this project board and added Colin's points from above as well as some of the previously suggested/used topics. If you think this is a good idea, let me know. Oh, and feel free to add/move/edit items! :)
@Florob, are you still interested in talking about caches? This is something I'd personally be interested in, but the list from above doesn't really have any low-level things (may depend on the audience though).
Maybe we can combine this with the sponsoring of 15 free Rustconf tickets for Libz Blitz participants! |
I'm happy to talk about caches eventually. Not necessarily at the upcoming meetup though. I'm still not entirely sure where to strike the balance on low vs. high level topics. Similarly we should find a beginner/advanced balance somewhere. |
Hey @Rustaceans/organizers-cologne, I just sent the save-the-date reminder as the date seemed fixed already and it was about time. :-) I updated the invitation draft to reflect the idea to make a crate polishing workshop. Please review, if you like it this way. It's based on the last crate-polishing-invitation with minor modifications (no special guest this time ;-))..).Please remember, that I will not be present at the meetup itself - I'm just helping out with the invitations. I'd target next weekend to send the final invitation, ok? |
Sorry for not jumping in earlier. Thanks, @colin-kiegel for taking care of the invitation. |
Thanks @colin-kiegel! I was about to suggest sending the invitation out tomorrow with the beginning of the new week. I think I'd focus more on the libz blitz issues and mention the possibility of winning a RustFest ticket: Based on the positive feedback in April, we will do another **Crate Polishing
Meetup**.
But this time, we'd like to skip the search for crates and issues: Instead, we
want to use the list of issues (and guidelines!) the Rust Libs Team's new [Libz
Blitz] initiative has created over the last months, and dive right into fixing
and improving code. You can, of course, work in teams.
One bonus for working on these issues: You can win RustFest Zürich tickets
(incl. travel and accommodations)! See [here][rustfest] for more details.
If you have a suggestion, feel free to comment in our [planning issue].
[Libz Blitz]: https://internals.rust-lang.org/t/rust-libz-blitz/5184
[rustfest]: http://blog.rustfest.eu/libz-blitz
[planning issue]: https://github.com/Rustaceans/rust-cologne/issues/35 |
@killercup cool, I like it. Feel free to update the draft. :-) |
I like it as well! - See [here][rustfest] for more details.
+ See [the RustFest announcement][rustfest] for more details. |
I changed the invite in the issue description. Anyone else want to add something? I think it's good to go. (I'll only have time to send it out this evening; if you want to, feel free to send it out earlier.) |
Sent an email and ticked some boxes. Anyone else want to have some social media flavored fun? 😄 |
calendar, reddit done. Next: urlo |
urlo done |
So, to prepare for tomorrow, let's gather some issues! Or, how about an ad hoc evaluation? Just grab the API guidelines and a crate like
Or: Contribute to the Rust Cookbook. |
Thanks for getting on board with this. You guys are totally awesome! 💯 |
Thank you all for coming tonight! |
ToDo
Invitation draft
Rust News
union
sloop {}
canbreak
with a valueeprintln!()
The text was updated successfully, but these errors were encountered: