#3320: Migrate grass-user mailing list to discourse
--------------------------------+---------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Keywords: discourse
--------------------------------+---------------------------
The grass-dev mailing list is moved now to discourse and we would like to
continue with [grass-user Info Page grass-
user].
We would like to import the archives and mirror the mailing list for some
time before we close it completely, the same way it was done for grass-dev
(see #3255).
I would also like the admin to send batch invitations (as Regina did for
grass-dev, we will provide the list of emails).
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3320>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by annakrat):
I would like to move on with this, is there an estimate when this could
get started?
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Hello,
We are waiting for budget to go thru.
And approval for this ticket to be worked on.
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by annakrat):
What is the status of the budget? We would really like to get this moving.
Thanks!
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
I am planning to work on this this Friday march 14.
Some questions:
Do you want/need a group?
- grass-user group: can See, Reply, Create
- everyone: can See, Reply
Or leave:
- everyone: can See, Reply, Create
For users we recommend the second option.
Will base the description of the group on this description
About the pgrouting-users category
and will hand over the description owner to annakart, for further
modifications.
Will also add a link to discourse on the mailing list description.
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by annakrat):
Great! Let's go with the second option then, no group.
We tried mirroring during the grass-dev list transition and I suggest not
to do it this time, it was somewhat confusing. We will just leave the
mailing list open for a while, no big traffic there. But it would be good
to close the user mailing list new subscriptions, similarly you did with
grass-dev:
grass-dev Info Page
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Will be posting work on progress/done in the comments:
List to be migrated: grass-user Info Page
Next steps:
- Copy the mailing list to container
- Prepare copy within discourse import
- Announce in discourse this ticket is taking place.
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Next steps:
- Proceed with the import
will take some time
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Index problems:
Many errors of this kind are happening:
(note: manually breaking into lines for readability)
{{{
Failed to index message in /shared/import/data/grass-user/grass-user.mbox
at lines 2651488-2651522
undefined method `sub' for nil
["/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:91:in
`block in index_emails'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:158:in
`block (2 levels) in all_messages'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:190:in
`block in each_mail'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:210:in
`block in each_line'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:210:in
`each_line'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:210:in
`each_line'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:187:in
`each_mail'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:150:in
`block in all_messages'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:143:in
`foreach'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:143:in
`all_messages'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:67:in
`index_emails'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:25:in
`block in execute'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:22:in
`each'",
"/var/www/discourse/script/import_scripts/mbox/support/indexer.rb:22:in
`execute'",
"/var/www/discourse/script/import_scripts/mbox/importer.rb:43:in
`index_messages'",
"/var/www/discourse/script/import_scripts/mbox/importer.rb:27:in
`execute'",
"/var/www/discourse/script/import_scripts/base.rb:47:in `perform'",
"script/import_scripts/mbox.rb:13:in `<module:Mbox>'",
"script/import_scripts/mbox.rb:11:in `<module:ImportScripts>'",
"script/import_scripts/mbox.rb:10:in `<main>'"]
}}}
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Last problem message:
{{{
Failed to index message in /shared/import/data/grass-user/grass-user.mbox
at lines 2764241-2764263
}}}
Will post related message on the mailing list on the next comment.
Creating users problems: Sent by mail to @annakrat
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Last message with indexing problems:
Labeling vectors/TIGER lines
Based on the date of the last problematic message:
Will not bring problematic messages over to discourse.
Next steps:
Set up:
- discourse mail
- category description, parent, moderator, etc
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
mail setup:
grass-user@lists.osgeo.org|grass-user@discourse.osgeo.org
Next steps:
mailman:
Change messages about migration on:
- digest and non digest modes: Header and footer.
- General options: Terse phrase, introductory description
- HTML pages: listinfo.html
- add discourse as member of the list.
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
There are a lot of mails that are marked with:
- nomail [reason]
Is delivery to the member disabled? If so, an abbreviation will be given
describing the reason for the disabled delivery.
Possible reasons are:
- U: Delivery was disabled by the user via their person options page.
- A: Delivery was disabled by the list administrators.
- B: Delivery was disabled by the system due to excessive bouncing from
the member's address.
- ?: The reason for disabled delivery isn't known. This is the case for
all membership which were disabled in older versions of Mailman.
Needs to be cleaned up before creating the invite.csv file
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Due to the number of subscriptions:
- Its a semi-mirror of the mailing list
- Messages will still arrive but they will need to be moderated
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Next steps:
- Clean the list to be able to generate the invites.csv
- generate the invites
- Show and tell on moderation to @annakrat
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by annakrat):
Thanks Vicky!
I noticed an inconsistency in grass user and developer category names and
URLs:
Developer category has name "GRASS GIS Developer" and URL:
https://discourse.osgeo.org/tags/c/grass/developer/61/
but user category is only "grass-user" and URL:
grass-user - OSGeo Discourse
Could we make it consistent?
Also, GRASS decided to phase out the "GIS" in the project's name, use just
"GRASS", so we would like to reflect that in discourse as well.
[GRASS-PSC] [Motion] Use GRASS as a project name
I don't think I have permissions to change it.
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------+------------------------------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2025-II (vicky)
Component: | Resolution: fixed
SysAdmin/Discourse |
Keywords: discourse |
--------------------------+------------------------------------------------
Comment (by annakrat):
Replying to [comment:16 cvvergara]:
> Hi Anna
>
> Removed the GIS from various places.
>
> I don't understand what you mean about the consistency.
> All these as long as there is the number 70 at the end take you to the
same category
>
> - grass-user - OSGeo Discourse
> - grass-user - OSGeo Discourse
> - grass-user - OSGeo Discourse
> - grass-user - OSGeo Discourse
> - grass-user - OSGeo Discourse
OK then but can we have here "GRASS User" instead of "grass-user" in the
same way there is "GRASS Developer":
GRASS - OSGeo Discourse
>
> You can edit to remove the GIS:
> - About the GRASS developer category
> - About the GRASS category
I can't edit About the GRASS category, there is still GIS left
in the text.
Thanks!
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------+------------------------------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2025-II (vicky)
Component: | Resolution: fixed
SysAdmin/Discourse |
Keywords: discourse |
--------------------------+------------------------------------------------
Comment (by cvvergara):
about About the GRASS category
You are owner of that description, you should be able to edit it.
Anyway I removed the GIS from that description.
About grass-user: I don't understand what you want
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------+------------------------------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2025-II (vicky)
Component: | Resolution: fixed
SysAdmin/Discourse |
Keywords: discourse |
--------------------------+------------------------------------------------
Changes (by cvvergara):
* milestone: Unplanned => Sysadmin Contract 2025-II (vicky)
* resolution: => fixed
* status: new => closed
Comment:
The invites will be done by @annakrat
Closing ticket
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3320: Migrate grass-user mailing list to discourse
--------------------------------+----------------------------
Reporter: annakrat | Owner: sac-tickets@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/Discourse | Resolution:
Keywords: discourse |
--------------------------------+----------------------------
Comment (by cvvergara):
Hi Anna
Removed the GIS from various places.
I don't understand what you mean about the consistency.
All these as long as there is the number 70 at the end take you to the
same category
- grass-user - OSGeo Discourse
- grass-user - OSGeo Discourse
- grass-user - OSGeo Discourse
- grass-user - OSGeo Discourse
- grass-user - OSGeo Discourse
You can edit to remove the GIS:
- About the GRASS developer category
- About the GRASS category
--
Ticket URL: <#3320 (Migrate grass-user mailing list to discourse) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.