Skip to content

Commit 910fbc2

Browse files
nyeatesnyeates
committed
Moved ‘Roles, Tasks, and Meetings’
Moved ‘Roles, Tasks, and Meetings’ content off to its own file; I want to simplify the CONTRIB as much as possible, yet still keep the added info when someone is interested; First and foremost, is getting a new person to contribute. This means not seeing a daunting set of initial instructions
1 parent 2439d03 commit 910fbc2

2 files changed

Lines changed: 21 additions & 22 deletions

File tree

‎CONTRIBUTING.md‎

Lines changed: 5 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,13 @@
11
# How to Contribute
22

3-
1. [Take part in our Meetings and Roles](#roles-tasks-and-meetings)
4-
2. [Add & Review patterns on Github](#add-and-review-patterns-on-github)
3+
1. [Add & Review patterns on Github](#add-and-review-patterns-on-github)
4+
2. [Take part in our Meetings and Roles](/meta/meetings.md)
55

6-
We encourage beginners seeking answers to jump in by creating ''donuts'' (filling in the problem, context, forces and resulting context fields but leaving the solution blank) as a way of asking the InnerSource Commons community for help (to find a proven solution or to brainstorm things to try). We encourage experts to pad their experience - these could easily become part of a book one day. Anyone can offer reviews and comments for [in-progress patterns](https://github.com/paypal/InnerSourcePatterns/pulls).
7-
8-
We work together via github, phone-meetings, Slack, etc. Do not hesitate to join the [#innersourcecommons](https://isc-inviter.herokuapp.com/) or #innersource-patterns slack channels and ask to be included in the patterns meetings (there is an email list).
9-
10-
[To learn about our technical github workflow, see below.](#innersource-patterns-workflow)
11-
12-
# Roles, Tasks, and Meetings
6+
# What to Help Us With
137

14-
Become involved with the people and communications of Inner Source Patterns:
15-
16-
* See our [complete list of patterns](https://docs.google.com/spreadsheets/d/17KPZdCoquTnYSj03pX4v2vn8lrSYO_6HK20u1cwaLPg/edit#gid=0) (discussed so far)
17-
* See Action Items for all who are interested in patterns:
18-
* Add any missing pattern or add new ones anytime
19-
* Add your name if you want to be on the author team. Mark your name in blue if you want to be the coordinator.
20-
* Add your name to the reviewer team if interested in the pattern
21-
* Coordinator role (per pattern): Setup meetings with pattern Authors to work through the patterns. Note the team can use Google docs or any other tool to work on the pattern. However github is the final destination for the patterns. It is recommended that github be kept as up-to-date as possible. Please keep the status and target updated for each pattern in the spreadsheet.
22-
* Every 4 weeks (or even sooner if necessary) we will have a meeting with a larger team and review the patterns.
23-
* Folks who want to join the pattern mining team but are new to this please let us know. We can bring you up to speed.
24-
25-
If you don't have access yet to the google drive shared folder, contact @thyao, @silona or @cedric on the Slack channel. They can add you to the google group. @cedric or @duane can ensure you have access to the #innersource-patterns slack channel.
8+
We encourage beginners seeking answers to jump in by creating ''donuts'' (filling in the problem, context, forces and resulting context fields but leaving the solution blank) as a way of asking the InnerSource Commons community for help (to find a proven solution or to brainstorm things to try). We encourage experts to pad their experience - these could easily become part of a book one day. Anyone can offer reviews and comments for [in-progress patterns](https://github.com/paypal/InnerSourcePatterns/pulls).
269

27-
Note: A transition from Wiki to Github is in the works. For the time being, some of both are being done until all is transferred. Default to github.
10+
We work together via Github, Webex, Slack, etc. Do not hesitate to join the [#innersourcecommons](https://isc-inviter.herokuapp.com/) or #innersource-patterns slack channels and ask to be included in the patterns meetings (there is an email list).
2811

2912

3013
# Add and Review Patterns on Github

‎meta/meetings.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Roles, Tasks, and Meetings
2+
3+
Become involved with the people and communications of Inner Source Patterns:
4+
5+
* See our [complete list of patterns](https://docs.google.com/spreadsheets/d/17KPZdCoquTnYSj03pX4v2vn8lrSYO_6HK20u1cwaLPg/edit#gid=0) (discussed so far)
6+
* See Action Items for all who are interested in patterns:
7+
* Add any missing pattern or add new ones anytime
8+
* Add your name if you want to be on the author team. Mark your name in blue if you want to be the coordinator.
9+
* Add your name to the reviewer team if interested in the pattern
10+
* Coordinator role (per pattern): Setup meetings with pattern Authors to work through the patterns. Note the team can use Google docs or any other tool to work on the pattern. However github is the final destination for the patterns. It is recommended that github be kept as up-to-date as possible. Please keep the status and target updated for each pattern in the spreadsheet.
11+
* Every 4 weeks (or even sooner if necessary) we will have a meeting with a larger team and review the patterns.
12+
* Folks who want to join the pattern mining team but are new to this please let us know. We can bring you up to speed.
13+
14+
If you don't have access yet to the google drive shared folder, contact @thyao, @silona or @cedric on the Slack channel. They can add you to the google group. @cedric or @duane can ensure you have access to the #innersource-patterns slack channel.
15+
16+
Note: A transition from Wiki to Github is in the works. For the time being, some of both are being done until all is transferred. Default to github.

0 commit comments

Comments
 (0)