Explain the problems with adding new forks
This commit is contained in:
parent
4f9b23ab1f
commit
32fc7abd2d
1 changed files with 1 additions and 1 deletions
|
@ -2,7 +2,7 @@
|
|||
Go [here](#branchfeature-list) for the new features.
|
||||
|
||||
### Don't we have enough Aegisub forks already??
|
||||
We absolutely do, and I'm aware that adding another one doesn't sound like a good idea on paper. However,
|
||||
We absolutely do, and I'm aware that adding another one [doesn't sound like a good idea on paper](https://xkcd.com/927/). However,
|
||||
|
||||
- None of the existing forks are completely satisfying at the moment:
|
||||
- [wangqr's fork](https://github.com/wangqr/Aegisub) is actively maintained, but focussing more on stability. It's missing most of the modern features.
|
||||
|
|
Loading…
Reference in a new issue