Issue 3069

_posts/2023-11-15-en-call-for-lessons.md

@@ -0,0 +1,78 @@
+---
+title: Call for Lessons (English edition)
+authors:
+- Alex Wermer-Colan  
+- Anisa Hawes
+layout: post
+
+categories: posts
+---
+
+The [English edition of Programming Historian](/en/lessons/) seeks proposals for new original lessons or translations to be considered for publication in 2024.
+
+**Submissions Open**: 15 November 2023  
+**Submissions Close**: 12 January 2024
+
+## What is a _Programming Historian_ lesson?
+
+A _Programming Historian_ lesson is a learn-by-doing resource that empowers readers to develop new, practical knowledge of a computational method or digital tool. Our aim is for readers to be able to apply what they learn to acquire, transform, analyse, visualise, or sustain data in their own research.
+
+Successful lessons centre real datasets and sample code that readers can handle and experiment with. These elements are supported by reflections on methodological decision-making as well as considerations of adaptations to methods or alternative tool options – this is what makes a _Programming Historian_ lesson distinct from software documentation.
+
+Our lessons are aimed at humanities and social science researchers, but are also read by self-learners with other interests. We encourage our authors to write as though they are explaining their method to a colleague or peer, to make lessons as accessible as possible.
+
+## What are the benefits of writing a _Programming Historian_ Lesson?
+
+Our lessons support readers who want to learn new skills, but the act of writing is also beneficial to authors. Writing to explain a methodology or tool to others deepens your own understanding and knowledge. It empowers your development as a critical, intentional and considered researcher, and is an opportunity to hone your technical writing skills. We encourage you to write about a method or tool that you know well, and that you have applied, adapted or advanced in your own research.
+
+## Ideas for Proposal Topics
+
+_Programming Historian_'s English edition is inviting proposals to fill gaps in our lesson directory. Please explore [our journal](/en/lessons/) to discover what’s already available, and consider what you might be able to add.
+
+If the method or approach you’re interested in writing a lesson about is already represented by the [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) editions of _Programming Historian_, we welcome proposals to translate those existing, original lessons into English. In this call, **proposals for translations will be prioritised for publication**.
+
+We’re also keen to extend our offer to learners, and invite proposals which focus on methodological approaches, digital techniques and tools including, but not limited to:
+- Text encoding, Natural Language Processing, especially for multilingual corpora
+- Statistics, machine learning, critical approaches to AI
+- Multimodal work (text/image, video/sound editing and analysis)
+- Javascript, web frameworks, static site generators
+- Web scraping, archiving and emulation
+- Mapping (especially mixing spatial and network analysis)
+- Interactive media and gaming
+- 3D modelling, scanning, and design
+- Immersive visualisation (VR/AR/XR)
+
+## How to Submit a Proposal
+
+Remember, you can either:
+
+- Propose an original English-language lesson
+- Propose a translation into English of an existing, original [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) lesson published in one of the other _Programming Historian_ editions.
+
+**If you have an idea, please send us a proposal by January 12th, 2024.**
+
+We've set up [a Google Form](https://tinyurl.com/ph-en-proposals) which you can submit directly online. There's also [a plain-text version](/assets/forms/Lesson.Query.Form.txt) which you can [send to us by email](mailto:[email protected]), if you prefer. The form has twelve questions.
+
+There is space for you to tell us about the research case study you'd like to centre within your lesson, and for you to explain how you came to use this method or tool as part of your work within the humanities.
+
+Our questions encourage you to think carefully about how your choices of software, programming languages and datasets can support our commitment to openness.
+
+We will also ask you to outline any technical prerequisites and potential limitations of access to this method or tool because our global readership work with different operating systems and have varying computational resources.
+
+It is important to us that our lessons can be translated for use in multilingual research-contexts, so we'll invite you to consider how your method or tool could be applied or adapted for use with non-English-language data.
+
+At the end of the form, you have the option to provide links to sample code or to a draft extract of your lesson if you'd like to.
+
+>In keeping with our commitment to diversity and equal access within digital humanities, we encourage proposals from women, members of minority groups, LGBTQ+ members, and peoples from the Global South. With this call, we strongly encourage the participation of Anglophone and multilingual communities beyond North America.
+
+## Questions
+
+If you’d like to ask any questions, please write to the Managing Editor of _Programming Historian_ in English, [Alex Wermer-Colan](mailto:[email protected]) or to our Publishing Manager, [Anisa Hawes](mailto:[email protected]).
+
+## Some background about _Programming Historian_
+
+Launched in 2012, _Programming Historian_ offers more than 200 novice-friendly, multilingual peer-reviewed lessons that help humanists learn a wide range of digital tools, techniques, and workflows to facilitate their research. In recent years, our interdisciplinary publication has expanded to include [Spanish](/es/lecciones/), [French](/fr/lecons/), and [Portuguese](/pt/licoes/) editions. Our journals are Diamond Open Access and in that spirit: authors retain copyright, never pay any fees to publish with us, all content is peer-reviewed, and access is always free for readers.
+
+We’re a volunteer-led initiative, supported by the Board of the charity ProgHist Ltd, a small team of publishing staff, and a global community of contributors. We’re funded by [a growing network of organisations](/en/supporters) across Europe, Canada, North America and Latin America who have invested in our success by subscribing to our [Institutional Partner Programme](/en/ipp).
+
+--

assets/forms/Lesson.Query.Form.txt

@@ -1,25 +1,73 @@
-# Programming Historian Lesson Proposal
-
-If you are interested in writing a lesson and submitting it to the Programming Historian, please fill in this form to give the Editorial Board enough detail to comment on your idea. If you are experiencing difficulty with the form you can contact our Managing Editor directly:
-
-English: Alex Wermer-Colan ([email protected])
-Spanish: Jennifer Isasi ([email protected])
-French: Marie Flesch ([email protected])
-Portuguese: Daniel Alves ([email protected])
-
-
-## About You
-1. Your name
-2. Your email address
-
-## Lesson Metadata
-3. Submission Language (delete as appropriate) English / Español / Français / Portuguese
-4. Proposed Lesson Title
-5. Lesson Abstract (3-4 sentences)
-6. Case Study Description (details about your historical example problem)
-7. Learning Outcomes (between 2-3)
-8. Research Phase most relevant to your lesson (delete as appropriate) Acquire / Transform / Analyze / Present / Sustain
-9. Research Area most relevant to your lesson (delete as appropriate) APIs / python / data management / data manipulation / distant reading / set up / linked open data / mapping / network analysis / web scraping / digital publishing / other
-10. Intended Submission Date
-11. Lesson will use open technology and data at no cost to the reader Yes / No
-12. Any other comments for the editor
+## Lesson Proposal for Programming Historian (English edition)
+
+_Programming Historian_ in English is inviting proposals for new lessons.
+
+We encourage prospective authors to think carefully about how their proposal could enhance our learning offer.
+
+You can [explore our journal](https://programminghistorian.org/en/lessons/) to discover what’s already available and consider what you might be able to add.
+
+If the method or approach you’re interested in writing a lesson about is already represented by the [Spanish](https://programminghistorian.org/es/lecciones/), [French](https://programminghistorian.org/fr/lecons/), or [Portuguese](https://programminghistorian.org/pt/licoes/) editions of _Programming Historian_, we welcome proposals to translate those existing, original lessons into English.
+
+---
+
+
+Name:  
+Email:
+
+This form has twelve questions. Please answer each one, providing as much detail as you can.
+
+**1.** What is your proposed lesson title?  
+
+**2.** What kind of lesson are you proposing?
+- [ ] An original English-language lesson
+- [ ] A translation into English from an existing, original Spanish, French, or Portuguese lesson
+
+**3.** Please tell us how your proposal could support, expand, or supplement the lessons we've already published.
+Use these questions to structure your answer:
+- To which existing _Programming Historian_ lesson(s) could your proposal provide a foundational introduction?
+- To which existing _Programming Historian_ lesson(s) could your proposal provide an advancement or extension?
+- How could your proposal fill a gap in our lesson directory?  
+
+[200-300 words]
+
+**4.** Please tell us what readers could expect to learn from your proposed lesson:  
+[3-4 sentences]
+
+**5.** Please share some insights into how you came to use this method or tool as part of your work within the humanities:  
+[100-300 words]
+
+**6.** If you are proposing an original lesson, please tell us about the research case study you propose centring within your lesson.
+Successful lessons centre real datasets and sample code that readers can handle and experiment with.  
+[100-300 words]
+
+**7.** If you are proposing a translation, please tell us if you plan to adapt or localise the research case study centred by the original lesson for your language community.
+Successful lessons centre real datasets and sample code that readers can handle and experiment with.
+[100-300 words]
+
+**8.** Please outline how your choice of software and data would support our commitment to openness:
+We advocate for the use of open source software, open programming languages, open access datasets wherever possible.
+Use these questions to structure your answer:
+- Which open source software, open tools, open programming languages, or open datasets does this lesson make use of?
+- Which (if any) proprietary software or commercial tools does this lesson make use of?
+We strongly recommend authors choose open source alternatives.
+- Which (if any) costs* or commitments are required to use this method or tool?
+*including the requirement for readers to supply their credit card information  
+[100-300 words]
+
+
+**9.** Please provide us with some information about how your method or tool could be applied or adapted for use in languages other than English:
+We have a strong preference for methodologies and tools that can be used in multilingual research-contexts.  
+[100-300 words]
+
+
+**10.** Please outline any technical prerequisites and potential limitations of access to using this method or tool:
+Our readers work with different operating systems and have varying computational resources.  
+[100-200 words]
+
+**11.** Optional link to sample code on your personal GitHub repository:
+
+**12.** Optional link to a draft extract of this proposed lesson on your personal GitHub repository:
+
+---
+
+Please send this form to the Managing Editor of _Programming Historian_ in English, [Alex Wermer-Colan](mailto:[email protected]).