sustainers / website Goto Github PK

Recap of chat with @jdorfman @whit537 @piamancini and @alnermcgunn

• narrative: the role of the event in the longer arc, how it fits in a larger narrative of sustain open source.

• 3 layers of participation, inverted pyramid (audience, facilitators, organizers). facilitators 'own' sessions to help other participants achieve their meeting goals. 20/30% of participants can be facilitators. Creating a space where other people can achieve their goals, keep the eye on quality.

• TO DOS:
  a) narrative now (Gunner to have a look at #9)
  b) refine event outcome, (Gunner to have a look at #9)
  c) figure out who's coming, (Justin to share wishlist)
  d) engage with them,
  e) put together a list of sessions and identify facilitators.

Next call 3/3 10.30PT https://meet.jit.si/pia

I believe May 22 or maybe 23 is the current proposal.

GitHub is not available during May due to construction.

Microsoft's public space is also under construction in the spring.

Other options?

If we get enough sponsorship (#31) then we could consider a scholarship fund.

Replace the #hashtag area with a Carousel of relevant Tweets.

• IRL Example: https://cl.ly/0o0M351W2H26 via https://slack.com/pricing/enterprise-grid

Tweets to include:

• https://twitter.com/browniefed/status/825764697777414145
• https://twitter.com/tjholowaychuk/status/825753076598403072
• https://twitter.com/changelog/status/825378157469560832
• https://twitter.com/rajkumartreads/status/824905425506095105
• https://twitter.com/ericholscher/status/824724818696101888
• https://twitter.com/jdorfman/status/824661518792863744
• https://twitter.com/vmbrasseur/status/821189899751563264

The iframe is failing on iOS webkit

Replace unconference & #sustainunconf via: https://opencollective.com/sustainoss#support

Talk about $utainOSS on gratipay.news

Make PR

Context (2 week traffic report):

Been bugging the shit out of me (on desktop):

On this page: https://opencollective.com/sustainoss/events/2017

"Sustain OSS" should be replaced with "$ustain" to keep consistent.

Edit: updated image

@BenJam has been talking to Sloan for travel support. The process might be that we need to make a formal application to support XX tix for XX participants. A way of managing that is to add a google form on the website for people to apply for assistance with travel details.

Suggested by @alnermcgunn. Have folks get in touch if they need financial assistance—light application/review process to avoid ticket speculation.

@piamancini to revise tickets on OC page.

@piamancini suggests on (private) weekly call that food is easier for companies to handle as gift-in-kind vs. money (budget, #31) per se.

Need to add sponsor logos to the sponsor page.

via @piamancini

• also, we need to come up with a confirmation email wording for when someone makes a donation
• so far they don't know they are confirmed
• if you can draft something, I can edit the open collective template on the back end

After adding another sponsor I adjusted the max-width to fit them on 1 line.

Mobile is another story:

301 unconf to oss

It would be helpful to have an input field where I could put my email address and receive notifications of updates.

During Tuesday's call, we decided to remove the "BROUGHT TO YOU by the following organizations" in the footer.

From the get-go, we said any profits will go back to the community. I think it would be fair to split those funds evenly between the two funding platforms involved, Gratipay & Open Collective.

Million dollar question: Which projects will these funds be distributed to?

cc @piamancini @whit537

Starting to brainstorm on (private) weekly call about who we want there.

WIP

• Link backs
  • Awesome JSON Datasets #71
• Podcast
  • Elevator pitch
  • Changelog - @jerodsanto
  • RFC - @piamancini not sure if they planned season 2 out yet cc: @jerodsanto
• Blog post
  • Opensource.com - @jdorfman (goes live 4.6.17 at 3am ET)
  • Gratipay News - @whit537 #70
  • GitHub Blog - Brandon Keepers
• Twitter
  • Setup OpenCollective auto tweet
  • Rename?
  • #hashtag:
    • #sustainoss
  • Schedule tweets
    • Thank GitHub
    • Thank StackPath
    • Thank Sticker Mule
    • Thank ...
• Answers for FAQs
  • What is $ustainOSS?
  • How is it written? (Sustain OSS, $ustainoss, $ustainOSS, $ustain OSS)
  • How many people will be there?
  • What is the price?
  • Will you have discounts for students?
  • What will you be serving for lunch?
  • Will there be talks?
  • How many days is it?
  • Will there be hotel accomidations?
  • Will there be other events in different countries?
  • Do you accept in-kind sponsorships?
  • When will I receive a ticket?
  • What other events can you compare $ustain OSS to?

Update title

It's helpful to be able to cross link Slack conversations in GitHub issues to give full context (e.g.), but the Nothing is already eating us. SlackArchive is the best solution I've found, though it's a bit rough around the edges.

The JavaScript Foundation has joined us as a sponsor. We need to add their logo and link on the sponsor page 2nd row:

Link: https://js.foundation/
Logo: https://cl.ly/0Z2y0B2M3m2Z

What would you all think of moving the Slack channel from OpenCollective to Changelog? Seems like a good hook to get Changelog more involved with $ustain, and it aligns well with their purpose and role in the wider community.

cc: @adamstac @jerodsanto

I can do this. We no longer use the opencollective slack to talk about this website.

Create a promo order for:

• New_Sustain_logo.svg 75 3" die cut stickers
• sustain-3in-square.svg 50 3" die cut stickers

Sustain-Stickers.zip

Gunner recommends against calling it an "unconf" because of baggage in the term. What else could we call it?

I believe Sauce Labs asked @piamancini for this.

How do we mix in Changelog w/ Gunner's event format?

• Make sure their are know speelling or grammar issue
• Find replacement for "unconf"

@jdorfman Could I get perms on this repo to configure for GH pages?

• Sustainer Jack
• Sustainer Jill

https://opencollective.com/sustainoss/events/2017

We can now use the open collective ticket page. We need to change a glitch in the time, because it displays it in the timezone of the user.

Lmk what you think about the ticket options.

Gunner is going to be a key player in this event. We should front-load that on the website and explain who he is and why we picked him to help us here.

Also, is he on GitHub? Feels weird to keep talking about him behind his back. ;-)

We need to be more transparent with who the organizers/co-founders are. I think we need to have a section in about with bios for:

• @jdorfman
• @whit537
• @piamancini

In response to https://twitter.com/SustainOSS/status/850089828980883456

What do we want to accomplish during the event?

What is the larger narrative this day fits within?

Just noticed that the Subscribe button doesn't use the same style (font, border, size) as the other buttons.

We need 2 calendars:

• Public - Events for attendees
• Private - Events for organizers, media partners, sponsors

related: #55

On the sponsors page, we've got three orgs in a top section, four more in a bottom section, and then nine in the footer. We have four on the Open Collective page. What is the intention regarding which to list where? It's not obvious to me from the current spread:

I was looking at this https://alterconf.com/sponsor and I think that professional childcare, could be a great way to help bring more women on board. I'd love to find a sponsor to cover this for SustainOSS. Also, maybe @bkeepers, is this sth github provides?

Thoughts on who can be interested in sponsoring are welcome!

Send pitch:

• https://opensource.com/ (✅ blog)
• https://itsfoss.com (✅ blog)
• http://fossforce.com/ (✅ confirmed)
• https://www.ossblog.org/ (❌ declined)
• Wired (❌ declined)
• https://fossbytes.com/ (form)
• https://thenewstack.io/ (emailed)
• https://dev.to (emailed)
• http://www.osfeels.com/ (emailed)
• Stormy Peters's blog (@piamancini?)
• Changelog
• https://medium.com/open-source-communities

• Answers for FAQs
  • What is $ustainOSS?
  • How is it written? (Sustain OSS, $ustainoss, $ustainOSS, $ustain OSS)
  • How many people will be there?
  • What is the price?
  • Will you have discounts for students?
  • What will you be serving for lunch?
  • Will there be talks?
  • How many days is it?
  • Will there be hotel accomidations?
  • Will there be other events in different countries?
  • Do you accept in-kind sponsorships?
  • When will I receive a ticket?
  • What other events can you compare $ustain OSS to?

re-setup webmaster tools on Google

• Add all your website versions
• Select your preferred version
• Select target country
• Share access with co-workers
• Associated Analytics web property
• Submit a sitemap file

This is an example of an email that goes when someone buys a tix

Dear NAME,

We are excited that you'll be joining us at Open Collective March Meetup on Wed Mar 08 2017, 7pm EDT at Swift Hiberian Lounge.

This confirms your 1 ticket.

In case you didn't know, we manage our budget transparently. You can follow our future activities and how we will be spending this money on our open collective page: https://opencollective.com/opencollective.

Warmly,

– The OpenCollective open collective

Remaining pieces:

• Static Site Generator
• finish copy
  • better formatting on Agenda
  • link links on About
  • Google form on Sponsor
  • proof-read all #7
  • Chad, Francesca, Fotis in MIT License
  • Remove #dollarsignustain on front page
• wire up "Buy Tickets" button
  • decide if we can support "19 remaining"
• Google Analytics
• meta name="theme-color"
• Open Graph meta
• Twitter meta
• Domain
• DNS
  • SSL / CloudFlare
• Add more organizers in COC under "Contact the..."
• Fotis Cleanup (@XhmikosR)
  • CSS for Table
  • CSS for mobile
  • Webperf
  • Favicons
  • manifest.json
  • urls
  • Add GA code

<script>
  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
  ga('create', 'UA-90698689-1', 'auto');
  ga('send', 'pageview');
</script>

For some reason on my Nexus 6P (Android/Chrome latest) the for isn't applying the style sheet correctly:

After the cache is cleared it looks like:

Before cache cleared: