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

docs: add contribution guide and update readme #143

Open
wants to merge 1 commit into
base: staging
Choose a base branch
from

Conversation

pythonpete32
Copy link
Contributor

@pythonpete32 pythonpete32 commented Jan 8, 2024

Description

  • add Contribution Guidelines
  • update Readme

Task: DX-59

Copy link
Contributor

@heueristik heueristik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This contribution guide assumes that there are issues for certain tasks being labeled properly that contributors can take over. However, our task planning and creation is generally done in JIRA.

Is the plan to move away from JIRA for the dev portal and use GH issues?

CONTRIBUTION_GUIDE.md Show resolved Hide resolved
@pythonpete32
Copy link
Contributor Author

This contribution guide assumes that there are issues for certain tasks being labeled properly that contributors can take over. However, our task planning and creation is generally done in JIRA.

Is the plan to move away from JIRA for the dev portal and use GH issues?

no but the task requested to add contribution guidelines. I believe the goal is more to allow external people to fix small bugs or maybe to add tutorials (i know we dont have a tutorials section yet). JIRA will still be the tool we use internally. AFAIK our JIRA is private

@heueristik
Copy link
Contributor

I don't see how this will lead to satisfying contributions if the tasks backlog is not visible to external collaborators and does not have "good first issue" labels.

Maybe an automated syncing between JIRA and developer portal related tasks is the answer. This is a general problem I see with all our repos: They are not really open/friendly to external collaborators because our backlog is not visible.

The PR itself LGTM so I'll approve this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants