[Nut-upsuser] RFC - new proposed variables and clarifications for the battery collection in NUT namespace

[Jim Klimov]

Good proposal, makes sense.

Sorry for slow replies, I'm now largely offline for a few weeks coming.

Jim

On Thu, Aug 12, 2021, 10:55 Roger Price <roger at rogerprice.org> wrote:

> On Thu, 12 Aug 2021, Arnaud Quette via Nut-upsuser wrote:
> > following a 10 days period after my above announcement, I've considered
> the
> > absence of feedback and comments as an implicit approval. I've hence
> merged
> > the above PRs, which results in the update of the NUT variables names
> and
> > instant commands update:
>
> >
> https://github.com/networkupstools/nut/blob/6d30b8cd190b25cafdbc46f8dc4602fb68692270/docs/nut-names.txt
>
> I'm wondering if it wouldn't be helpful in the long term if the process
> you have
> inaugurated were written into the file nut-names.txt  Something like:
>
> Adding names to this file
> =========================
>
> If you want to add (change or remove) names in this file, then remember
> that it
> is part of RFC XXXX, and that your action requires the "rough consensus"
> due to
> an RFC.  In practice this means large approval in the NUT mailing list.
> Post
> your intended change and invite comments.  If, after 10 days you have
> received
> no objections, then you may assume that you have large approval.  Make a
> second
> announcement in the NUT mailing list that you now intend to make the
> change.
>
> Roger
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210812/2dcdb71a/attachment.htm>