Good point. The PostgreSQL database that stores everything can be backed up, stored as a file anywhere and restored fairly easily: https://meta.discourse.org/t/122710 I'm only a mod (not an admin), so I don't know if we're actually doing it right now, but maybe Brett or one of the other admins does—might be a good idea to do regularly just in case.
Besides being restored to another Discourse instance (including self hosted), the db schema is documented as comments at the bottom of each file in the `app/models` directory, e.g. for posts: https://github.com/discourse/discourse/blob/main/app/models/post.rb#L1257-L1327 and thus one could browsed, query and extract, e.g. an archive of posts via a PostgreSQL client or a script, as well as in the official first-party maintained data explorer plugin that runs inside the instance: https://meta.discourse.org/t/discourse-data-explorer/32566
Discourse also has an API: https://docs.discourse.org/ , and you can get the data on any page as JSON via adding `.json` to the URL, https://discuss.python.org/t/27957.json, so the public data could also be scraped and archived that way by anyone interested if desired (just like the ML can).
Does that help address your concern?
It does address the question of how to backup Discourse content, but leaves open the concern of whether we or the PSF are actually doing any of the above to keep a copy of it under our control.
This may not be important to many people, but we have always been very careful to maintain our collective history in the past and should continue to do so going forward. With more and more MLs moving to Discourse, this is becoming more relevant as well. I just used this request for another move as trigger to start the discussion.
I can reach out to Ee, the PSF director of infra, to see whether
this is on his radar.
Thanks,
CAM
C.A.M. Gerlach
On Tue, Jul 4, 2023 at 4:57 AM Marc-Andre Lemburg <mal@egenix.com> wrote:
The only concern I have with moving off of the MLs and to Discourse is
archiving of messages.
With MLs, the archiving process is pretty straight forward and built
into Mailman, but for Discourse this is less obvious.
Do we have a solution to archiving Discourse content in place which is
under PSF control ? (AFAIK, we are using a hosted Discource installation)
Thanks.
On 04.07.2023 06:57, C.A.M. Gerlach wrote:
> FWIW, +1 to archiving to reduce duplication. If decided, I can help out
> making the appropriate devguide, PEP, etc. changes, as I've done for
> several previous transitions now.
>
> Thanks,
> CAM
>
> /C.A.M. Gerlach/
>
>
> On Mon, Jul 3, 2023 at 2:15 PM Brett Cannon <brett@python.org
> <mailto:brett@python.org>> wrote:
>
> The question has come up as to whether people still find this
> mailing list useful enough to keep around. Looking at the archive
> (https://mail.python.org/archives/list/python-committers@python.org/latest <https://mail.python.org/archives/list/python-committers@python.org/latest>), this list seems to be used for two things:
>
> 1. Announcing new releases
> 2. Announcing new core developers
>
> In both cases the things are announced (at least) at
> discuss.python.org <http://discuss.python.org>, and so are not
> exclusive to this list.
>
> So, do people find this list useful enough to keep around, or should
> we archive it?
> _______________________________________________
> python-committers mailing list -- python-committers@python.org
> <mailto:python-committers@python.org>
> To unsubscribe send an email to python-committers-leave@python.org
> <mailto:python-committers-leave@python.org>
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> <https://mail.python.org/mailman3/lists/python-committers.python.org/>
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/WAVEXV3FAK6IFMXTVO7PRNYOY66NBP2F/ <https://mail.python.org/archives/list/python-committers@python.org/message/WAVEXV3FAK6IFMXTVO7PRNYOY66NBP2F/>
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> <https://www.python.org/psf/codeofconduct/>
>
>
> _______________________________________________
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-leave@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/UIXSQYCMSWOAU5CLU6YF72ZNJDNXZMSG/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Experts
>>> Python Projects, Coaching and Consulting ... http://www.egenix.com/
>>> Python Database Interfaces ... http://products.egenix.com/
________________________________________________________________________
::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
http://www.malemburg.com/
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Experts
>>> Python Projects, Coaching and Consulting ... http://www.egenix.com/
>>> Python Database Interfaces ... http://products.egenix.com/
________________________________________________________________________
::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
http://www.malemburg.com/