DevOps FSMK -- Managing Knowledge Sharing


#1

Hey All,

We successfully had our first DevOps Meetup in FSMK’s banner. I was a great experience we had. As a part of our discussions, we wanted to document the Session Presentations, Reference links, Example stuff used by the speakers in a single place, which would later serve us a reference. So basically to do this there are two ways of doing it.
Documenting both, would be open to critics and responses on the same.

  1. Maintain a gitlab in the following structure

    Repo Name : DevOps FSMK Meetup

    * DevOps November 2015 (folder):
        * Talk /Hands on 1 (folder):
            * Presentation
            * Code/Config Examples (If any)
            * Reference Links
            * ReadMe on how what this is about (A   quick short intro)
        * Talk/Hands on 2 (folder):
            * Presentation
            * Code/Config Examples (If any)
            * Reference Links
            * ReadMe on how what this is about (A quick short intro)
    * DevOps December 2015 (folder):
        * Talk /Hands on 1 (folder):
            * Presentation
            * Code/Config Examples (If any)
            * Reference Links
            * ReadMe on how what this is about (A quick short intro)
        * Talk/Hands on 2 (folder):
            * Presentation
            * Code/Config Examples (If any)
            * Reference Links
            * ReadMe on how what this is about (A quick short intro)
    
  2. Use GitBook, and follow a similar structure.

Personal Thought :
I see an advantage I see with Gitlab is it becomes easy for us to port any git tool, but with gitbook, that might be a complex process. Tough gitbook provides a way for us to store the pages in github, I would prefer not to use GitHub, and stick to GitLab, which is a Free Software alternative. Also when the repo grows to heavy or we want to do a self hosted version, it becomes easier for us to migrate in GitLab