Removed dupe of contribution guidelines

Signed-off-by: Usha Mandya <usha.mandya@docker.com>

_data/toc.yaml

@@ -18,7 +18,6 @@ horizontalnav:
 - title: Contribute
   path: /contribute/overview/
   node: contribute
-  # TODO unify navbbar links: homepage currently has a custom "articles" link
   hide_home: true
 
 home: {}
@@ -376,8 +375,6 @@ guides:
         title: Use the VFS storage driver
 - path: /get-started/resources/
   title: "Educational resources"
-- path: /opensource/
-  title: "Contribute to documentation"
 
 reference:
 - path: /reference/

_layouts/landing.html

@@ -21,8 +21,7 @@
         {%- for entry in site.data.toc.horizontalnav -%}
           {%- if entry.hide_home -%}{% continue %}{%- endif -%}
           <li{% if entry.node == "home" %} class=active{% endif %}><a href="{{ entry.path }}" id="{{ entry.node }}">{{ entry.title }}</a></li>
-        {%- endfor -%}
-        <li><a href="https://www.docker.com/blog/">Articles</a></li>  
+        {%- endfor -%} 
         <li><a href="/contribute/overview/">Contribute</a></li>
         </ul>
         <ul class="nav navbar-nav navbar-right">

contribute/overview.md

@@ -3,6 +3,7 @@ title: Contribute to Docker's docs
 toc_max: 1
 redirect_from:
 - /CONTRIBUTING/
+- /opensource/
 ---
 
 We deeply value documentation contributions from the Docker community. We'd like to make it as easy

opensource/index.md

@@ -1,75 +0,0 @@
----
-description: Contribute to Docker documentation
-keywords: Docker documentation, contributing, overview
-title: Contribute to documentation
-redirect_from:
-- /contributing/
-- /contributing/contributing/
-- /opensource/code/
-- /opensource/project/who-written-for/
-- /opensource/project/software-required/
-- /opensource/project/software-req-win/
-- /opensource/project/set-up-git/
-- /opensource/project/set-up-dev-env/
-- /opensource/project/test-and-docs/
-- /opensource/project/who-written-for/
-- /opensource/workflow/advanced-contributing/
-- /opensource/workflow/
-- /opensource/workflow/coding-style/
-- /opensource/workflow/create-pr/
-- /opensource/workflow/find-an-issue/
-- /opensource/workflow/make-a-contribution/
-- /opensource/workflow/review-pr/
-- /opensource/workflow/work-issue/
-- /opensource/FAQ/
-- /opensource/get-help/
-- /opensource/code/
-- /opensource/doc-style/
-- /opensource/governance/
-- /opensource/governance/dgab-info/
-- /opensource/governance/board-profiles/
-- /opensource/governance/conduct-code/
-
----
-
-Contributing to the Docker documentation can be a rewarding experience. When you
-offer feedback, questions, edits, or new content, you help us, the projects you
-work on, and the larger Docker community. Feel free to create pull requests and
-file issues. Our docs are completely open source and we deeply appreciate
-contributions from the Docker community!
-
-## Provide feedback
-
-We’d love to hear your feedback. Please file documentation issues only in the
-docs GitHub repository. You can file a new issue to suggest improvements or if
-you see any errors in the existing documentation.
-
-Before submitting a new issue, check whether the issue has already been
-reported. You can join the discussion using an emoji, or by adding a comment to
-an existing issue. If possible, we recommend that you suggest a fix to the issue
-by creating a pull request.
-
-You can ask general questions and get community support through the [Docker
-Community Slack](http://dockr.ly/slack). Personalized support is available
-through the Docker Pro, Team, and Business subscriptions. See [Docker
-Pricing](https://www.docker.com/pricing) for details.
-
-If you have an idea for a new feature or behavior change in a specific aspect of
-Docker, or have found a product bug, file that issue in the project's code
-repository.
-
-We've made it really easy for you to file new issues.
-
-- Click **New issue** on the docs repository and fill in the details, or
-- Click **Request docs changes** in the right column of every page
-  and add the details.
-
-![Docs feedback on each page](/opensource/images/docs-site-feedback.png)
-
-## Contribute to Docker docs
-
-We value your contribution. We'd like to make it as easy as possible to submit
-your contributions to the Docker docs repository. Changes to the docs are
-handled through pull requests against the `master` branch. To learn how to
-contribute, see the
-[Contribution guidelines](../contribute/overview.md).

opensource/ways.md

@@ -1,129 +0,0 @@
----
-description: How to support the Docker community, organize meetups, or become a mentor
-keywords: meetups, community, mentoring
-title: Other ways to contribute
-redirect_from:
-- /opensource/ways/community/
-- /opensource/ways/meetups/
-- /opensource/ways/issues/
-- /opensource/ways/test/
-- /project/who-written-for/
-- /project/make-a-contribution/
----
-
-Beyond the documentation contributions we cover here, there are many other ways
-to contribute to Docker. Whether you are just getting started or are expert in
-your field, you have a unique perspective that is a valuable resource to share
-with others. The Docker community, meetups, mentoring, and open source projects
-all need your participation, ideas, feedback, and vision.
-
-* [Organize a Docker meetup](#organize-a-docker-meetup)
-* [Learn about the Docker Community](#learn-about-the-docker-community)
-* [Contribute to the Moby open source project](#contribute-to-the-moby-open-source-project)
-
-## Organize a Docker meetup
-
-Anyone interested in Docker can become an active member of the Docker community
-by becoming a co-organizer of a Docker Meetup group.
-
-If a Meetup group does not already exist in your area and you are willing to
-start a new one, the best way to proceed is to contact us so that we can create
-it for you, as long as it makes sense geographically speaking.
-
-If you have already created a Docker Meetup group that is fine, we
-ask you to add us as a co-organizer so that we can ensure a consistent support
-to the group in terms of community and Meetup management.
-
-Before contacting us to create a new Docker Meetup Group, take a look at our
-Meetup Groups page to make sure a group does not already exist in the area.
-
-### Get started putting on a Docker Meetup
-
-Now that you are a co-organizer of a Docker Meetup Group, here are a few tips and
-suggestions to help you get started:
-
-* Attend similar DevOps or Developers Meetups to gain experience and gauge interest in Docker
-* Contact other people interested in Docker to help you organize and promote future Meetups
-* Research High-Tech companies in your area willing to host a Docker Meetup event
-* Research what would be the best date(s) to schedule the Meetups based on availabilities with regard to competing events in the area and other calendar imperative
-* Research what are the topic of interest to your audience prior to set an agenda for the meetup
-* Pay attention to the Meetup page aesthetics, add logos and pictures, invite members to leave comments and reply to these comments
-* Promote the event on social media and make sure that the list of keywords is well define if you have created the Docker Meetup Group on your own
-
-### How Docker can help you organize
-
-We can support the co-organizers of the Docker Meetup Groups based on their specific needs. For instance, we might be able to:
-
-* Send you Docker T-shirts and stickers
-* Put you in contact with other people interested in being a co-organizer of a Docker Meetup group, and which are in the same area
-* Put you in contact with companies willing to host a Docker Meetup in your area
-* Introduce you to people willing to give a lightning talk about Docker
-* Promote your Docker Group on Docker.com, Docker Weekly and Social Media
-  Hackday Picture
-
-### Host a Docker meetup at your location
-
-![Meetup](../assets/images/docker-friends.png)
-
-### Want to host a Docker Meetup?
-
-We are always looking for new office space to host Docker Meetups. If your
-company is willing to host a Docker Meetup, contact us by email at
-meetup@docker.com. Previous Docker Meetups have been hosted by companies such
-as Rackspace, Twitter, MongoDB, BrightCove, DigitalOcean, Viadeo and Edmodo.
-#### How many attendees?
-
-The company hosting the event fixes the number of attendees depending on their
-office size and availability. This number usually varies between 30 and 200.
-
-#### How long is a Docker Meetup?
-
-Once again, each company hosting the event decides when does the meetup start,
-and how long it lasts. Usual meetups tend to last 2 hours, and start between
-4pm and 6pm.
-
-## Learn about the Docker Community
-
-Go to the **[Docker Community GitHub repository](https://github.com/docker/community/blob/master/README.md){:target="_blank" rel="noopener" class="_"}**
-for resources and information on the community. Those pages are the most
-up-to-date for finding out about the community and making connections.
-
-The topics below provide some additional links, but it's likely that everything
-you need is on the GitHub repository.
-
-### Become a Mentor
-
-With millions of Docker users all over the world, there's always someone who
-needs a helping hand. Like many open source projects, the Docker project relies
-on community support channels like forums, IRC, and StackOverflow.  You should
-contribute mentoring if you have good knowledge of:
-
-* how open source projects run
-* using Docker in some particular domain (for example, testing or deployment)
-* using Git, Go, GitHub, IRC, or other common tools
-
-Also, choose mentoring if you like to be happy. Studies show that [helping others](https://www.huffpost.com/entry/five-minute-favor-adam-rifkin_n_3805090){: target="_blank" rel="noopener" class="_"} is a great way to
-boost your own well being.
-
-
-### Docker users
-
-Docker users are people using Docker in their daily work. To help Docker users, visit:
-
-* the [Docker community Slack channel](https://dockr.ly/slack){: target="_blank" rel="noopener" class="_"}
-* the [Docker Community Forum](https://forums.docker.com/){: target="_blank" rel="noopener" class="_"}
-* [StackOverflow](https://stackoverflow.com/questions/tagged/docker){: target="_blank" rel="noopener" class="_"}
-
-You can also check the lists of [open issues on the Docker docs]({{ site.repo }}/issues){: target="_blank" rel="noopener" class="_"} and [open issues on the Moby project](https://github.com/moby/moby/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fquestion+-label%3Astatus%2Fclaimed+-label%3Astatus%2Fassigned+no%3Aassignee){: target="_blank" rel="noopener" class="_"}.
-
-
-### Docker contributors
-
-Docker contributors are people like you, interested in the open source projects
-and product documentation. Contributors may need help with IRC, Go programming,
-Markdown, or with other aspects of contributing. To help Docker contributors,
-join the [Docker community Slack channel](https://dockr.ly/slack){: target="_blank" rel="noopener" class="_"}.
-
-## Contribute to the Moby open source project
-
-{% include content/moby.md %}

registry/help.md

@@ -13,4 +13,3 @@ If you want to report a bug:
 - be sure to first read about [how to contribute](https://github.com/distribution/distribution/blob/master/CONTRIBUTING.md).
 - you can then do so on the [GitHub project bugtracker](https://github.com/distribution/distribution/issues).
 
-You can also find out more about the Docker's project [Getting Help resources](../opensource/ways.md).