PR#5: A lot of changes again - fedora-docs/modularity

Adam Samalik • 6 years ago

2b89942

Adam Samalik • 6 years ago

9fac050

Adam Samalik • 6 years ago

22c518b

Adam Samalik • 6 years ago

bf5351a

_topic_map.yml

file modified

+2 -2

		`@@ -42,8 +42,8 @@`
		`File: Building_Software`
		`- Name: Consuming Software`
		`File: Consuming_Software`
		`- - Name: For Modularity Contributors`
		`- Dir: contributors`
		`+ - Name: Community`
		`+ Dir: community`
		`Topics:`
		`- Name: Communication`
		`File: Communication`

en-US/Making_Modules.adoc

file modified

		`@@ -1,5 +1,7 @@`
		`= Making Modules`

		`+ NOTE: This page is a placeholder. You can make this page more useful by submitting a pull-request to https://pagure.io/fedora-docs/modularity/`
		`+`
		`== Overview of module files`

		`explain module.yaml, what it should be named, what the branch should be called, where to find the spec, some example`

en-US/References.adoc

file modified

+11 -4

		`@@ -1,7 +1,14 @@`
		`= References`

		`- == modulemd specification`
		`+ https://pagure.io/modulemd[Module metadata definitions (modulemd)]::`
		`+ A modulemd file is used to define a module, and also to provide metadata for the end result. This is a specification of the file.`
		`+ We are currently on version 1 of the specification with version 2 due very soon.`

		`- The format of the module definition, referred to as a "modulemd" or "module yaml," is specified by the https://pagure.io/modulemd[modulemd Pagure repository].`
		`- See link:Making_Modules.html#overview-of-module-files[Making Modules] for more details on how to name this file.`
		`- We are currently on version 1 of the specification with version 2 due very soon.`
		`\ No newline at end of file`
		`+ https://pagure.io/modularity/issues[General issue tracker for Modularity]::`
		`+ General issues that are tracked here.`
		`+`
		`+ https://pagure.io/group/modularity[Modularity on Pagure]::`
		`+ Pagure is the default place for most of our git repositories.`
		`+`
		`+ https://github.com/fedora-modularity/[Modularity on GitHub]::`
		`+ GitHub is an alternative place for some of our repositories.`

en-US/Using_Modules.adoc

file modified

		`@@ -1,5 +1,7 @@`
		`= Using Modules in Fedora`

		`+ NOTE: This page is a placeholder. You can make this page more useful by submitting a pull-request to https://pagure.io/fedora-docs/modularity/`
		`+`
		`== Enable Modularity on Fedora 28`

		`how do you turn on the modular repo? is it there by default?`

en-US/architecture/Main_Concepts.adoc

file modified

+1 -1

		`@@ -55,7 +55,7 @@`
		`image::mod-doc-stream.png[,80%,]`

		`A stream is a series of versions having a goal such as backwards API/ABI compatibility or delivering the latest stable version.`
		`- A “nodejs” interpreter can have streams such as “https://src.fedoraproject.org/modules/nodejs/branch/6[6]” or “https://src.fedoraproject.org/modules/nodejs/branch/8[8]” (two current versions of nodejs), but also “devel” or “latest”.`
		`+ A “nodejs” interpreter can have streams such as https://src.fedoraproject.org/modules/nodejs/branch/6[6] or https://src.fedoraproject.org/modules/nodejs/branch/8[8] (two current versions of nodejs), but also “devel” or “latest”.`
		`Some packages don’t have a major version.`
		`An example could be the “calc” package that is being developed in two branches “stable” and “unstable”.`