Merge branch 'sonic-net:master' into master

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,4 +7,4 @@ assignees: ''
 
 ---
 
-**We do not triage issue for this repo. All issues are triaged in Azure/sonic-buildimage repo**
+**We do not triage issue for this repo. All issues are triaged in sonic-net/sonic-buildimage repo**

.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

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

CONTRIBUTING.md

@@ -33,21 +33,21 @@ For example:
 * 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/Azure/SONiC/wiki/HOWTO-write-a-PTF-Test) defined in the [sonic-mgmt repo](https://github.com/Azure/sonic-mgmt/tree/master/ansible/roles/test/tasks).
+## 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 commiting a new feature with a new test, please complete a [test plan from the template](doc/SONiC%20Test%20Plan%20Template.md)
+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
+## 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 a contribution license agreement before 
-contributions can be accepted.  Send email to [sonic-cla](mailto:[email protected])
-to request a copy of the contributors a license agreement to be signed.
+## 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>

Github Project User Guide for SONiC Project.md

@@ -0,0 +1,55 @@
+# Github Project User Guide for SONiC Project
+Status: Drafting | Ready for Review | Reviewed  
+
+This document provides guidance to use Github project to track SONiC community release. Example is [SONiC 202305 Release](https://github.com/orgs/sonic-net/projects/8)
+
+### Background
+Before using Github project, SONiC community used [Google Sheet](https://docs.google.com/spreadsheets/u/0/d/19OkV0WjPcHVK6Xm_uq8dao8FjifP-MicbqEKvmpL8AA/edit) to track the community feature status which required the community leads to update the status periodically and manually. This google sheet is only visible to very limited audience, which is not convenient for others who want to check the release status.
+By adopting Github project, we expect to <br>
+1) Reduce the manual effort to update status, add PRs etc by leveraging the seamless integration between Github project and Github PR & Issue etc. <br>
+2) Consolidate the release tracking to Github. <br>
+
+The Github project is public to anyone who wants to check SONiC release status, no matter if you joined the SONiC community or not, but only limited audiences can edit.
+
+### How to Use?
+For people who have NO edit permission to this project but want to contribute, please follow the “Call for participation” message, e.g Re: [Call for participation for SONiC 202305 release](https://lists.sonicfoundation.dev/g/sonic-dev/message/46) (sonicfoundation.dev).  
+For people who can edit github project, if you want to propose a new feature from scratch, please refer to Sample Feature - PLEASE READ · [Issue #1125](https://github.com/sonic-net/SONiC/issues/1125) 
+<br>
+1) On the "Table View" of project, click Control + Space and provide the Title <br>
+2) Click “Enter” button to create a new work item. You can create new item from other views, but steps may be slightly different. <br>
+3) Fulfill the fields in the ticket (click "Show all fields" to display all fields) <br>
+	* Mandatory fields when you submit proposal
+	* Title
+	* Short Description
+	* SAI Header (API) Change Required?
+	* Owner Company -- company name who proposed this feature. Please use your personal name if this comes from individual contributor
+4) On the left side of the newly created item, click “Convert to issue”
+5) Close the issue after the feature is delivered. The issue is used for project tracking purpose, please use HLD PR and code PRs to track the feature design and implementation.
+
+If the HLD PR already exists, the PR can be added into the release plan by changing the “Projects” field of the PR. Please remember to update the fields info according to the Sample Feature above.
+
+![Eg](images/user_guide_1.png)
+
+### How to change the status?
+There are two ways to update the status of one proposed feature. 
+
+##### Option 1: Drag & drop the feature to different slot on “Board View”
+
+You can drag one feature to another slot to change the status.
+
+![Option 1](images/user_guide_2.png)
+
+##### Option 2: Change the “Status” field on the feature page
+
+![Option 2](images/user_guide_3.png)
+
+### Feature status change flow
+
+1) A new feature proposal will by default go to “Backlog” slot. You can create new feature proposal for future releases in this slot.
+2) Once you plan to contribute one specific feature to one specific release, say “SONiC 202305 Release”, you should move that feature to “In Plan Features” slot and leave a comment in the feature PR/Issue by saying “A feature target xxx release”. After this, team should start working on the HLD PR
+3) Once the HLD is ready for review by community, the feature should be moved to “HLD Ready for Review” slot and specify an expected “HLD Review Date”. The weekly SONiC community meeting will be used for the HLD review. We will publish the community calendar with Google calendar later, before that, you can pick up a slot which is not booked yet on the project, or ask help from Yanzhao Zhang
+4) After the HLD is reviewed in SONiC community, the feature should be moved to “In Progress” slot. Team should update the HLD based on the community feedbacks while working on the code PRs. Code PRs need be added to HLD PR by referring to Pull Request [#806](https://github.com/sonic-net/SONiC/pull/806) 
+5) Later, after all code PRs and HLD PR are merged, the feature should be moved to “Done” slot.
+6) If one feature need be deferred or withdrawn, the feature should be moved to “Deferred” slot (candidate for next release), or “Backlog” slot (candidate for future releases post next release).
+
+