Overview: May 2020 Sprint

[mike-thompson-day8]

Isaac and I are doing a three-week-long sprint on re-frame - starting 4th May. Isaac's time is being paid for by ClojuristTogether funding. My time is paid for by Day8. So between us, we have about 6 man-weeks.

At a high level, the strategy is:

• [x] do the low hanging fruit (there are a few smaller, easier issues)
• [x] do a 1.0.0 release (it is about time)
• [x] create a grown-up website and fix up documentation which has fallen a bit into disrepair. This is a bit scary because it could take an infinite amount of time, so how do we limit it?
• [ ] attack three of the bigger, meatier issues: BranchScope, Multiple frames on a page, views. All three of these issues are interrelated.
• [ ] do a release

This will likely take longer than six man-weeks. And then there will be necessary adjustments to re-frame-10x. To quote a line from the movie Get Shorty "This is only the second day, and we're already two weeks behind." But, one step at a time, let's just see how we go.

I will update this issue with new thoughts as we go. We will probably engage with the community via the clojurians #re-frame channel. If you are interested in the process, please keep an eye out there.

[mike-thompson-day8]

Progress on the early, low-hanging-fruit step:

• [x] thoroughly review all the existing issues and PRs.
• [x] close any issues which need it
• [x] assemble the candidate list of issues we identify as "low hanging fruit"

Progress ...

Closed with explanations:

• 553

• 572

• 555

• 112

• 481

• 164

• 554

• 480

Picked Fruit, so far:

• 544

• 456

• 216

Issues arising:

• 588

Building a grown-up website https://github.com/day8/re-frame/issues/582:

• [x] A review of options and likely paths has commenced.

[mike-thompson-day8]

• [x] some distracting issues with re-frame-template, shadow-c;lj and Lein-Shadow. See https://github.com/day8/re-frame-template/issues/128 and https://gitlab.com/nikperic/lein-shadow/-/merge_requests/3
• [x] some distractions with re-frame-10x (almost there)
• [x] #570 - Implement a way to add global interceptors
• [x] about to cut a new release which includes all the low hanging fruit

New website progress

• [x] learning new static site generator (good decision so far, but there's always stuff to learn)
• [x] we've spent far too long getting Klipse going (to supply a page of live coding)
• [x] a GithubActions based build system for new website
• [x] a LOT of rewriting, writing and thinking
• [x] integration with API docs

New docs include the following:

• Reusable Components . Addresses issue #264
• On Dynamics
• Subscriptions. Previously a neglected area.

Hoping to deploy the new website over the coming weekend.

We're down to about 18 issues and 3 PRs. When we started, I think it was 30 issues and 9 PRs.

[mike-thompson-day8]

The new re-frame website is now up at: http://day8.github.io/re-frame/

The re-frame logo has been tweaked. See it here: http://day8.github.io/re-frame/re-frame/

And a release candidate for 1.0.0 is also out

Also, we're now down to about 16 issues and 2 PRs.

Now we begin on the meatier issues.

[mike-thompson-day8]

The task of addressing meatier issues is now slightly delayed.

• [x] new FAQ item added which closes https://github.com/day8/re-frame/issues/538
• [ ] #478
• [ ] in light of negative feedback we have received, we are reworking the new website. Goal is to present code earlier and require less initial reading.

We are down to 13 open issues and 2 PRs, which is a numerical measure of some success.

[mike-thompson-day8]

Many improvements to the docs have been made recently. Too many to mention but some are notable:

• added a new FAQ on laggy input
• added a new FAQ on field focus
• added to existing FAQ on global interceptors
• Additions made to External-Resources
• completely reworked Infographics for Dominoes 1,2 3
• completely reworked Infographics for Interceptors. See also other explanations added to that tutorial.

Also:

• closed #590
• created #627 and developed a corresponding PR #628
• we continue to wrestle with getting a v1.0.0 out. React native niggles still exist. See #604 #614 #615.

Numerically, we're at 13 issues and 3 pull requests.