Closed aeiras closed 2 years ago
@aeiras This is a good idea, but I wonder if it's more scalable to have language-specific videos that describe JakartaOne as a whole, and this can be used as part of social media?
I would like to see every year the new and known contributors part of the JakartaOne committees, JUG leaders rotates from time to time. This requires a logistic for recording, editing, and producing video for each JakartaOne edition every year.
You have a point, @cesarhernandezgt!
Within the past few years and a few iterations of JakartaONEs, we have seen members rotate when events return/iterate.
Since all members contributing to each regional event are volunteers, it is up to those committees to decide how to introduce themselves. Either video, using Jakarta INFRA videos or similar... blogs via jakarta news, etc...
What I see lacking is a written guideline in the form of WIKI in the JakartaONE repo. The document, currently a PDF explaining how to bring forth a JakartaONE event, ought to be a wiki under the project's REPO. Those making the events ought to be welcome to submit their feedback via PRs directly via that wiki directly.
When PDF is a guideline set, it shows no room for improvement and welcomes no feedback.
@aeiras the pdf itself has the text:
Community members interested in organizing their own language specific Language SpecificJakartaOne Livestream events should create a GitHub issue
And this point to https://github.com/jakartaee/jakartaone.org/issues.
Having the PDF + a wiki on the https://github.com/jakartaee/jakartaone.org repositories has the following challenges:
https://jakartaone.org/becomeahost
rather than being pointed to github wiki.One improvement I see over having the guidelines in a community editable way under Github Pull Request workflow, I think we can migrate the PDF content into a page on the website like https://jakartaone.org/hostanevent/
.
I created https://github.com/jakartaee/jakartaone.org/issues/417 alonw with https://github.com/jakartaee/jakartaone.org/pull/418 Live preview: https://deploy-preview-418--jakartaee-jakartaone.netlify.app/hostanevent/ Screenshot
This https://deploy-preview-418--jakartaee-jakartaone.netlify.app/hostanevent/ is what i was talking about. Great job, Cesar.
IMO, the PDF guideline shouldn't exist with reference to volunteering for JakartaONEs. :)
@aeiras Closing this ticket now since the PR was already merged into the live website, thank you all for the feedback! https://jakartaone.org/hostanevent/
Using the Jakarta EE Studio youtube channel, requirement for all those present to speak Spanish, ONLY, a short 20 to maybe 30mins video recorded needs to at least:
follow a normalized questionnaire that shows not only data of the event, expectations & value but also states clearly how the community can help by stating the tools in place that brings a 365 collaboration & ownership.
introduce the volunteer committee
explain why you are involved, tracing on how the event took place- in this case this is a PILOT :) fun right!
tell us how many speakers slots are desired
tell us if the committee is going to use any of those slots either via a 20mins Event introduction (highly recommended panel) & a 30 to 40mins (jakarta EE in Español panel)
clarify if Sponsorship is possible and if so, how is that budget going to be used? Either to provide swag for all the speakers & volunteers NICE to have & push forward & whatever else that likely support the JUGs that might become involved. With this I mean, JUGs within the Communities that speak Spanish could benefit for their participation by directly getting $$$ budget added to fund their own community to push forward Jakarta EE initiates. When a sponsor knows that their money stays with the Community event, there is a level of protecting such investment to know how the money will be distributed. Clear, transparent.
Tell potential speakers what they can speak if her/his sessions are accepted- from support on slides to media designs to twitter broadcasting to video introductions, to after event how their sessions will live on. :) the value is endless.