Excellent way to prioritize the documentation rewrite/expansion. I'm ready 
to start writing too. 

Neil

On Thursday, June 4, 2020 at 12:45:59 PM UTC-4, Adam Cox wrote:
>
> Hello everyone,
>
> Angela Labrador and I are planning to coordinate a community-oriented 
> documentation writing sprint to bring the current Arches documentation 
> up-to-date with the most recent release, v5.0 as best as we can. Hopefully 
> we can also address some aspects of the documentation that needed attention 
> prior to the update.
>
> We'd like to begin by soliciting feedback from all forum members on the 
> following:
>
>    - Which aspects of the documentation have you found confusing or 
>    misleading?
>    - Are there topics that you would like to see added to the official 
>    documentation?
>
> Please respond with your thoughts in this thread or email us directly. 
> Feel free to second other people's posts if someone has already mentioned 
> the same thing you were thinking--more input is better than less at this 
> stage.
>
> We'll begin comparing your ideas with known documentation "to-dos" as 
> recorded in the arches-docs issue tracking. 
> <https://github.com/archesproject/arches-docs/issues>Then we can put out 
> a call for help, especially to those most knowledgeable in these specific 
> topics, and start organizing a "sprint" of a few days where we can make 
> some real progress on the content itself.
>
> We won't get everything perfect, but hopefully a concerted and coordinated 
> effort can make some big improvements.
>
> Adam
>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/archesproject/8d54b14b-19d8-4f1c-9e8d-56a9eb3d9079o%40googlegroups.com.

Reply via email to