Re: Github issue tracker - wrapping up for sdo-gozer release

A quick update.

We continue to play whack-a-mole [1] with the issue list.  We are
making good cleanup progress but I believe hopes for a release early
next week are over-optimistic.

1. The recipe-related issue #165 was prematurely closed by me last
week. Stephane reminded us of some further flaws, and I've just
committed (and pushed a test build) of the new re-resolution of that
issue. (some
discussion continues...) now says
"Fix to #165: Renamed ingredients to recipeIngredient, improved the
description, and added ItemList as a possible value for

2. Vicki and I discussed today the RsvpAction/ReplyAction/AskAction vs
Question/Answer situation - . It is messier than
we first suspected, and needs some cleanup. This is one of those areas
in which we have Action-based and non-action based vocabulary
addressing the same problem space, compounded by poor examples and the
larger need for more clarity around UserInteraction vs Comment+Action.

3. Peter Mika and I will meet up tomorrow in London and spend some
time on this stuff.

4. The BibExtend Community Group mailing list is super busy as they
work towards a first cut at a Bibliographic extension, see
... including very natural questions about scope, e.g. whether/when to
include 'archives', and how to engage archivists if so.

In summary I think our initial hopes around a release early next week
may be over ambitious but a solid release candidate for final review
on that timescale ought to be feasible if we keep moving...

See below for how-to-help links,



On 21 April 2015 at 21:56, Dan Brickley <> wrote:
> Checking it is
> clear that most of the activities towards our next release
> are (as planned!) happening over in Github and the Community Group
> list discussion here so far has focussed on other topics. So I thought
> I ought to send a quick update here (as well as a reminder that a
> account is very useful for participating more fully in
> discussions).
> The next release is code-named sdo-gozer ("sdo" stands for
> We use these (Ghostbusters-inspired) names for Git(hub)
> work-in-progress branches and for test versions of the site published
> on
> For info, is a
> meta-bug with a l reasonable annotated listing of gozer-related
> issues. See also Vicki's doc about possible renamings of terms that
> have very generic or confusing names,
> (the specific list
> there was intended a conversation starter).
> The build of the site visible on is based on the
> work-in-progress sdo-gozer branch within Github, i.e. this will become
> the candidate next release soon. A good entry point is the draft new
> version of the /docs/releases.html page, i.e.
> You can filter Github by milestone and label. At this time filtering
> on Gozer release and ' vocab' provides a useful status
> report:
> This currently reveals 24 open issues, which need analysis, agreement
> and closure (or postponing to a future release). Do please take a look
> at the discussions and jump in with any observations and proposals
> that you think can help progress things. While there are also some
> software fixes in progress (sdo-scripts branch), we are optimistic
> that this next release can be wrapped up within days rather than
> weeks. If comments in Github can be made in the spirit of resolving
> (or resolving to postpone) issues rather than opening, broadening or
> prolonging discussion that would be super helpful!
> cheers,
> Dan

Received on Wednesday, 22 April 2015 20:54:58 UTC