# Improving Nextcloud Documentation and community engagement

**URL:** <https://help.nextcloud.com/t/improving-nextcloud-documentation-and-community-engagement/142505>\
**Category:** 💻 Development\
**Created:** [July 20, 2022, 6:40pm UTC](https://help.nextcloud.com/t/improving-nextcloud-documentation-and-community-engagement/142505 "2022-07-20T18:40:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon75456558](https://help.nextcloud.com/letter_avatar/anon75456558/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon75456558](https://help.nextcloud.com/u/anon75456558)\
**Post date:** [July 20, 2022, 6:40pm UTC](https://help.nextcloud.com/t/improving-nextcloud-documentation-and-community-engagement/142505/1 "2022-07-20T18:40:17Z")

</div>

Continuing the discussion from [Boosting community app development](https://help.nextcloud.com/t/boosting-community-app-development/142442/9):

> [@Boosting community app development](https://help.nextcloud.com/t/boosting-community-app-development/142442/9):
>
> Might be worth just checking the issue list of the documentation:
> 
> [Issues · nextcloud/documentation · GitHub](https://github.com/nextcloud/documentation/issues?page=1&q=is:issue%2Bis:open%2Blabel:%22manual:%2Bdeveloper%22)
> 
> and even some pull requests:  
> [https://github.com/nextcloud/documentation/pulls?q=is%3Apr+is%3Aopen+label%3A"manual%3A+developer"](https://github.com/nextcloud/documentation/pulls?q=is%3Apr+is%3Aopen+label%3A%22manual%3A+developer%22)
> 
> Even here on the forum, if you have to wait 6 month for a response ([\OC\_User::getDisplayName($userId) deprecated/ remove](https://help.nextcloud.com/t/oc-user-getdisplayname-userid-deprecated-remove/130920)), missed follow up answers ([Nextcloud Event Debugging](https://help.nextcloud.com/t/nextcloud-event-debugging/139633)), no answer ([Change user language from app controller](https://help.nextcloud.com/t/change-user-language-from-app-controller/140647)).
> 
> If the documentation is great and there is some timely feedback on development questions, you will at least not discourage interested developers.

Agreed, documentation is a problem. I would also argue that it is simply impossible to work with as-is.

- _Who is accepting documentation pull requests on Github_? If the current people are unable to commit their time, turn this task over to others who can be trusted to make it happen. The community should be trusted with this.

- Where is our community documentation?

Why are we not allowing and even actively encouraging contributions from the community? There is a reason [wikis rule](https://wiki.archlinux.org/) and it stems from easy and effective community engagement.

My opinion is that we need a more effective documentation source _for and from our community_. This forum could be an option, but we also gatekeep #📑 How to when we should simply make all topics into wikis be default with the only requirement being registering a forum account or attaining `@trust_level_1` after a few days registration. #Wiki category was made to fill this gap, because we do not have an issue with bad actors; rather, we lack options for people who want to contribute in any meaningful way + we have not clarified with users where/how to contribute. [See this attempt on explaining things to ncp users who might want to contribute](https://help.nextcloud.com/t/contribute-to-nextcloudpi/126384).

NextcloudPi has been porting all of our #NextcloudPi Documentation to the forum. All you must do is join our forum [group](https://help.nextcloud.com/g) and you’ll have full access to #NCP Documentation Drafts (draft) documentation yourself. All topics are wiki by default, because we want contributors! And all documents are visible to our [bridged telegram+matrix](https://matrix.to/#/#NCP_Wiki_Team:matrix.org) chat groups via RSS, where they are happy to assist further with docs.

Thanks for reading!

---

<div class="post-metadata">

**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\
**Post date:** [July 20, 2022, 6:44pm UTC](https://help.nextcloud.com/t/improving-nextcloud-documentation-and-community-engagement/142505/2 "2022-07-20T18:44:01Z")

</div>

cc @Daphne

---

<div class="post-metadata">

**Author:** ![anon75456558](https://help.nextcloud.com/letter_avatar/anon75456558/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon75456558](https://help.nextcloud.com/u/anon75456558)\
**Post date:** [July 20, 2022, 6:49pm UTC](https://help.nextcloud.com/t/improving-nextcloud-documentation-and-community-engagement/142505/4 "2022-07-20T18:49:58Z")

</div>

> [@tflidd](#):
>
> there are contributions from the community, however if reviews take months, the motivation is not very high.

Exactly, this necessitates the need for community maintained documentation, which could have handled the same documentation at their leisure.