SingularityNET-Archive / SingularityNET-Archive

The SingularityNET Archive GitHub Organisation
Apache License 2.0
1 stars 1 forks source link

Guidelines on how to make a document community-owned #148

Open VanCardui opened 6 months ago

VanCardui commented 6 months ago

In the meeting on 1st May 2024, in the light of the SC Blueprint doc and the whole process of archival docs management, we discussed the concept of a Google doc being "community owned" rather than owned by an individual.

We realised that perhaps some people are not aware of the problems that arise if they delete a doc that they hold, delete comments, resolve comments without consultation, etc.

Vanessa will draft a brief guidance doc on how to work with a doc that you created in such a way as to treat it as "community-owned".

This links to André's work on open-source docs management https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/108 and will probably no longer be needed once a doc management process is in place - but in the meantime it might be useful as education

VanCardui commented 6 months ago

There may be issues with google docs sometimes, that people don't always create headings or format their docs. Doing so makes them more navigable. Is this something we could usefully train people on?

Also, consent? Do we need to look at educating people that when they attach a doc, they are giving consent for it to be archived? And how should it be licensed? Creative Commons - but attributed to whom?

Adding a header, to say who created a doc, and attribute it to them? Maybe do we need to create a template for Google docs that people submit

VanCardui commented 4 months ago

Draft doc is here https://docs.google.com/document/d/1hQs4ocUhT6mrvgn-ZjTO7O2aVDm-KEsYIiPaAOQH1Gc/edit?usp=sharing

Comments are open and are invited.

stephen-rowan commented 2 months ago

Relate to Open Source presentation ?

Ideas from this doc could be used in the presentation. Apart from that - issue can be closed