Skip to content

Conversation

@Perksey
Copy link
Member

@Perksey Perksey commented Jul 28, 2021

This creates a roadmap and basic software development plan for 3.0, as well as a support & breaking change policy after the initial 3.0.

@Perksey Perksey changed the base branch from main to proposal/all-3.0-proposals July 28, 2021 20:50
@Perksey Perksey mentioned this pull request Jul 28, 2021
5 tasks
@Perksey Perksey marked this pull request as ready for review July 28, 2021 21:00
@Perksey
Copy link
Member Author

Perksey commented Jul 28, 2021

I think this is ready for review (but I may have missed something!) I think we should save roadmap discussion for the Working Group meeting as I think it's better to discuss that in a voice format, but if you have any initial objections to anything else before the meeting let me know.

- We have solved this in the form of the proposal you are reading and all linked proposals: getting all the design done now and documented now, to prevent design debates later down the line. This should reduce friction when actually working on the library.
- We have been keeping the working group and key stakeholders in the loop with the 3.0 kickoff (again, see this proposal you are reading)
- The team are trying to communicate with eachother and figure out how to distribute work among themselves depending on individual circumstances and free time
- Codeowners have been established
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have they?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. ThomasMiz for input, you for Maths. We can have a more in-depth discussion on this to reiterate here prior to the meeting.

- We have solved this in the form of the proposal you are reading and all linked proposals: getting all the design done now and documented now, to prevent design debates later down the line. This should reduce friction when actually working on the library.
- We have been keeping the working group and key stakeholders in the loop with the 3.0 kickoff (again, see this proposal you are reading)
- The team are trying to communicate with eachother and figure out how to distribute work among themselves depending on individual circumstances and free time
- Codeowners have been established
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. ThomasMiz for input, you for Maths. We can have a more in-depth discussion on this to reiterate here prior to the meeting.

@Perksey
Copy link
Member Author

Perksey commented Jul 31, 2021

Can I get a follow-up on this and resolve discussions if you think they're fine?

@Perksey Perksey requested a review from HurricanKai July 31, 2021 20:10
Copy link
Member

@HurricanKai HurricanKai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other then the code ownership question this is fine.

@Perksey
Copy link
Member Author

Perksey commented Aug 3, 2021

@ThomasMiz are you happy with this? Please approve on GitHub if you are.

@Perksey Perksey merged commit bb032e5 into proposal/all-3.0-proposals Aug 3, 2021
@Perksey Perksey deleted the proposal/sdp branch August 3, 2021 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants