scriptorium issueshttps://lab.allmende.io/degrowth/scriptorium/-/issues2023-11-30T19:02:50Zhttps://lab.allmende.io/degrowth/scriptorium/-/issues/253Transparent and accountable workflow2023-11-30T19:02:50Zjon ryala@allmende.ioTransparent and accountable workflowFrom the last conference we learned that it is best to:
- [ ] Have concrete development contract available
- [ ] Have physical meeting together for setting up a project
- [ ] Have a process ready that describes the methodology of develo...From the last conference we learned that it is best to:
- [ ] Have concrete development contract available
- [ ] Have physical meeting together for setting up a project
- [ ] Have a process ready that describes the methodology of development
- [ ] Act with time loyalty
- [ ] Guide maintainers through phase changes #252
These workflow changes will help other conference organisers to understand the cooperation better.Long-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/252Documentation for different usage phases of the conference platform is missing2023-11-30T19:02:50Zjon ryala@allmende.ioDocumentation for different usage phases of the conference platform is missingWe currently lack documentation that guides conference maintainers through the phases of:
- [ ] setting up a conference
- [ ] preparing the call for papers
- [ ] conducting the call for papers
- [ ] peer review
- [ ] configuring rooms a...We currently lack documentation that guides conference maintainers through the phases of:
- [ ] setting up a conference
- [ ] preparing the call for papers
- [ ] conducting the call for papers
- [ ] peer review
- [ ] configuring rooms and time slots
- [ ] scheduling of sessionsLong-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/216Documentation does not contain specifications nor a human-readable Changelog2018-03-22T23:04:27Zjon ryala@allmende.ioDocumentation does not contain specifications nor a human-readable ChangelogIn #211 mladen was so friendly to give deeper insight into the Budapest procedure
@gandhiano @viktoriya.kulikova I suggest we add a space for specifications about the workflows for different versions of our releases to the https://lab.a...In #211 mladen was so friendly to give deeper insight into the Budapest procedure
@gandhiano @viktoriya.kulikova I suggest we add a space for specifications about the workflows for different versions of our releases to the https://lab.allmende.io/degrowth/scriptorium/wikis/home and keep a little more track about what we are implementing here, i.e.
- https://lab.allmende.io/degrowth/scriptorium/wikis/review-workflow
- https://lab.allmende.io/degrowth/scriptorium/wikis/degrowth-changes-to-frab
The first could be a collection copy and pasted from the channel, pads and issues, while the second could be compiled from the past issues.Long-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/207Call for papers peer review workflow2019-12-05T19:52:43Zjon ryala@allmende.ioCall for papers peer review workflowThis is a continuation of #204. The call for papers review workflow is currently optimised for the Budapest conference.
After allowing all event types for review, we found the following:
1. One can create only one Special Session.
2. O...This is a continuation of #204. The call for papers review workflow is currently optimised for the Budapest conference.
After allowing all event types for review, we found the following:
1. One can create only one Special Session.
2. One can create as many poster and participatory sessions as wanted.
3. After creating an individual paper, all submissions will be closed, but review allowed
This is encoded in https://lab.allmende.io/degrowth/scriptorium/blob/deployment/app/models/ability.rb
@gandhiano suggests to work with @mladen and @viktoriya.kulikova around the past and current requirements and redesign the flow as intended.Long-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/192Co-authors to be shown in the schedule2018-10-02T15:50:24ZMladenCo-authors to be shown in the scheduleThe official Public Schedul eof the conference is now being used as repository of presentations, and a book of abstracts of sorts. In that respect, co-authors of papers who were not present at the conference (i.e. were not registered par...The official Public Schedul eof the conference is now being used as repository of presentations, and a book of abstracts of sorts. In that respect, co-authors of papers who were not present at the conference (i.e. were not registered participants) would like to see their names publicly listed. We did notz want to originally list them as speakers (As they were not speakers). They also laregly did not have activated user accounts, as they were just listed by the Submitter as co-authors.
Could we please open up a new field in the public schedule interface listing the co-authors tied to the paper? Names of these people exist in the database, and they don't have to be clickable (as they don't have functioning user accounts) and can just be listed on the page of individual paper as co-authors. Improve on DG2016 conference weak pointsPonder StibbonsPonder Stibbons2016-09-30https://lab.allmende.io/degrowth/scriptorium/-/issues/62Check and document backup & restore2018-05-16T22:20:31ZGualterCheck and document backup & restoreHow are backups being done for dbp2016-live / Dokku?
Are they automated? How frequent?
How to recover, import them back if something goes wrong?How are backups being done for dbp2016-live / Dokku?
Are they automated? How frequent?
How to recover, import them back if something goes wrong?jon ryala@allmende.iojon ryala@allmende.io