This is an automated email from the ASF dual-hosted git repository.
paulk pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new b4a320f no hyphen in mailing list
b4a320f is described below
commit b4a320f24204f853eb0015e33424f7bf32c3ced5
Author: Mattias Reichel <[email protected]>
AuthorDate: Tue Oct 28 14:44:48 2025 +0100
no hyphen in mailing list
---
site/src/site/includes/support-navbar.groovy | 2 +-
site/src/site/pages/contribute.groovy | 8 ++++----
site/src/site/pages/mailing-lists.groovy | 4 ++--
site/src/site/pages/reporting-issues.groovy | 2 +-
site/src/site/pages/support.groovy | 2 +-
site/src/site/sitemap-dev.groovy | 2 +-
site/src/site/sitemap-user.groovy | 6 +++---
site/src/site/wiki/GEP-1.adoc | 6 +++---
site/src/site/wiki/GEP-10.adoc | 2 +-
site/src/site/wiki/GEP-11.adoc | 2 +-
site/src/site/wiki/GEP-6.adoc | 2 +-
site/src/site/wiki/GEP-7.adoc | 2 +-
site/src/site/wiki/GEP-8.adoc | 2 +-
13 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/site/src/site/includes/support-navbar.groovy
b/site/src/site/includes/support-navbar.groovy
index e6c2456..ed4f144 100644
--- a/site/src/site/includes/support-navbar.groovy
+++ b/site/src/site/includes/support-navbar.groovy
@@ -4,7 +4,7 @@ ul(class: 'nav-sidebar') {
'support': 'Support',
'https://groovy.apache.org/index': 'Contribute',
'reporting-issues': 'Reporting issues',
- 'mailing-lists': 'Mailing-lists',
+ 'mailing-lists': 'Mailing lists',
'events': 'Events',
'usergroups': 'User groups',
'thanks': 'Thanks'
diff --git a/site/src/site/pages/contribute.groovy
b/site/src/site/pages/contribute.groovy
index 0beef25..2e892e7 100644
--- a/site/src/site/pages/contribute.groovy
+++ b/site/src/site/pages/contribute.groovy
@@ -20,7 +20,7 @@ layout 'layouts/main.groovy', true,
ul {
li {
yield 'helping other users or
discussing future language directions on the '
- a(href:
'https://groovy-lang.org/mailing-lists.html', 'mailing-lists')
+ a(href:
'https://groovy-lang.org/mailing-lists.html', 'mailing lists')
}
li {
yield 'contribute to discussions on '
@@ -58,12 +58,12 @@ layout 'layouts/main.groovy', true,
}
hr(class: 'divider')
- h2 'Discussing on the mailing-lists and forums'
+ h2 'Discussing on the mailing lists and forums'
p {
yield '''
If you encounter a problem, want to
discuss a new feature,
share interesting findings, and more,
then the '''
- a(href:
'https://groovy-lang.org/mailing-lists.html', 'mailing-lists')
+ a(href:
'https://groovy-lang.org/mailing-lists.html', 'mailing lists')
yield '''
are the place to go to start a
conversation with the Groovy developers
and other Groovy users. Discussions on
the mailing list are archived.
@@ -166,7 +166,7 @@ layout 'layouts/main.groovy', true,
yield '''
of possible easy contributions that
could get you started on your journey
to become a Groovy committer. Just
raise your hand on the Groovy developer '''
- a(href:
'https://groovy-lang.org/mailing-lists.html', 'mailing-list')
+ a(href:
'https://groovy-lang.org/mailing-lists.html', 'mailing list')
yield ''' to tell us about your desire to
work on that ticket.'''
}
p '''
diff --git a/site/src/site/pages/mailing-lists.groovy
b/site/src/site/pages/mailing-lists.groovy
index dede574..d4d3499 100644
--- a/site/src/site/pages/mailing-lists.groovy
+++ b/site/src/site/pages/mailing-lists.groovy
@@ -1,5 +1,5 @@
layout 'layouts/main.groovy', true,
- pageTitle: 'The Apache Groovy programming language - Mailing-lists',
+ pageTitle: 'The Apache Groovy programming language - Mailing lists',
mainContent: contents {
div(id: 'content', class: 'page-1') {
div(class: 'row') {
@@ -12,7 +12,7 @@ layout 'layouts/main.groovy', true,
include template:
'includes/contribute-button.groovy'
h1 {
i(class: 'fa-classic fa-regular fa-envelope')
{}
- yield ' Mailing-lists'
+ yield ' Mailing lists'
}
p '''The Groovy mailing lists are a great way to
interact with the Groovy developers and Groovy users.'''
hr(class: 'divider')
diff --git a/site/src/site/pages/reporting-issues.groovy
b/site/src/site/pages/reporting-issues.groovy
index 539995a..32bcd9f 100644
--- a/site/src/site/pages/reporting-issues.groovy
+++ b/site/src/site/pages/reporting-issues.groovy
@@ -36,7 +36,7 @@ layout 'layouts/main.groovy', true,
}
li {
yield "You'll frequently wish to
discuss your issue first on one of the "
- a(href: 'mailing-lists.html',
'mailing-lists')
+ a(href: 'mailing-lists.html', 'mailing
lists')
yield '''
or in one of the forums to make sure
what you believe is a bug isn't really
a feature or to gather support and
ideas for your feature enhancement request.
diff --git a/site/src/site/pages/support.groovy
b/site/src/site/pages/support.groovy
index 19a6768..060ff09 100644
--- a/site/src/site/pages/support.groovy
+++ b/site/src/site/pages/support.groovy
@@ -17,7 +17,7 @@ layout 'layouts/main.groovy', true,
article {
p 'There are numerous ways to get help with
Groovy™: '
ul {
- li "discuss language usage or direction
with other Groovy users and developers through the ${$a(href:
'mailing-lists.html', 'mailing-lists')} - this is the place for all official
discussions"
+ li "discuss language usage or direction
with other Groovy users and developers through the ${$a(href:
'mailing-lists.html', 'mailing lists')} - this is the place for all official
discussions"
li "discuss matters on ${$a(href:
'https://www.groovycommunity.com/', 'Slack')}; it's run by Groovy enthusiasts
in the community for casual conversations and Q&A"
li "ask a question on ${$a(href:
'https://stackoverflow.com/questions/tagged/groovy', 'Stack Overflow')}; these
are answered by Groovy enthusiasts in the community"
li "find known issues (or create new ones)
in our ${$a(href: 'reporting-issues.html', 'bug tracker')}"
diff --git a/site/src/site/sitemap-dev.groovy b/site/src/site/sitemap-dev.groovy
index c007431..977bc01 100644
--- a/site/src/site/sitemap-dev.groovy
+++ b/site/src/site/sitemap-dev.groovy
@@ -45,7 +45,7 @@ menu {
}
group('Socialize') {
- item 'Discuss on the mailing-list',
"${userSiteBase}mailing-lists.html", 'fa-classic fa-regular
fa-envelope'
+ item 'Discuss on the mailing list',
"${userSiteBase}mailing-lists.html", 'fa-classic fa-regular
fa-envelope'
item 'Groovy on X', 'https://x.com/ApacheGroovy',
'fa-brands fa-x-twitter'
item 'Groovy on Bluesky',
'https://bsky.app/profile/groovy.apache.org', 'fa-brands fa-bluesky'
item 'Groovy on Mastodon',
'https://fosstodon.org/@ApacheGroovy', 'fa-brands fa-mastodon'
diff --git a/site/src/site/sitemap-user.groovy
b/site/src/site/sitemap-user.groovy
index 97cf6ea..c7d6824 100644
--- a/site/src/site/sitemap-user.groovy
+++ b/site/src/site/sitemap-user.groovy
@@ -43,14 +43,14 @@ menu {
}
group('Socialize') {
- item 'Discuss on the mailing-list', "mailing-lists.html",
'fa-classic fa-regular fa-envelope'
+ item 'Discuss on the mailing list', 'mailing-lists.html',
'fa-classic fa-regular fa-envelope'
item 'Groovy on X', 'https://x.com/ApacheGroovy',
'fa-brands fa-x-twitter'
item 'Groovy on Bluesky',
'https://bsky.app/profile/groovy.apache.org', 'fa-brands fa-bluesky'
item 'Groovy on Mastodon',
'https://fosstodon.org/@ApacheGroovy', 'fa-brands fa-mastodon'
item 'Groovy on LinkedIn',
'https://www.linkedin.com/company/106402668/admin/dashboard/', 'fa-brands
fa-linkedin'
- item 'Events and conferences', "events.html",
'fa-classic fa-solid fa-calendar-days'
+ item 'Events and conferences', 'events.html',
'fa-classic fa-solid fa-calendar-days'
item 'Source code on GitHub',
'https://github.com/apache/groovy', 'fa-brands fa-github'
- item 'Report issues in Jira', "reporting-issues.html",
'fa-classic fa-solid fa-bug'
+ item 'Report issues in Jira', 'reporting-issues.html',
'fa-classic fa-solid fa-bug'
item 'Stack Overflow questions',
'http://stackoverflow.com/questions/tagged/groovy', 'fa-brands
fa-stack-overflow'
item 'Slack Community', 'http://www.groovycommunity.com/',
'fa-brands fa-slack'
}
diff --git a/site/src/site/wiki/GEP-1.adoc b/site/src/site/wiki/GEP-1.adoc
index d2f132a..f634666 100644
--- a/site/src/site/wiki/GEP-1.adoc
+++ b/site/src/site/wiki/GEP-1.adoc
@@ -26,7 +26,7 @@ The concept of the GEP was freely inspired from Python's
http://www.python.org/d
== Rationale: Why a GEP?
-For non-trivial, complex or strategic features, discussions on mailing-lists
are difficult to lead and follow, and often
+For non-trivial, complex or strategic features, discussions on mailing lists
are difficult to lead and follow, and often
don't help reach a consensus. Writing a proper document explaining the design
and implications of said feature allows both
the originator of the idea and the community at large to have a chance to
provide interesting and useful feedback and
helps better understanding the rationale, the design decisions, the impact of
the proposal.
@@ -68,7 +68,7 @@ Final:: when the GEP has been integrated into a released
version of Groovy and h
Beyond all these metadata, as appropriate, a GEP should also:
-* give pointers to existing mailing-list discussions (through Nabble, Markmail
or Ponymail)
+* give pointers to existing mailing list discussions (through Nabble, Markmail
or Ponymail)
* list existing papers or documentations related to this feature that provides
additional material for understanding the concepts or implementation
difficulties
* provide samples showing how the feature should be used and how idiomatic
Groovy the solution is
@@ -76,7 +76,7 @@ Beyond all these metadata, as appropriate, a GEP should also:
The general workflow of a Groovy Enhancement Proposal is as follows:
-The inception of a GEP generally stems from a discussion on the Groovy
mailing-lists about a new feature or change
+The inception of a GEP generally stems from a discussion on the Groovy mailing
lists about a new feature or change
when the Groovy Despot and the development team deem necessary to properly
document and articulate this new idea,
for further discussion and analysis. Generally, simple bug fixes and minor
enhancements don't require a full-blown GEP.
A GEP is started solely with the agreement of the Groovy PMC.
diff --git a/site/src/site/wiki/GEP-10.adoc b/site/src/site/wiki/GEP-10.adoc
index c508cba..cd3a6ae 100644
--- a/site/src/site/wiki/GEP-10.adoc
+++ b/site/src/site/wiki/GEP-10.adoc
@@ -245,7 +245,7 @@ def template() { new MarkupBuilder().html { p('Hello') } }
* http://blackdragsview.blogspot.com/2011/10/flow-sensitive-typing.html[Flow
Sensitive Typing?]
*
https://web.archive.org/web/20150508040745/http://www.jroller.com/melix/entry/groovy_static_type_checker_status[Groovy
static type checker: status update] (web archive)
-=== Mailing-list discussions
+=== Mailing list discussions
* https://marc.info/?l=groovy-dev&m=132095119732500&w=2[groovy-dev: Static
compilation for Groovy]: +
An interesting discussion where dynamic lovers explain why they do not want
static compilation
diff --git a/site/src/site/wiki/GEP-11.adoc b/site/src/site/wiki/GEP-11.adoc
index 6f5d677..8704970 100644
--- a/site/src/site/wiki/GEP-11.adoc
+++ b/site/src/site/wiki/GEP-11.adoc
@@ -255,7 +255,7 @@ Differences to groovy.mop.internal.DefaultMetaProperty:
*
https://web.archive.org/web/20150508123746/http://docs.codehaus.org/display/GroovyJSR/GEP+11+-+Groovy+3+semantics+and+new+MOP[GEP-11:
Groovy 3 semantics and new MOP] (web archive link)
-=== Mailing-list discussions
+=== Mailing list discussions
* https://marc.info/?l=groovy-user&m=134070969008201&w=2[groovy-user: Groovy 3]
diff --git a/site/src/site/wiki/GEP-6.adoc b/site/src/site/wiki/GEP-6.adoc
index d7658f5..e6359b1 100644
--- a/site/src/site/wiki/GEP-6.adoc
+++ b/site/src/site/wiki/GEP-6.adoc
@@ -72,7 +72,7 @@ I guess now is a good time to also look at that option.
== References and useful links
-=== Mailing-list discussions
+=== Mailing list discussions
* https://marc.info/?l=groovy-dev&m=128540553001110&w=2[groovy-dev: OpenJDK 7
Groovy Build and NIO2 support]
* https://docs.oracle.com/javase/8/docs/technotes/guides/io/index.html[Java
I/O, NIO and NIO.2]
diff --git a/site/src/site/wiki/GEP-7.adoc b/site/src/site/wiki/GEP-7.adoc
index b84e047..3deb6c1 100644
--- a/site/src/site/wiki/GEP-7.adoc
+++ b/site/src/site/wiki/GEP-7.adoc
@@ -154,7 +154,7 @@ JSON Spec and Java implementations
* http://tools.ietf.org/html/rfc4627[RFC-4627]
* http://json-lib.sourceforge.net/[json-lib]
-=== Mailing-list discussions
+=== Mailing list discussions
* https://marc.info/?l=groovy-dev&m=129623197505984&w=2[groovy-dev: Built-in
JSON support in 1.8]
diff --git a/site/src/site/wiki/GEP-8.adoc b/site/src/site/wiki/GEP-8.adoc
index 1dc82f9..32190c1 100644
--- a/site/src/site/wiki/GEP-8.adoc
+++ b/site/src/site/wiki/GEP-8.adoc
@@ -284,7 +284,7 @@ The proposed behaviour is therefore to align the instanceof
case with multicatch
* http://blackdragsview.blogspot.com/2011/10/flow-sensitive-typing.html[Flow
Sensitive Typing?]
*
https://web.archive.org/web/20150508040745/http://www.jroller.com/melix/entry/groovy_static_type_checker_status[Groovy
static type checker: status update] (web archive)
-=== Mailing-list discussions
+=== Mailing list discussions
* https://marc.info/?l=groovy-user&m=131805623302039&w=2[groovy-user: [grumpy
mode\] What to do on assignment?] Discussion about the expected behaviour when
STC detects a potential error on assignment (for example, possible loss of
precision on implicit number casts)
