Re: [Nut-upsuser] RFC - new proposed variables and clarifications for the battery collection in NUT namespace
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 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 , 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@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] RFC - new proposed variables and clarifications for the battery collection in NUT namespace
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 , 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@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] RFC - new proposed variables and clarifications for the battery collection in NUT namespace
Le lun. 2 août 2021 à 15:16, Arnaud Quette a écrit : > Hi there, > > as discussed on the below Github PRs, I've recently proposed some > additional variables to deal with battery information in general, and some > Li-Ion specifics: > > * PR https://github.com/networkupstools/nut/pull/1060/files > ** Add "battery.packs.external": Number of external battery packs > > * PR https://github.com/networkupstools/nut/pull/1062/files > ** Add "battery.voltage.cell.max": Maximum battery voltage seen of the > Li-ion cell (V) > ** Add "battery.voltage.cell.min": Minimum battery voltage seen of the > Li-ion cell (V) > ** Add "battery.capacity.nominal": Nominal battery capacity (Ah) > ** Add "battery.status": Health status of the battery (opaque string) > ** Add "battery.temperature.cell.max": Maximum battery temperature seen of > the Li-ion cell (degrees C) > ** Add "battery.temperature.cell.min": Minimum battery temperature seen of > the Li-ion cell (degrees C) > > * PR https://github.com/networkupstools/nut/pull/1063/files > ** Clarify "battery.date": Battery installation or last change date > (opaque string) > ** Add "battery.date.maintenance": Battery next change or maintenance date > (opaque string) > > As usual with RFC for new variables, feedback and comments are warmly > welcome. > > Thanks and cheers > Arno > Hi NUT users, 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 A special thanks to Roger Price for his support in this updated process! Thanks and cheers, Arno ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] RFC - new proposed variables and clarifications for the battery collection in NUT namespace
Hi there, as discussed on the below Github PRs, I've recently proposed some additional variables to deal with battery information in general, and some Li-Ion specifics: * PR https://github.com/networkupstools/nut/pull/1060/files ** Add "battery.packs.external": Number of external battery packs * PR https://github.com/networkupstools/nut/pull/1062/files ** Add "battery.voltage.cell.max": Maximum battery voltage seen of the Li-ion cell (V) ** Add "battery.voltage.cell.min": Minimum battery voltage seen of the Li-ion cell (V) ** Add "battery.capacity.nominal": Nominal battery capacity (Ah) ** Add "battery.status": Health status of the battery (opaque string) ** Add "battery.temperature.cell.max": Maximum battery temperature seen of the Li-ion cell (degrees C) ** Add "battery.temperature.cell.min": Minimum battery temperature seen of the Li-ion cell (degrees C) * PR https://github.com/networkupstools/nut/pull/1063/files ** Clarify "battery.date": Battery installation or last change date (opaque string) ** Add "battery.date.maintenance": Battery next change or maintenance date (opaque string) As usual with RFC for new variables, feedback and comments are warmly welcome. Thanks and cheers Arno ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
