Date: Tue, 18 Apr 2023 00:37:06 +0200
From: Jiri Vlasak <jiri.hubacek@gmail.com>
To: risturiz@gusl.org
Cc: ~qeef/damn-project@lists.sr.ht
Subject: Re: Fediverse? ( RSS )
Message-ID: <ZD3KEqR2g0iqtw6R@gmail.com>
References: <9a4c43219d10c883ada08cf7c81194c0@gusl.org>
 <ZBo88u4zQzjKiO2n@gmail.com>
 <f91870f233487a0e26b4f40367a9076a@gusl.org>
 <ZDX0CQj9pZbRcySA@gmail.com>
 <051805d323e8f0088072b9dc051fd45b@gusl.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <051805d323e8f0088072b9dc051fd45b@gusl.org>

> > I guess that link to area is link to manager? It will be solved as
> > soon as the manager is moved to new codebase for web clients. I will
> > prioritize this.
> 
> If i understand right ( sorry if my use case is "noob" point of view
> ), you lock the area -> work -> done -> review ( all this should have
> and specific url bbox? ( coordinates )... The RSS could have that
> link? ... But i would wait for your idea and test it :-)

I think I should clarify/recapitulate the approach of the damn project a
little bit.

You specify _area_ to be mapped in the manager [1]. The RSS feeds [2]
track information about the particular area or all areas.

An _area_ is divided into _squares_ when created, and the state of all
(just created) squares is set to "to map". There are well defined
transitions between square's states [3]; in the diagrams, the arrows
depict locking (arrow leaves the oval) and unlocking (arrow enters the
oval) of the particular square.

Now, I will try to answer this:

> you lock the area -> work -> done -> review ( all this should have and
> specific url bbox? ( coordinates )

- You usually lock a square.

- When "locked" state is explicitely stated, the transitions looks like
  "to map" -> "locked" -> "to review" -> "locked" -> "done", where the
  first "locked" is "working on mapping" and the second "locked" is
  "working on review".

- It is possible to retrieve GeoJSON of any area (not just bounding
  box).

- It is possible to retrieve GPX of any square (not just bounding box).

> But i would wait for your idea and test it :-)

The history of the square's states is available [4], but will be
improved during the "mappy" web client rework. For example, I plan to
include links to 3rd party tools to reworked mappy client, to simplify
monitoring changes of area and/or each square.

> The RSS could have that link?

Yes, the plan is to include the link to the "history of the square's
states" of the (reworked) "mappy" web client into the "squares to
review" RSS feeds.

> > I am still not sure about the notification/monitoring problem. RSS feeds
> > of the damn project are updated every day at 3:33 UTC. It should be
> > possible to convert RSS feed to wide range of notification systems.
> > 
> > > I added 4 RSS url:
> > > 
> > > - changes
> > > - abandoned
> > > - completion status
> > > - squares to review
> > 
> > These are feeds about what happened to the area in the context of the
> > damn project (please, do not confuse these RSS feeds with the feeds
> > about changes to the OpenStreetMap).
> 
>      Yes, when i work on the area i can see commits: ( but only on panel? )
> 
>      4/3/2023, 1:06:18 AM | risturiz: This square is done. (227 done)

"Old" web clients [5], [6] has link to "statistics" for each area. It is
possible to see the history of the square (see the bottom of
"statistics" page), but it is rough and not well accessible.

It is not possible to see the "statistics" page in the panel web client.

> If this could have RSS notifications could be useful ( some teacher
> monitoring students )...

This is the reason for "squares to review" RSS feed, for example of area
7112 [7].

Or you mean to have RSS feed (with history of the states) for each
square? I doubt it is useful -- when you monitor students, you probably
want to know which "squares [are ready] to review".

However, "squares done" RSS feed could be probably useful for the second
round of review?

> So in this case all feeds only update at specific time?

Yes. Locking square (or any other update to the database) does not
trigger any action. All the upkeep is triggered periodically.

> ( oh, btw any chance to have timezone manager? )

Hmm, I am not sure how to do that in RSS feeds. Every date/time in the
damn server is UTC. Every date/time in any web client is (or will be
after rework) in local time. However, I am not sure how to say "display
this time in local time" to RSS reader, if it is even possible.

(The reason for this approach is the date/time is generated
automatically in the database by update action; it is not specified by a
user.)

> I see this way, i don't want to monitor all globe for changesets but
> have some info about people working on my damn project area?...

There is currently some information about mappers in "statistics" page
of "old" clients. See for example "all creators", "all mappers", or
"local mappers" in the bottom of the "statistics" page.

This information will be more accessible in the reworked version of
mappy web client.

> Actually i don't know what would be the best information for RSS
> notification, maybe user/areamessage/urlbbox ( RSS from QA and Neis
> lack for some formatting, but its fine ); if you additionally
> integrate this workflow would be amazing, i didn't think about it.

It depends on the use-case, I believe:

- If you care about the overall quality, you probably subscribe to "new
  areas of the damn-project.org".

- If you care about the area, you probably subscribe to "changes" and
  "abandoned" of particular area (items of these RSS feeds will be
  supplemented with the link to particular area in the (reworked)
  manager web client).

- If you are reviever, you may subscribe to "squares to review" of
  particular area (items of "squares to review" RSS feeds will be
  supplemented with the link to the square in reworked mappy client when
  ready).

BTW, RSS feeds from QA [2] are formatted with HTML and that should be
possible by the specification. I am willing to improve the format.

[1]: https://manager.damn-project.org/
[2]: https://qa.damn-project.org/rss/
[3]: https://damn-project.org/#squares-state-transitions
[4]: https://mappy.damn-project.org/?stats=2443&of=277
[5]: https://client.damn-project.org/
[6]: https://mappy.damn-project.org/
[7]: https://qa.damn-project.org/rss/area-7112-squares-to-review.xml