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.

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

[Partnerships] Document a short how-to guide for opening a GH issue #792

Closed
wants to merge 7 commits into from

Conversation

jnywong
Copy link
Member

@jnywong jnywong commented Jan 17, 2024

A simple how-to guide to opening a GH issue from a non-engineering perspective.


📚 Documentation preview 📚: https://2i2c-team-compass--792.org.readthedocs.build/en/792/

@jnywong jnywong requested a review from jmunroe January 17, 2024 16:32
@jnywong jnywong self-assigned this Jan 17, 2024
@jnywong jnywong added the Documentation A change to our documentation. label Jan 17, 2024
@jnywong
Copy link
Member Author

jnywong commented Jan 17, 2024

Might be worth checking with @2i2c-org/engineering if they agree that this approach works with how they organise their workflow (especially regarding assignees, I'm just going off my limited experience thus far!)

@damianavila
Copy link
Contributor

Recently, we have seen a request in support about dealing with showcase issues as any other support issue (and prioritize properly). Are these GH issues, any other issues besides support-related ones?

@jnywong
Copy link
Member Author

jnywong commented Jan 29, 2024

Recently, we have seen a request in support about dealing with showcase issues as any other support issue (and prioritize properly). Are these GH issues, any other issues besides support-related ones?

Thanks for the message @damianavila. The request is to deal with showcase issues coming from FreshDesk only like any other support issue (and prioritize properly), so that we can "simulate" the customer experience.

Other showcase GH issues, or other issues from the partnerships, should follow the existing, 2i2c-internal process I believe.

@jnywong
Copy link
Member Author

jnywong commented Feb 6, 2024

I suspect the outcome of this will depend on how we iterate on our general delivery service model going forward, so archiving this one for now.

@jnywong jnywong closed this Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation A change to our documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants