first

course/12-local_development/exercises/2a-package_naming/multiple_choice.json

@@ -0,0 +1,10 @@
+{
+  "question": "Given the import path of path/to/rand, which of these is a valid package name?",
+  "answers": [
+    "Any of these",
+    "path",
+    "rand",
+    "random",
+    "spam"
+  ]
+}

course/12-local_development/exercises/2a-package_naming/readme.md

@@ -0,0 +1,21 @@
+# Package Naming
+
+## Naming Convention
+
+By *convention*, a package's name is the same as the last element of its import path. For instance, the `math/rand` package comprises files that begin with:
+
+```go
+package rand
+```
+
+That said, package names aren't *required* to match their import path. For example, I could write a new package with the path `github.com/mailio/rand` and name the package `random`:
+
+```go
+package random
+```
+
+While the above is possible, it is discouraged for the sake of consistency.
+
+## One Package / Directory
+
+A directory of Go code can have **at most** one package. All `.go` files in a single directory must all belong to the same package. If they don't an error will be thrown by the compiler. This is true for main and library packages alike.