initial set up

initial set up

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,10 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**We do not triage issue for this repo. All issues are triaged in sonic-net/sonic-buildimage repo**

.github/ISSUE_TEMPLATE/workgroup-request.md

@@ -0,0 +1,61 @@
+---
+name: Workgroup request
+about: SONiC workgroup request (create new workgroup)
+title: "[workgroup request]: "
+labels: working group onboarding
+assignees: lucyhyde
+
+---
+
+<!--
+   assign Lucy Hyde (@lucyhyde) and any other needed members. Please use the "working group onboarding" label.
+-->
+
+**Working Group Details**
+<!-- 
+   Please fill working group scope and desriptions
+-->
+
+**--Working Group Name:**
+
+**--Working Group Presenter (name and email):**
+
+**--TSC Approval Date:**
+
+**--Presentation Files (if applicable):**
+
+
+**Mailing List**
+
+* [ ] (PM) Create mailing list in groups.io 
+* [ ] (PM/WG) Configure settings as appropriate (WG, please select the following features):
+    * [ ] Wiki
+    * [ ] Calendar
+    * [ ] Files
+    * [ ] Directory
+    * [ ] Database
+    * [ ] Polls
+* [ ] (PM) Import necessary working group contacts and set the following members as owners of mailing list
+    * [ ] Owner Name/GitHub ID:  Guohan Lu/lguohan
+    * [ ] Owner Name/GitHub ID:
+    * [ ] Owner Name/GitHub ID:
+
+
+**Zoom**
+
+* [ ] (PM) Share credentials with primary/alternate
+    * [ ] Name/GitHub ID:
+    * [ ] Name/GitHub ID:
+
+
+**Calendar**
+
+* [ ] (PM) Share credentials with primary/alternate
+    * [ ] Name/GitHub ID:
+    * [ ] Name/GitHub ID:
+
+**Other**
+_Please insert any other needs of the working group using the following empty bullet points and assign as appropriate_
+* [ ] (PM/WG) 
+* [ ] (PM/WG)
+* [ ] (PM/WG)

.github/workflows/sonic_image_links_create_workflow.yml

@@ -0,0 +1,21 @@
+# This is a basic workflow to help you get started with GitHub Actions
+
+name: Run the shell script to generate sonic image links in sonic_image_links.json in a dedicated branch
+
+# Run the script once in a minute. Github may take 15 minutes to run this even though we request once in a minute, which is OK.
+on:
+  schedule:
+    - cron:  '0 0 * * *'
+
+jobs:
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      - uses: actions/checkout@v2 
+
+      - name: Run the script to build a json file with details about various builds for various platforms
+        run: sh ./generate_sonic_image_links.sh
+

.github/workflows/supported_devices_platforms_md.yml

@@ -0,0 +1,20 @@
+# This is a basic workflow to help you get started with GitHub Actions
+
+name: Run the shell script to generate sonic image links in supported_devices_platforms_md.sh in a dedicated branch
+
+# Run the script once in a minute. Github may take 15 minutes to run this even though we request once in a minute, which is OK.
+on:
+  schedule:
+    - cron:  '0 0 * * *'
+
+jobs:
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      - uses: actions/checkout@v2 
+
+      - name: Run the script to build a json file with details about various builds for various platforms
+        run: sh ./supported_devices_platforms_md.sh

.gitignore

@@ -0,0 +1,5 @@
+*~
+*.swp
+*.un~
+.DS_Store
+.vscode/

.markdownlint.json

@@ -0,0 +1,5 @@
+{
+    "line-length": false,
+    "no-inline-html": false,
+    "fenced-code-language": false
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,53 @@
+## GitHub Workflow
+
+We're following basic GitHub Flow. If you have no idea what we're talking 
+about, check out [GitHub's official guide](https://guides.github.com/introduction/flow/). 
+Note that merge is only performed by the repository maintainer.
+
+Guide for performing commits:
+
+* Isolate each commit to one component/bugfix/issue/feature
+* Use a standard commit message format:
+
+>     [component/folder touched]: Description intent of your changes
+>
+>     [List of changes]
+>
+> 	  Signed-off-by: Your Name [email protected]
+
+For example:
+
+>     swss-common: Stabilize the ConsumerTable
+>
+>     * Fixing autoreconf
+>     * Fixing unit-tests by adding checkers and initialize the DB before start
+>     * Adding the ability to select from multiple channels
+>     * Health-Monitor - The idea of the patch is that if something went wrong with the notification channel,
+>       we will have the option to know about it (Query the LLEN table length).
+>
+>       Signed-off-by: [email protected]
+
+
+* Each developer should fork this repository and [add the team as a Contributor](https://help.github.com/articles/adding-collaborators-to-a-personal-repository)
+* Push your changes to your private fork and do "pull-request" to this repository
+* Use a pull request to do code review
+* Use issues to keep track of what is going on
+
+## Expectations for pull requests
+Pull requests should be free of any known bugs and be accompanied by tests and appropriate documentation.  Test coverage may include unit tests, integration tests such as [PTF tests](https://github.com/sonic-net/SONiC/wiki/HOWTO-write-a-PTF-Test) defined in the [sonic-mgmt repo](https://github.com/sonic-net/sonic-mgmt/tree/master/ansible/roles/test/tasks).
+
+## Commiting new test
+When committing a new feature with a new test, please complete a [test plan from the template](doc/SONiC%20Test%20Plan%20Template.md)
+
+
+## Responding to pull requests
+Responsible individual: A contribution needs to be looked at by its 
+maintainers. In the absence of the maintainer, the project leader can respond.
+A pull request should be responded to in approximately 48 hours. This does 
+not mean the contribution will be resolved in 48 hours.  It could even mean 
+an email that states: “busy now, will get to it soon.” 
+
+## Contributors License Agreement
+All contributors must sign an [Individual Contributor License Agreement (ICLA)](https://docs.linuxfoundation.org/lfx/easycla/v2-current/contributors/individual-contributor) before 
+contributions can be accepted. This process is managed by the [Linux Foundation - EasyCLA](https://easycla.lfx.linuxfoundation.org/) and automated
+via a GitHub bot. If the contributor has not yet signed a CLA, the bot will create a comment on the pull request containing a link to electronically sign the CLA.

Calendar.html

@@ -0,0 +1,122 @@
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+    <meta charset="utf-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <meta name="viewport" content="width=device-width, initial-scale=1">
+    <title>SONiC | Community Meeting Calendar</title>
+
+    <!-- Favicon -->
+    <link rel="shortcut icon" href="assets/img/logo_on_tab.png" type="image/x-icon">
+
+    <!-- Font awesome -->
+    <link href="assets/css/font-awesome.css" rel="stylesheet">
+    <!-- Bootstrap -->
+    <link href="assets/css/bootstrap.css" rel="stylesheet">
+    <!-- Slick slider -->
+    <link rel="stylesheet" type="text/css" href="assets/css/slick.css">
+    <!-- Fancybox slider -->
+    <link rel="stylesheet" href="assets/css/jquery.fancybox.css" type="text/css" media="screen" />
+    <!-- Theme color -->
+    <link id="switcher" href="assets/css/theme-color/default-theme.css" rel="stylesheet">
+
+    <!-- Main style sheet -->
+    <link href="assets/css/style.css" rel="stylesheet">
+
+    <!-- Google Fonts -->
+    <link href='https://fonts.googleapis.com/css?family=Montserrat:400,700' rel='stylesheet' type='text/css'>
+    <link href='https://fonts.googleapis.com/css?family=Roboto:400,400italic,300,300italic,500,700' rel='stylesheet' type='text/css'>
+
+    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
+    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
+    <!--[if lt IE 9]>
+      <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
+      <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
+    <![endif]-->
+
+</head>
+
+<body>
+
+    <!--START SCROLL TOP BUTTON -->
+    <a class="scrollToTop" href="#">
+        <i class="fa fa-angle-up"></i>
+    </a>
+    <!-- END SCROLL TOP BUTTON -->
+
+    <!-- Start menu -->
+    <section id="mu-menu">
+    </section>
+    <!-- End menu -->
+    <!-- Start search box -->
+    <div id="mu-search">
+        <div class="mu-search-area">
+            <button class="mu-search-close"><span class="fa fa-close"></span></button>
+            <div class="container">
+                <div class="row">
+                    <div class="col-md-8">
+                        <form class="mu-search-form">
+                            <input type="search" placeholder="Type Your Keyword(s) & Hit Enter">
+                        </form>
+                    </div>
+                </div>
+            </div>
+        </div>
+    </div>
+    <!-- End search box -->
+    <!-- Page breadcrumb -->
+    <section id="mu-page-breadcrumb">
+        <div class="container">
+            <div class="row">
+                <div class="col-md-8">
+                    <div class="mu-page-breadcrumb-area">
+                        <h2 style="text-align: center;"> SONiC Community Meeting Calendar</h2>
+					</div>
+                </div>
+            </div>
+        </div>
+    </section>
+    <!-- End breadcrumb -->
+
+
+<p><iframe src="https://calendar.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23ffffff&ctz=Asia%2FKolkata&src=c29uaWNmdW5kcmVhbEBnbWFpbC5jb20&color=%23EF6C00" style="text-align:center" "border:solid 1px #777" width="1250" height="600" frameborder="0" scrolling="no"></iframe></p>
+
+
+    <!-- Start footer -->
+    <footer id="mu-footer">
+
+        <!-- start footer bottom -->
+        <div class="mu-footer-bottom">
+            <div class="container">
+                <div class="mu-footer-bottom-area">
+                </div>
+            </div>
+        </div>
+        <!-- end footer bottom -->
+    </footer>
+    <!-- End footer -->
+
+    <!-- jQuery library -->
+    <script src="assets/js/jquery.min.js"></script>
+    <script type="text/javascript">
+        $("#mu-menu").load("menu.html");
+    </script>
+    <!-- Include all compiled plugins (below), or include individual files as needed -->
+    <script src="assets/js/bootstrap.js"></script>
+    <!-- Slick slider -->
+    <script type="text/javascript" src="assets/js/slick.js"></script>
+    <!-- Counter -->
+    <script type="text/javascript" src="assets/js/waypoints.js"></script>
+    <script type="text/javascript" src="assets/js/jquery.counterup.js"></script>
+    <!-- Mixit slider -->
+    <script type="text/javascript" src="assets/js/jquery.mixitup.js"></script>
+    <!-- Add fancyBox -->
+    <script type="text/javascript" src="assets/js/jquery.fancybox.pack.js"></script>
+
+    <!-- Custom js -->
+    <script src="assets/js/custom.js"></script>
+
+</body>
+
+</html>