Proposta de Lição: Investigar a literatura lusófona através dos tempos usando a Literateca #599
Comments
|
@dianamsmpsantos já compartilhou o pacote de submissão comigo, contendo texto markdown, figuras e recursos de dados. Nossa equipe de Publicação (@anisa-hawes e @charlottejmc) processará os novos materiais da lição em setembro e preparará uma prévia do rascunho inicial. Eles discutirão qualquer dúvida com o colaborador e postarão um comentário nesta questão para fornecer a localização de todos os arquivos-chave, bem como um link para a prévia, onde os colaboradores poderão ler a lição conforme o rascunho avança. Em breve teremos a indicação do/a editor/a responsável pela lição. |
|
Thank you, @ericbrasiln! @charlottejmc and I will process these submission materials and set up the lesson preview for you this week ✨ |
|
Olá @ericbrasiln e @dianamsmpsantos, Pode encontrar os ficheiros principais aqui:
Pode consultar a pré-visualização da lição aqui: Dear @dianamsmpsantos, There are a few small things I noticed while setting up your submission, which I have outlined below:
Alt-text enables screen readers to read the information conveyed in the images for people with visual impairments, different learning abilities, or who cannot otherwise view them, for example due to a slow internet connection. It's important to say that We have found Amy Cesal's guide to Writing Alt Text for Data Visualization useful. This guide advises that alt-text for graphs and data visualisations should consist of the following:
What Amy Cesal's guide achieves is prompting an author to reflect on their reasons for including the graph or visualisation. What idea does this support? What can a reader learn or understand from this visual? The Graphs section of Diagram Center's guidance is also useful. Some key points (relevant to all graph types) we can take away from it are:
For general images, Harvard's guidance notes some useful ideas. A key point is to keep descriptions simple, and adapt them to the context and purpose for which the image is being included. Would you feel comfortable redrafting the alt-text for each of the figures? This is certainly a bit time-consuming, but we believe it is very worthwhile in terms of making your lesson accessible to the broadest possible audience. We would be very grateful for your support with this. Thank you!! |
|
Dear Charlotte, Thanks a lot! |
|
Thank you, Diana @dianamsmpsantos. To create I've done the first one for you so that you can follow this way of working: 4c0fade You can edit your file directly here: /pt/esbocos/originais/investigar-literatura-lusofona-literateca.md. Just let Charlotte and I know if you have any difficulties, or need advice. We are very happy to help. 🙂 Best, |
|
Dear @anisa-hawes @charlottejmc and @dianamsmpsantos |
|
Dear Anisa,
I am having the following error:
"There was an error committing your changes: File could not be edited"
What can I do to solve it?
Thanks a lot in advance
Diana
Anisa Hawes ***@***.***> escreveu (quinta, 5/09/2024 à(s)
12:53):
… Thank you, Diana @dianamsmpsantos <https://github.com/dianamsmpsantos>.
To create inline code, we use single backticks ` before and after the
individual words/snippets we want to display as code.
To create code blocks, we use three backticks ``` above and three
backticks below the block we want to display as code.
I've done the first one for you so that you can follow this way of
working: 4c0fade
<4c0fade>
You can edit your file directly here:
/pt/esbocos/originais/investigar-literatura-lusofona-literateca.md
<https://github.com/programminghistorian/ph-submissions/blob/gh-pages/pt/esbocos/originais/investigar-literatura-lusofona-literateca.md>
.
Just let Charlotte and I know if you have any difficulties, or need
advice. We are very happy to help. 🙂
Best,
Anisa
—
Reply to this email directly, view it on GitHub
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44U66GLI2TDJF5A35KTZVAZ4JAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZRGIYTMOJTG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hello Diana @dianamsmpsantos, I have double checked that you have the Write access you need to contribute to our repository. I note that you have successfully made several edits to the Markdown file. Does this mean the problem is now solved? Or are you trying to edit some other kinds of files? (for example data assets or figure images) Thank you for your patience. |
|
Dear Anisa,
I am sorry, I had been thrown away from github, and this is why I was not
able to edit or make changes. Now I logged in again, and made all
subsequent changes.
I want only to change one figure, figure 8, because I found an error in it.
Should I try to remove and upload the new one, or send it directly to you?
Best
Diana
Anisa Hawes ***@***.***> escreveu (sexta, 6/09/2024 à(s)
10:14):
… Hello Diana @dianamsmpsantos <https://github.com/dianamsmpsantos>,
I have double checked that you have Write access you need to contribute to
this repository. I note that you have successfully made several edits to
the Markdown file
<https://github.com/programminghistorian/ph-submissions/commits/gh-pages/pt/esbocos>.
Does this mean the problem is now solved?
Or are you trying to edit some other kinds of files? (for example data
assets or figure images)
In this case, it is usually necessary to delete and then replace the file.
Please let @charlottejmc <https://github.com/charlottejmc> or I know what
you would like to edit, and we can help you directly / or make the changes
on your behalf.
Thank you for your patience.
Anisa
—
Reply to this email directly, view it on GitHub
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44T5Z7JAJFLLU3JK25DZVFP5PAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGQ4TSNBVHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Ah! That explains it! Thank you, @dianamsmpsantos. Could you email it to Charlotte please? (publishing.assistant[@]programminghistorian.org). Thank you, |
|
Sorry again, I need to change a lot of data files and at least two figures.
(I found out that there was a typo in a date, and therefore one text was in
the 12th century instead of the 20th... And this shows clearly in the
distributions by decade.)
So, please tell me how to proceed.
Diana
Diana Santos ***@***.***> escreveu (sexta, 6/09/2024 à(s)
10:47):
… Dear Anisa,
I am sorry, I had been thrown away from github, and this is why I was not
able to edit or make changes. Now I logged in again, and made all
subsequent changes.
I want only to change one figure, figure 8, because I found an error in
it. Should I try to remove and upload the new one, or send it directly to
you?
Best
Diana
Anisa Hawes ***@***.***> escreveu (sexta, 6/09/2024 à(s)
10:14):
> Hello Diana @dianamsmpsantos <https://github.com/dianamsmpsantos>,
>
> I have double checked that you have Write access you need to contribute
> to this repository. I note that you have successfully made several edits
> to the Markdown file
> <https://github.com/programminghistorian/ph-submissions/commits/gh-pages/pt/esbocos>.
> Does this mean the problem is now solved?
>
> Or are you trying to edit some other kinds of files? (for example data
> assets or figure images)
> In this case, it is usually necessary to delete and then replace the
> file. Please let @charlottejmc <https://github.com/charlottejmc> or I
> know what you would like to edit, and we can help you directly / or make
> the changes on your behalf.
>
> Thank you for your patience.
> Anisa
>
> —
> Reply to this email directly, view it on GitHub
> <#599 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB6H44T5Z7JAJFLLU3JK25DZVFP5PAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGQ4TSNBVHA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
Ok, I'll do it!
Thank you
Diana
Anisa Hawes ***@***.***> escreveu (sexta, 6/09/2024 à(s)
10:51):
… Ah! That explains it!
Thank you, @dianamsmpsantos <https://github.com/dianamsmpsantos>. Could
you email it to Charlotte please? (publishing.assistant[@]
programminghistorian.org).
Thank you,
A.
—
Reply to this email directly, view it on GitHub
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44RSDTYC5NHZWVXD3K3ZVFUJJAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGU3DKMRXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thank you, @dianamsmpsantos. Sem problema! Please email @charlottejmc a list of these edits, and share the new files with her. Charlotte can re-process the files and make the adjustments needed |
|
Thank you @dianamsmpsantos, I've now replaced those files with the new versions you've sent by email ✨ |
|
Thank you, @charlottejmc <https://github.com/charlottejmc>!
There are still two problems, though: Figure 9 disappeared. Should I send
it to you again?
And paragraph 36 should be inside note 7, not in the main text.
Can you help me with this?
Otherwise I think the lesson is ready.
Best
Diana
charlottejmc ***@***.***> escreveu (quarta, 11/09/2024 à(s)
10:00):
… Thank you @dianamsmpsantos <https://github.com/dianamsmpsantos>, I've now
replaced those files with the new versions you've sent by email ✨
—
Reply to this email directly, view it on GitHub
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44T2XYRJVA4IBQ6AT63ZV72AJAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBSHEZDSOBXHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks for flagging this @dianamsmpsantos! It should all be working as expected now. |
|
Thank you, everything is fixed.
Is there anything else I need to do?
Best,
Diana
charlottejmc ***@***.***> escreveu (quarta, 11/09/2024 à(s)
11:11):
… Thanks for flagging this @dianamsmpsantos
<https://github.com/dianamsmpsantos>! It should all be working as
expected now.
—
Reply to this email directly, view it on GitHub
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44R5B3QJLXRPZ3LO3XDZWACMLAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBTGA4DIMZYGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi @dianamsmpsantos, I've checked off my three tick-boxes from my initial comment as I can see you've worked on those. Your lesson is ready to move on to Phase 2: Initial Edit! |
|
But since this is my first time, what does this mean? What do I need to do
now?
Thanks in advance
charlottejmc ***@***.***> escreveu (quarta, 11/09/2024 à(s)
13:39):
… Hi @dianamsmpsantos <https://github.com/dianamsmpsantos>, I've checked
off my three tick-boxes from my initial comment
<#599 (comment)>
as I can see you've worked on those. Your lesson is ready to move on to
Phase 2: Initial Edit!
—
Reply to this email directly, view it on GitHub
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44VSJ3F2QADJWQSPHWDZWATWBAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBTGQZTANJWGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Olá Diana @dianamsmpsantos, 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 Eric @ericbrasiln will read your lesson, and provide some initial feedback. Eric will post feedback and suggestions as a comment in this issue, so that you can revise your draft in the following phase (Phase 3: Revision 1). %%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#886814', '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 (@ericbrasiln)
Expected completion date? : October 11
Section Phase 3 <br> Revision 1
Who's responsible? : Author (@dianamsmpsantos)
Expected timeframe? : ~30 days after feedback is received
|
|
Hi @anisa-hawes, Just like with the other lesson from Diana, I’ve already reviewed this one, and the initial feedback and comments were addressed during our previous discussions. We’re ready to move forward to the next phase. I’m also in the process of finding editors for this lesson. Best regards |
|
Olá Diana @dianamsmpsantos, What's happening now?Your lesson has been moved to the next phase of our workflow which is Phase 3: Revision 1. I understand that you have already revised your draft in response to @ericbrasiln's initial feedback. %%{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 (@ericbrasiln)
All Phase 2 tasks completed? : Yes
Section Phase 3 <br> Revision 1
Who's working on this? : Author (@dianamsmpsantos)
Expected completion date? : DONE
Section Phase 4 <br> Open Peer Review
Who's responsible? : Reviewers (TBC)
Expected timeframe? : ~60 days after request is accepted
|
|
Olá Diana @dianamsmpsantos, What's happening now?Your lesson has been moved to the next phase of our workflow which is Phase 4: Open Peer Review. This phase is an opportunity for you to hear feedback from peers in the community. Eric @ericbrasiln will invite two reviewers to read your lesson, test your code, and provide constructive feedback. In the spirit of openness, reviews will be posted as comments in this issue (unless you specifically request a closed review). After both reviews, Eric will summarise the suggestions to clarify your priorities in Phase 5: Revision 2. %%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#886814', 'cScaleLabel1': '#ffffff',
'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
} } }%%
timeline
Section Phase 3 <br> Revision 1
Who worked on this? : Author (@dianamsmpsantos)
All Phase 3 tasks completed? : Yes
Section Phase 4 <br> Open Peer Review
Who's working on this? : Reviewers (TBC)
Expected completion date? : ~60 days after request is accepted
Section Phase 5 <br> Revision 2
Who's responsible? : Author (@dianamsmpsantos)
Expected timeframe? : ~30 days after editor's summary
|
|
Thank you all. Can I also invite reviews from colleagues? In that case, how
can they see the lesson(s)?
Thanks a lot in advance
Diana
Anisa Hawes ***@***.***> escreveu (quarta, 2/10/2024 à(s)
16:14):
… Olá Diana @dianamsmpsantos <https://github.com/dianamsmpsantos>,
What's happening now?
Your lesson has been moved to the next phase of our workflow which is *Phase
4: Open Peer Review*.
This phase is an opportunity for you to hear feedback from peers in the
community.
Eric @ericbrasiln <https://github.com/ericbrasiln> will invite two
reviewers to read your lesson, test your code, and provide constructive
feedback. In the spirit of openness, reviews will be posted as comments in
this issue (unless you specifically request a closed review).
After both reviews, Eric will summarise the suggestions to clarify your
priorities in Phase 5: Revision 2.
%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
'cScale1': '#886814', 'cScaleLabel1': '#ffffff',
'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
} } }%%
timeline
Section Phase 3 <br> Revision 1
Who worked on this? : Author ***@***.***)
All Phase 3 tasks completed? : Yes
Section Phase 4 <br> Open Peer Review
Who's working on this? : Reviewers (TBC)
Expected completion date? : ~60 days after request is accepted
Section Phase 5 <br> Revision 2
Who's responsible? : Author ***@***.***)
Expected timeframe? : ~30 days after editor's summary
Loading
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
<#599 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6H44U3N5PZ6L537OBULALZZP5TZAVCNFSM6AAAAABCHNDWUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYG42TQNJQHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hello Diana @dianamsmpsantos, Yes! Of course. We welcome additional reviews from your colleagues ! Members of the wider community may also choose to contribute reviews. The lesson is available to read as a preview here: http://programminghistorian.github.io/ph-submissions/pt/esbocos/originais/investigar-literatura-lusofona-literateca We ask that:
|
|
Boa tarde, gente! Informo que @LFreitas27 e @suemi-higuchi aceitaram ser as revisoras da lição inédita proposta pela @dianamsmpsantos Coloco aqui as Diretrizes para revisores. Podem incluir suas revisões e sugestões em um comentário aqui na issue, de preferência utilizando tasklist ( Os arquivos referentes à lição podem ser acessados nos seguintes links:
Qualquer dúvida é só me marcar por aqui. Agradeço a colaboração dos colegas e à contribuição inédita da @dianamsmpsantos. |
|
Muito obrigada pelo convite, @ericbrasiln ! Será um prazer contribuir com a revisão desta lição! :) |
O Programming Historian em Português recebeu uma proposta de lição original com o título provisório "Investigar a literatura lusófona através dos tempos usando a Literateca".
Para promover uma publicação oportuna, propomos que a lição seja entregue em meados de março de 2024. A autora entrará em contato com o editor com antecedência caso não consiga cumprir a data de entrega e precise de uma prorrogação.
Se a lição não for entregue, o editor tentará entrar em contato com a autora da lição. Se nenhuma notícia for recebida, a issue será fechada. Ela poderá ser reaberta no futuro, a pedido da autora.
O contato principal para esta lição é, por enquanto, @ericbrasiln. Se ocorrer algum problema, a autora pode entrar em contato com o mediador do PH em português (Luis Ferla - http://programminghistorian.org/pt/equipe).
The text was updated successfully, but these errors were encountered: