[opkg][PATCH 0/1] Migrate mailing list to lists.yoctoproject.org

[Alex Stewart]

Google Groups is an abandoned project by Google, and has not been
actively developed in many years. Hosting the opkg development list here
is becoming progressively more difficult as the platform ages.

It is relatively difficult for contributors to subscribe to the list.
The lists' email exchange servers do not properly honor security
headers. And it is not integrated with any other yocto tooling or the
yocto community lists on lists.yoctoproject.org. Until now!

We have a new opkg mailing list at lists.yoctoproject.org/g/opkg. Please
re-subscribe there, and address all future posts to
<op...@lists.yoctoproject.org>. We're also changing the default thread
tag from [opkg-devel] to just [opkg], which some people were already
using.

Starting next week, I'll restrict posting on the opkg-devel Group. But
the instance will remain online for archival purposes.

https://lists.yoctoproject.org/g/opkg

Alex Stewart (1):
migrate mailing list to lists.yoctoproject.org

README.md | 3 +--
docs/CONTRIBUTING.md | 6 +++---
docs/MAINTAINING.md | 4 ++--
3 files changed, 6 insertions(+), 7 deletions(-)

--
2.40.1

[Alex Stewart]

Google Code/Groups is a legacy product which is not being actively
maintained by Google, and it is becoming progressively more difficult to
maintain the opkg-devel list there.

Instead, move the canonical opkg mailing list for the yocto fork to the
lists.yoctoproject.org site, where it can live with the other
contemporary yocto projects.

Signed-off-by: Alex Stewart <alex.s...@ni.com>
---

README.md | 3 +--
docs/CONTRIBUTING.md | 6 +++---
docs/MAINTAINING.md | 4 ++--
3 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 4da3a66..b0e4fe7 100644
--- a/README.md
+++ b/README.md
@@ -7,9 +7,8 @@ This repo is part of [The Yocto Project](https://www.yoctoproject.org/), which u
This project is a sibling to the [OpenWRT/opkg](https://openwrt.org/docs/guide-user/additional-software/opkg) project, and both are descendants of the discontinued [Itsy Package Manager (ipkg)](https://en.wikipedia.org/wiki/Ipkg).


-* Website: http://code.google.com/p/opkg/
-* Mailing List:http://groups.google.com/group/opkg-devel
* Bug Tracker: https://bugzilla.yoctoproject.org/buglist.cgi?product=opkg
+* Mailing List: https://lists.yoctoproject.org/g/opkg
* Git Repository: https://git.yoctoproject.org/opkg/


diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index a0e8fec..74394a5 100644
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -10,7 +10,7 @@ This document should provide useful information for how to get started developin

Clone the **source** from the Yocto project's [git server](https://git.yoctoproject.org/opkg/), and read the [README](https://git.yoctoproject.org/opkg/tree/README).

-Get **help** using this repository and **discuss** changes on the [opkg-devel](https://groups.google.com/g/opkg-devel) google group mailing list.
+Get **help** using this repository and **discuss** changes on the [opkg mailing list](https://lists.yoctoproject.org/g/opkg).

File **bugs** and **enhancement** requests to the Yocto project's [opkg bugzilla tracker](https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=Product%3Aopkg)

@@ -110,13 +110,13 @@ git commit -s --trailer Closes=12345
----
## Submitting Changes Upstream

-**Git Send-Email.** Once you have *tested* your change, you can submit it to the opkg mainline by embedding it into an email, and sending it to the opkg-devel mailing list (<opkg-...@googlegroups.com>). When you do, please prefix your email with the tags: `[opkg][PATCH]`.
+**Git Send-Email.** Once you have *tested* your change, you can submit it to the opkg mainline by embedding it into an email, and sending it to the opkg mailing list (<op...@lists.yoctoproject.org>). When you do, please prefix your email with the tags: `[opkg][PATCH]`.

The easiest way to do this is using the git send-email extension. You can use the following commands to configure your opkg workspace with the correct defaults.

```bash
git config diff.renames copy
-git config format.to "opkg-...@googlegroups.com"
+git config format.to "op...@lists.yoctoproject.org"
git config format.subjectprefix "opkg][PATCH"
```

diff --git a/docs/MAINTAINING.md b/docs/MAINTAINING.md
index 959ba8a..e3e5e94 100644
--- a/docs/MAINTAINING.md
+++ b/docs/MAINTAINING.md
@@ -38,7 +38,7 @@ If there have been no substantial changes to the project source since the prior

To carry out the steps in this section, you must have:
1. **permission** from the Yocto project to act as maintainer (obviously)
- * If you believe it is appropriate for you to be a maintainer, start a discussion on the opkg-devel mailing list (see CONTRIBUTING) and on the Yocto project mailing list <yo...@lists.yoctoproject.org>.
+ * If you believe it is appropriate for you to be a maintainer, start a discussion on the opkg mailing list (see CONTRIBUTING) and on the Yocto project mailing list <yo...@lists.yoctoproject.org>.

2. a consistent **GPG signing keypair**, for artifact signing.
* Google around for how to make one.
@@ -82,7 +82,7 @@ To carry out the steps in this section, you must have:
git push yocto v${VERSION}
```

-9. Make an announcement to the opkg-devel mailing list that the new release is available. Include the release notes in the email.
+9. Make an announcement to the opkg mailing list that the new release is available. Include the release notes in the email.

10. Prepare an upgrade commit for the [OE-core opkg recipe](https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/opkg). Once the source tar is available on the download mirror, upstream the recipe upgrade with the OE-core mailing list.

--
2.40.1