-
Notifications
You must be signed in to change notification settings - Fork 229
Phase change comment 2 to 3
Anisa Hawes edited this page Oct 2, 2024
·
8 revisions
Contents of this page:
Hello Author @author,
### What's happening now?
Your lesson has been moved to the next phase of our workflow which is **Phase 3: Revision 1**.
This phase is an opportunity for you to revise your draft in response to @editor's initial feedback.
I've sent you an invitation to join us as an Outside Collaborator here on GitHub. This will give you the 'write access' you'll need to edit your lesson directly.
OR
I've checked to ensure that you have the 'write access' you'll need to edit your draft directly.
We ask authors to work on their own files with direct commits: _we prefer you don't fork our repo, or use the Pull Request system to edit in ph-submissions_. You can make direct commits to your file here: [/en/drafts/originals/lesson-slug.md](https://github.com/programminghistorian/ph-submissions/blob/gh-pages/en/drafts/originals/lesson-slug.md). @charlottejmc and I can help if you encounter any practical problems!
When you and Editor are both happy with the revised draft, we will move forward to Phase 4: Open Peer Review.
[REPLACE WITH THREE BACKTICKS ```]mermaid
%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#882b4f', 'cScaleLabel1': '#ffffff',
'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
} } }%%
timeline
Section Phase 2 <br> Initial Edit
Who worked on this? : Editor (@name)
All Phase 2 tasks completed? : Yes
Section Phase 3 <br> Revision 1
Who's working on this? : Author (@name)
Expected completion date? : Month 1
Section Phase 4 <br> Open Peer Review
Who's responsible? : Reviewers (TBC)
Expected timeframe? : ~60 days after request is accepted
[REPLACE WITH THREE BACKTICKS ```]
>Note: _The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment._
Hola Author @author,
### What's happening now?
Your lesson has been moved to the next phase of our workflow which is **Phase 3: Revision 1**.
This phase is an opportunity for you to revise your draft in response to @editor's initial feedback.
I've sent you an invitation to join us as an Outside Collaborator here on GitHub. This will give you the 'write access' you'll need to edit your lesson directly.
OR
I've checked to ensure that you have the 'write access' you'll need to edit your draft directly.
We ask authors to work on their own files with direct commits: _we prefer you don't fork our repo, or use the Pull Request system to edit in ph-submissions_. You can make direct commits to your file here: [/es/borradores/originales/lesson-slug.md](https://github.com/programminghistorian/ph-submissions/blob/gh-pages/es/borradores/originales/lesson-slug.md). @charlottejmc and I can help if you encounter any practical problems!
When you and Editor are both happy with the revised draft, we will move forward to Phase 4: Open Peer Review.
[REPLACE WITH THREE BACKTICKS ```]mermaid
%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#535d7f', 'cScaleLabel1': '#ffffff',
'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
} } }%%
timeline
Section Phase 2 <br> Initial Edit
Who worked on this? : Editor (@name)
All Phase 2 tasks completed? : Yes
Section Phase 3 <br> Revision 1
Who's working on this? : Author (@name)
Expected completion date? : Month 1
Section Phase 4 <br> Open Peer Review
Who's responsible? : Reviewers (TBC)
Expected timeframe? : ~60 days after request is accepted
[REPLACE WITH THREE BACKTICKS ```]
>Note: _The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment._
Bonjour Author @author,
### What's happening now?
Your lesson has been moved to the next phase of our workflow which is **Phase 3: Revision 1**.
This phase is an opportunity for you to revise your draft in response to @editor's initial feedback.
I've sent you an invitation to join us as an Outside Collaborator here on GitHub. This will give you the 'write access' you'll need to edit your lesson directly.
OR
I've checked to ensure that you have the 'write access' you'll need to edit your draft directly.
We ask authors to work on their own files with direct commits: _we prefer you don't fork our repo, or use the Pull Request system to edit in ph-submissions_. You can make direct commits to your file here: [/fr/en-cours/originales/lesson-slug.md](https://github.com/programminghistorian/ph-submissions/blob/gh-pages/fr/en-cours/originales/lesson-slug.md). @charlottejmc and I can help if you encounter any practical problems!
When you and Editor are both happy with the revised draft, we will move forward to Phase 4: Open Peer Review.
[REPLACE WITH THREE BACKTICKS ```]mermaid
%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#3d7c81', 'cScaleLabel1': '#ffffff',
'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
} } }%%
timeline
Section Phase 2 <br> Initial Edit
Who worked on this? : Editor (@name)
All Phase 2 tasks completed? : Yes
Section Phase 3 <br> Revision 1
Who's working on this? : Author (@name)
Expected completion date? : Month 1
Section Phase 4 <br> Open Peer Review
Who's responsible? : Reviewers (TBC)
Expected timeframe? : ~60 days after request is accepted
[REPLACE WITH THREE BACKTICKS ```]
>Note: _The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment._
Olá Author @author,
### What's happening now?
Your lesson has been moved to the next phase of our workflow which is **Phase 3: Revision 1**.
This phase is an opportunity for you to revise your draft in response to @editor's initial feedback.
I've sent you an invitation to join us as an Outside Collaborator here on GitHub. This will give you the 'write access' you'll need to edit your lesson directly.
OR
I've checked to ensure that you have the 'write access' you'll need to edit your draft directly.
We ask authors to work on their own files with direct commits: _we prefer you don't fork our repo, or use the Pull Request system to edit in ph-submissions_. You can make direct commits to your file here: [/pt/esbocos/originais/lesson-slug.md](https://github.com/programminghistorian/ph-submissions/blob/gh-pages/pt/esbocos/originais/lesson-slug.md). @charlottejmc and I can help if you encounter any practical problems!
When you and Editor are both happy with the revised draft, we will move forward to Phase 4: Open Peer Review.
[REPLACE WITH THREE BACKTICKS ```]mermaid
%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#886814', 'cScaleLabel1': '#ffffff',
'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
} } }%%
timeline
Section Phase 2 <br> Initial Edit
Who worked on this? : Editor (@name)
All Phase 2 tasks completed? : Yes
Section Phase 3 <br> Revision 1
Who's working on this? : Author (@name)
Expected completion date? : Month 1
Section Phase 4 <br> Open Peer Review
Who's responsible? : Reviewers (TBC)
Expected timeframe? : ~60 days after request is accepted
[REPLACE WITH THREE BACKTICKS ```]
>Note: _The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment._
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees