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

PEP-003 current status #2315

Closed
nsemikov opened this issue Aug 30, 2022 · 3 comments
Closed

PEP-003 current status #2315

nsemikov opened this issue Aug 30, 2022 · 3 comments
Labels
question Halp plz

Comments

@nsemikov
Copy link

What is your question?
I want to understand when pep-003 will be implemented and maybe help with this work. What is the current state of pep-003?

What have you tried already?
I tried to find state of pep-003 on roadmap, project board and pep-003 page and couldn't find it.

@nsemikov nsemikov added the question Halp plz label Aug 30, 2022
@carolynvs
Copy link
Member

PEP 003 is in the proof of concept stage on our roadmap (under Advanced Dependencies). I just realized that it accidentally linked to PEP 004, and I have fixed that card to link to the correct PEP.

We have a design, and I have done some initial work to vet it under the pep003-advanced-dependencies label. Further work has stopped while I have shifted focus to releasing v1 this month.

I would like to get #2099 updated, split out into smaller PRs and merged before trying to coordinate adding more people to the feature, so that we can better isolate and define tasks that people can help with. Unfortunately the feature isn't in a state yet where I can just point to curated issues that someone could understand and take on without much coordination.

@nsemikov
Copy link
Author

Thanks for the quick response!

Porter and Mixins automation moved this from Inbox to Done Aug 31, 2022
@carolynvs
Copy link
Member

I anticipate that we will start work on this immediately after v1 is released and get it split up so that people can help implement. 👍 The best way to keep up to date on that would be to join our Slack channel, and we'll probably have some additional coordination in our community meetings.

https://getporter.org/community

If you can't attend those it's not a big deal, let's just keep in sync over Slack so that you can jump in and help when we start on that feature. I really would appreciate help both with reviewing the design, trying out the feature on realistic bundles, obviously implementing it, and writing documentation. So there's plenty of work for us to all share. 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Halp plz
Projects
Development

No branches or pull requests

2 participants