Import standard GitHub workflow files

Signed-off-by: Laurent Broudoux <laurent.broudoux@gmail.com>

Author: lbroudoux

.github/workflows/stale-issues-prs.yml

@@ -0,0 +1,49 @@
+# This workflow is used to manage stale issues and PRs in the Reshapr project.
+name: Manage stale issues and PRs
+
+on:
+  schedule:
+    - cron: "0 0 * * *"
+
+permissions:
+  contents: read
+
+jobs:
+  stale:
+    permissions:
+      issues: write  # for actions/stale to close stale issues
+      pull-requests: write  # for actions/stale to close stale PRs
+    if: startsWith(github.repository, 'microcks/')
+    name: Mark issue or PR as stale
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # To pin v10.2.0
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          stale-issue-message: |
+            This issue has been automatically marked as stale because it has not had recent activity :sleeping:
+            
+            It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. 
+            
+            There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Reshapr is an Open Source project not owned by a single for-profit company. It is a community-driven initiative ruled under [open governance model](https://github.com/reshapr/.github/blob/main/CODE_OF_CONDUCT.md). 
+            
+            Let us figure out together how to push this issue forward. Connect with us through [one of many communication channels](https://reshapr.io/community/) we established here.
+            
+            Thank you for your patience :heart:
+          stale-pr-message: |
+            This pull request has been automatically marked as stale because it has not had recent activity :sleeping:
+            
+            It will be closed in 30 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.
+            
+            There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. Reshapr is an Open Source project not owned by a single for-profit company. It is a community-driven initiative ruled under [open governance model](https://github.com/reshapr/.github/blob/main/CODE_OF_CONDUCT.md). 
+            
+            Let us figure out together how to push this pull request forward. Connect with us through [one of many communication channels](https://reshapr.io/community/) we established here.
+            
+            Thank you for your patience :heart:
+          days-before-stale: 30
+          days-before-close: 30
+          stale-issue-label: stale
+          stale-pr-label: stale
+          exempt-issue-labels: keep-open
+          exempt-pr-labels: keep-open
+          close-issue-reason: not_planned

.github/workflows/welcome-new-users.yml

@@ -0,0 +1,70 @@
+# Welcome new users by commenting on the first-time issue/PR.
+# Adding a friendly message in the comment to tip non-stargazers to star our repo.
+#
+# Props to https://github.com/wow-actions/welcome 
+
+name: Welcome New Users with Thanks and Tip non-stargazers ;-)
+on:
+  pull_request_target:
+    types: [opened, closed]
+  issues:
+    types: [opened]
+permissions:
+  contents: read  # Set permissions as read-only by default at the top level
+jobs:
+  run:
+    permissions:
+      issues: write  # for wow-actions/welcome to comment on issues
+      pull-requests: write  # wow-actions/welcome to comment on PRs
+    runs-on: ubuntu-latest
+    steps:
+      - uses: wow-actions/welcome@68019c2c271561f63162fea75bb7707ef8a02c85 # To pin v1.3.1
+        with:
+          # GitHub token as default GITHUB_TOKEN
+      
+          FIRST_ISSUE_REACTIONS: '+1, hooray, rocket, heart'
+          
+          FIRST_ISSUE: |
+            👋 @{{ author }}
+            
+            Welcome to the Reshapr community! 💖
+            
+            Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.
+            
+            📢 If you're using Reshapr in your organization, please [add your company name to this list](https://github.com/reshapr/.github/blob/main/ADOPTERS.md). 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
+            
+            If you need to know why and how to add yourself to the list, please read the blog post ["Join the Reshapr Adopters list and Empower the vibrant open source Community 🙌"](https://reshapr.io/blog/join-adopters-list/)
+            
+            Hope you have a great time there! 
+          
+          FIRST_PR_REACTIONS: '+1, hooray, rocket, heart'
+          
+          FIRST_PR: |
+            👋 @{{ author }}
+            
+            Welcome to the Reshapr community! 💖
+            
+            Thanks and congrats 🎉 for opening your first pull request here! Be sure to follow the pull request template or please update it accordingly.
+            
+            Hope you have a great time there! 
+          
+          FIRST_PR_MERGED: |
+            🎉 @{{ author }}
+            
+            You are now a Reshapr community contributor! 💖
+            
+            Thanks and congrats 🚀 on merging your first pull request! We are delighted and very proud of you! 👏 
+            
+            📢 If you're using Reshapr in your organization, please [add your company name to this list](https://github.com/reshapr/.github/blob/main/ADOPTERS.md). 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
+            
+            If you need to know why and how to add yourself to the list, please read the blog post ["Join the Reshapr Adopters list and Empower the vibrant open source Community 🙌"](https://reshapr.io/blog/join-adopters-list/)
+            
+            Kudos and please keep going, we need you 🙌
+            
+          STAR_MESSAGE: |
+            🌟 ~~~~~~~~~ 🌟
+
+            📢 If you like Reshapr, please ⭐ star ⭐ our repo to support it!
+            
+            🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
+            

CODE_OF_CONDUCT.md

@@ -0,0 +1,35 @@
+# Reshapr Community Code of Conduct
+
+Reshapr project adheres to the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md), aligning with the values of collaboration, transparency, and inclusivity that define open source.
+
+## Our Pledge
+
+As contributors and maintainers of the Reshapr project, we are committed to fostering an open, welcoming, and inclusive environment. By participating in our community, we pledge to:
+
+- Promote a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, experience level, nationality, personal appearance, race, religion, or sexual identity and orientation.
+- Support a spirit of mutual respect, empathy, and cooperation, ensuring that every contribution—big or small—is valued.
+- Encourage collaboration, knowledge-sharing, and continuous learning, as these are the cornerstones of any successful open-source community.
+
+## Our Standards
+
+To ensure a productive, positive experience for all community members, we ask everyone to:
+
+- **Be respectful and considerate**: Engage with others constructively, appreciating the diverse perspectives and ideas within the community.
+- **Be collaborative**: Open-source thrives on shared efforts and diverse input. Offer help where needed and seek help when necessary.
+- **Lead by example**: Encourage new contributors and foster an environment where everyone feels welcome to participate.
+- **Value inclusivity**: Open source is for everyone. Actively support a diverse range of contributors and voices, regardless of background.
+
+## Enforcement
+
+Instances of unacceptable behavior—including harassment, abusive language, or any other forms of misconduct—should be reported to the Reshapr project team at **info@reshapr.io**.
+
+The project team will:
+- Review and investigate all reports confidentially.
+- Take action deemed appropriate for the situation, including potential temporary or permanent bans from the community.
+- Keep the identity of the reporter confidential, ensuring a safe and respectful process for all involved.
+
+## A Community-Driven Open Source
+
+Reshapr thrives because of its open-source community. We encourage all members to actively contribute, share knowledge, and help make our project better for everyone. By following this Code of Conduct, we can create a community that supports innovation, collaboration, and the open-source values we all believe in.
+
+Thank you for being part of the Reshapr community!