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

Have a clear product/technical roadmap for OpenFisca Core #942

Closed
bonjourmauko opened this issue Jan 31, 2020 · 8 comments
Closed

Have a clear product/technical roadmap for OpenFisca Core #942

bonjourmauko opened this issue Jan 31, 2020 · 8 comments
Labels
policy:rfc Request For Comments: chime in!

Comments

@bonjourmauko
Copy link
Member

Image

cc @Morendil @sandcha

@bonjourmauko bonjourmauko added the policy:rfc Request For Comments: chime in! label Jan 31, 2020
@bonjourmauko bonjourmauko changed the title Roadmap Refactoring Create a roadmap for OpenFisca Core Apr 15, 2021
@bonjourmauko bonjourmauko changed the title Create a roadmap for OpenFisca Core Create a product/technical roadmap for OpenFisca Core Apr 15, 2021
@bonjourmauko bonjourmauko pinned this issue Apr 15, 2021
@bonjourmauko bonjourmauko changed the title Create a product/technical roadmap for OpenFisca Core Have a clear product/technical roadmap for OpenFisca Core Apr 15, 2021
@bonjourmauko
Copy link
Member Author

I've tried to distill what could be a short-mid term roadmap for OpenFisca-Core here:

@MattiSG I see that you've been successfully running RFCs lately, I would love to have your help/opinion on this one, most of it are elements we've been discussing for a while now.

@MattiSG
Copy link
Member

MattiSG commented Oct 7, 2021

Thank you for that contribution @maukoquiroga. It certainly improves the readability of the existing PRs! 😀

I believe that roadmap are promises to be upheld by those who publish them, and I unfortunately do not command enough resources a the moment to commit to such a roadmap 🙁 I am thus not sure what to do with those milestones.

@bonjourmauko
Copy link
Member Author

@MattiSG At least for #1061 , #1062 , and #1063 , if there's no preliminary waver needed from the community, I just had in mind to ask for contributions —but not before I'm sure those contributions will have a reasonably % of merging (to avoid #976 for example).

For the rest, I agree, this was more intented to let people know how to contribute than to agree on delivery.

@MattiSG
Copy link
Member

MattiSG commented Oct 7, 2021

Thank you for these clarifications 👍

As explained in #1054 (review), I believe these do not need preliminary community agreement. Agreement would be in my view necessary in order to make accepting contributions dependent on the respect of documentation / typing standards.

#976 is a good example: why has it been blocked? Do you confirm that #1054 and following are re-implementations of the same concern?

@bonjourmauko
Copy link
Member Author

@MattiSG Exactly, that could have been accepted ...

@MattiSG
Copy link
Member

MattiSG commented Oct 7, 2021

So why wasn't it? 🤔

@bonjourmauko
Copy link
Member Author

Because you forgot to click the accept button 🤣

Joking, closing this issue as is not actionable.

@bonjourmauko
Copy link
Member Author

I consolidated current efforts in the wiki:
https://github.com/openfisca/openfisca-core/wiki/Ongoing-Efforts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
policy:rfc Request For Comments: chime in!
Projects
None yet
Development

No branches or pull requests

2 participants