Dear NEST users and developers,
some of you may already have noticed, that we recently updated a lot of
issues and pull-requests in our repository. The changes are completely
organizational and aim to provide a better overview and service to our
In particular, we removed the "C:" category labels (Model, Kernel,
PyNEST, Documentation, ...) and instead now make use of corresponding
GitHub projects. There, issues and pull-requests are represented as
"cards" on a Kanban-like board, which gives a comprehensive view on the
current topics and enables dedicated discussions to focus more easily.
For each project we assigned a contact person that will take care of
organizing work for that subset of cards. You notice that also the "P:"
progress labels have mostly been removed (except "blocked" and "won't
fix"), as this is automatically tracked in the columns of the projects
and is much easier to manage there.
The change to GitHub projects enables us to discuss topics in a more
focused fashion than detailed issue-by-issue, which will also be
reflected in the Open NEST Developer Video Conference. Projects will
give a general status update and can raise overarching questions into
the discussion. The detailed issue-by-issue work on the other hand, is
organized by the project groups separately and each group may decide to
do separate meetings to discuss details.
Besides the long-running projects corresponding to the category labels,
larger short/mid-term activities are organized in "Feature-Projects".
These projects aim to help developers to work on special or
cross-cutting topics and are expected to be "finished" at some point.
The open VC will cover them similar to the long-term projects if required.
We hope these changes improve the overview over the work ongoing in all
the many areas for users and developers, facilitate detailed discussions
between relevant and interested people and make the work on the
simulator more transparent.
Show replies by date