Project structure - Versionsgeschichte

Jan R.B.-Wein: /* Wiki */ Remove redundant entry.

2017-06-18T19:51:41Z

Wiki: Remove redundant entry.

Jan R.B.-Wein: /* Repository */ Add a missing closing brace.

2017-06-18T19:50:06Z

Repository: Add a missing closing brace.

Jan R.B.-Wein: /* Wiki */ Be specific and note that developers usually are those interested in understanding relations between not yet released projects.

2017-06-18T19:45:53Z

Wiki: Be specific and note that developers usually are those interested in understanding relations between not yet released projects.

Jan R.B.-Wein: /* Wiki */ Shorten, clarify. Increase formatting consistency.

2017-06-18T19:43:03Z

Wiki: Shorten, clarify. Increase formatting consistency.

Jan R.B.-Wein: /* Wiki */ Remove some unnecessary phrases.

2017-06-18T19:36:53Z

Wiki: Remove some unnecessary phrases.

Jan R.B.-Wein: /* Wiki */ Remove "if it was" because it is broken English in this context.

2017-06-18T19:33:21Z

Wiki: Remove "if it was" because it is broken English in this context.

Jan R.B.-Wein: followed -> follows

2017-06-18T19:30:55Z

followed -> follows

Jan R.B.-Wein: Add category `toolchain`.

2017-06-18T11:53:39Z

Add category `toolchain`.

Jan R.B.-Wein: Tag this pages with organization, workflow, worlddevelopment (as it uses this setup).

2017-01-02T23:04:58Z

Tag this pages with organization, workflow, worlddevelopment (as it uses this setup).

Jan R.B.-Wein: /* Forum */ Remove accidentally added forum post contents.

2017-01-02T23:00:36Z

Forum: Remove accidentally added forum post contents.

@@ Zeile 11: / Zeile 11: @@
 ==Wiki==
 * Documentation
 * Guidance, e.g. a very short outline of useful functionality modules. The wiki is a better place than base repositories because such a collection is
 ** subjective,

@@ Zeile 6: / Zeile 6: @@
 * Version control of development files.
 * Distributed development.
-* Automatic backups (due to existing on several systems of distributed developers / users.
+* Automatic backups (due to existing on several systems of distributed developers / users).
 * Integration with a versatile [[0install | release and dependency tool]].
 ==Wiki==

@@ Zeile 22: / Zeile 22: @@
 ** Somehow a connection must be created between Wiki and repositories. And such eco modules listings are one possiblity for achieving that.
-* Tagging: The projects' documentation/guidance is tagged using Wiki categories in accordance with the categories listed in the module's feed XML (if using package manager [[0install]] for release distribution). This is slightly redundant but necessary because the wiki lists ''not yet released'' projects and may serve as an overview to many people while searching for ''released'' projects should be done using the cross platform package manager.
+* Tagging: The projects' documentation/guidance is tagged using Wiki categories in accordance with the categories listed in the module's feed XML (if using package manager [[0install]] for release distribution). This is slightly redundant but necessary because the wiki lists ''not yet released'' projects and may serve as an overview to many people (mostly developers) while searching for ''released'' projects should be done using the cross platform package manager.
 ==Forum==

@@ Zeile 20: / Zeile 20: @@
 ** hard coded
 ** or a movement may want to link to a certain eco-flavored fork of a base module giving the reader guidance in what repository / release to install.
-** Tagging: Somehow a connection must be created between Wiki and repositories. And such eco modules listings are one possiblity for achieving that.
+** Somehow a connection must be created between Wiki and repositories. And such eco modules listings are one possiblity for achieving that.
-Then the projects can be tagged properly using the Wiki categories.
+* Tagging: The projects' documentation/guidance is tagged using Wiki categories in accordance with the categories listed in the module's feed XML (if using package manager [[0install]] for release distribution). This is slightly redundant but necessary because the wiki lists ''not yet released'' projects and may serve as an overview to many people while searching for ''released'' projects should be done using the cross platform package manager.
 ==Forum==

@@ Zeile 14: / Zeile 14: @@
 * As functionality modules collection/guide.
 * Documentation
-* Guidance, e.g. as a very short outline of useful functionality modules: Because each module has its own repository and thus such a collection had to be located in the base repository. The wiki is a better place because such a collection is
+* Guidance, e.g. a very short outline of useful functionality modules. The wiki is a better place than base repositories because such a collection is
 ** subjective,
 ** context dependent, e.g. eco focus versus gigantism focus, and

← Abfassung vorher		Version vom 18. Juni 2017, 19:30 Uhr
Zeile 1:		Zeile 1:
−	A project may be structured as ~~followed~~:	+	A project may be structured as follows:

@@ Zeile 34: / Zeile 34: @@
 [[Category:organization]]
 [[Category:workflow]]
 [[Category:worlddevelopment]]

← Abfassung vorher		Version vom 2. Januar 2017, 23:04 Uhr
Zeile 31:		Zeile 31:
	* news / announcements all in one location without having to create a new website for each and every project / module.		* news / announcements all in one location without having to create a new website for each and every project / module.
	* general discussion (while topic specific discussion for reference in commit messages goes into Github issues).		* general discussion (while topic specific discussion for reference in commit messages goes into Github issues).
		+
		+
		+	[[Category:organization]]
		+	[[Category:workflow]]
		+	[[Category:worlddevelopment]]

← Abfassung vorher		Version vom 2. Januar 2017, 23:00 Uhr
Zeile 31:		Zeile 31:
	* news / announcements all in one location without having to create a new website for each and every project / module.		* news / announcements all in one location without having to create a new website for each and every project / module.
	* general discussion (while topic specific discussion for reference in commit messages goes into Github issues).		* general discussion (while topic specific discussion for reference in commit messages goes into Github issues).
−
−	~~Repositories exist on [url=http://github.com/worlddevelopment]worlddevelopment github[/url] only if it fits into one of the following categories:~~
−	* club matters
−	* selection / collection of repositories (e.g. like the GVCS 50 of the OSE US but consistent, more flexible/forkable and version controlled). This is just a complementation to the Wiki that allows to add, remove all released modules of a category at once. For getting an overview of which projects are in development one should ideally get a good overview via the [url=http://wiki.opensourceecology.de/Spezial:Kategorien]category listing on the Wiki[/url].if every project on the Wiki is tagged extensively. (Currently it is inconsistent and incomplete.)
−
−	~~The repositories are collected from any eco github organization or eco individual across the world (as long as it is a hosted project, e.g. Git or 0install or a UNIX distribution package).~~
−
−	It must be admitted that worlddevelopment is not consistently using 0install for dependency handling as of now. Sometimes it is still using Git submodules which is deprecated because it is no dependency handling at all and does not allow to define a compatible version range but only one and exactly one commit.
−	~~This inconsistency is targetted.~~