Additionally, leveraging PlantUML to visualize the dependencies and
interactions between the modules in Baremaps could be a great way to
provide clarity.
For example, we could draw like JUnit 5:
https://github.com/junit-team/junit5/blob/main/documentation/src/plantuml/component-diagram.puml
I’d a
Hi Yongjun,
Thank you for sharing these suggestions from the perspective of a new
contributor.
Could you describe the specific changes you’d like to make?
We truly appreciate your contributions:)
On Sun, Jan 26, 2025 at 12:20 PM 홍용준 wrote:
> Dear Baremaps Team,
> When I first explore an open-so
I’ be interested in using template to see if it helps gathering more
information. However, we should keep in mind that the nature of the issues may
vary greatly in Apache Baremaps. For instance, we may have styling issues in
the basemap (in which case we need coordinates, a screenshot and browse
Of course!
Since I have contributed significantly to the JUnit5 framework, I am most
familiar with that project. That’s why I often refer to it in my examples.
1. Issue Labeling
In JUnit5, issues are automatically labeled based on their type when they
are created.
For example, a feature request
