Skip to content
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.

London Meetup #51

Closed
ZeeCoder opened this issue Jan 24, 2018 · 11 comments
Closed

London Meetup #51

ZeeCoder opened this issue Jan 24, 2018 · 11 comments

Comments

@ZeeCoder
Copy link
Collaborator

I'm not sure where else to discuss this: it seems I'll do a talk on container queries and how they work with react components.

If anyone has ideas on what I should not forget to mention, feel free to post a comment here.
I'll definitely talk about existing plugins, and about the movement at the WICG for example.

@ZeeCoder
Copy link
Collaborator Author

Here's a link to the meetup, it's very popular with developers queuing at the entrance every month:
https://react.london/

@eeeps
Copy link
Collaborator

eeeps commented Jan 24, 2018

::wonders if we should start a Discourse or a Slack or something::

Edit: or perhaps a wiki will do?

@ZeeCoder
Copy link
Collaborator Author

I think using Slack is a fab idea!
It would be much easier to discuss stuff like this for example.

Which is definitely not fit for a wiki :D

@tomhodgins
Copy link
Collaborator

Discourse > Slack, as far as system resources go. Slack is a beast :'(

@ZeeCoder
Copy link
Collaborator Author

I usually run it in a tab and it's a-ok, but I'm on board with discord too

@ZeeCoder
Copy link
Collaborator Author

Ah wait, you said Discourse? I have no experience with that one :D

@ZeeCoder
Copy link
Collaborator Author

At a glance I would still prefer Discord, or Slack, but let's wait for others to chime in too. :D

@tomhodgins
Copy link
Collaborator

Whoops, I meant Discord 👀 I have just started using it because Slack was too heavy for my Macbook Air :/

@ZeeCoder
Copy link
Collaborator Author

In case someone's interested, I've sent in my abstract on what I'll try to fit in my 20m talk:
https://github.com/ZeeCoder/react-london-container-queries

On another note: shall we make a Discord channel then?
I'm not sure if we need it tbh, but worst case scenario we won't use it much. 🤔
/cc @eeeps @tomhodgins

@eeeps
Copy link
Collaborator

eeeps commented Jan 28, 2018

I went ahead and spun up a Slack. To signup, go here.

Slack because:

  1. I'm used it, and it was easy to set up.
  2. I have zero data to back this up, but I feel like webby/engineer-y/design-y people are comfortable in it (whereas Discord looks (?) more catered to the gaming community (?))

@tomhodgins, I turned on the IRC and XMPP gateways to the channel, which should allow you to chat with a (much) lighter client, if you need to. I just tested it with IRC and while the setup was cumbersome (❤️ U IRC), it worked; here are the docs; let me know if you need help setting that up.

@ZeeCoder awesome! I added your talk + a link to the abstract to the minty-fresh Wiki that @andykirk just set up, under an “Upcoming Events” heading. Looks like you’re off to an awesome start and I can’t wait to hear about (and hopefully see? are they recording?) the talk.

I’ll leave it up to you whether you want to leave this issue open for more visibility, or close it. But hopefully the Slack workspace provides a more appropriate place for discussion about community events and other such things that aren’t issues with the Use Cases and Requirements doc, going forward.

@ZeeCoder
Copy link
Collaborator Author

Maybe just put it on the wiki plus we can link it whenever we think we need to move a particular discussion there.
Thanks for the setup btw, I've joined now. 👍
I believe the talk should be available, but I'll double check.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants