[roadmap/gsoc26] Updated: X.509 Certificate Generator Templates

[nemesifier]

Added more details to the spec of the x509 generator template idea, added a mention to this feature in the roadmap.

[coderabbitai]

Warning

Rate limit exceeded

@nemesifier has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e50d8a1 and 70e09e2.

📒 Files selected for processing (4)

• build.py
• developer/gsoc-ideas-2026.rst
• general/roadmap-2030.rst
• spelling_wordlist.txt

Walkthrough

This pull request updates OpenWISP project documentation to expand and restructure the GSoC 2026 X.509 Certificate Templates project idea. The project scope increases from 90 to 175 hours and shifts focus from OpenVPN-specific certificates to general-purpose certificate generation for broader use cases (HTTPS, mutual TLS, internal APIs). The proposal integrates with django-x509 infrastructure and device properties, enabling certificates to incorporate device-specific data like hostname, MAC address, and UUID. Configuration variables are introduced to expose certificate PEM data for deployment. The roadmap is updated to reference this feature, and spelling wordlist entries are added for new terminology.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title directly reflects the main changes: updating X.509 Certificate Generator Templates specifications and roadmap for GSoC 2026.
Description check	✅ Passed	The description accurately summarizes the changeset by mentioning the detailed spec updates for the x509 generator template and the addition to the roadmap.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-plans

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@general/roadmap-2030.rst`:
- Around line 338-347: Reflow the long list item "General Purpose X.509
Certificate Templates" into a properly indented RST paragraph: wrap the text to
normal sentence length, keep inline code roles like ``django-x509`` and ``PEM``
intact, then place the :ref: reference on its own indented continuation line
(indented at least one level to match the list item) with a blank line before it
so the linter treats it as part of the item; update the bullet so the
description lines are consistently indented and the reference appears as a
separate wrapped line (e.g., break after "automated deployment to networking
devices." then add the indented :ref: line).
- Around line 84-86: The bullet list item containing the :ref: target is wrapped
incorrectly for reStructuredText; fix it by reflowing the item so the :ref:
reference stays on the same logical line or any continuation lines are indented
to align with the start of the list text (i.e., after the hyphen and space), for
example join the sentence into a single line or indent the wrapped line to the
same column as "Facilitate" so the :ref: token (OpenWISP VPN Deployer Linux
Package GSoC 2026 Project Idea / :ref:) is not broken across incorrect
indentation.

🧹 Nitpick comments (1)

developer/gsoc-ideas-2026.rst (1)

151-157: Consider consistent “X.509” capitalization in narrative text.
You use “x509” in sentences while the section title uses “X.509”; aligning casing improves polish.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2716e96 and e50d8a1.

📒 Files selected for processing (3)

• developer/gsoc-ideas-2026.rst
• general/roadmap-2030.rst
• spelling_wordlist.txt

🧰 Additional context used

🪛 GitHub Actions: OpenWISP Docs

general/roadmap-2030.rst

[error] 1-1: ReStructuredText check failed. File could be reformatted (1 of 44 files).

🔇 Additional comments (4)

spelling_wordlist.txt (2)

151-151: Wordlist update looks good.
No issues with adding “lifecycle” to the dictionary.

---

291-291: Wordlist update looks good.
Adding “Unassignment” is consistent with the new lifecycle terminology.

developer/gsoc-ideas-2026.rst (2)

137-138: Anchor addition looks good.
No issues with the new gsoc-2026-x509-templates target.

---

170-313: No RST formatting issues detected. The file's heading underlines match their title lengths, and all lines in the specified range are within acceptable length limits. The code is properly formatted and does not require corrective action.

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}