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

Add issue templates for requesting new repository & adding new contributor #6298

Closed
planetf1 opened this issue Mar 3, 2022 · 8 comments
Closed
Assignees

Comments

@planetf1
Copy link
Member

planetf1 commented Mar 3, 2022

Add new issue templates to support the following tasks - similar to enhancement, bug, release
see odpi/egeria-docs#217 for requesting new repository
see odpi/egeria-docs#347 for adding new contributors

The templates will capture required info & provide a checklist of tasks to complete

@planetf1 planetf1 self-assigned this Mar 3, 2022
@planetf1
Copy link
Member Author

planetf1 commented Mar 3, 2022

Once complete, create new repository requests for

  • strimzi connector

@mandy-chessell
Copy link
Contributor

OK to have templates for requesting a new repo - but I would think the voting process involved in adding new contributors/maintainers should remain private to the maintainers?

@planetf1
Copy link
Member Author

planetf1 commented Mar 9, 2022

Suggestion as discussed at TSC

  • we create a new private mailing list for Egeria maintainers only
  • this is the list used for proposing a new maintainer etc
  • a github template can help with the checklist for the actions to take once the vote is complete

planetf1 added a commit to planetf1/egeria that referenced this issue Mar 16, 2022
@planetf1
Copy link
Member Author

Initial template for requesting a new repo has been added - to gather info from author, and to provide a checklist to work through. Will refine as we go through adding an entry for the new strimzi connector.

planetf1 added a commit that referenced this issue Mar 16, 2022
@planetf1
Copy link
Member Author

Review comments to be actioned in next iteration of template - from PR #6325

  • template refers to egeria docs 'Add link in egeria docs' -- this should be a link
  • under 'Release' note that the release process for the new repo should be updated in usual place (add link)
  • The assumptions is a long list, maybe better as a link to process docs. My response - we don't have the process docs yet. Checklist is a quick start. Will raise issue or add here to complete those docs

@planetf1
Copy link
Member Author

planetf1 commented Mar 16, 2022

Review comments to be actioned in next iteration of template - from PR #6325 - thanks @davidradl

  • template refers to egeria docs 'Add link in egeria docs' -- this should be a link
  • under 'Release' note that the release process for the new repo should be updated in usual place (add link)
  • The assumptions is a long list, maybe better as a link to process docs. My response - we don't have the process docs yet. Checklist is a quick start. Will raise issue or add here to complete those docs

planetf1 added a commit to planetf1/egeria that referenced this issue Mar 25, 2022
planetf1 added a commit that referenced this issue Mar 25, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label May 25, 2022
@planetf1 planetf1 removed the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label May 27, 2022
@planetf1
Copy link
Member Author

As the steps for adding a new contributor are fairly limited, and also since there may be some discussion on a private list (as for maintainers), it doesn't seem necessary to add a new template for this. So closing. See referenced issues for doc updates.

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

No branches or pull requests

2 participants