scriptorium issueshttps://lab.allmende.io/degrowth/scriptorium/-/issues2020-01-27T14:03:52Zhttps://lab.allmende.io/degrowth/scriptorium/-/issues/261Database can't be seeded2020-01-27T14:03:52ZPonder StibbonsDatabase can't be seededWhile migrations are working again since #199 is fixed, it is still not possible to seed the database. We've previously added mandatory properties to the conference that were not added to `db/seeds.rb`.
It should be possible to use `db/...While migrations are working again since #199 is fixed, it is still not possible to seed the database. We've previously added mandatory properties to the conference that were not added to `db/seeds.rb`.
It should be possible to use `db/seeds.rb` to seed the database to be able to log in.Manchester 2020Ponder StibbonsPonder Stibbonshttps://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/258Development instance2020-01-28T21:38:20Zjon ryala@allmende.ioDevelopment instanceWith the latest advent in `development` activity, we will also need ways to facilitate quick integration into `production`. We can use the `deployment` and `master` branches respectively.
We can replicate the setup from Malmö 2018:
- `...With the latest advent in `development` activity, we will also need ways to facilitate quick integration into `production`. We can use the `deployment` and `master` branches respectively.
We can replicate the setup from Malmö 2018:
- `production` encapsulated in a Compose setup on `panda`
- `development` pushed into a Dokku application holding a recent-enough copy of the live database and assets.
To assure the general availability and velocity of the platform, we can migrate the Compose into our `alpaca` powerhorse.
And the all updated `dokku.ecobytes.net` instance will come in handy as a development sandbox.Manchester 2020https://lab.allmende.io/degrowth/scriptorium/-/issues/257Subcategories and user profiles2019-12-09T16:56:36Zjon ryala@allmende.ioSubcategories and user profilesThe *Assign Review-Subcategories* tab in a user profile (people, account) is broken, presumably because of removing subcategories in the path.
They are also still visible and configurable in https://scriptum.degrowth.net/en/manchester20...The *Assign Review-Subcategories* tab in a user profile (people, account) is broken, presumably because of removing subcategories in the path.
They are also still visible and configurable in https://scriptum.degrowth.net/en/manchester2020/conference/edit_subcategoriesManchester 2020Ponder StibbonsPonder Stibbonshttps://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/255Separate instances per conference2023-11-30T19:02:18ZGualterSeparate instances per conferenceOur fork of the `frab` codebase has evolved last year from the Budapest conference to the Malmö conference. This lead to changes in the models as well as in the views. The general application logic, the controllers, has mostly not been t...Our fork of the `frab` codebase has evolved last year from the Budapest conference to the Malmö conference. This lead to changes in the models as well as in the views. The general application logic, the controllers, has mostly not been touched.
The changes in code lead to errors in the presentation of the Budapest conference. Additional regressions for both Budapest and Malmö can be expected with the integration of further requirements and changes for upcoming conferences, like Manchester and alike.
Following up from this high level perspective, we can already conclude to:
- [x] Redeploy current scriptum.degrowth.net to malmo.degrowth.net
- [x] delete other conferences on malmo.degrowth.net
- [x] test email delivery, e.g. password reset
- [x] Redeploy current scriptum.degrowth.net to budapest.degrowth.net
- [x] delete other conferences
- [x] Bonus: ideally rollback the codebase to a post-conference state
- [x] test email delivery, e.g. password reset
- [ ] Provide a simple landing page on scriptum.degrowth.net to explain the situation
- [ ] Redirect the conference's respective namespaces to their new subdomains to preserve old links
- [ ] Deploy manchester.degrowth.net as an empty conferenc from the adapted state of the application that solves #199, and create a conference example
The subdomains and their naming scheme (`*.scriptum.degrowth.net`, `*.scriptorium.degrowth.net`, `conference`?) can be debated.Manchester 2020jon ryala@allmende.iojon ryala@allmende.iohttps://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/242Session types are unordered throughout the system.2019-02-21T21:56:26Zjon ryala@allmende.ioSession types are unordered throughout the system.In https://lab.allmende.io/degrowth/scriptorium/merge_requests/21#note_7950 I've found that event types are listed in random order, either on
- the statistics view,
- the session filters or
- in the event editor.
Alternatively, we woul...In https://lab.allmende.io/degrowth/scriptorium/merge_requests/21#note_7950 I've found that event types are listed in random order, either on
- the statistics view,
- the session filters or
- in the event editor.
Alternatively, we would want to put event types in the same order in all places everywhere.Malmo 2018 IIjon ryala@allmende.iojon ryala@allmende.iohttps://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/206Sessions overview does not integrate with current workflows2018-10-02T15:55:25Zjon ryala@allmende.ioSessions overview does not integrate with current workflowsThe sessions overview at https://scriptum.apps.ecobytes.net/en/malmo2018/events does still reference subcategories, while it does not show if events have a time slot nor a room assigned, or not.
- [x] Remove the unused column Subcategor...The sessions overview at https://scriptum.apps.ecobytes.net/en/malmo2018/events does still reference subcategories, while it does not show if events have a time slot nor a room assigned, or not.
- [x] Remove the unused column Subcategory
- [ ] Add colums for time slots, start time and roomMalmo 2018 IIjon ryala@allmende.iojon ryala@allmende.iohttps://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/191Availability is not used, but influences sessions shown to public2019-02-21T21:57:42ZGualterAvailability is not used, but influences sessions shown to publicIn order to have a session appear in the public program, the availability of each presenter needs to be set. By default, new accounts have no availability, so they have either to be entered by the user itself or by the organisers.
This ...In order to have a session appear in the public program, the availability of each presenter needs to be set. By default, new accounts have no availability, so they have either to be entered by the user itself or by the organisers.
This process is a burden for the user and error prone when done by the organisers. The result has been that some sessions don't appear in the program, and you can only notice it by comparing both internal and public programs, or by checking if in the internal sessions page no notice is given about missing availability of the presenters.
I suggest we completely disable the availability feature if there is no specific need for it from conference organisers, or make it modular.https://lab.allmende.io/degrowth/scriptorium/-/issues/171Display all 4 IPs in a Timeslot as a single Block in the public schedule.2018-10-03T16:27:05ZPonder StibbonsDisplay all 4 IPs in a Timeslot as a single Block in the public schedule.the public schedule (matrix view by days and rooms) should show in a given room/time slot a single block consisting of all 4 IPs in the slot, with IP title (30 characters max) and names of speakers (author and a paid co-author). clicking...the public schedule (matrix view by days and rooms) should show in a given room/time slot a single block consisting of all 4 IPs in the slot, with IP title (30 characters max) and names of speakers (author and a paid co-author). clicking on the titles and and names should open detailed information about event or all 4 events (whichever is possible).The Public Schedule is BeautifulPonder StibbonsPonder Stibbonshttps://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