Re. DocJam: I’m thinking of aiming for the week-end of May 18-19-20 (I’m including a Friday in case some people are more available during week-time), because it happens to be convenient for me and there is not much point in doing a poll at this scale. I’m leaving myself some time to think it again and for people to complain, but otherwise I can open a thread here and announce it on the caml-list and reddit.
What we need to get running (besides an agreement on the dates) is:
- a document that describes the purpose of the event, the process, and how to join
- a way to broadcast suggestions of libraries to look at; (if the organization document is on a wiki, we could have another page for these suggestions)
- a communication channel (I’m thinking of staying with Discuss, but maybe also an #ocaml-docjam IRC with a link the Matrix bridge)
- some agreed way to aggregate/collect a list of things that have been done during the jam, to write a summary post/description after the fact
- people willing to participate
One thing that must be articulated carefully is the question of how to review the work produced by the jam. People may be uncertain about whether their documentation or example proposal is actually “the right way” to do it, and we need to liberate ourselves from this worry by addressing it upfront and having a process in place. The simplest thing to try would be to encourage people to submit an upstream PR and share the link on the Jam thread, to encourage others to review it (before, or in addition to, the actual maintainer(s) of the library). But maybe some people will want a way to pre-screen their submission proposals – maybe they could create a PR from their doc-branch to their own trunk-branch for fellow jammers to review, and only send upstream after that is done.