[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [H-source-users] Introduction

From: Yuchen Pei
Subject: Re: [H-source-users] Introduction
Date: Mon, 02 Aug 2021 10:30:16 +1000
User-agent: mu4e 1.4.13; emacs 27.2

Hi Ian,

Thanks for the reply!
Ian Gilfillan <ian@greenman.co.za> writes:

On 2021/07/19 02:34, bill-auger wrote:
* Less maintain burden
it already requires basically zero maintenance - that is
evident by the fact that it has been un-maintained for several
years, yet it is still running

Unfortunately I don't have time to contribute beyond the trivial right
now, but some comments on maintenance:

- there's quite a bit of spam being submitted on h-node, which I
occasionally clean out. Yesterday, there were three spam wiki pages created. Issues and comments are regular targets. There is only one other moderator who also sometimes helps out. The current site 'works' in this sense, but as far as I know doesn't sent out email notifications about updates, and more could be done to reduce spam and reduce the maintenance burden on moderators, as well as improve the appearance of the site, which quite often sits with visible spam for a

How do I remove spam? Do I need to create an admin account for myself on the server?

- the only regular code maintenance required is updating the list of operating systems, as pointed out elsewhere on this thread. With h-source and the h-node code being so out of sync, I used to do this
manually on the server (Trisquel 9 at least needs to be added)

Is this what the files in MySQL_changelog <https://git.savannah.nongnu.org/cgit/h-source.git/tree/h-source/MySQL_changelog> are for?

- I abandoned my attempt to get the h-node and h-source code in sync
  due to time constraints. The differences were quite large, old
software version requirements became an obstacle, and quite a few changes had been made directly on the server. My preference as the easiest option was to make a clean start based on the current h-node

AIUI this is the current plan.

PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]