WinCC OA Tools Pack

Professional project management and development tools for Siemens WinCC Open Architecture

This organization collects modular Node.js libraries, GitHub Actions, reusable workflows, and VS Code extensions for Siemens WinCC Open Architecture (SCADA) development. It provides essential tools for project management, code quality, testing, deploy and documentation for locale developments (vs-code extensions, AI MPC-server) and various CI/CD tools like github, gitlab, Jenkins, azure ...

🧰 WinCC OA Tools Pack — Community & Governance

Welcome to the winccoa-tools-pack organization!
This space hosts the shared standards, documentation, issue templates, and contribution workflows that power the entire WinCC OA open‑source ecosystem.

Our mission is simple:

Make WinCC OA development modern, open, modular, and community‑driven.

This repository defines how ideas flow, how features are evaluated, and how contributors can participate.

---

🚀 What This Repository Contains

This .github repository provides:

• Organization‑wide issue templates
• A unified pull request template
• The Code of Conduct
• The Contribution Guide
• The Triage Guide
• Shared governance rules
• Documentation for community processes

It acts as the central hub for collaboration across all child repositories.

---

🤝 How to Contribute

We welcome ideas, feature proposals, documentation improvements, and DevOps enhancements.

Before contributing, please review:

• Contribution Guide
  https://github.com/winccoa-tools-pack/.github/blob/main/CONTRIBUTING.md

• Triage Guide
  https://github.com/winccoa-tools-pack/.github/blob/main/docs/triage-guide.md

• Code of Conduct
  https://github.com/winccoa-tools-pack/.github/blob/main/CODE_OF_CONDUCT.md

These documents explain how ideas move through the ecosystem and how we keep everything organized.

---

📝 Issue Templates

All new issues must use one of the templates provided in:

.gith8b/ISSUE_TEMPLATE/

Available templates include:

• VS Code extension ideas
• GitHub Actions / CI‑CD enhancements
• WinCC OA testing features
• WinCC OA AI features
• Integrations & sub‑projects
• Jenkins ideas
• Documentation requests
• General ideas / visions

Every new issue automatically receives the triage label.

---

🧭 Triage Workflow

All new issues start in triage.

During triage, maintainers decide whether the idea:

✔ Becomes a project

For large, multi‑step, cross‑repo features.

✔ Moves directly to a child repository

For small, isolated tasks.

✔ Needs more information

Label: needs-info

✔ Is rejected

Label: rejected

Full details:
https://github.com/winccoa-tools-pack/.github/blob/main/docs/triage-guide.md

---

🗂️ Projects & Backlogs

Large features become GitHub Projects.

Each project must include:

• A Project Plan
• A backlog of issues
• A delivery order
• A clear goal and scope

Project plan template:
https://github.com/winccoa-tools-pack/.github/blob/main/docs/project-plan-template.md
(or wherever you place it)

Small features skip the project phase and go directly into the relevant repository.

---

🧱 Repository Structure

The organization consists of:

• VS Code extensions
• CI/CD tooling & GitHub Actions
• Jenkins integrations
• AI‑assisted development tools
• Testing utilities
• Integrations & sub‑projects
• Documentation repositories
• This .github meta‑repository

Each repository contains its own README and contribution notes.

---

❤️ Community

This ecosystem is built by and for the WinCC OA community.
We value:

• Openness
• Collaboration
• Respect
• Clear communication
• Shared innovation

Thank you for helping modernize WinCC OA development.

---

Organization-wide Labeling System

See LABELS.md for full guidelines.

---

Made with ❤️ for and by the WinCC OA community