Hello,

> 1.- What happen with 100% done areas? I have to archive manually? Or some
> cron will do it eventually?

Yes, you need to archive them manually. The best way to do so is to set
the priority of the area to -10, and wait for 90 days. When the area has
the priority -10 and it is not updated for 90 days, it is moved to
read-only finished areas [1].

The frontend for finished areas is planned, but not yet done.

> 2.- It´s possible to make close(changeset/note) configurable? ( like some
> predefined auto option? ) "josm plugin"

> > There is a change in the downloading notes automatically. The JOSM
> > preference
> > 
> > 	damn.download_notes_automatically
> > 
> > is not needed anymore and will be removed in the future. To enable
> > downloading notes automatically, please, update your area in the manager
> > [1]. Particularly, in the instructions sections, use
> > 
> > 	+ add configuration: _download_notes_automatically
> > 
> > You may need to refresh the manager web page with ctrl + shift + R (in
> > Firefox) to see that option.
> 

Hello again,

I have updated the DAMN plugin. Feel free to upgrade to version 0.7.0.

> the DAMN plugin automatically

There is a change in the downloading notes automatically. The JOSM
preference

	damn.download_notes_automatically

is not needed anymore and will be removed in the future. To enable
downloading notes automatically, please, update your area in the manager
[1]. Particularly, in the instructions sections, use

Hi,

> We are using the Damn project to solve notes, which is very helpful.

I am glad the project is useful.

> We want to take a step forward and create a methodology to solve notes
> in real-time. I mean, while people are on the ground, they create
> notes, and armchair volunteers can solve them or ask questions with
> comments about the notes.
> 
> We see the DAMN project could help us with this. Our idea is that when
> one “locks” an area in JOSM, the DAMN plugin automatically and
> periodically downloads the notes in that area.

Dear mappers,

based on the "Policy for finished areas" [1] I have marked the following
areas for archivation:

	Areas abandoned on https://server.damn-project.org since
	2022-07-15T18:57:25.
	In last 90 days:
	- 2359 has only 2 commits
	- 2364 has only 4 commits
	- 2366 has only 0 commits
	Finished.

The parameters used for abandoned areas are still in testing -- I would

Hi and thanks for the report.

> Hi, i'm getting (maybe?) the same error that don't show map background
> on areas "2407", "2408" and "2409"...

I can confirm the same error ("Too many requests"). I did run the
service manually and background images are available.

To avoid similar issues in the future, I will be looking at new areas
closely, checking their status.

> These are Notes areas that work from Josm plugin, any planned option
> to add a button for refresh the area (inside manage area) and bring
> image background?

> I know you are a fan of the plane text that we are using now and that
> you dislike html email. I very much agree with the sentiment.

I do not think it is "sentiment". It is fact. Ask an impaired person
what he or she thinks about HTML emails.

> But, surely it is not the final form of such technologies?

The problem this technology solves is information transfer. Plain text
is "just" encoding.

HTML is used to improve interaction and readability, but not to improve
the encoding.

Hello Andres,

> I have started using DAMN for notathons and we define areas according
> to different criteria that produce circular or non-square polygons.
> However, in many parts of the applications, it refers to “square” to
> the working area. I propose to change it to task, area, or another
> word.

thank you for your feedback, it is greatly appreciated. First, I would
like to present why "square" is used. Then, I am open to the proposals
for the better naming, but there are some requirements.

First, the term "square" is used historically: An _area_ stored in the
"Divide and map. Now." [1] was divided into the rectangular shapes. The

Hello guys,

I would like to make a quick update on BARE standardization. I joined
IETF 114 DISPATCH meeting [1] presenting the BARE draft.

I am not good at presentation (sorry). There was some positive and some
negative feedback. The argument that there are a lot of competing
standards that are not properly standardized, and BARE covering them
all, is not enough.

The conclusion from the meeting is to form small WG to discuss this
topic further. I will continue the work in the mid of September.

The future steps are to write WG charter, form the WG, research this

On Sat, Aug 13, 2022 at 06:55:17AM +0300, ~obk wrote:
> From: Ömer Bahadır Kundak <bahadir@kundak.dev>
> 
> ---
>  index.html | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/index.html b/index.html
> index db2050a..2e175f3 100644
> --- a/index.html
> +++ b/index.html
> @@ -507,10 +507,9 @@
>      <ol>
>        <li>In the accounts tab, right click on your account</li>