structure / naming of the repositories

[ghost]

following the ML thread, IMHO we should settle on a clear and simple setup.

Root: Qubes-Community-Collaboration (maybe make it "Qubes-Community" ? it should be implicit that since it's on github with several members it should be a collaboration).

• staging-doc
  • that's where documentation "matures" until a PR is submitted to the official qubes-doc
  • should host the public wiki
  • should host issues with the qubes-doc documentation, to help people drop "drive-by" contributions.
• unofficial-doc
  • documents that we know wont be accepted by qubes-doc for whatever reason (like allowing to shoot yourself in the foot with security)
  • [?] interesting documents that were in staging-doc but that were rejected by qubes-doc
• projects
  • various projects living in the organization (it seems @Aekez transformed his account in the organization ; FYI the email invitation's first link proposed to do the same for mine, until I clicked the second link and simply accepted the invitation; otherwise I guess my projects would have migrated to the organization)
  • links to other interesting github projects (I don't think we should ask someone's approval for linking, their projects are already public on github)

[Aekez]

aight, suppose I need to have a look at github notifications later, memorizing the number of replies in each issue to see if there were new replies becomes tricky.

By any chance, do you know a good font or formatting tricks to make this page look less clutterly? https://github.com/Qubes-Community/Qubes-Community

[Aekez]

@one7two99 I made a sub-folder for screenshot scripts, when you upload yours, can you use the same folder so people can easier browse them for their needs?

[ghost]

closing. discussion about workflows, structures, & co. ought to happen in the workflows' respective issues