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/254Requirements gathering of Manchester conference2023-11-30T19:02:50ZGualterRequirements gathering of Manchester conferenceFrom the involvement into the [long-term stability of the conference platform](https://lab.allmende.io/degrowth/scriptorium/-/milestones/15) we learn to take care of a [transparent and accountable workflow](https://lab.allmende.io/degrow...From the involvement into the [long-term stability of the conference platform](https://lab.allmende.io/degrowth/scriptorium/-/milestones/15) we learn to take care of a [transparent and accountable workflow](https://lab.allmende.io/degrowth/scriptorium/issues/253) and to [document usage phases of the conference platform](https://lab.allmende.io/degrowth/scriptorium/issues/252) in order to increase accessibility of the process and its product.
As there are ongoing conversations with the organisers of the upcoming conference in Manchester, we are enquiring about their requirements and constraints with regards to their conference. This is mainly about understanding where to fit into their schedule.
- When is the conferences happening?
- When do they intend to open and close the call for contributions?
- When will peer review and scheduling of sessions take place?
- When do they want to open registration?
Each of these phases brings different usage patterns for visitors and curators of the conference platform. The development process itself also brings its own dynamics. Both need to be transparently communicated to the partner.
To allow for customisations similar to [the 111 commits of Malmö](https://lab.allmende.io/degrowth/scriptorium/compare/c7d445a02ddb6dccb0f572c9fc998ea20fba4e27...0ee69a4d877a7ef50db1069bdeb1b724c58606c5), we would like to know
- Which kinds of submissions / tracks / sessions / events are anticipated?
Then these can be implemented in the existing codebase, and the conference is ready to go.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/251Some sessions/availabilities cannot be edited, throw error2018-08-21T14:22:35ZGualterSome sessions/availabilities cannot be edited, throw errorAfter scrutiny on several sessions and why this happens, this seems now to be filtered down to https://scriptum.degrowth.net/en/malmo2018/events/542 and the participation of person 1067.
* we cannot set the availability of this person ...After scrutiny on several sessions and why this happens, this seems now to be filtered down to https://scriptum.degrowth.net/en/malmo2018/events/542 and the participation of person 1067.
* we cannot set the availability of this person for that day (but we managed to set his availability for all other days, then no error is thrown)
* we cannot change the time slot or rooms of this or any other conflicting event
* we cannot set the availability of any person associated with this or any other conflicting event
While opening the mentioned event, the following error is thrown:
```
D, [2018-08-16T22:56:21.644216 #8] DEBUG -- : Person Load (0.3ms) SELECT "people".* FROM "people" WHERE "people"."user_id" = $1 LIMIT 1 [["user_id", 5]]
I, [2018-08-16T22:56:21.645205 #8] INFO -- : Rendered shared/_flash.html.haml (0.1ms)
I, [2018-08-16T22:56:21.645570 #8] INFO -- : Completed 200 OK in 53ms (Views: 38.8ms | ActiveRecord: 7.6ms)
I, [2018-08-16T22:56:21.898376 #8] INFO -- : Started GET "/assets/images/ui-bg_glass_75_ffffff_1x400.png" for 46.81.159.140 at 2018-08-16 22:56:21 +0000
F, [2018-08-16T22:56:21.900597 #8] FATAL -- :
ActionController::RoutingError (No route matches [GET] "/assets/images/ui-bg_glass_75_ffffff_1x400.png"):
actionpack (4.2.4) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
actionpack (4.2.4) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
railties (4.2.4) lib/rails/rack/logger.rb:38:in `call_app'
railties (4.2.4) lib/rails/rack/logger.rb:20:in `block in call'
activesupport (4.2.4) lib/active_support/tagged_logging.rb:68:in `block in tagged'
activesupport (4.2.4) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (4.2.4) lib/active_support/tagged_logging.rb:68:in `tagged'
railties (4.2.4) lib/rails/rack/logger.rb:20:in `call'
request_store (1.2.0) lib/request_store/middleware.rb:8:in `call'
actionpack (4.2.4) lib/action_dispatch/middleware/request_id.rb:21:in `call'
rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
rack (1.6.4) lib/rack/runtime.rb:18:in `call'
activesupport (4.2.4) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (4.2.4) lib/action_dispatch/middleware/static.rb:116:in `call'
rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
railties (4.2.4) lib/rails/engine.rb:518:in `call'
railties (4.2.4) lib/rails/application.rb:165:in `call'
rack (1.6.4) lib/rack/content_length.rb:15:in `call'
puma (2.14.0) lib/puma/server.rb:541:in `handle_request'
puma (2.14.0) lib/puma/server.rb:388:in `process_client'
puma (2.14.0) lib/puma/server.rb:270:in `block in run'
puma (2.14.0) lib/puma/thread_pool.rb:106:in `call'
puma (2.14.0) lib/puma/thread_pool.rb:106:in `block in spawn_thread'
```
Setting the availability of the mentioned user for day 23 (and similar for any of the related users):
```
D, [2018-08-16T22:57:52.500084 #8] DEBUG -- : Event Load (1.1ms) SELECT DISTINCT "events".* FROM "events" INNER JOIN "event_people" ON "events"."id" = "event_people"."event_id" WHERE "event_people"."person_id" = $1 AND "events"."conference_id" = $2 [["person_id", 1067], ["conference_id", 2]]
D, [2018-08-16T22:57:52.502448 #8] DEBUG -- : Day Load (0.3ms) SELECT "days".* FROM "days" WHERE "days"."id" = $1 ORDER BY "days"."start_date" ASC LIMIT 1 [["id", 9]]
D, [2018-08-16T22:57:52.503966 #8] DEBUG -- : SQL (0.3ms) DELETE FROM "conflicts" WHERE "conflicts"."event_id" = $1 [["event_id", 542]]
D, [2018-08-16T22:57:52.505102 #8] DEBUG -- : SQL (0.4ms) DELETE FROM "conflicts" WHERE "conflicts"."conflicting_event_id" = $1 [["conflicting_event_id", 542]]
D, [2018-08-16T22:57:52.506606 #8] DEBUG -- : Room Load (0.3ms) SELECT "rooms".* FROM "rooms" WHERE "rooms"."id" = $1 ORDER BY "rooms"."rank" ASC LIMIT 1 [["id", 28]]
D, [2018-08-16T22:57:52.509061 #8] DEBUG -- : Event Load (0.7ms) SELECT "events".* FROM "events" WHERE "events"."state" IN ('confirmed', 'unconfirmed', 'paid') AND ("events"."start_time" >= '2018-08-23 12:30:00.000000') AND ("events"."start_time" < '2018-08-23 14:00:00.000000') AND ("events"."id" != $1) AND ("events"."room_id" != $2) [["id", 542], ["room_id", 28]]
D, [2018-08-16T22:57:52.511426 #8] DEBUG -- : Event Load (0.8ms) SELECT "events".* FROM "events" WHERE "events"."state" IN ('confirmed', 'unconfirmed', 'paid') AND "events"."room_id" = $1 AND ("events"."start_time" >= '2018-08-22 22:00:00.000000') AND ("events"."start_time" <= '2018-08-23 21:59:59.999999') AND ("events"."id" != 542) [["room_id", 28]]
D, [2018-08-16T22:57:52.513247 #8] DEBUG -- : Conference Load (0.3ms) SELECT "conferences".* FROM "conferences" WHERE "conferences"."id" = $1 LIMIT 1 [["id", 2]]
D, [2018-08-16T22:57:52.514112 #8] DEBUG -- : CACHE (0.0ms) SELECT "conferences".* FROM "conferences" WHERE "conferences"."id" = $1 LIMIT 1 [["id", 2]]
D, [2018-08-16T22:57:52.514877 #8] DEBUG -- : (0.2ms) ROLLBACK
D, [2018-08-16T22:57:52.516513 #8] DEBUG -- : PaperTrail::Version Load (0.3ms) SELECT "versions".* FROM "versions" WHERE "versions"."item_id" = $1 AND "versions"."item_type" = $2 ORDER BY "versions"."created_at" ASC, "versions"."id" ASC [["item_id", 1067], ["item_type", "Person"]]
I, [2018-08-16T22:57:52.517184 #8] INFO -- : Completed 500 Internal Server Error in 43ms (ActiveRecord: 7.6ms)
F, [2018-08-16T22:57:52.518881 #8] FATAL -- :
NoMethodError (undefined method `*' for nil:NilClass):
app/models/event.rb:196:in `end_time'
app/models/event.rb:362:in `overlap?'
app/models/event.rb:601:in `block in update_event_conflicts'
app/models/event.rb:600:in `update_event_conflicts'
app/models/event.rb:382:in `update_conflicts'
app/models/availability.rb:40:in `block in update_event_conflicts'
app/models/availability.rb:39:in `update_event_conflicts'
app/models/person.rb:226:in `update_attributes_from_slider_form'
app/controllers/availabilities_controller.rb:16:in `update'
```jon ryala@allmende.iojon ryala@allmende.iohttps://lab.allmende.io/degrowth/scriptorium/-/issues/250Problems with scheduling2018-08-21T14:17:28ZViktoriyaProblems with schedulingEmergy accounting as a tool to assess megaprojects, while trying to delete a cancelled submitter Francesco Gonella from https://scriptum.degrowth.net/en/malmo2018/events/785Emergy accounting as a tool to assess megaprojects, while trying to delete a cancelled submitter Francesco Gonella from https://scriptum.degrowth.net/en/malmo2018/events/785https://lab.allmende.io/degrowth/scriptorium/-/issues/249Rooms are missing from public schedule2018-08-21T14:16:07ZGualterRooms are missing from public scheduleMany rooms are missing from the public schedule. This is not a bug, but rather a result of events not being fully confirmed/fulfilling the criteria of the system to be published.
This relates to part of the problems mentioned on #245Many rooms are missing from the public schedule. This is not a bug, but rather a result of events not being fully confirmed/fulfilling the criteria of the system to be published.
This relates to part of the problems mentioned on #245Malmo 2018 IIjon ryala@allmende.iojon ryala@allmende.iohttps://lab.allmende.io/degrowth/scriptorium/-/issues/248PDF export of schedule is not working2018-08-21T14:19:53ZViktoriyaPDF export of schedule is not workinglog in as admin - click at schedule (in the main green tap) - create custom pdf export
- this selection does not represent any schedule while trying to export a pdf of one or of many roomslog in as admin - click at schedule (in the main green tap) - create custom pdf export
- this selection does not represent any schedule while trying to export a pdf of one or of many roomshttps://lab.allmende.io/degrowth/scriptorium/-/issues/247Link to public schedule is not working2018-08-21T14:22:13ZViktoriyaLink to public schedule is not workinglog in as admin - click at schedule (in the main green tap) - view public schedule (upper right corner)
Problems: - The link to the public schedule directs to https://budapest.degrowth.org/schedule/ not the actual schedule
- Cl...log in as admin - click at schedule (in the main green tap) - view public schedule (upper right corner)
Problems: - The link to the public schedule directs to https://budapest.degrowth.org/schedule/ not the actual schedule
- Clicking at the days (21st to 25th) shows error or too few sessions from all of the booked venues and sessionsMalmo 2018 IIGualterGualterhttps://lab.allmende.io/degrowth/scriptorium/-/issues/246Schedule is overlapping2018-08-14T10:12:56ZViktoriyaSchedule is overlapping![schedule_does_not_work](/uploads/03310b9cf72fb8d2543fbbe01d9e4f7f/schedule_does_not_work.png)![schedule_does_not_work](/uploads/03310b9cf72fb8d2543fbbe01d9e4f7f/schedule_does_not_work.png)Malmo 2018 IIhttps://lab.allmende.io/degrowth/scriptorium/-/issues/245Public schedule day view fails when events without time slots and/or speakers...2023-11-30T19:02:17ZViktoriyaPublic schedule day view fails when events without time slots and/or speakers/contributorsSchedule says "We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly." when trying to click on the next day or any other day.
Public schedule does not show everything from the sch...Schedule says "We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly." when trying to click on the next day or any other day.
Public schedule does not show everything from the schedule, the information is really limited: the sessions are missing, time slots missing, venues missingMalmo 2018 IIViktoriyaViktoriyahttps://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/243Unscheduled events are not visible2018-08-09T20:24:29Zjon ryala@allmende.ioUnscheduled events are not visibleRecently we monkey patched the display of unscheduled events in cf476386641330244eecd0905128b5b8c82f99f1, in so #239 can be closed.
Unfortunately this is a code smell that asks for further investigation.Recently we monkey patched the display of unscheduled events in cf476386641330244eecd0905128b5b8c82f99f1, in so #239 can be closed.
Unfortunately this is a code smell that asks for further investigation.Malmo 2018 IIhttps://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.io