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.

Sign up for GitHub

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

Jump to bottom

Create a process document #55

Closed
jkup opened this issue Sep 28, 2023 · 2 comments
Closed

Create a process document #55

jkup opened this issue Sep 28, 2023 · 2 comments

Comments

@jkup
Copy link
Collaborator

jkup commented Sep 28, 2023

I'm not sure if this conversation has been started elsewhere but it would be good to start a discussion on how new features can move through our task group and make it into the spec.

TC39 has this great process document: https://tc39.es/process-document/

For example, the next time someone wants to add a new field to source maps (like #25) - we should have a process document on how to submit a proposal, how we move proposals forward, a list of tools and browsers we work with, how many "implementers" it takes to ship something, etc.
@littledan
Copy link
Member

We have https://github.com/tc39/source-map-rfc/blob/main/PROCESS.md . Does that meet the requirements for this issue? Does anyone have further recommendations or concerns?

@Meysamsarabadani Meysamsarabadani moved this from Todo to In Progress in Source map Spec Standardization Nov 20, 2023
@jkup
Copy link
Collaborator Author

jkup commented Dec 12, 2023

Perfect!

@jkup jkup closed this as completed Dec 12, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Source map Spec Standardization Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@littledan @jkup