Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Wiki Content to GitHub Repository #97

Open
ibrahim-kabir opened this issue Jan 19, 2024 · 3 comments · May be fixed by #111
Open

Move Wiki Content to GitHub Repository #97

ibrahim-kabir opened this issue Jan 19, 2024 · 3 comments · May be fixed by #111
Assignees

Comments

@ibrahim-kabir
Copy link
Contributor

ibrahim-kabir commented Jan 19, 2024

Multiple wiki pages contains training and information for the developer that should be stored in the dev-rel-docs repository.

Tasks:


Refer to the csboard ticket #75352 to take a look of the documentation to move

Acceptance Criteria:


  • No internal documents from the CFIA should be in this repository
  • Every documentation and training that a developer would need that is not CFIA related should be in the repository
  • Documentation should be :
    • Placed by categories in the right repository
    • Given a meaningful title
    • Formatted to be easily readable and easy to understand
  • Meetings notes that rely heavily on pointing out specific persons and specific tasks that need to follow up internally are UNSUITABLE for publication.
  • Postmortem that are written internally stay internal as they have sensitive information about our processes.
  • Thoughts and reflexions have no places on a public forum.
  • Internal architectures and deployment information are to be excluded.
  • Older documents that have been deprecated in favor of new information are not suitable.
  • Document fragments should not be published.
  • Documents that are heavily specific to our internal setup should be excluded.
@ibrahim-kabir ibrahim-kabir self-assigned this Jan 19, 2024
@rngadam
Copy link
Contributor

rngadam commented Jan 22, 2024

Projects field should always be selected. Classified as McLuhan which is our catch-all for our communication efforts.

@ghost ghost self-assigned this Feb 1, 2024
ghost pushed a commit that referenced this issue Feb 1, 2024
ghost pushed a commit that referenced this issue Feb 1, 2024
@ghost ghost linked a pull request Feb 1, 2024 that will close this issue
ghost pushed a commit that referenced this issue Feb 1, 2024
@ghost
Copy link

ghost commented Feb 1, 2024

Closed the PR after talking with Ibrahim. I will let him finish his folder structure, then rebase myself and incorporate my files, then remake the PR so we can all avoid conflict as much as possible.

This will also allow me to discuss with Ricky about the markdown Link issues

ghost pushed a commit that referenced this issue Feb 1, 2024
ghost pushed a commit that referenced this issue Feb 1, 2024
ghost pushed a commit that referenced this issue Feb 1, 2024
@ghost
Copy link

ghost commented Feb 1, 2024

I fixed my Markdown issues. Waiting for Ibrahim PR for the new repos

ibrahim-kabir added a commit that referenced this issue Feb 1, 2024
ibrahim-kabir added a commit that referenced this issue Feb 2, 2024
@ibrahim-kabir ibrahim-kabir linked a pull request Feb 2, 2024 that will close this issue
2 tasks
@ibrahim-kabir ibrahim-kabir linked a pull request Feb 2, 2024 that will close this issue
2 tasks
ibrahim-kabir added a commit that referenced this issue Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants