> On Jun 20, 2022, at 2:46 AM, Adi Roiban <adiroi...@gmail.com> wrote:
>
> Hi,
>
> The latest plan is to wait this week for more feedback about the Trac
> to Github issues migration.
>
> If nobody asked for the migration to be blocked, the plan is to do the
> "real deal" next Monday, during UK working hours.
>
> ------------
>
> About the wiki migration, more info is below.
>
> On Sat, 18 Jun 2022 at 00:17, Glyph <gl...@twistedmatrix.com
> <mailto:gl...@twistedmatrix.com>> wrote:
>>
>> Seeing the message about archiving the wiki into a git repo, are we trying
>> to migrate the wiki at the same time as issues?
>>
>> I just noticed this bit:
>>
>> On Jun 17, 2022, at 2:23 AM, Adi Roiban <adiroi...@gmail.com> wrote:
>>
>>
>> C Trac Wiki pages
>>
>> The plan is to store the existing wiki pages as normal files with edit
>> revisions in a git repo.
>> In this way, we preserve all the edit author and edit time and edit comments.
>> The git repo will be read only.
>>
>> The long term plan is to stop using the wiki pages.
>> Any valuable content that is not hosted on the wiki, should be moved
>> into our narrative docs pages ,
>> hosted at https://docs.twistedmatrix.com/
>>
>>
>> It seems like we should be finishing the issues migration before attempting
>> to touch the much more annoying issue of the old site's hosting. Not a
>> blocker or anything, but we can still leave Trac running while having the
>> frontend server just directing /trac/ticket/ and friends over to github.
>
> Yes. The ticket migration is ongoing.
> the wiki migration is independent of the issue migration.
Cool. Thanks, that was my main concern.
> While waiting for feedback for the ticket migration, I wanted to go
> ahead and do some work for the other parts of Trac and
> twistedmatrix.com <http://twistedmatrix.com/> website.
Love to see work happening in parallel without blocking :).
> The existing VM can stay online for as long as we want.
> Note that since it was created I haven't logged it to do any software
> or security updates.
FWIW I do log in periodically and do that. And since you mentioned it I just
rebooted it now ;-).
> This is why I would like to put if offline ASAP.
It would definitely be nice to junk the whole thing. I still really want to set
up some dynamic subdomains of twisted.org <http://twisted.org/> to do cool and
interesting things with Twisted, and a green-field deployment of some freshly
built containers would be much nicer than dragging this awkwardly-configured VM
limping along.
> Also, instead of updating the internal VM configuration and the
> Twisted web application that is used to serve Trac,
> I would prefer to leave it as it is, and do the redirection via
> external services, as this is what we will use for the long term.
+1, this all sounds good.
_______________________________________________
Twisted mailing list -- twisted@python.org
To unsubscribe send an email to twisted-le...@python.org
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/twisted@python.org/message/JFZ3YZOUIK5DX5XR4STDQ6E6XS3AVGRO/
Code of Conduct: https://twisted.org/conduct
