Closed wolstaeb closed 3 years ago
Awesome work Robert!
Don't know how you manage to get this amount of details since you were also a moderator. Please kindly find notes from my side through this following link : https://docs.google.com/document/d/1AeQIo6SQjnfri67fjrBX8iQ3aywWNDneGYKw6zSkijg/edit#
Since the format you have developed is different from what I am used to. How would you reckon the method of me adding points to it. Would I just edit directly or would you prefer I provide my documentations as above and for you to edit the documents?
There are points that I forgot to remind everyone are :
Would really appreciate everyone's input. Will also share this onto our Discord channel also.
Awesome regards, Yan
@wolstaeb , would it be possible to share the raw files of the template you designed for the landing page? I would like to use the semi-transparent geometric shapes you overlay on top of the Zoom profiles collage. My intent is to continue that style for the 9 Instagram steps first iteration.
@YanTirta should have permission to just edit the content. So please go ahead and update it with additional details. If you'd prefer that I do it just say.
Since the format you have developed is different from what I am used to. How would you reckon the method of me adding points to it.
@YanTirta I'll send you the files.
would it be possible to share the raw files of the template you designed for the landing page?
Great notes @wolstaeb - a pleasure to see !
@wolstaeb , kindly find the translated document that we previously talked about. With a short reminder, "we agreed to have a tab on the landing page that translates on how to propose a proposal and how to become a CA. With intent for my community -and others in their own languages- to have a baseline understanding of how things might work."
Link for How To Propose a Proposal : https://docs.google.com/document/d/1zvk6UWk_Q6n88RPoPz2_4AACvLrchFcbhlFggNbGAtU/edit?usp=sharing
Link for How To Become a CA : https://docs.google.com/document/d/1NpIMAiUAS_cJC3EcoaRMKYml4L6YyYfJ0bplkq8sEK4/edit?usp=sharing
Thanks @YanTirta I'll turn these into markdown files in a documentation repo. These will then be pulled into the website.
kindly find the translated document that we previously talked about.
Link for How To Propose a Proposal : https://docs.google.com/document/d/1zvk6UWk_Q6n88RPoPz2_4AACvLrchFcbhlFggNbGAtU/edit?usp=sharing
Link for How To Become a CA : https://docs.google.com/document/d/1NpIMAiUAS_cJC3EcoaRMKYml4L6YyYfJ0bplkq8sEK4/edit?usp=sharing
Hi @YanTirta, do you have the links to the original source documents you translated these from?
I do, please kindly find the original sources @PardusEidolon : How To Propose a Proposal : https://docs.google.com/document/d/1oE_cnP0gksdAanXV4w5DYaDNp_tbYEvyHhTUG4HYZ3Q/edit?disco=AAAAG42-Ypk&usp_dm=true
How To Become a CA : https://cardanocataly.st/community-advisor/guide.html
I do, please kindly find the original sources @PardusEidolon : How To Propose a Proposal : https://docs.google.com/document/d/1oE_cnP0gksdAanXV4w5DYaDNp_tbYEvyHhTUG4HYZ3Q/edit?disco=AAAAG42-Ypk&usp_dm=true
How To Become a CA : https://cardanocataly.st/community-advisor/guide.html
Thanks! @YanTirta
However the link to the community advisor guide is broken is there an alternative link elsewhere?
edit: I've found the CA Guide on the ideascale website is this what you translated it from? https://docs.google.com/document/d/1QkdaFK1tigrSI40iMeV3UP9GyTGsoqVmCUp7OJz0WFs/edit
Eastern Hemisphere Meeting - Saturday, 7th August 2021 - 6:00 UTC
Attendees
Documentation
Overview of Discussion
Notes
Answering Questions in Breakout Rooms
@YanTirta raised an issue about answering questions in the breakout room. He attempts to answer questions but people in the rooms may be more knowledgeable about Cardano. They are Stake Pool operators and as a moderator, he didn't know as much about the topic being raised.
Reflecting on the English room, @wolstaeb had these comments.
One suggestion is that room moderators can/should invite others into their room to answer questions. The request can be put in sessions chat and @wolstaeb Greg etc could jump in. Where a moderator could do the needed interpretation.
NOTE: In Discord, Tim O'Brien has suggested also doing a FAQ that would help with answering questions.
Fund 6 Community Challenge Setting
Dor has suggested C3ETH group put up some language/country-specific community challenges.
Dor also provided links earlier to a Challenge setting workshop notes and the recording of the workshop.
The aim is that the challenge, the proposals, the review process, and the voting, are all done in the native language of the country. To do this would require developing a full pipeline and on-boarding for Catalyst:
This is rather a large undertaking, so we'll have to consider which language/countries to do first. There is also a matter of compensation for effort/time that may fall into one of the Fund 6 C3ETH Proposals.
@FelixfromSwarm suggested as a way to onboard and start the proposal funnel is to use the Catalyst Swarm Hackathon and the Mini-proposals. See issue #18 notes.
Fund 6 C3ETH Proposal(s)
The C3ETH proposal(s) should be structure into two parts:
The intention is these proposals help fund the effort to build the community and compensate for doing the work required on projects like developing a native language Community Challenge proposal and proposal funnel. As Greg has suggested these proposals will be half retroactive funding (funding for past effort), and proactive funding.
These proposals will be fully translated into as many C3ETH languages as possible and the proposal structure and artefacts will support doing that. Video will also play an important role in communicating the goals of C3ETH and the proposals.
Translation
The C3ETH is made up of lots of languages and cultures. In order to reflect that, and be as inclusive as possible, it is very important to do language translations.
To make this tractable for our community we will be using Git/Github/Gitbook and Markdown. For more advanced documentation @wolstaeb prefers asciidoc. Along with tools such as the website static site generator hugo to make it as easy and consistent as possible.
To help develop team skills using these tools:
@wolstaeb demonstrated markdown and how it can be used to update the published C3ETH website (when it is up.).
NOTE: Tim O'Brien's suggestion of an FAQ would also be a good exercise in helping the team do translations.
Instagram Nine Steps
@YanTirta brought up his aim of developing social media posters - nine steps to project catalysts. The aim is to use these social media assets to promote both Catalyst and C3ETH. @YanTirta asked if these would be useful for helping with translation exercises. @wolstaeb agreed and suggested doing the text of these posters first, then branding. Putting the text up into GitHub and work on the translations.
Website and Landing Page.
@wolstaeb discussed a draft landing page design/poster Tim had sent (as per discussion in #15 ) that was based around the original C3ETH presentation design @FelixfromSwarm had done.
Two issues with the approach were raised by @wolstaeb:
Just prior to the meeting @wolstaeb did a mockup of a website design using some collecting images from prior meetings. The idea was to explore a more fun/friendly design while avoiding being too slick. This was presented to the team present, and they liked the approach and agreed with moving ahead in that direction and refining it.
@YanTirta asked how others can help, and @wolstaeb suggested working on the content of the site.
Website Video Mockup.
Continuing on the Website work, @wolstaeb asked @PardusEidolon to quickly create a mockup video suitable for the website's home page. The work would also lead to developing banner videos discussed in #15. The draft video was presented to the team.
People liked the direction so it was agreed to refine the video. Since the video used what sources we had available we will need to take action to collect better source content (peoples zoom video) from an upcoming meeting. This will require peoples consent.
We also discussed creating (rendering) multiple videos for each language. These would be presented on the respective language home page. To do that we will need translations. Since the amount of translating need is small, there was seen as a good exercise to get team members to use to using Git/Github and markdown for translations.