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

Proposing a Jenkins Special Interest Group process #81

Merged
merged 5 commits into from Apr 16, 2018

Conversation

@rtyler
Copy link
Member

rtyler commented Apr 11, 2018

No description provided.

@bitwiseman
Copy link
Contributor

bitwiseman commented Apr 11, 2018

@rtyler Is this a submission for approval as draft or are you asking for feedback from the community in this PR first?

Copy link
Member

batmat left a comment

Posting here typos and things probably not worth discussing on the ML.

summary of ad hoc SIG meetings to the the SIG mailing list.
* Use existing proposal and <<pull-request, PR process>>
* Announce new SIG on jenkinsci-dev@googlegroups.com
* Submit a PR to add a row for the SIG to the table in the kubernetes/community README.md file, to create a kubernetes/community directory, and to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory.

This comment has been minimized.

Copy link
@batmat

batmat Apr 11, 2018

Member

I guess you forgot to update this with Jenkins related values when copying https://github.com/kubernetes/community/blob/master/sig-governance.md

various topics, every SIG has to use multiple accounts to GitHub mentioning and
notifications. Below the procedure is explained step-by-step.

NOTE: This procedure is managed and maintained by **[@idvoretskyi](https://github.com/idvoretskyi)**; please, reach him directly in case of any questions/suggestions.

This comment has been minimized.

Copy link
@batmat
* To add the owners, visit the Group Settings (drop-down menu on the right
side), select Direct Add Members on the left side and add Sarah and Ihor via
email address (with a suitable welcome message); in Members/All Members
select Ihor and Sarah and assign to an "owner role";

This comment has been minimized.

Copy link
@batmat

batmat Apr 11, 2018

Member

same, "Ihor and Sarah" here, and above.


Name convention:

* jenkinsci-foo (the discussion group)

This comment has been minimized.

Copy link
@batmat

batmat Apr 11, 2018

Member

I'm aware this would be inconsistent with historical naming, but should we take opportunity to remove the ci suffix from jenkinsci?

[[irc]]
==== Recorded IRC Meetings

THe Jenkins project already operates a `#jenkins-meeting` channel on the

This comment has been minimized.

Copy link
@batmat

batmat Apr 11, 2018

Member

Typo THe

@rtyler
Copy link
Member Author

rtyler commented Apr 11, 2018

@batmat thanks for catching all those! I must have been pretty tired at the end of the day yesterday.

@bitwiseman I labeled this as a work-in-progress just to get the initial rounds of feedback before it's ready for @jenkinsci/jep-editors. As you may have noticed, it's not quite ready 🤦‍♂️

rtyler added 3 commits Apr 4, 2018
Thanks to @batmat for catching all my stupids.
@rtyler rtyler force-pushed the rtyler:sig-jep branch from 040924b to 6ff6a35 Apr 16, 2018
bitwiseman added 2 commits Apr 16, 2018
@bitwiseman bitwiseman merged commit a76277b into jenkinsci:master Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.