Chronological Thread 

< Chronological >      < Thread >

---

Hi all,

The CellML editorial board met last week and to aid transparency and
openness we share the minutes from that meeting below.

Cheers,
Andre, on behalf of the editorial board.


-

Membership of
editors AT cellml.org
-

Other COMBINE standards tending to include all current and previous
editors on their editors list
-

Should we do something similar? Or keep the editors list for editors
and ensure cellml-discussion is used for all broader discussions.
-

For now we can keep the editors list for the current editorial board
-

We should look to update the pages on cellml.org to ensure/guide the
community to the discussion forum.
-

This should include making these meeting notes public.
-

Posting meeting minutes to cellml-discussion following each
meeting, omitting anything due to privacy concerns as needed.
-

CellML 2.0 specification
-

Source at:
https://protect-au.mimecast.com/s/-FUeC1WLoBTOGz9gfLGIzT?domain=github.com
-

Spec-improvements to add
-

Indexable sectioning variation
-

In implementing full validation in libCellML it has become
clear that it is not always possible to identify the
specific clause in the
spec relevant to a given validation check (multiple
validation rules in a
single identifiable section in the spec)
-

Would be good to ensure that all validation rules have their
own identifiable clause.
-

Would be used to help refer users to the specific validation
rule that has been broken in a given model.
-

Need to ensure there is a consistent method for identifying
aspects of the specification - could look to define a way
to consistently
address the current (frozen) spec or look to revise the
specification.
-

Using section numbers has an added benefit of being able to use
the URL for that section that tool developers may present
to users in order
to see that specific rule/clause. But also requires that
section numbering
can support the required depth.
-

Will look at in the libCellML implementation and report back
-

Guidelines for contributing to PMR
-

Could look to schedule a session at COMBINE to get an initial group
together for some discussion
-

Where we can reach out to some of the other repositories.
-

What can we learn that other repositories could make use of.
-

Andre: schedule a call with interested parties (including at least
Andre and Michael)
-

cellml.org website
-

Currently using Zope/Plone based on Python 2, also looking dated and
not so easy to keep up-to-date
-

Should look to migrate to a new platform that is easier to maintain
-

Need to investigate some options and migration plans
-

COMBINE website currently migrating to Hugo
(https://protect-au.mimecast.com/s/36FWC2xMp1U63l9rs11AEr?domain=gohugo.io),
using github actions to update as pull requests are merged in (

https://protect-au.mimecast.com/s/jqhtC3QNqKIxKAE3f2Om2E?domain=github.com).
Could look to
follow that approach.
-

Need to ensure maintenance and updates is easy for people to manage
and contribute. Reduce the barriers for people to contribute.
-

Will loop back to this at the next editors meeting to see what new
information is available, progress has been made in other
projects that we
can learn from, etc.
-

Upcoming changes to PMR, Physiome journal, etc. that we can look
to leverage.
-

Future meetings:
-

Aim for monthly and see how schedules for the editors line up.
-

Expect to meet at least every couple of months.

---

• [cellml-discussion] CellML Editors - minutes from September 2021 meeting, David Nickerson, 09/28/2021

---

Archive powered by MHonArc 2.6.18.