documentation

CONTRIBUTING to LUGAN

LUGAN is built by its community. We don’t just use Free Software; we build it, research it, and govern it together. Your input, whether code or conversation, is vital to our mission.

TL;DR

Type of Contribution	Platform/Location	Action Required
Code & Documentation	GitHub Repositories	Fork, submit Pull Requests (PRs), or open Issues for bugs and features.
Organizational Governance	GitHub Issues & Discussions	Open an Issue to propose changes to guidelines (MANIFESTO, CoC), and use Discussion Polls for formal voting.
Informal Feedback & Quick Ideas	Telegram / Discord	Use chat for quick polls, rapid affirmation (“Yes, cool, let’s do it!”), and immediate sentiment gauging.
In Person Input	UNIVPM Meetings (Talks/Workshops)	Participate in physical sessions to challenge ideas, propose new research, and share opinions.

---

Before You Start

🤝 Code of Conduct

Please review our Code of Conduct before contributing. We expect all contributors to follow these guidelines to ensure a welcoming, respectful, and productive environment.

🔍 Where to Contribute

We primarily distinguish between two types of contributions: Technical/Code and Governance/Organizational.

---

Technical & Code contributions

All active development happens on our GitHub repositories. This is the place for code, documentation, and specific feature proposals.

A. Submitting code changes (Pull Requests)

If you have written code, fixed a bug, or improved documentation for any project managed by LUGAN:

• Fork the relevant project repository.
• Make your changes in a new branch.
• Ensure your code adheres to any existing project guidelines.
• Open a Pull Request (PR) against the main branch.

B. Reporting bugs and proposing features (Issues)

If you find a problem in our code or have an idea for a new feature:

• Open an Issue in the relevant project repository.
• Use clear and descriptive titles.
• Follow the provided Issue template (if available).

Please follow these rules for commit naming conventions:

• [YASE

  setup git repo](https://leviathan36.github.io/yase/rest_api_101/5_setup_git_repo/Setup_git_repo.html)

• [conventional commits

  summary](https://www.conventionalcommits.org/en/v1.0.0/#summary)

---

Shaping the organization (LUGAN governance)

Our group structure and rules are managed collaboratively, often referred to as “Governance as Code.”

A. Proposing changes to group guidelines

To formally propose changes, modifications, or discussions regarding foundational documents:

• Open an Issue against the main LUGAN repository (or the repository where the document resides).
• This applies to files like the MANIFESTO, Code of Conduct (CoC), and other internal guidelines.
• Treat these changes with the same rigor as a Pull Request, explaining the reasoning and the intended impact.

B. Formal group voting

When formal consensus is required for key decisions (e.g., electing officers, approving major budget items, adopting new policies):

• Use the GitHub Discussions tab for structured debate.
• Formal votes are held using the Polls feature within the Discussions tab to ensure transparency and trackability.

---

Informal feedback and quick sync

Not every contribution needs a formal PR or Issue. We highly value quick feedback and active participation in our daily stream.

🚀 Community chat & quick polls

For spontaneous ideas, quick affirmation, or low-friction feedback:

• Join our Telegram or Discord channels (JOIN_US.md).
• Share quick ideas, run simple polls, or simply affirm support by saying things like “Yes, cool, let’s do it!“ or “Thumbs up!“ This rapid feedback helps the project leaders gauge immediate community sentiment.

🎙️ In person discussion

Our physical meetings at UNIVPM are a vital space for discussion and debate.

• Participate in talks and workshops. Use these sessions to say your piece, challenge ideas, or propose new research directions in person.

---

Thank you for helping us build LUGAN!

This site is open source. Improve this page.