Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upOwnership Request: Explore Team #1473
Comments
|
@kenyonj I feel like you and I had talked about explore-feed in the past and you mentioned that it was unused? Should I retire it from the service catalog? I don't know what Marketing Crons is, but the name strikes me as being more closely related to @github/site-engineering cc @talsafran for thoughts? |
That’s correct @derekprior. explore-feed is not used anywhere and was just an experiment. |
|
|
|
@talsafran would you be willing to open a PR and link it to this issue for your team to take on ownership of marketing-crons and retire it? @derekprior would it make sense for your team to take on explore-feed and retire it, or should that also live with site-engineering? |
|
@mms710 can happily do that. So, I probably should've asked this yesterday
|
|
It makes sense for us to take explore-feed. @kenyonj - are you able to grant me access to the |
I'm trying to figure this out too! In the case of explore-feed, it seems like the moda app is alredy deprovisioned, so I think I just need to remove the ownership information from the repo? |
Just added @github/explore as admins on the github/explore-feed repo |
|
@talsafran Thanks for asking! You are absolutely correct that the next step to officially "claim" the service is to update the @derekprior is absolutely right that we don't have a playbook for how to sunset a service (yet!). I'd recommend working with your product counterparts first to determine if any customer communications are needed before you sunset the service, then tackling the engineering portion. |
We're doing the first round of follow-ups based on research that a group of senior and staff engineers did on ownership for items in the service catalog. We want to suggest/ask if your team is willing to own the following items and has the staffing to do so. It's possible that this question might arise just due to out of date documentation and you already do own these items, but we want to make sure to check in and get your team's explicit approval or disapproval because we want to make sure there's no surprises as part of this process. If you do agree to own these items, we would ask that your team updates the ownership.yaml file referenced in the service catalog to show your ownership. As a note, this is just the first round of research on the items the team felt were most critical, and we expect to do one more round once we've done a more thorough review of the remaining items.
Requests:
Due Dates:
We would ideally like to have an answer on this and a PR to fix the underlying documentation by May 15th. However, this is a short timeline so please feel free to push back if that won't work for the team.
List of Services:
(cc @derekprior )