-
Notifications
You must be signed in to change notification settings - Fork 27
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
Feature Request: Add 2023 F2F workshop content #195
Comments
Hi @hexsecs , |
sure @shubhusion go ahead |
Can you provide me the Content ? |
cc @hexsecs , @jhdalek55 |
I have both the master slides from 2022 (our slides) plus the featured speaker presentations. I also have the speaker presenetations from 2023 and from the virtual workshop in March of 23. Do we have permission to post the featured speakers talks? |
@jhdalek55 provide me the content to be added |
Sure, take your time!
|
I've attached presentations from the 2022 workshop and 2023 workshop. Below I've also included the master slide set from our March 2023 workshop |
Ideas for Adding Workshop Content to the Website1. Dedicated Workshop Pages
2. Resource Library
3. Blog Posts or Articles
@jhdalek55 let me know how content should be added. |
@hexsecs @iramcdonald @tkfu @JustinCappos I'd like to get your input on this. I was thinking option number 1, where each of our workshop sessions had it own page. That page could include presenter bios, and abstracts. However, I could also see this done as Option 2, where we could categorize this content by topic. What does everyone think? |
I actually like both options 2 and 3 where we have a page for the all workshop content in one place and then have a recap blog post following each workshop. The blog post is useful for promoting Uptane and giving a recap of the workshop which we can publish to the mailing list, linked in, and discord group. |
Since I have a lot of the resource materials, I'm happy to put content together which ever way the group wants to go. |
@jhdalek55 So How should I add Workshop Content? Which option do you prefer from the above suggested? |
I'm waiting to hear from other team members. It's not my decision alone. |
Hi,
I like Phil's suggestions for combined options 2 and 3.
Cheers,
- Ira
…On Sun, May 26, 2024, 8:35 AM Philip Lapczynski ***@***.***> wrote:
I actually like both options 2 and 3 where we have a page for the all
workshop content in one place and then have a recap blog post following
each workshop. The blog post is useful for promoting Uptane and giving a
recap of the workshop which we can publish to the mailing list, linked in,
and discord group.
—
Reply to this email directly, view it on GitHub
<#195 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE33UO3BMJW524DOJU4XZ2LZEHJIZAVCNFSM6AAAAABFJDQPPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGIYDKMJYGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Based on the above suggestions, the group prefers a combined approach of Options 2 and 3. Please advise on how to proceed. @hexsecs @jhdalek55 |
@shubhusion I think this requires some new copy before it can be implemented. @hexsecs do you want me to draft this? |
Coming back to this because I have a question--@hexsecs, why was this initiated when the 2022 workshop materials are already on the website, under audio-visuals. The only thing missing from that page at https://uptane.org/learn-more/audio is the Spring 2023 materials. Perhaps all that is needed is to change the title of this section to "Workshop Presentations" as, with the exception of the original demo and Trishank's original Uptane presentation at escar Europe, all of these are workshop presentations. We could still add a blogpost with a link to this page. |
It was a typo in the title, @jhdalek55 is correct, it should be 2023. |
Is your feature request related to a problem? Please describe.
No response
Describe how you would like this problem to be resolved
No response
Describe alternatives you've considered
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered: