惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
爱范儿
爱范儿
博客园 - 三生石上(FineUI控件)
Vercel News
Vercel News
M
MIT News - Artificial intelligence
L
LangChain Blog
大猫的无限游戏
大猫的无限游戏
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Azure Blog
Microsoft Azure Blog
J
Java Code Geeks
Recent Announcements
Recent Announcements
Stack Overflow Blog
Stack Overflow Blog
人人都是产品经理
人人都是产品经理
IT之家
IT之家
F
Fortinet All Blogs
博客园 - 聂微东
U
Unit 42
Martin Fowler
Martin Fowler
腾讯CDC
博客园_首页
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
量子位
阮一峰的网络日志
阮一峰的网络日志
博客园 - Franky

Danb Blog

August 2026: What I've Been Working On · Danb Blog Great Tech: Intel 2500k CPU · Danb Blog July 2026: What I've Been Working On · Danb Blog My Experience with Ubuntu Desktop 26.04 · Danb Blog Thumbnails for Orca 3MF in GNOME Files · Danb Blog Cheaper Sodastream Gas with a Big Tank · Danb Blog June 2026: What I've Been Working On · Danb Blog Running Snyk On Forgejo/Codeberg Actions · Danb Blog Tuta & Proton: An Open Source Client Does Not Result in an Open Source Service · Danb Blog May 2026: What I've Been Working On · Danb Blog 3D Printing Parts for my Greenhouse, Round 2 · Danb Blog Great Devices: Nexus 7 2013 · Danb Blog R36S Console RetroArch Stuck Menu Issue · Danb Blog April 2026: What I've Been Working On · Danb Blog Basic OpenCode Sandboxing with Docker · Danb Blog Games Played in 2025 · Danb Blog March 2026: What I've Been Working On · Danb Blog Shivam Mathur's "node-docker" Images are Awesome for PHP CI · Danb Blog February 2026: What I've Been Working On · Danb Blog My Sovol SV08 3D Printer Setup in 2026 · Danb Blog January 2026: What I've Been Working On · Danb Blog Epson Printer: The administrator password you entered was not recognized · Danb Blog Pressure to Follow Process · Danb Blog Online Shopping Email Notifications · Danb Blog My HomeLab Setup in 2026 · Danb Blog Linux Label Printing with the Phomemo D30 · Danb Blog Reporting to the CMA: Google Android Developer Verification · Danb Blog OPNsense & Dnsmasq: Responding with specific DNS servers · Danb Blog An Impromptu Introduction to ZFS Drive Replacement at 1am · Danb Blog Experience with UK Medical Cannabis for Ankylosing Spondylitis · Danb Blog
Your BookStackApp project was assigned as a project for m...
2026-02-26 · via Danb Blog

Below is an email I received in December 2024, but this is just one example of various encounters I’ve had where students have been led to contribute to the project by their tutor. I don’t mind spending time to help assisting contributions from those that have a genuine interest in the project, as that can help foster a longer term contributor relationship which is healthy for the project overall, but these contributions are often done with the core intent of passing course requirements.


Their Email

Hello Mr. Brown,

I am studying software engineering at <UNIVERSITY NAME REMOVED>. Your BookStackApp project was assigned as a project for my Software Architecture course. We were asked to suggest architectural changes that would increase the scalability of the project. We wanted to meet with you because you rejected our last pull request. We would be very happy if you could help us with the architectural changes and provide feedback.

Best regards Have a nice day


My Response

Hi <NAME_REMOVED>,

Sorry I rejected your pull request. The problem is though, if you’re providing/offering changes, with the expectation of them being merged/included, with the main aim of passing/progressing a course, then that’s contributing under the wrong motivations.

Architecture and scalability are quite high-level concerns, and as a decade-old & stability-focused project such as BookStack, these aren’t topics which would have or need direct contributions provided by fly-by contributions that don’t have prior context or deeper experience/understanding of our goals & scope.

Lastly, I did not consent nor agree for my project to be used within your course, and I’m not keen on spending time discussing or integrating change for the sake of change, or for a University course. If there’s a specific thing to address, which is an actual issue, I’m happy to hear back from our community members on that, but I’m not going to change architectural or scope decisions based upon an assignment we did not agree to be part of.

I’m often happy to spend the time needed to support less experienced developers in helping contribute, but only where they’re happy to match effort for that, and where they have an ongoing active interest in the project.

Regards, Dan