[REVIEW]: ur-scape: harnessing data for stakeholder participation in city-making processes #4664

editorialbot · 2022-08-10T05:18:37Z

Submitting author: @luyuhao0326 (Yuhao Lu)
Repository: https://github.com/UrbanRuralSystems/ur-scape
Branch with paper.md (empty if default branch): paper
Version: v0.9.96
Editor: @hugoledoux
Reviewers: @winstonyym, @cforgaci
Archive: 10.3929/ethz-b-000578490

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/a26d6189208eb13b4f406922ee875891"><img src="https://joss.theoj.org/papers/a26d6189208eb13b4f406922ee875891/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/a26d6189208eb13b4f406922ee875891/status.svg)](https://joss.theoj.org/papers/a26d6189208eb13b4f406922ee875891)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@winstonyym & @cforgaci, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @hugoledoux know.

✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨

Checklists

📝 Checklist for @winstonyym

📝 Checklist for @cforgaci

The text was updated successfully, but these errors were encountered:

editorialbot · 2022-08-10T05:18:39Z

Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

editorialbot · 2022-08-10T05:18:45Z

Software report:

github.com/AlDanial/cloc v 1.88  T=1.47 s (513.4 files/s, 201844.9 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Unity-Prefab                   207             24              0         154338
C#                             502          17826          23491          88823
Python                           5            575            501           5095
Qt                               1              0              0           1839
HLSL                            22            349            233           1775
JSON                             3              0              0            363
TeX                              1             32              0            173
Markdown                         4             80              0            140
Visual Basic                     1             28             12            103
JavaScript                       1             15              1             71
XML                              1              0              0             46
Objective-C                      1             10              0             37
YAML                             1              1              4             18
HTML                             1              0              0             17
CSS                              1              0              0              8
DOS Batch                        1              2              0              6
-------------------------------------------------------------------------------
SUM:                           753          18942          24242         252852
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

editorialbot · 2022-08-10T05:18:48Z

Wordcount for paper.md is 1197

editorialbot · 2022-08-10T05:19:29Z

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- None

MISSING DOIs

- 10.1016/j.compenvurbsys.2022.101825 may be a valid DOI for title: Free and open source urbanism: Software for urban planning practice
- 10.1057/udi.2010.25 may be a valid DOI for title: Geographic information system: Old principles with new capabilities
- 10.1038/467912a may be a valid DOI for title: A unified theory of urban living
- 10.3390/ijgi9010049 may be a valid DOI for title: Strengthening Participation Using Interactive Planning Support Systems: A Systematic Review
- 10.1007/978-3-319-18368-8_1 may be a valid DOI for title: Introduction to ‘planning support systems and smart cities’
- 10.1111/1475-5661.00062 may be a valid DOI for title: Spaces of labour control: Comparative perspectives from Southeast Asia
- 10.1038/sdata.2017.1 may be a valid DOI for title: High Resolution Global Gridded Data for Use in Population Studies
- 10.1007/978-3-319-08299-8_21 may be a valid DOI for title: Geodesign in Practice: What about the urban designers
- 10.2104/ag060022 may be a valid DOI for title: Geographical visualization: A participatory planning support tool for imagining landscape futures
- 10.1177/08854122211068526 may be a valid DOI for title: Semantic City Planning Systems (SCPS): A Literature Review
- 10.1080/18626033.2012.749602 may be a valid DOI for title: A framework for geodesign: Changing geography by design
- 10.1038/sdata.2017.4 may be a valid DOI for title: WorldPop, Open Data for Spatial Demography

INVALID DOIs

- None

editorialbot · 2022-08-10T05:20:24Z

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

winstonyym · 2022-08-13T09:05:56Z

cforgaci · 2022-08-15T10:32:33Z

Review checklist for @cforgaci

Conflict of interest

I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

I confirm that I read and will adhere to the JOSS code of conduct.

General checks

Repository: Is the source code for this software available at the https://github.com/UrbanRuralSystems/ur-scape?
License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
Contribution and authorship: Has the submitting author (@luyuhao0326) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines

Functionality

Installation: Does installation proceed as outlined in the documentation?
Functionality: Have the functional claims of the software been confirmed?
Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
State of the field: Do the authors describe how this software compares to other commonly-used packages?
Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

winstonyym · 2022-09-09T09:23:59Z

I have completed a first pass of the software and tested the major functionalities. Overall, ur-scape is a beautifully designed software and has clear pragmatic implications for urban planning. It is easy to use and quite aesthetically pleasing. The focus on rapid urbanisation issues in Southeast Asia is indeed a critical and under-studied area. This is especially important given that more than 50% of urbanisation will happen in Asia over the next decade. Software would go a long way to helping planners and local decision makers in these cities. I have raised some minor issues for the authors to consider.

winstonyym · 2022-09-30T04:27:18Z

I have completed my final pass of ur-scape and expanding testing of the main package functionalities. The authors have kindly addressed the raised issues and we have resolved them successfully. The package works really well, use cases are interesting as well. It was quite an amazing user experience and ur-scape will definitely benefit many city planners in Southeast Asia.

luyuhao0326 · 2022-09-30T04:39:35Z

Thank you @winstonyym for pointing out these overlooked issues of ur-scape and working with us during the review process. Much appreciated from the ur-scape team 🙏

luyuhao0326 · 2022-10-03T02:49:38Z

Dear editor(s) @editorialbot @hugoledoux: the authors have addressed the comments from @winstonyym. Please advise our next step moving forward :)

hugoledoux · 2022-10-03T07:23:02Z

@luyuhao0326 I have seen yes.

Now we need to wait for @cforgaci feedback, he promised me to do it this week.

cforgaci · 2022-10-05T20:44:16Z

I have concluded my first review in which I tested the functionalities of ur-scape and examined the documentation. The software is a beautifully designed data visualization and analysis tool with a very accessible interface and considerable impact demonstrated with specific use cases. It would be great if the excellent video material and training data mentioned in UrbanRuralSystems/ur-scape#9 would be made more accessible in the documentation. I raised a couple of minor issues that should be easy to resolve.

cforgaci · 2022-10-06T09:37:48Z

@hugoledoux, please consider my review concluded. @luyuhao0326, thank you for resolving the issues promptly and in full. ur-scape is clearly relevant, versatile, and impactful for the targeted use cases and geographic context. It was a pleasure reviewing it.

luyuhao0326 · 2022-10-10T08:06:00Z

@cforgaci thank you very much for the feedback -- they are meticulous and very helpful. It was a great experience working on this with you.

hugoledoux · 2022-10-12T14:10:29Z

@editorialbot generate pdf

editorialbot · 2022-10-12T14:11:50Z

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

hugoledoux · 2022-10-12T14:13:30Z

@editorialbot check references

editorialbot · 2022-10-12T14:21:44Z

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- None

MISSING DOIs

- 10.1016/j.compenvurbsys.2022.101825 may be a valid DOI for title: Free and open source urbanism: Software for urban planning practice
- 10.1057/udi.2010.25 may be a valid DOI for title: Geographic information system: Old principles with new capabilities
- 10.1038/467912a may be a valid DOI for title: A unified theory of urban living
- 10.1080/01944360903409493 may be a valid DOI for title: Planning support systems for cities and regions
- 10.3390/ijgi9010049 may be a valid DOI for title: Strengthening Participation Using Interactive Planning Support Systems: A Systematic Review
- 10.1007/978-3-319-18368-8_1 may be a valid DOI for title: Introduction to ‘planning support systems and smart cities’
- 10.1111/1475-5661.00062 may be a valid DOI for title: Spaces of labour control: Comparative perspectives from Southeast Asia
- 10.1038/sdata.2017.1 may be a valid DOI for title: High Resolution Global Gridded Data for Use in Population Studies
- 10.1007/978-3-319-08299-8_21 may be a valid DOI for title: Geodesign in Practice: What about the urban designers
- 10.2104/ag060022 may be a valid DOI for title: Geographical visualization: A participatory planning support tool for imagining landscape futures
- 10.1177/08854122211068526 may be a valid DOI for title: Semantic City Planning Systems (SCPS): A Literature Review
- 10.1080/18626033.2012.749602 may be a valid DOI for title: A framework for geodesign: Changing geography by design
- 10.1038/sdata.2017.4 may be a valid DOI for title: WorldPop, Open Data for Spatial Demography

INVALID DOIs

- None

hugoledoux · 2022-10-12T14:42:58Z

I see that the issues from the reviewers have been fixed (pretty quick!) and that the reviewers are happy.

One thing we need to discuss however, and it's a not-so-nice topic: authorship. I see that only 3 of the six authors have contributed to the code, and JOSS works differently from academic. We don't allow the person funding a project to put their names because of the fact that they have the money. The rules are there: https://joss.readthedocs.io/en/latest/submitting.html?highlight=authorship#authorship You'll see that it's not only git commits that count, but since I can't see the contributions of 3 of the authors (especially the first one), could you please elaborate on their contributions to this package?

Also, I went over your paper and fixed a few things, please accept this PR: UrbanRuralSystems/ur-scape#12

luyuhao0326 · 2022-10-21T01:13:33Z

Thank you @hugoledoux for coordinating our submission. Your question on (co)authorship is critical and I will clarify the roles of each author below.

As you may have noticed, ur-scape is relatively mature with its own UI/UX and a large (growing) body of users (and hopefully more developers with this submission at JOSS). One thing that I can be clear of is that none of the co-authors were included simply because of their "purely financial and organizational" roles in the ur-scape development.

In general, ur-scape is supported by three categories of contributors: designers, scientists, and software engineers. Some of them are coders on Github, and some of them are not. Some of them work astride multiple categories, and some of them have a very focused work task given their expertise. In our submission, we included key contributors from each category to credit their work in the development of ur-scape. In addition, due to the nature and key audience of JOSS, we prioritized contributors with a more software development focus.

The first three authors (Neudecker, Joos, and Zaol-kefli) are key contributors that translated ur-scape from a vision into usable software. Neudecker, in particular, with his expertise in UX/UI and excellent programming skills, not only created a smooth and intuitive user experience but also managed to help us overcome many technical obstacles (e.g. qgis importer).

Lu and Mangal provided support in data management, GIS, and capacity building. ur-scape was never intended to compete with ESRI and QGIS as a mapping software. It however heavily relies on principles and techniques that are crucial to the accuracy and precision of the software. Even though these technicalities are often hidden behind the curtains in ur-scape, we need experts like Lu and Mangal to ensure the science and relevance to the GIS community. Mangal with her background in urban designing also contributes to bringing forth the tool to a range of users varying from experts to non-experts through engagements such as Charrettes and collaborative projects with City governments. She has also developed the capacity-building platform for ur-scape to facilitate an easy uptake of the software. Lu also contributed to the writing, submission, and revision of this submission.

Cairns, the principal investigator of ur-scape, leads the team of software developers and scientists, as well as external designers and professionals to make sure that ur-scape is a piece of software that answers the needs of real-world planners and policy-makers. With his training in architecture, Cairns also pushes ur-scape in its pragmatic and aesthetic capabilities, two important qualities that made stakeholder engagement and idea exchange in ur-scape so effortless and pleasant. Cairns also contributed to the writing of this article.

Ur-scape has also welcomed other developers and contributors in the past, which we have acknowledged on its Github homepage. The authors listed above are the current core team of ur-scape.

arfon · 2022-11-18T16:41:29Z

@editorialbot recommend-accept

editorialbot · 2022-11-18T16:41:31Z

Attempting dry run of processing paper acceptance...

editorialbot · 2022-11-18T16:43:29Z

👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3732, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

editorialbot · 2022-11-18T16:47:45Z

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1177/23998083211016122 is OK
- 10.1016/j.compenvurbsys.2022.101825 is OK
- 10.1057/udi.2010.25 is OK
- 10.1038/467912a is OK
- 10.1080/01944360903409493 is OK
- 10.3390/ijgi9010049 is OK
- 10.1007/978-3-642-37533-0 is OK
- 10.1007/978-3-319-18368-8_1 is OK
- 10.1111/1475-5661.00062 is OK
- 10.1038/sdata.2017.1 is OK
- 10.1007/978-3-319-08299-8_21 is OK
- 10.2104/ag060022 is OK
- 10.1177/08854122211068526 is OK
- 10.1177/0739456X15581606 is OK
- 10.1038/sdata.2017.4 is OK

MISSING DOIs

- None

INVALID DOIs

- None

arfon · 2022-11-18T16:53:19Z

@luyuhao0326 – I found a few typos in your paper. Could you please merge this PR? UrbanRuralSystems/ur-scape#13

arfon · 2022-11-20T08:20:05Z

@editorialbot recommend-accept

editorialbot · 2022-11-20T08:20:06Z

Attempting dry run of processing paper acceptance...

editorialbot · 2022-11-20T08:21:42Z

👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3734, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

editorialbot · 2022-11-20T08:22:16Z

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1177/23998083211016122 is OK
- 10.1016/j.compenvurbsys.2022.101825 is OK
- 10.1057/udi.2010.25 is OK
- 10.1038/467912a is OK
- 10.1080/01944360903409493 is OK
- 10.3390/ijgi9010049 is OK
- 10.1007/978-3-642-37533-0 is OK
- 10.1007/978-3-319-18368-8_1 is OK
- 10.1111/1475-5661.00062 is OK
- 10.1038/sdata.2017.1 is OK
- 10.1007/978-3-319-08299-8_21 is OK
- 10.2104/ag060022 is OK
- 10.1177/08854122211068526 is OK
- 10.1177/0739456X15581606 is OK
- 10.1038/sdata.2017.4 is OK

MISSING DOIs

- None

INVALID DOIs

- None

arfon · 2022-11-20T18:49:53Z

@luyuhao0326 – apologies but I have one more fix. The references aren't rendering properly and this PR should fix it: UrbanRuralSystems/ur-scape#14

luyuhao0326 · 2022-11-20T23:53:29Z

@arfon PR merged! And thanks for checking this for us. I should have done this myself first. Overall, this has been a very enjoyable and productive process with JOSS. Look forward to engaging with you, @hugoledoux, and other editors in the coming years.

arfon · 2022-11-21T10:05:46Z

@editorialbot recommend-accept

editorialbot · 2022-11-21T10:05:48Z

Attempting dry run of processing paper acceptance...

editorialbot · 2022-11-21T10:07:34Z

👋 @openjournals/sbcs-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#3737, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

editorialbot · 2022-11-21T10:08:41Z

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1177/23998083211016122 is OK
- 10.1016/j.compenvurbsys.2022.101825 is OK
- 10.1057/udi.2010.25 is OK
- 10.1038/467912a is OK
- 10.1080/01944360903409493 is OK
- 10.3390/ijgi9010049 is OK
- 10.1007/978-3-642-37533-0 is OK
- 10.1007/978-3-319-18368-8_1 is OK
- 10.1111/1475-5661.00062 is OK
- 10.1038/sdata.2017.1 is OK
- 10.1007/978-3-319-08299-8_21 is OK
- 10.2104/ag060022 is OK
- 10.1177/08854122211068526 is OK
- 10.1177/0739456X15581606 is OK
- 10.1038/sdata.2017.4 is OK

MISSING DOIs

- None

INVALID DOIs

- None

arfon · 2022-11-21T10:11:53Z

@editorialbot accept

editorialbot · 2022-11-21T10:11:55Z

Doing it live! Attempting automated processing of paper acceptance...

editorialbot · 2022-11-21T10:14:35Z

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

editorialbot · 2022-11-21T10:14:36Z

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.04664 joss-papers#3739
Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.04664
If everything looks good, then close this review issue.
Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

arfon · 2022-11-21T10:18:56Z

@winstonyym, @cforgaci – many thanks for your reviews here and to @hugoledoux for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨

@luyuhao0326 – your paper is now accepted and published in JOSS ⚡🚀💥

editorialbot · 2022-11-21T10:18:58Z

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.04664/status.svg)](https://doi.org/10.21105/joss.04664)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04664">
  <img src="https://joss.theoj.org/papers/10.21105/joss.04664/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04664/status.svg
   :target: https://doi.org/10.21105/joss.04664

This is how it will look in your documentation:

We need your help!

The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:

Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://joss.theoj.org/reviewer-signup.html
Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss

editorialbot added C# HLSL review ShaderLab labels Aug 10, 2022

editorialbot assigned hugoledoux Aug 10, 2022

editorialbot mentioned this issue Aug 10, 2022

[PRE REVIEW]: ur-scape: harnessing data for stakeholder participation in city-making processes #4573

Closed

This was referenced Sep 9, 2022

JOSS Review – Software paper UrbanRuralSystems/ur-scape#8

Closed

JOSS Review - Functionality UrbanRuralSystems/ur-scape#9

Closed

editorialbot added the Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences label Sep 10, 2022

editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Nov 18, 2022

editorialbot added accepted published Papers published in JOSS labels Nov 21, 2022

arfon closed this as completed Nov 21, 2022

editorialbot mentioned this issue Oct 1, 2023

[PRE REVIEW]: WPSS, a web panel sample service #5733

Closed

editorialbot mentioned this issue Nov 1, 2023

[PRE REVIEW]: Pysewer: A Python Library for Sewer Network Generation in Data Scarce Regions #6006

Closed

editorialbot mentioned this issue Jan 6, 2024

[PRE REVIEW]: seesus: a social, environmental, and economic sustainability classifier for Python #6051

Closed

editorialbot mentioned this issue Jun 24, 2024

[PRE REVIEW]: Advanced Multi-Surface Navigation for Unmanned Ground Vehicles (UGVs) Using 4D Path Planning Techniques (ugv_nav4d) #6911

Closed

editorialbot mentioned this issue Sep 22, 2024

[PRE REVIEW]: Flood Resilience Digital Twin: A system to enable flood risk analysis and prediction #7266

Open

[REVIEW]: ur-scape: harnessing data for stakeholder participation in city-making processes #4664

[REVIEW]: ur-scape: harnessing data for stakeholder participation in city-making processes #4664

Comments

editorialbot commented Aug 10, 2022 • edited Loading

Status

Reviewer instructions & questions

Checklists

editorialbot commented Aug 10, 2022

editorialbot commented Aug 10, 2022

editorialbot commented Aug 10, 2022

editorialbot commented Aug 10, 2022

editorialbot commented Aug 10, 2022

winstonyym commented Aug 13, 2022 • edited Loading

Review checklist for @winstonyym

Conflict of interest

Code of Conduct

General checks

Functionality

Documentation

Software paper

cforgaci commented Aug 15, 2022 • edited Loading

Review checklist for @cforgaci

Conflict of interest

Code of Conduct

General checks

Functionality

Documentation

Software paper

winstonyym commented Sep 9, 2022

winstonyym commented Sep 30, 2022 • edited Loading

luyuhao0326 commented Sep 30, 2022

luyuhao0326 commented Oct 3, 2022

hugoledoux commented Oct 3, 2022

cforgaci commented Oct 5, 2022

cforgaci commented Oct 6, 2022

luyuhao0326 commented Oct 10, 2022

hugoledoux commented Oct 12, 2022

editorialbot commented Oct 12, 2022

hugoledoux commented Oct 12, 2022

editorialbot commented Oct 12, 2022

hugoledoux commented Oct 12, 2022 • edited Loading

luyuhao0326 commented Oct 21, 2022 • edited Loading

arfon commented Nov 18, 2022

editorialbot commented Nov 18, 2022

editorialbot commented Nov 18, 2022

editorialbot commented Nov 18, 2022

arfon commented Nov 18, 2022

arfon commented Nov 20, 2022

editorialbot commented Nov 20, 2022

editorialbot commented Nov 20, 2022

editorialbot commented Nov 20, 2022

arfon commented Nov 20, 2022

luyuhao0326 commented Nov 20, 2022

arfon commented Nov 21, 2022

editorialbot commented Nov 21, 2022

editorialbot commented Nov 21, 2022

editorialbot commented Nov 21, 2022

arfon commented Nov 21, 2022

editorialbot commented Nov 21, 2022

editorialbot commented Nov 21, 2022

editorialbot commented Nov 21, 2022

arfon commented Nov 21, 2022

editorialbot commented Nov 21, 2022

editorialbot commented Aug 10, 2022 •

edited

Loading

winstonyym commented Aug 13, 2022 •

edited

Loading

cforgaci commented Aug 15, 2022 •

edited

Loading

winstonyym commented Sep 30, 2022 •

edited

Loading

hugoledoux commented Oct 12, 2022 •

edited

Loading

luyuhao0326 commented Oct 21, 2022 •

edited

Loading