scriptorium issueshttps://lab.allmende.io/degrowth/scriptorium/-/issues2019-12-05T20:31:57Zhttps://lab.allmende.io/degrowth/scriptorium/-/issues/260docker-entrypoint.sh can be omitted2019-12-05T20:31:57Zjon ryala@allmende.iodocker-entrypoint.sh can be omittedFrom looking at the file `docker-entrypoint.sh`, we can certainly assume that it would also suit into the `CMD` directive.From looking at the file `docker-entrypoint.sh`, we can certainly assume that it would also suit into the `CMD` directive.Long-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/259No development process2019-12-18T00:45:43Zjon ryala@allmende.ioNo development processAcoording to https://lab.allmende.io/degrowth/scriptorium/issues/217#note_13857 we are now floating the git flow between `master` and `develop`. The latter is our working branch, which merge requests are filed at against.
Feature branch...Acoording to https://lab.allmende.io/degrowth/scriptorium/issues/217#note_13857 we are now floating the git flow between `master` and `develop`. The latter is our working branch, which merge requests are filed at against.
Feature branches branch off for integration of new (sic!) features. They can be named according to the issue they implement, `fix/nn`. For issue #254 this could be `fix/254`.
`master` releases happen from time to time manually, to which hotfixes are employed.
Also see: https://www.bluesource.at/blog/detail/git-flow/Long-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/256Rebase on Upstream2019-12-05T01:17:23Zjon ryala@allmende.ioRebase on UpstreamThis issue is a meta issue to track questions related with rebasing our current codebases back on Upstream.
Related upstream issues are:
- Plugin System (open since **29.12.2011** !!!)
https://github.com/frab/frab/issues/10
- Make ...This issue is a meta issue to track questions related with rebasing our current codebases back on Upstream.
Related upstream issues are:
- Plugin System (open since **29.12.2011** !!!)
https://github.com/frab/frab/issues/10
- Make event types configurable (*18.03.2017*)
https://github.com/frab/frab/issues/302
- configurable event types per conference (opened *03.09.2019* - **merged** *25.10.2019*)
https://github.com/frab/frab/pull/530
- README.PaaS.md should require a persistent storage (open since 06.03.2019)
https://github.com/frab/frab/issues/466Long-term stability of the conference platformhttps://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/244Budapest 2016 issue leftovers are not considered in long-term planning2018-07-05T12:54:01Zjon ryala@allmende.ioBudapest 2016 issue leftovers are not considered in long-term planningWhen grooming https://lab.allmende.io/degrowth/scriptorium/issues we find that many issues can be useful for the https://lab.allmende.io/degrowth/scriptorium/milestones/15 milestone. Moving some of them in there, or closing, would also a...When grooming https://lab.allmende.io/degrowth/scriptorium/issues we find that many issues can be useful for the https://lab.allmende.io/degrowth/scriptorium/milestones/15 milestone. Moving some of them in there, or closing, would also allow us to close legacy milestones on https://lab.allmende.io/degrowth/scriptorium/milestones and focus on the current ones.Long-term stability of the conference platformhttps://lab.allmende.io/degrowth/scriptorium/-/issues/217There is no release process2019-12-05T19:54:23Zjon ryala@allmende.ioThere is no release processCurrently patches are developed on feature branches and then merged into deployment. From there they are pushed to production.
Unfortunately we missed #216 and as such have no versioning and release cycle at hands, which would allow to ...Currently patches are developed on feature branches and then merged into deployment. From there they are pushed to production.
Unfortunately we missed #216 and as such have no versioning and release cycle at hands, which would allow to identify spikes in development much more easier in retrospect.Long-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/210Admins can see more buttons in Reviewable Sessions than actions that are avai...2018-03-22T23:04:27Zjon ryala@allmende.ioAdmins can see more buttons in Reviewable Sessions than actions that are availableComing from #203, for example as an admin listing the Reviewable Sessions on https://scriptum.apps.ecobytes.net/en/malmo2018/cfp/events/reviewable, I am presented not only with workable buttons, i.e. Reserve for Review, but also with the...Coming from #203, for example as an admin listing the Reviewable Sessions on https://scriptum.apps.ecobytes.net/en/malmo2018/cfp/events/reviewable, I am presented not only with workable buttons, i.e. Reserve for Review, but also with the others. Yet these only work *after* a submission has been reserved by oneself.
We propose not to work with an admin user on the platform for day to day use, but rather use a less priviledged `crew` user, also for verification of the authentication and permissions scheme.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/166Maybe deploy a halfnarp for fine-tuning the schedule?2018-07-05T12:40:26ZPonder StibbonsMaybe deploy a halfnarp for fine-tuning the schedule?https://github.com/tomster/halfnarp is great and integrates with frab. It allows participants to say what in the schedule they are interested in. Like this, the organizing team receives feedback on how to best schedule the conference to ...https://github.com/tomster/halfnarp is great and integrates with frab. It allows participants to say what in the schedule they are interested in. Like this, the organizing team receives feedback on how to best schedule the conference to fit everyones needs.
It would be great if we could offer this to the budapest team.Long-term stability of the conference platformjon ryala@allmende.iojon ryala@allmende.io