docker / opensource Goto Github PK

Algolia v/s Google Search

How to find an issue by label should be documented

In https://docs.docker.com/opensource/project/set-up-dev-env/
---> Task 2. Start a development container
---> Step 7. Copy the binary to the container’s /usr/bin directory.

root@a8b2885ab900:/go/src/github.com/docker/docker# cp bundles/1.12.0-dev/binary/docker* /usr/bin

The source path of this copy command is incorrect. The directories created as part of the build artifacts are bundles/binary-client and bundles/binary-daemon.

So the command(s) should be:

root@a8b2885ab900:/go/src/github.com/docker/docker# cp bundles/1.12.0-dev/binary-client/docker* /usr/bin/

and

root@a8b2885ab900:/go/src/github.com/docker/docker# cp bundles/1.12.0-dev/binary-daemon/docker* /usr/bin/

Should go here https://github.com/docker/opensource/blob/master/docs/project/set-up-dev-env.md

Update docs to reflect new membership and working groups resulting from newest DGAB meeting: https://github.com/docker/opensource/blob/master/docs/governance/board-profiles.md

Just built the latest version of the docs and noticed minor update would be required to Organize our issues page for missing reference to Windows platform. Jump to section ===> How Do I triage ?

kitematic/kitematic     Kitematic is a simple application for managing Docker containers on Mac OS X.

should be replaced to

kitematic/kitematic     Kitematic is a simple application for managing Docker containers on Mac OS X and Windows.

This repo needs a README explaining what it is for

I noticed some PRs were merged without a sign-off, and there's no contributing.md or maintainers file present in this repository. Some boilerplating can be found here https://github.com/docker/opensource/tree/master/project-template

• Remove duplicate/redundant labels
• Remove labels which are not being used
• Make sure they are formatted using the same structure

This project needs a top level file

I've just been following the (excellent) instructions in Get the required software for Windows and when I got to step 9 from Install Go and cross-compile it, it fails with:

PS C:\go\src> .\make.bat
##### Building Go bootstrap tool.
cmd/dist
ERROR: Cannot find C:\Users\matt\Go1.4\bin\go.exe
"Set GOROOT_BOOTSTRAP to a working Go tree >= Go 1.4."

I'm running on WIndows Server 2016 TP5.

I tried to install Go 1.4 via the msi, and that uninstalled Go 1.7. I then re-installed Go 1.7, and that uninstalled Go 1.4.

https://www.docker.com/get-started

I coudent edit the web site so I made an issue here as there is no issue page for docker.com
Tnx

Problem, I went to the site to see the developer page
The page links to get-started instead

@thaJeztah

• Develop a presentation on contributing for writers
• Hold meetups for writers and deliver presentation

Create a directory containing all documents and instructions on how to setup a new repository;

• standard LICENSE and NOTICE
• CONTRIBUTING.md (including DCO instructions)
• instructions how to set up DCO check
• MAINTAINERS file
• CI config (and instructions)

Hi! Just spotted this: on http://docs.docker.com/opensource/governance/board-profiles/ Steve Francia is still listed, and Arnaud’s name has a typo (s/Poterie/Porterie/)
Board member profiles

jpetazzo [9:26 AM]
Also, for consistency, I guess the last section (“User”) should at least be “Users” since all other sections are plural

@thaJeztah ^^ (not urgent)

We should have a central readme for documentation contributors and then included it in every project/docs. README should cover these topics which we all agree on:

• 80 character wrap is standard across the projects
• Gists process is preferred over line-by-line commentary
• After Gist round if a user just cut-n-paste but no formatting: pull and carry formatting fix
• Editing directly in Git while easy to do; follow on changes can quickly overwhelm the newbie user who is gravitates to it (Thea)

It's hard for people be active on multiple chat channels. Maybe decide on one and stop using others

We should have a repository that new contributors can use to create pull-requests on, to learn the contributing procedures. The "contributing guide" should use that repository in the examples (to prevent users from accidentally creating PRs against the "real" repositories).

Gordon/Leeroy can automatically respond to those PR's, and do fun things like "congratulate" them on a successful pull request, teach how to sign-off commits, rebase, etc.

For some background, see moby/moby#17330 (comment)

/cc @moxiegirl @SvenDowideit

Should they be merged?