Closed baywet closed 3 years ago
ping @corradio @martincollignon
Hi @baywet, Thank you very much for pushing forward on this. I don't know if you're aware that we're sunsetting the North app (see https://www.tmrow.com/blog/sunsetting-north/). This repository is now geared towards the Bloom (bloomclimate.com) product geared towards SMEs.
This doesn't mean the water model will not be used, but it means that it will be of lower priority for us in terms of UI.
As guidance, I suggest adding a water purchase in m3. It doesn't need to be price based. The ambition with footprint.yml is to be a tree based on coicop categories, see https://unstats.un.org/unsd/classifications/unsdclassifications/COICOP_2018_-_pre-edited_white_cover_version_-_2018-12-26.pdf
I suggest introduce a new category corresponding to water? Maybe this one?
thanks for sharing. Closing as I won't invest time in an app being sunset. Too bad it was a good app. Good luck for the next steps!
Thanks for the support Vincent!
On Mon, Dec 14, 2020 at 4:09 PM Vincent Biret notifications@github.com wrote:
Closed #446 https://github.com/tmrowco/bloom-contrib/issues/446.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tmrowco/bloom-contrib/issues/446#event-4109751704, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMUIKFPFJWJZGX5I6CCGBTSUYTBPANCNFSM4Q44CG5A .
--
Olivier Corradi
Founder, CEO
https://www.linkedin.com/in/oliviercorradi https://twitter.com/corradio
tmrow.com
Hi Team, I'm writing to follow up on #404 . Now I understand the team is busy with other priorities to build a dedicated UI if we add another model. In the PR discussion it was indicated to add it as a purchase instead, and I'd like to get guidance/understand what's already there so I don't send another PR which ends up being closed. We have multiple entries in the purchase model:
So my questions are:
Thanks for the help!