Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration of community documentation #29

Open
AbcSxyZ opened this issue Sep 14, 2020 · 4 comments
Open

Integration of community documentation #29

AbcSxyZ opened this issue Sep 14, 2020 · 4 comments

Comments

@AbcSxyZ
Copy link

AbcSxyZ commented Sep 14, 2020

I would warn about potential unorganized work who will append.
A message on gitter

take a look at this guide we made, it might be useful to you https://labs.openheritage.eu/pages/participatorytext

You can improve your documentation with this kind of work. Your strategy should have a stronger
focus on community work, how to include them. It look like you're doing it in a small group of persons,
without communication.

Some guys work on documentation for they own structure because there is a lack of doc, it seem you're not trying to reach this resources.

@AbcSxyZ AbcSxyZ changed the title Integration of collaborative documentation Integration of community documentation Sep 14, 2020
@microstudi
Copy link
Contributor

What about making a public call to post resources that community has made? this would make easy the task to collect and maybe create a wiki-style guides

@AbcSxyZ
Copy link
Author

AbcSxyZ commented Sep 14, 2020

Good idea, a public call + create a guide to introduce other developer to the production of the documentation. Having a contribution guideline, explain philosophy of the documentation, explain needs, etc.

Communicate to introduce other developer to the process

@andreslucena
Copy link
Member

I actually reached to OpenSourcePolitics last week regarding this issue, as they have a documentation site, although they don't have a free license ("© Open Source Politics 2020"). I've asked them if it's possible to have it licensed compatible with ours license (gdfl and cc-by-sa) cc @paulinebessoles @virgile-dev

I've also found https://digidemlab.org/decidim-docs/docs/en/1-discover-decidim.html

What about making a public call to post resources that community has made? this would make easy the task to collect and maybe create a wiki-style guides

That'd be really nice!!

Regarding the current Admin Manual, there is already a work in progress about translating it from Spanish and updating it at #13

You can improve your documentation with this kind of work. Your strategy should have a stronger
focus on community work, how to include them. It look like you're doing it in a small group of persons,
without communication.

There's a saying in Spanish demonstrations that says: "no nos mires, únete". Translated that'd be "do not watch us, join us"

@AbcSxyZ
Copy link
Author

AbcSxyZ commented Sep 15, 2020

There's a saying in Spanish demonstrations that says: "no nos mires, únete". Translated that'd be "do not watch us, join us"

I'm not actually working on decidim, I hope I will do that, it's why I'm (mainly) watching what is happening. For sure, your sentence is true. But if you don't show you, they won't watch you, and they won't join you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants