Comments (14)
I think we got agreement on this, the only final thing is deciding who needs to be part of sig-end-user-maintainers
. @open-telemetry/end-user-wg could you review membership?
from community.
Ah, I see #1575. Makes sense. I'm happy with calling the repo sig-end-user
. The general idea of prefixing repos with opentelemetry-
is to help with forks, but I don't know if we'd expect many people forking that repo. Clarity in the name may be more beneficial.
from community.
We also need to update the repo maintainers to remove sharrmander, as she is no longer involved in the OTel community (😞).
from community.
So, in summary, this request implies:
- New repo called
sig-end-user
end-user-wg
team renamed tosig-end-user-maintainers
sig-end-user-maintainers
givenMaintain
role in the new repo
I see sharrmander
is no longer in the end-user-wg
team, but team membership may need to be reviewed.
from community.
I believe if we take sig-security-maintainers
as an example, they take on all responsibilities of the group equally. However, if you think you may need sig-end-user-triagers
or sig-end-user-approvers
that can be discussed later?
from community.
Per the definition of Maintainer
in the role table, I think it makes sense to start sig-end-user-maintainers
with the following members:
- @danielgblanco
- @avillela
- @reese-lee (myself)
And we can revisit other roles as needed down the road.
from community.
@open-telemetry/end-user-wg (possibly renamed to @open-telemetry/end-user-approvers)
Since there is some similarity to [sig-security-maintainers](https://github.com/orgs/open-telemetry/teams/sig-security-maintainers)
, I would suggest sig-end-user-maintainers
?
from community.
After creating the repo for the End User SIG, I'd like to wish for one thing: let's make sure that "end user facing content" continues to live on the website. What do I mean by that: we ask all SIGs to have their end-user facing docs on the website, and only their SIG-specific material (charters, tooling, pre-release/draft docs, ...) in their repo. A good example is SIG security: https://opentelemetry.io/docs/security/ vs https://github.com/open-telemetry/sig-security. So, when I read that "survey results, aggregated feedback" should be housed in the End User SIG repository, I hope this means the raw data and that end-user facing summaries end up on the website.
from community.
same for the repo name, similar to https://github.com/open-telemetry/sig-security?
from community.
That's interesting. Was there a discussion when the sig-security
repo was created to not follow guidance in https://github.com/open-telemetry/community/blob/main/docs/how-to-configure-new-repository.md ?
from community.
Thoughts on this SIG having different roles as outlined here? Or does sig-end-user-maintainers
encompass all those roles?
from community.
Thoughts on this SIG having different roles as outlined here? Or does
sig-end-user-maintainers
encompass all those roles?
Yes, I agree with @reese-lee that we should have different roles. This way, folks can contribute as per their capacity.
from community.
Yes, absolutely @svrnm! I think in terms of survey results, I would expect the raw/CSV results form surveys to be in that repo, but anything digested and well presented to live in the website.
from community.
I've just updated the issue definition to match all the comments in this thread
from community.
Related Issues (20)
- REQUEST: Repository maintenance on opentelemetry-rust HOT 11
- REQUEST: New membership for xrmx HOT 4
- REQUEST: New membership for @devrimdemiroz HOT 5
- Onboard mviitane as SIG OTel Demo maintainer HOT 2
- REQUEST: New membership for asafm HOT 7
- REQUEST: New membership for ycombinator HOT 4
- REQUEST: Repository maintenance on weaver HOT 2
- Create @open-telemetry/specs-profiling-approvers team HOT 2
- Single meeting invite for Prometheus Interoperability end-user feedback session HOT 2
- REQUEST: New membership for @maryliag HOT 4
- Create End-User SIG recurring meeting in public calendar HOT 3
- REQUEST: Repository maintenance on opentelemetry-collector-releases HOT 1
- REQUEST: New membership for gregkalapos HOT 3
- Remove myself from demo-approvers group for the website HOT 3
- Rename "Working group" (WG) to SIG everywhere HOT 1
- REQUEST: Create new Docker Hub repository: otel/opentelemetry-collector-k8s HOT 7
- REQUEST: New membership for carsonip HOT 3
- REQUEST: New membership for florianl HOT 3
- REQUEST: New membership for tiffany76 HOT 3
- Cancel future end-user discussion sessions for EMEA and AMER HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from community.