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

Project Tracking: Profiling #2731

Closed
tigrannajaryan opened this issue Aug 16, 2022 · 5 comments
Closed

Project Tracking: Profiling #2731

tigrannajaryan opened this issue Aug 16, 2022 · 5 comments
Assignees
@Rperry2174
Labels
project-tracking

Comments

@tigrannajaryan
Copy link
Member

tigrannajaryan commented Aug 16, 2022 •
edited
Loading

[Profiling Workgroup will complete the description below].

Description

Describe the goals, objectives, and requirements for the project. This include the motivations for starting the project now, as opposed to later.

Project Board

Once approved by TC, a project should be managed using a GitHub project board. This project board should be pre-populated with issues that cover all known deliverables, organized by timeline milestones.

A Technical Committee (TC) member associated with the project can create the board, along with a new project-specific GitHub label to automatically associate issues and PRs with the project. The project lead and all other relevant project members should have edit access to the board.

Once created, please link to the project board here.

Deliverables

A description of what this project is planning to deliver, or is in the process of delivering. This includes all OTEPs and their associated prototypes.

In general, OTEPs are not accepted unless they come with working prototypes available to review in at least two languages. Please discuss these requirements with a TC member before submitting an OTEP.

Staffing / Help Wanted

Who is currently planning to work on the project? If a project requires specialized domain expertise, please list it here. If a project is missing a critical mass of people in order to begin work, please clarify.

Required staffing

Projects cannot be started until they the following participants have been identified:

  • Every project needs a project lead, who is willing to bottom line the project and address any issues which are not handled by other project members.
  • At least two sponsoring TC members. TC sponsors are dedicated to attending meetings, reviewing proposals, and in general being aware of the state of the project and it's technical details. TC sponsors guide the project through the spec process, keep the tracking issue up to date, and help to ensure that relevant community members provide input at the appropriate times.
  • Engineers willing to write prototypes in at least two languages (if relevant to project). Languages should be fairly different from each other (for example: Java and Python).
  • Maintainers or approvers from those languages committed to reviewing the prototypes.

Meeting Times

Once a project is started, the working group should meet regularly for discussion. These meeting times should be posted on the OpenTelemetry public calendar.

Timeline

What is the expected timeline the project will aim to adhere to, and what resources and deliverables will be needed for each portion of the timeline? If the project has not been started, please describe this timeline in relative terms (one month in, two weeks later, etc). If a project has started, please include actual dates.

Labels

The tracking issue should be properly labeled to indicate what parts of the specification it is focused on.

Linked Issues and PRs

All PRs, Issues, and OTEPs related to the project should link back to the tracking issue, so that they can be easily found.
@tigrannajaryan tigrannajaryan changed the title Profiling Project Tracking: Profiling Aug 16, 2022
@tigrannajaryan tigrannajaryan moved this to Potential Projects in 🔭 Main Backlog Aug 16, 2022
@tigrannajaryan
Copy link
Member Author

@Rperry2174 I can't assign this to you since you are not a member of Otel github org. Please apply to become a member, see: https://github.com/open-telemetry/community/blob/main/community-membership.md#member

@Rperry2174
Copy link
Contributor

Rperry2174 commented Aug 17, 2022 •
edited
Loading

I am now a member @tigrannajaryan feel free to assign me now

@reyang reyang added the [label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR label Aug 24, 2022
@Rperry2174 Rperry2174 mentioned this issue Aug 30, 2022
Merged
tigrannajaryan pushed a commit to open-telemetry/oteps that referenced this issue Sep 22, 2022
@Rperry2174
Propose OpenTelemetry Profiling Vision (#212)
6e18af5 
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project. 

A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. 

This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](#139) created in October 2020. 

If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). 

Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
@tedsuo tedsuo moved this from Potential Projects to Current Projects in 🔭 Main Backlog Nov 22, 2022
@austinlparker
Copy link
Member

@mtwo will be the GC Facilitator for this project.

This is a new responsibility the GC is adopting to better support cross-functional projects in OpenTelemetry. There will be a document in the community repo in the future detailing these responsibilities -- in general, the facilitator will help ensure that required TC sponsors are available and assigned, and will be a resource for project maintainers.

@mtwo
Copy link
Member

mtwo commented Dec 7, 2023 via email

@marcalff marcalff mentioned this issue May 6, 2024
Open
@austinlparker austinlparker removed the [label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR label Jun 18, 2024
@austinlparker
Copy link
Member

Closing as this is a SIG now.

carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this issue Oct 21, 2024
@Rperry2174 @carlosalberto
Propose OpenTelemetry Profiling Vision (open-telemetry#212)
bb20a9a 
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project.

A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months.

This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry/oteps#139) created in October 2020.

If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md).

Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto pushed a commit to carlosalberto/oteps that referenced this issue Oct 23, 2024
@Rperry2174
Propose OpenTelemetry Profiling Vision (open-telemetry#212)
fb950b0 
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project. 

A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. 

This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry#139) created in October 2020. 

If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). 

Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto pushed a commit to carlosalberto/oteps that referenced this issue Oct 23, 2024
@Rperry2174
Propose OpenTelemetry Profiling Vision (open-telemetry#212)
4336176 
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project. 

A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. 

This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry#139) created in October 2020. 

If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). 

Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto pushed a commit to carlosalberto/oteps that referenced this issue Oct 30, 2024
@Rperry2174
Propose OpenTelemetry Profiling Vision (open-telemetry#212)
365edee 
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project. 

A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. 

This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry#139) created in October 2020. 

If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). 

Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto pushed a commit that referenced this issue Nov 8, 2024
@Rperry2174 @carlosalberto
Propose OpenTelemetry Profiling Vision (open-telemetry/oteps#212)
8e25cc0 
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project. 

A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. 

This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry/oteps#139) created in October 2020. 

If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). 

Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rperry2174 Rperry2174

Labels
project-tracking
Projects
🔭 Main Backlog
Status: Completed Projects
Milestone
No milestone
Development

No branches or pull requests
7 participants
@tedsuo @mtwo @yurishkuro @austinlparker @tigrannajaryan @reyang @Rperry2174