Skip to content
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

How do attendees communicate? #25

Closed
val-pf opened this issue Apr 11, 2024 · 14 comments
Closed

How do attendees communicate? #25

val-pf opened this issue Apr 11, 2024 · 14 comments

Comments

@val-pf
Copy link
Contributor

val-pf commented Apr 11, 2024

Hello,
what is the preferred way of allowing communication between attendees, and possibly attendees and speakers?
GIthub?
Slack?
Gitter @julianpistorius ?
hackMD?
etherpad?
...???
Discuss please!

@val-pf
Copy link
Contributor Author

val-pf commented Apr 11, 2024

Here's my thoughts:
Hack MD:

  • love how accessible they are, but might need to 'teach' how to use them
  • last year, having two large hackMDs did not work well
  • two years ago, one hackMD per session was challenging to navigate for attendees
    Slack:
  • two years ago, everyone HAD to join slack, we still have ~300 zombie accounts in the slack from that, and engagement in those channels was fairly low
  • we do miss out on people if we ONLY use slack for communication
  • retrograde amnesia

@jcoliver
Copy link
Member

Depends on primary goals of communication.

  • For IMs, Slack is pretty nice (acknowledging great points by Val, above, 🧟 ).
  • If there are announcements that need to go to everyone (more one-way messaging), then...e-mail? 🦕
  • Collaborative documents - vanilla Google Docs can work pretty well, although they don't really allow some of us to flex our markdown 💪 🤓

@hidyverse
Copy link
Contributor

Did we land on just e-mail?

@lwdozal
Copy link
Contributor

lwdozal commented May 1, 2024

Not to overwhelm our webmaster, but is there a way to have some type of announcements on the webiste? like put a social media or slack feed, or have the 'vanilla' google doc/google sheet on the page?

Or do we want a space where participants can comment back and ask questions?

@julianpistorius
Copy link
Member

julianpistorius commented May 9, 2024

I would vote for Gitter. And I would set up a bridge from Gitter to Slack.

Update: It's also possible to view the messages as a feed on the website - https://view.matrix.org/room/!zjSBLlUkYiQKGGCyTt:gitter.im/

@julianpistorius
Copy link
Member

@hidyverse
Copy link
Contributor

My preference is gitter > X largely because of the topics @Aariq brought up here

@lwdozal
Copy link
Contributor

lwdozal commented May 12, 2024

OK! how do we get gitter onto the website? Or how can we get participants onto it so we can communicate. Should we include this in our last push of messaging tomorrow? Sorry I'm V new to gitter.

@Aariq
Copy link

Aariq commented May 13, 2024

There are several built-in ways to add "comments" to Quarto pages, although I suspect this is not quite what we want. https://quarto.org/docs/output-formats/html-basics.html#commenting

@julianpistorius
Copy link
Member

julianpistorius commented May 13, 2024

I recommend:

  1. Use an HTML iframe element to embed the read-only Gitter messages view for ResBaz/Arizona (see the link I posted above) into the conference page (and possibly the home page)
  2. Add a link to the ResBaz/Arizona Gitter channel just above the embedded Gitter messages view. Gitter should prompt people to sign up/log in.
  3. Email attendees information about Gitter, and the link to the ResBaz/Arizona Gitter channel.

This way anyone who visits the website can read the most recent event chatter without needing to log in to Gitter, but there is a link that they can follow to take part if they want to.

How does that sound?

@julianpistorius
Copy link
Member

Currently there is no information about the event sessions. What do folks think about creating individual HackMD docs for each session, and linking to them from the schedule Google Sheet (similar to the unconference sessions which link to self-signup Google Sheets.)

Each HackMD can contain the speaker bio, background information, learning outcomes (if a workshop), etc. We can link to the 'read' view for each HackMD (to avoid confusing people with a full Markdown editor.)

I believe HackMD makes it easy to embed a HackMD document into a website. That way we don't need to send people to a different site to view up-to-date event information.

Thoughts?

@Aariq
Copy link

Aariq commented May 13, 2024

Yes, let's do that. I'd love to have a space to take notes or at least get contact info for attendees should they wish to provide it

@lwdozal
Copy link
Contributor

lwdozal commented May 14, 2024

So, for communication with participants I'll send out information of where to find the Gitter feed and HackMD docs each day in an email? Will have some drafts ready that will go out each day.

@julianpistorius
Copy link
Member

@lwdozal & @Aariq I've created the HackMDs for each session and linked them from the schedule.

Can we please let the presenters know so they can add any links and resources there? They can use it to whatever extent they want, including for notes, slides, etc.

Day 1 (Virtual):

Day 3 (In-person):

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

No branches or pull requests

6 participants