(AdonisJS + Storybook) - React = Success? I'll detail what I found out about how to make Storybook work with AdonisJS WITHOUT adding an extra UI layer on the frontend. Basic pieces Storybook's server adapter. Without this, nothing here would be possible. This allows us to write anything we want on the server, and then for Storybook to dynamically fetch said anything for use in stories. Storybook's {builder,manager}-webpack5 packages. When using Adonis' Encore-based Webpack tooling, it uses Webpack 5. Storybook ships with Webpack 4. You can guess that those different versions don't like each other, so we can tell Storybook to use Webpack 5 instead. Adonis' components. Adonis encourages writing components that can take props and slots, just like in component systems like React. Putting them together Install Storybook

Introduction This is a general-purpose guide designed to onboard people into the CouchDB release cycle. Parts of it can also be adapted to troubleshoot building CouchDB on your local device (something that, as an end user, you shouldn't need to do unless we don't support your architecture/OS). This guide is currently a work in progress. Prerequisites To build CouchDB, you will need: A bit of free space on the disk you're building CouchDB on. Erlang/OTP. This can be any version above or equal to OTP 19, but for the sake of convenience with using couchdb-pkg, it should be OTP 20 (I use 20.3.8.26, the latest in the 20 release line). I'd recommend asdf for managing multiple Erlang installations.

Docs I used: https://docs.github.com/en/actions/guides/building-and-testing-nodejs https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions I restricted the branches to master and feat/gha (my branch) first during PR testing. Env Vars

Photo policy: get badges or lanyards or something where you can tell someone's preference from a picture Presentation Part AUN: add cargo --version to slides (in the installation segment) AUN: add visual studio installation to slides (or link to tutorial) finish the port of the tutorial to ggez (rather review things that should be familiar from other languages to get everyone on a similar level) in presentation focus on what people need now. AUN: add xcode to mac

This guide covers everything you can currently do after you've gotten people to sign up to your BA run. Prioritizing Attendees The central feature of Ferne right now is the ability to easily sort attendees into parties. However, no attendee is created equal - there are some who you might want to guarantee a spot first, such as party leaders or first timers. First things first, you need to see all of the people you want to give priority to in one spot. You can use the attendee list page's search and filter functions for this. For example, party leaders will usually sign up first, so they will be all in one spot if you sort the "signed up at" column. First-timers can be identified by searching for "Never entered", or sorting the column for that field. Once you have all of the people you'd like, you can click the checkboxes to select them. Shift-clicking a checkbox selects all attendees between the previously checked box and that one. You can also use the "select all" checkbox at the top, it'll select every attendee you can currently see (but not the ones you can't see, e.g. if you searched for something). This could look something like this: You can then click on the blue button to the right to select all of these attendees for inclusion. Being selected for inclusion (I'm open for a less confusing term) basically means these people are guaranteed a spot in the event and have priority when being assigned to a party. The list might break a little bit when you do this, that's something I'm working on, it just resets the order of things, but your selections are still locked.

--- tags: rustbridge --- # RustBridge Berlin Meeting 20 Nov 2019 - Tanks: Stickers for nametags have been ordered, will be printed on Friday ## TODO - Marisa: Host Rusty Snake book somewhere - Marisa: Write emails to students (install rust, set up editor) and volunteers (look at tutorial, prepare a motivational talk if they want to) - Tanks: Print stickers and stuff - Tanks: Finish tutorial Meeting time on Saturday: 9:30

--- tags: rustbridge, rustfest --- # The 2nd Great Patriotic Bridge Building Effort - RustBridge (https://github.com/rustbridge) and Rustlings (https://github.com/rust-lang/rustlings) need some work done - We did the exact same thing last year at the impl days, because I have no motivation to do it otherwise - If you want to work on anything, come talk to me (Marisa) in room 208 or ping me on Discord! (marisa#0229) ## RustBridge Tasks - We need to update the website at rustbridge.com. This w

--- tags: rustbridge, postmortem --- # RustBridge RF Barcelona Postmortem ### What went well? - Rustlings is still genuinely helpful, even with the 2-day structure - Putting it in the middle allowed people to challenge their current understanding ### What could have gone better? - The two day structure was generally not a great idea for retaining the audience - A lot of people dropped off on the second day to visit a different workshop - Maybe it would have been better to just run it

--- tags: rustbridge, rbber, meeting --- # RustBridge Berlin orga meeting 2019/09/25 - Sollte: einfaches slidedeck - Host website on Netlify - Workshop Date: 30th/23rd of November ## Workshop schedule - snake! as an introductory project - Installation in the beginning/ morning - Be prepared to answer questions about Windows installation problems - intro slides check/update/expand (eg crates.io etc) - rustlings until lunch (and maybe a bit after) - Maybe have lightning talks about different fi