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

Website content constraints #96

Open
AOrthVector opened this issue Feb 13, 2021 · 2 comments
Open

Website content constraints #96

AOrthVector opened this issue Feb 13, 2021 · 2 comments
Labels

Comments

@AOrthVector
Copy link
Contributor

One of the constraints the website has is content. As one of the webmasters, what I have to rely on to publish on the site is pulling content from recorded TSC meetings, looking at screen shots of slide decks on the website, sharing the occasional podcast or webinar. I don't often have something to publish that has been created by, as it were, by the GenevaERS project.

I want to have current content on the website. We have a lot of work streams running in parallel but not much public published information on those workstreams. I think it will also help anyone interested in GenevaERS, regardless of why, get a feel for what's going on with the project.

One aspirational goal is that GenevaERS.org has new content every 7 to 10 days.
Methods of making this achievable that I can think of is:

  • Screen recording explanations / demos of just completed or in progress work. For those that don't have existing software, there is open source software called Open Broadcaster Software (OBS) that can meet this need
  • Be like Bob. Bob frequently provides updates in writing on his work. I think Bob is someone to model off of in this regard. But I think we need to be mindful of also providing some high level context that would make it easier to grab some content and create a website post out of it.
  • Provide all the powerpoints! Uploading powerpoints, Word, etc. documents makes it easier to copy and paste text or publish snippets of a topic on the website.

Please provide thoughts

@KipTwitchell
Copy link
Member

@AOrthVector, in working through the Spark POC, I realized there was a meeting where I presented the result of a Scala POC that did Common-Key buffering. I have uploaded it to GenevaTV (unlisted now, link is https://youtu.be/rj_ZJQ6Tgq0). I have also made a blog entry (draft) with the slides shown in the video. Not sure how you might use this, but I think at least it is some good historical content. @neilbeesley and @SaPeresi, you might be interested in checking out the video link.

@KipTwitchell
Copy link
Member

Location determination, and then people can upload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

2 participants