Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flower Farms #520

Open
kirstenalarsen opened this issue May 14, 2024 · 2 comments
Open

Flower Farms #520

kirstenalarsen opened this issue May 14, 2024 · 2 comments
Labels
Funded Feature Issue is part of the (potential) funded features pipe

Comments

@kirstenalarsen
Copy link

kirstenalarsen commented May 14, 2024

NB. ALL product, design and estimation work should be put against Clockify code # 12476 Flower Farms

@RachL @tschumilas creating an organising issue for the flower farms work, so that we have a code to link to Clockify etc. Please edit / provide text for me to update this to summarise where this is at, and any 'quick win' contenders that might be ready for work to commence e.g. minimum spend, product preview, order products by on-hand in new product screen?

@kirstenalarsen kirstenalarsen added the Funded Feature Issue is part of the (potential) funded features pipe label May 15, 2024
@RachL
Copy link
Contributor

RachL commented May 15, 2024

@kirstenalarsen @tschumilas so far discussion with the team shows that there are no quick wins. Or at least that we need to have calls to talk it through otherwise we end up with estimate that are far to high.
However my apologies but I didn't understand that the budget was already there for these features.
Product preview has already been estimated, but I didn't understand that this was funded. We can start working on it as soon as Mario gets back. Can I clarify how much budget was found for this one?

@tschumilas
Copy link

tschumilas commented May 15, 2024

Here
is a summary of the flower farm priority features. Those highlighted in yellow are the top priorities - but also the largest things.
Those in peach are priorities that might be easier wins.

But money has not been allocated to these yet. I think the next step is for me to do a discourse post related to the 2 larger issues to see if work underway with the API might get us close to solutions.

We don't need to deliver all of these in this project - but we need to clearly identify 5 features to be implemented by March 2026. So far, $19,000 AUS is in global. $9500 of this has been allocated to core, and $9500 needs to be pinned to a specific feature. An additional $22,000 AUS can be sent before December, and a final $22,000 after April 2025. We are ok using part of these contributions for core as well. We just need to make sure we can report 5 features were developed. So, if we do the same 50% to core, it means we have $31,500 Aus to allocate.

Personally, I would love to put $20,000 toward the 'future orders' big ticket item, if we thought it would get us there. I think we could do several other things on the list with integrations and report those as accomplished for this grant. But when will we have another opportunity to do something big? Thats my 2 cents anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Funded Feature Issue is part of the (potential) funded features pipe
Projects
Status: Funded Features
Development

No branches or pull requests

3 participants