The Kanban dev process was used many years ago but never in Nextcloud.
Therefore the process description is not just outdated but misleading.
We still use the labels, albeit their description was mildly outdated.
They were restructured and grouped for better comprehensibility.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
* Add missing debugging page
* Remove dead request lifecycle sub pages TOC
* Remove dead link to core translations page
* Revive link to basics debugging page
* Fix traige workflow image path
* Remove dead link to performance page
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
While setting up a local dev checkout of nextcloud/server, I noticed
that the part about creating the 'config' directory is outdated: this
directory already exists in the repository and doesn't need to be created
during setup.
I have fixed that part of the guide and also clarified some wordings
elsewhere in this guide.
Signed-off-by: Nina Pypchenko <22447785+nina-py@users.noreply.github.com>
Add mention to cloning external shipped apps into the apps folder in the
development environment, to be able to test upgrades as these apps will
be required at that point.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
This moves lots of pages around. The high-level changes are
* Better main sections, so it's more *general*, *into*, *basics* and *details*
* Move more general topics to a *Basic* section, which are not
app-specific
* Remove app docs to the stuff that is likely used, anything else goes
into "Digging deeper"
* Move general guides into a prologue
* Try to *compress*/combine some pages with similar content
* Try to have better consistencs on level ob abstraction across pages
* Split app development and maintenance pages into two sections
* Integrate bugtracker info into prologue
* Integrate Android pages into client APIs section
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
