Skip to content
Permalink
Browse files

Merge pull request #111 from StingRayZA/moving-wiki

Fixing a couple of non-relative links & moved wiki links to new InnerSourceCommons location
  • Loading branch information...
lenucksi committed Mar 28, 2019
2 parents 6ebd093 + 3d56d81 commit 5f42f1b37c9f7a60b946e31a9f3b0946acc87b6c
Showing with 24 additions and 24 deletions.
  1. +11 −11 README.md
  2. +1 −1 meta/FAQ.md
  3. +2 −2 meta/markdown-info.md
  4. +1 −1 meta/meetings.md
  5. +1 −1 meta/pattern-states.md
  6. +2 −2 meta/publishing.md
  7. +6 −6 meta/technical-git-howto.md
@@ -30,8 +30,8 @@ possible to either deploy the same service in independent environments with sepa
* [Cross-Team Project Valuation](crossteam-project-valuation.md) - *It's hard to sell the value of cross-team, inner sourced projects that don't provide a direct impact on company revenue. Here's a data-driven way to represent your project that both articulates its value and amplifies it.*
* [Reluctance to Receive Contributions](https://docs.google.com/document/d/13QDN-BpE_BixRFVGjao32n4Ctim0ROXAHbBWMBOijb4/edit) - *Core owner of shared asset is reluctant to take contributions due to the required maintenance that comes with them.*
* [What Before How or Services Documentation](https://docs.google.com/document/d/1_N1wsQeDusfIcNy-O2ZXenY3PL7ZbvkUDRZxGUuegZw/edit?usp=drive_web) - *A lack of common understanding between different management tiers creates funding barriers and increases the risk that solutions will not deliver required business outcomes.*
* [Overcome Acquisition Based Silos - Developers](https://github.com/paypal/InnerSourceCommons/wiki/Overcome-Acquisition-based-Silos)
* [Overcome Acquisition Based Silos - Managers](https://github.com/paypal/InnerSourceCommons/wiki/Overcome-Acquisition-based-Silos)
* [Overcome Acquisition Based Silos - Developers](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Overcome-Acquisition-based-Silos)
* [Overcome Acquisition Based Silos - Managers](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Overcome-Acquisition-based-Silos)
* [Open Source Trumps InnerSource](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/46) - *People find the InnerSource project but, after all things are considered, even if the InnerSource component meets their needs, they still go with the open source component.*
* [Overcoming Project Management Time Pressures](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/47) - *Project management believes timeline pressure and commitments on feature content does not allow for developers to spend the time needed to develop shareable code and provide support.*
* [Start as Experiment](start-as-experiment.md) - *An inner source initiative is considered but not started, because management is unsure about its outcome and therefore unwilling to commit to the investment.*
@@ -41,18 +41,18 @@ possible to either deploy the same service in independent environments with sepa

* [Don't Bother Looking](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/60)
* [Junkyard Styled Inner Sourcing](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/61)
* [Shared Code Repo Different from Build Repo](https://github.com/paypal/InnerSourceCommons/wiki/Shared-Code-Repo-Different-from-Build-Repo) - *Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.*
* [Incentive Alignment](https://github.com/paypal/InnerSourceCommons/wiki/Donut:-Creating-Developer-Incentive-Alignment-for-InnerSource-Contribution)
* [Change the Developers Mindset](https://github.com/paypal/InnerSourceCommons/wiki/Pattern:-change-the-developers-mindset)
* [Share Your Code to Get More Done - Likely Contributors Variant](https://github.com/paypal/InnerSourceCommons/wiki/Pattern:-Share-Your-Code-to-Get-More-Done---Likely-Contributors-Variant)
* [Shared Code Repo Different from Build Repo](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Shared-Code-Repo-Different-from-Build-Repo) - *Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.*
* [Incentive Alignment](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut:-Creating-Developer-Incentive-Alignment-for-InnerSource-Contribution)
* [Change the Developers Mindset](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Pattern:-change-the-developers-mindset)
* [Share Your Code to Get More Done - Likely Contributors Variant](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Pattern:-Share-Your-Code-to-Get-More-Done---Likely-Contributors-Variant)

#### Pattern Donuts (needing a solution)

* [Donut 3: How to Defeat the Hierarchical Constraints](https://github.com/paypal/InnerSourceCommons/wiki/Donut-3%3A-how-to-defeat-the-hierarchical-constraints)
* [Donut 5: Project Management Time Pressures](https://github.com/paypal/InnerSourceCommons/wiki/Donut-5:-project-management-time-pressures)
* [Donut 6: Organizational Mindset Change](https://github.com/paypal/InnerSourceCommons/wiki/Donut-6:-organizational-mindset-change)
* [Donut 8: Not Invented Here](https://github.com/paypal/InnerSourceCommons/wiki/Donut-8:-Not-invented-here)
* [Donut: Bad Weather For Liftoff](https://github.com/paypal/InnerSourceCommons/wiki/Donut:-Bad-weather-for-liftoff)
* [Donut 3: How to Defeat the Hierarchical Constraints](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-3%3A-how-to-defeat-the-hierarchical-constraints)
* [Donut 5: Project Management Time Pressures](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-5:-project-management-time-pressures)
* [Donut 6: Organizational Mindset Change](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-6:-organizational-mindset-change)
* [Donut 8: Not Invented Here](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-8:-Not-invented-here)
* [Donut: Bad Weather For Liftoff](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut:-Bad-weather-for-liftoff)
* [Get Contributions Despite Silo Thinking](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/38)


@@ -1,7 +1,7 @@
This is a list of frequently asked questions about InnerSource Patterns

## What are the different parts of a pattern? What do they mean?
* See the [pattern template](https://github.com/paypal/InnerSourcePatterns/blob/master/meta/pattern-template.md) (in the *meta* subdirectory)
* See the [pattern template](meta/pattern-template.md) (in the *meta* subdirectory)

## Why use a patterns approach to InnerSource?
* It abstracts information from known instances of proven solutions so that other people/companies can understand not only what was done by why it worked and how to adapt it to their own situations.
@@ -2,7 +2,7 @@

A markdown file is a plain ASCII text file that is meant to be easy to read in plaintext, while also being pretty once rendered.

It is similar to the format that many wiki's have. As an example, you can see [this rendered pattern](https://github.com/paypal/InnerSourcePatterns/blob/master/dedicated-community-leader.md) of ours also [in plain text](https://raw.githubusercontent.com/paypal/InnerSourcePatterns/master/dedicated-community-leader.md). You can do this for any markdown file by clicking the ``Raw`` button when viewing a file online.
It is similar to the format that many wiki's have. As an example, you can see [this rendered pattern](dedicated-community-leader.md) of ours also [in plain text](/../../raw/master/dedicated-community-leader.md). You can do this for any markdown file by clicking the ``Raw`` button when viewing a file online.

The ASCII is marked up in a standard format. Here are two cheatsheets for that format:

@@ -14,4 +14,4 @@ You can test your markdown on these online "live" editors:
* http://socrates.io/
* https://jbt.github.io/markdown-editor/

If you have content in Word or Google docs, you can simply copy the existing text and paste it in to plain text, and then modify the titles and bullets to be in markdown format. There might be a converter.
If you have content in Word or Google docs, you can simply copy the existing text and paste it in to plain text, and then modify the titles and bullets to be in markdown format. There might be a converter.
@@ -2,7 +2,7 @@

Become involved with the people and communications of Inner Source Patterns:

* See our [complete list of patterns](https://github.com/paypal/InnerSourcePatterns/#list-of-patterns) (written, discussed, reviewed so far)
* See our [complete list of patterns](/README.md#list-of-patterns) (written, discussed, reviewed so far)
* See Action Items for all who are interested in patterns:
* Add any missing pattern or add new ones anytime
* Add your name if you want to be on the author team. Mark your name in blue if you want to be the coordinator.
@@ -32,6 +32,6 @@ I kept "Donut" as I tried a couple meaningful names, but it just sounds too catc

The "Review Steps" refer to what needs to be done NEXT. This keeps reviews on track and knowing what comes next.

The numbering / order helps on Github to visualize and keep reviewers on track. The coloring also helps with visualization. Go check it out live: https://github.com/paypal/InnerSourcePatterns/pulls
The numbering / order helps on Github to visualize and keep reviewers on track. The coloring also helps with visualization. [Go check it out live](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls)

"Early Idea" tag is for Issues where very initial or place holder ideas can be placed. "Non-Pattern" can be used for meta Pull Requests such as edits to README.md.
@@ -33,5 +33,5 @@ contains the sources for the GitHub pages website for innersourcecommons.org.


[commons]: http://innersourcecommons.org
[patternsRepo]: https://github.com/paypal/InnerSourcePatterns
[commonsRepo]: https://github.com/paypal/InnerSourceCommons
[patternsRepo]: https://github.com/InnerSourceCommons/InnerSourcePatterns
[commonsRepo]: https://github.com/InnerSourceCommons/innersourcecommons.org
@@ -1,16 +1,16 @@
# Command-line git steps for creating a new Pattern

If you want to contribute a new pattern, the workflow is done through Branches and Pull Requests (PR's). You can see the available branches on [the branches URL](https://github.com/paypal/InnerSourcePatterns/branches/all) and existing PR's on the [Pull Request page](https://github.com/paypal/InnerSourcePatterns/pulls). Branches are meant to separate content, so that multiple people can work all at once. Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern.
If you want to contribute a new pattern, the workflow is done through Branches and Pull Requests (PR's). You can see the available branches on [the branches URL](https://github.com/InnerSourceCommons/InnerSourcePatterns/branches/all) and existing PR's on the [Pull Request page](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls). Branches are meant to separate content, so that multiple people can work all at once. Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern.

There are indeed multiple ways to start a discussion:

* Send a Pull Request for your branch and the maintainers will receive a notification.
* Create an Issue and ask for comments from some of the maintainers. You can mention them using the '@' symbol prior to their github nickname.
* Add reviewers to the Pull Request on the website - this sends requests to review your work

New patterns should use, as their base, the [pattern template file](https://raw.githubusercontent.com/paypal/InnerSourcePatterns/master/meta/pattern-template.md).
New patterns should use, as their base, the [pattern template file](meta/pattern-template.md).

Please, when starting a new pattern, make sure that it does not already exist. Take a look at some of the [existing patterns in this repository](https://github.com/paypal/InnerSourcePatterns#reviewed-patterns-proven-and-reviewed).
Please, when starting a new pattern, make sure that it does not already exist. Take a look at some of the [existing patterns in this repository](/README.md#reviewed-patterns-proven-and-reviewed).

## Overview of steps

@@ -24,7 +24,7 @@ The basic steps below can be thought of as *branch*, *commit*, *pull request*, a
First you need to create a branch (no need to ask for permission!). For this, let's clone the repository:

```
$ git clone https://github.com/paypal/InnerSourcePatterns.git
$ git clone https://github.com/InnerSourceCommons/InnerSourcePatterns.git
```

Then you should see a message similar to the following one:
@@ -87,7 +87,7 @@ $ git checkout -b pattern/ewoks-do-not-hunt
$ touch ewoks-do-not-hunt.md
```

You can fill your [markdown](/meta/markdown-info.md) file with the [pattern template text](https://raw.githubusercontent.com/paypal/InnerSourcePatterns/master/meta/pattern-template.md) and begin to fill it in with your pattern.
You can fill your [markdown](meta/markdown-info.md) file with the [pattern template text](meta/pattern-template.md) and begin to fill it in with your pattern.

Once our pattern file is ready to go, we need to add the file to the repo and
commit that change to our new branch.
@@ -105,4 +105,4 @@ $ git push origin pattern/ewoks-do-not-hunt

Then, if you feel the pattern is ready to be reviewed, you can start a Pull Request (PR) asking to join your new branch to the github master branch. To do this, navigate to the github web repo and get into your new branch. You should see a 'Create pull request' button while in your branch.

PR's are the mechanism we use for our multi-step Review process. See next steps in [Interacting with Pattern Reviews](/CONTRIBUTING.md#c-interacting-with-patterns-reviews).
PR's are the mechanism we use for our multi-step Review process. See next steps in [Interacting with Pattern Reviews](/CONTRIBUTING.md#c-interacting-with-patterns-reviews).

0 comments on commit 5f42f1b

Please sign in to comment.
You can’t perform that action at this time.