Communicating Material Culture Diversity by Creating 3D Online or Virtual Reality Scenes or Games with Three.js

[hawc2]

Programming Historian in English has received a proposal for a lesson, 'Communicating Material Culture Diversity by Creating 3D Online or Virtual Reality Scenes or Games with Three.js' by @tosca-har and @mathieuleclerc17.

I have circulated this proposal for feedback within the English team. We have considered this proposal for:

• Openness: we advocate for use of open source software, open programming languages and open datasets
• Global access: we serve a readership working with different operating systems and varying computational resources
• Multilingualism: we celebrate methodologies and tools that can be applied or adapted for use in multilingual research-contexts
• Sustainability: we're committed to publishing learning resources that can remain useful beyond present-day graphical user interfaces and current software versions

We are pleased to have invited @tosca-har to develop this Proposal into a Submission to be developed under the guidance of @carlonim as editor.

The Submission package should include:

• Lesson text (written in Markdown)
  • For guidance, we recommend Sarah Simpkin's lesson Getting Started with Markdown
• Figures: images / plots / graphs (if using)
• Data assets: codebooks, sample dataset (if using)

We ask @tosca-har to share their Submission package with our Publishing team by email, copying in @carlonim .

We've agreed a submission date of April. We ask @tosca-har to contact us if they need to revise this deadline.

When the Submission package is received, our Publishing team will process the new lesson materials, and prepare a Preview of the initial draft. They will post a comment in this Issue to provide the locations of all key files, as well as a link to the Preview where contributors can read the lesson as the draft progresses.

_If we have not received the Submission package by April, @carlonim will attempt to contact @tosca-har. If we do not receive any update, this Issue will be closed.

Our dedicated Ombudspersons are Ian Milligan (English), Silvia Gutiérrez De la Torre (español), Hélène Huet (français), and Luis Ferla (português) Please feel free to contact them at any time if you have concerns that you would like addressed by an impartial observer. Contacting the ombudspersons will have no impact on the outcome of any peer review.

[charlottejmc]

Hello @carlonim, @tosca-har and @mathieuleclerc17,

You can find the key files here:

• .md: /en/drafts/originals/communicating-diversity-in-3D-and-VR.md
• images: /images/communicating-diversity-in-3D-and-VR
• assets: /assets/communicating-diversity-in-3D-and-VR

You can review a preview of the lesson here:

• http://programminghistorian.github.io/ph-submissions/en/drafts/originals/communicating-diversity-in-3D-and-VR

---

I've updated the links to images within the lesson file so that they follow our liquid syntax:
{% include figure.html filename="file-name-1.png" alt="Visual description of figure image" caption="Figure 1. Caption text to display" %}

I have updated the image file names to follow our image naming convention, but there are still two important parts for you to fill in: the image 'alt-text' (Visual description of figure for visually impaired readers) and the caption. Please feel free to make these edits directly to the markdown file, or to write them to me in a comment (or via email: publishing.assistant[@]programminghistorian.org).

I also left out two images: scene.jpg and final_scene.png, because I could not see them in the markdown file. If you'd like to add them in though, please do let me know!

Thank you!

[anisa-hawes]

Hello Kristine @tosca-har and Mathieu @mathieuleclerc17,

What's happening now?

Your lesson has been moved to the next phase of our workflow which is Phase 2: Initial Edit.

In this Phase, your editor Massimiliano @carlonim will read your lesson, and provide some initial feedback. Massimiliano will post feedback and suggestions as a comment in this Issue, so that you can revise your draft in the following Phase 3: Revision 1.

%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
              'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
              'cScale1': '#882b4f', 'cScaleLabel1': '#ffffff',
              'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
       } } }%%
timeline
Section Phase 1 <br> Submission
Who worked on this? : Publishing Assistant (@charlottejmc) 
All  Phase 1 tasks completed? : Yes
Section Phase 2 <br> Initial Edit
Who's working on this? : Editor (@carlonim)  
Expected completion date? : June 3
Section Phase 3 <br> Revision 1
Who's responsible? : Authors (@tosca-har + @mathieuleclerc17)
Expected timeframe? : ~30 days after feedback is received

Note: The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment.

[tosca-har]

Hello Anissa Mathieu's GitHub is mathieuleclerc17 Forgive my ignorance but am I correct in thinking that when there are reviewer / editor comments I'll get notified through GitHub? Regards Kris Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Anisa Hawes ***@***.***> Sent: Friday, May 3, 2024 4:22 AM To: programminghistorian/ph-submissions ***@***.***> Cc: Kristine Hardy ***@***.***>; Mention ***@***.***> Subject: Re: [programminghistorian/ph-submissions] Communicating Material Culture Diversity by Creating 3D Online or Virtual Reality Scenes or Games with Three.js (Issue #607) Hello Kristine @tosca-har<https://github.com/tosca-har> and Mathieu (Kristine, Please could you share Mathieu's GitHub handle with us?), What's happening now? Your lesson has been moved to the next phase of our workflow which is Phase 2: Initial Edit. In this Phase, your editor Massimiliano @carlonim<https://github.com/carlonim> will read your lesson, and provide some initial feedback. Massimiliano will post feedback and suggestions as a comment in this Issue, so that you can revise your draft in the following Phase 3: Revision 1. %%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': { 'cScale0': '#444444', 'cScaleLabel0': '#ffffff', 'cScale1': '#882b4f', 'cScaleLabel1': '#ffffff', 'cScale2': '#444444', 'cScaleLabel2': '#ffffff' } } }%% timeline Section Phase 1 <br> Submission Who worked on this? : Publishing Assistant ***@***.***) All Phase 1 tasks completed? : Yes Section Phase 2 <br> Initial Edit Who's working on this? : Editor ***@***.***) Expected completion date? : June 3 Section Phase 3 <br> Revision 1 Who's responsible? : Authors ***@***.*** + Mathieu) Expected timeframe? : ~30 days after feedback is received Note: The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment. — Reply to this email directly, view it on GitHub<#607 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANVXZEFBQWM7ZA6D3JFSRY3ZAJ76JAVCNFSM6AAAAABE52Z67SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGIZDAMRYGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[anisa-hawes]

Thank you, Kristine @tosca-har! I've now tagged Mathieu in my earlier comments.

You can configure your GitHub notifications by navigating to Settings (accessed from the menu which opens when you click on your profile avatar image in the upper right corner). Select Notifications and scroll down to define your Subscriptions. It sounds as though you want to receive notifications in the Participating, @mentions and custom category. Click on the grey button which reads: Notify me. This opens a small pop-up where you can select the channels via which you would like to receive notifications. Select the notification channels of your choice and click Save.

When receiving notifications in Participating, @mentions and custom category, you will be notified if anyone comments in this Issue (or any other Issues you have contributed to), or @mentions your name.

--

Massimiliano @carlonim will provide initial feedback as a comment in this Issue within the coming ~10 days. 🙂