Mirror grass-dev mailing list to discourse

[neteler]

As per ​https://discourse.osgeo.org/docs?topic=6765, "Option 2: Move to discourse completely" the GRASS GIS team kindly asks to migrate the "grass-dev" list (​https://lists.osgeo.org/pipermail/grass-dev/) to discourse, with the full mbox file which starts back in Dec 1991).

The organization shall be:

• grass
  category, used as a folder, for sub-categories.

• grass/grass-dev
  sub-category used to provide a searchable archive of the original grass-dev full archive (currently at ​https://lists.osgeo.org/pipermail/grass-dev/).

The needed mbox file is found on the list server at
/var/lib/mailman/archives/private/grass-dev.mbox/grass-dev.mbox

Desired admin setup (OSGeo-IDs):

• main admin: annakrat
• co-admins: veroandreo, neteler, wenzeslaus

Reference: ​https://lists.osgeo.org/pipermail/grass-dev/2024-August/096338.html

Thanks in advance!

[cvvergara]

Hi, sorry for the delay

I will need some information:

• Link to logo
• Short description (I will append to the description how people can post on the list)

The categories can be linked to a group Group: grass-dev

Category grass: everyone: can see

Category grass/grass-dev: group permissions: grass-dev can see, can reply, can create everyone: can see

That way, any one can see what is going on if they want, but to reply or create a post they must register to the grass-dev group

I will also manage a little the users that I can see sent a mail recently and already signed into discourse:

• will add them to the group.
• will give them a trust level 2

To the group admins:

• will give them a trust level 4

please read about trust levels ​https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/

[cvvergara]

The import did not work well there were many errors while indexing, for example:

Failed to index message in /shared/import/data/grass-dev/grass-dev.mbox at lines 3298741-3298976
undefined method `sub' for an instance of Symbol

will need to break up the file into parts, do the import on staging by sections so to find the problem with it.

the category was never created because of the errors I think.

[veroandreo]

Hi Vicky, thanks. I just checked the staging link that Regina shared on GRASS gitter channel. Seems threads are lost and this is something we want to avoid.

Please see this: ​https://lists.osgeo.org/pipermail/grass-dev/2024-September/thread.html. There's an email by Olivia with a reply from @neteler that does not appear in the staging discourse instance (​https://discourse.staging.osgeo.org/c/grass-dev).

[robe]

Replying to veroandreo:

Hi Vicky, thanks. I just checked the staging link that Regina shared on GRASS gitter channel. Seems threads are lost and this is something we want to avoid.

Please see this: ​https://lists.osgeo.org/pipermail/grass-dev/2024-September/thread.html. There's an email by Olivia with a reply from @neteler that does not appear in the staging discourse instance (​https://discourse.staging.osgeo.org/c/grass-dev).

The threads should be back now.

[neteler]

How cool, email threads are back!

[veroandreo]

Great! Thanks!

[cvvergara]

Setting group owners: netteler and veroandreo

Some messages could not be improted because of some errors:

Last not imported mail error trace while indexing:

Failed to index message in /shared/import/data/grass-dev/grass-dev.mbox at lines 3298741-3298976
undefined method `sub' for an instance of Symbol
[
"/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>'"]

last non imported mail date:

From yyy at xxx.xxx.xxx.xx  Fri Jan 25 03:31:16 2008

Some of those were parent messages:

Parent message 20010418031022.16455..... doesn't exist. Skipping 3ADD0D8A.9EEEF612 ...
Re: [GRASS5] start using grass5

[cvvergara]

TODO: create the group

[cvvergara]

tasks done:

• Added myself to the list. to be able to send mails to the list.
• Added discourse to the members on the list
• Only members of group grass-dev can create new topics, any one can reply
• Sent a mail directly to grass-dev at discourse.osgeo.org
  • ​​https://discourse.osgeo.org/t/mail-test-to-grass-dev-at-discourse/85566
  • Anna Petrasova replied by email

• mail sent to mailing lists:
  • ​​https://lists.osgeo.org/pipermail/grass-dev/2024-September/096357.html
• set up the mirror
  • replied to that mail, now it shows on discourse
  • ​​https://discourse.osgeo.org/t/re-grass-dev-migration-to-discourse-info-and-test/85568/2

[cvvergara]

Group created. Mirror works. Migrated list message on mailing list

To definitively close the mailing list open a new ticket.