KairoiAI / An_Incomplete_History_of_Research_Ethics

The text for https://www.tiki-toki.com/timeline/entry/1753034/A-History-of-Research-Ethics/
Creative Commons Attribution 4.0 International
19 stars 1 forks source link

Clear story-review process/life-cycle #28

Closed Ismael-KG closed 2 years ago

Ismael-KG commented 2 years ago

This issue is to spell out Protocol 3: Lifecycle of a Story.

Ismael-KG commented 2 years ago

Attempt 1 (one)

Protocol 3: Lifecycle of a Story

There are 7 stages to the development of stories for The Timeline. Each one can be repeated, and you can always revisit previous steps. You are also encouraged to develop stories (i) with the help of others and (ii) by creating an issue using the "lightbulb moments 💡" template.

Step 1: Idea generation

This is where you can put your most creative self to work. There are at least two approaches to idea generation:

Once you have clarity on the idea or feel you need support to develop it, raise an issue following the "lightbulb moment 💡" template and invite discussion.

Step 2: Compiling Resources

You are encouraged to employ diverse sources of information when at the idea generation stage. Once an idea becomes clearer, you should draw on sources that adhere to Protocol 5.

Step 3: Finding coherent narratives

With the general idea and the vast quantity of resources you have found, it is finally time to establish the outline of the story and any philosophical arguments to be put forth. Protocol 4 can help you structure your thoughts.

Also, don't be afraid to discard academic papers, articles or books that become irrelevant. The story must be clear and coherent. This is not to say you should adjust evidence to your own narrative (that would be deeply unethical), but that you must focus on clear arguments and not lead readers astray by introducing too many topics or events.

One more thing, having made it to step three, the story will have earned a file in the "Stories in Progress" folder! Just mention @Ismael-KG in the lightbulb moment issue for the story and ask to have the file created. Be clear about the event's date, so it can be added to Tiki-Toki.

Step 4: Draft and re-draft the story

And re-draft again and again and again! You can choose to do this publicly using HackMD or your preferred collaboration tool, or you can draft work privately. Be open to holding discussions on GitHub, but don't feel pressured to share things publicly until you feel comfortable to do so.

Step 5: Pre-Publication Peer Review

I find GitHub terribly exclusionary. For this reason, stories, once drafted, are placed in this online HackMD document (as described in issue #5). This wil require signing up to HackMD.

Drafts are kept in the pre-publication document for a period of anything between nine and fifteen days, the last day of which will always be a Saturday.

During this time, the HackMD document is re-shared publicly and people are encouraged to contribute and help improve the drafts.

Step 6: Publish on GitHub

Every Thursday, the pre-publication file must be checked and an issue - following the "Sunday uploads" template - must be created.

On the day after the end of the pre-publication peer review, the new story is revised one last time and given a file in the Stories folder following the relevant template.

Step 7: Publish on tiki-toki

@Ismael-KG can now go ahead and publish new stories on the tiki-toki platform, as he has the admin rights.

Ismael-KG commented 2 years ago