tgupdate: merge t/DO-NOT-MERGE-mptcp-enabled-by-default base into t/D…

…O-NOT-MERGE-mptcp-enabled-by-default

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: [matttbe]

.github/ISSUE_TEMPLATE/01-bug.yml

@@ -0,0 +1,64 @@
+---
+name: Bug report
+about: Create a report to help us improve
+labels: ["bug", "triage"]
+
+---
+
+**Describe the bug**
+<!-- A clear and concise description of what the bug is.. -->
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. **TODO**
+
+**Expected behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**System: Client**
+ - Kernel version (`uname -a`): **TODO**
+ - Distribution and version (or `cat /etc/os-release`): **TODO**
+ - MPTCP sysctl (`sysctl net.mptcp`):
+```
+TODO
+```
+ - MPTCP PM Endpoints (`ip mptcp endpoint show`):
+```
+TODO
+```
+ - MPTCP PM limits (`ip mptcp limits show`):
+```
+TODO
+```
+
+**System: Server**
+ - Kernel version (`uname -a`): **TODO**
+ - Distribution and version (or `cat /etc/os-release`): **TODO**
+ - MPTCP sysctl (`sysctl net.mptcp`):
+```
+TODO
+```
+ - MPTCP PM Endpoints (`ip mptcp endpoint show`):
+```
+TODO
+```
+ - MPTCP PM limits (`ip mptcp limits show`):
+```
+TODO
+```
+
+**Up-to-date kernel?**
+<!-- Did you try to reproduce the issue with ideally the last stable kernel version, or at least the last LTS version (or the development version using our `export` branch?
+See https://www.kernel.org for the supported versions -->
+
+**Additional context**
+<!--
+Add any other context about the problem here.
+Note: It might help to get the output of  `ip mptcp monitor` while reproducing the issue, in addition to the output from these commands executed just before **and** after the issue:
+```
+ss -ManiH
+nstat
+```
+Packet traces (TCPDump / WireShark) can be helpful too. See https://www.mptcp.dev/debugging.html for more details.
+mptcpd's `mptcp-get-debug` script (mptcpd >= 0.13) can help to collect such infos: https://raw.githubusercontent.com/multipath-tcp/mptcpd/refs/heads/main/scripts/mptcp-get-debug
+-->

.github/ISSUE_TEMPLATE/02-feature.yml

@@ -0,0 +1,18 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+labels: ["enhancement", "triage"]
+
+---
+
+**Is your feature request related to a problem?**
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+**Describe the solution you'd like**
+<!-- A clear and concise description of what you want to happen. -->
+
+**Describe alternatives you've considered**
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+**Additional context**
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/03-question.yml

@@ -0,0 +1,10 @@
+---
+name: Question
+about: Ask any questions here
+labels: ["question", "triage"]
+
+---
+
+Please use the bug report template if you have a question related to the current behavior: we will need details about your system.
+
+https://github.com/multipath-tcp/mptcp_net-next/issues/new/choose

SECURITY.md

@@ -0,0 +1,17 @@
+# Security Policy
+
+## Supported Versions
+
+The ones mentioned on [kernel.org](https://www.kernel.org).
+
+## Reporting a Vulnerability
+
+Please report any issues to us, either via
+[GitHub](https://github.com/multipath-tcp/mptcp_net-next/security/advisories/new),
+or via emails to the MPTCP maintainers:
+
+ - Matthieu Baerts <[email protected]>
+ - Mat Martineau <[email protected]>
+
+(Check the [MAINTAINERS](https://github.com/multipath-tcp/mptcp_net-next/blob/export/MAINTAINERS)
+file to get the up-to-date list.)