Category:OpenDevOps - Revision history

RobertBushman at 17:07, 9 November 2021

2021-11-09T17:07:43Z

← Older revision		Revision as of 17:07, 9 November 2021
Line 11:		Line 11:
	# Network-enabled office suite, for collaborative document development.		# Network-enabled office suite, for collaborative document development.
	# Real office suite, for making high quality docs.		# Real office suite, for making high quality docs.
			# Calendar Server
	# Source code repository, for version control.		# Source code repository, for version control.
	# Ticket tracker, for change requests.		# Ticket tracker, for change requests.

RobertBushman at 19:08, 7 February 2021

2021-02-07T19:08:06Z

← Older revision		Revision as of 19:08, 7 February 2021
Line 14:		Line 14:
	# Ticket tracker, for change requests.		# Ticket tracker, for change requests.
	# Kanban board, for project tracking.		# Kanban board, for project tracking.
	# Mind Mapping, preferably shared, networked.		# [[Mind Mapping]], preferably shared, networked.

	And there is one thing that Open Source can do better than proprietary: Platform Interoperation.		And there is one thing that Open Source can do better than proprietary: Platform Interoperation.

RobertBushman at 19:06, 7 February 2021

2021-02-07T19:06:33Z

← Older revision		Revision as of 19:06, 7 February 2021
Line 14:		Line 14:
	# Ticket tracker, for change requests.		# Ticket tracker, for change requests.
	# Kanban board, for project tracking.		# Kanban board, for project tracking.
			# Mind Mapping, preferably shared, networked.

	And there is one thing that Open Source can do better than proprietary: Platform Interoperation.		And there is one thing that Open Source can do better than proprietary: Platform Interoperation.

RobertBushman at 23:56, 25 January 2021

2021-01-25T23:56:24Z

← Older revision		Revision as of 23:56, 25 January 2021
Line 21:		Line 21:
	In Open Source world, anyone working on any piece of OpenDevOps can work on them all, or they can talk with counterpart engineers in an open forum without having to sign NDAs, and with the ability to point to specific lines of code or revision diffs. Open Source encourages development of interoperability in a way that proprietary software cannot.		In Open Source world, anyone working on any piece of OpenDevOps can work on them all, or they can talk with counterpart engineers in an open forum without having to sign NDAs, and with the ability to point to specific lines of code or revision diffs. Open Source encourages development of interoperability in a way that proprietary software cannot.

	[[Category:~~OpenDevOps~~]]		[[Category:Hacking]]

RobertBushman at 23:55, 25 January 2021

2021-01-25T23:55:45Z

← Older revision		Revision as of 23:55, 25 January 2021
Line 20:		Line 20:

	In Open Source world, anyone working on any piece of OpenDevOps can work on them all, or they can talk with counterpart engineers in an open forum without having to sign NDAs, and with the ability to point to specific lines of code or revision diffs. Open Source encourages development of interoperability in a way that proprietary software cannot.		In Open Source world, anyone working on any piece of OpenDevOps can work on them all, or they can talk with counterpart engineers in an open forum without having to sign NDAs, and with the ability to point to specific lines of code or revision diffs. Open Source encourages development of interoperability in a way that proprietary software cannot.

			[[Category:OpenDevOps]]

RobertBushman at 23:46, 25 January 2021

2021-01-25T23:46:49Z

← Older revision		Revision as of 23:46, 25 January 2021
Line 14:		Line 14:
	# Ticket tracker, for change requests.		# Ticket tracker, for change requests.
	# Kanban board, for project tracking.		# Kanban board, for project tracking.

			And there is one thing that Open Source can do better than proprietary: Platform Interoperation.

			Proprietary software has an inherent limitation in the ability to do network-based interoperation. Their software cannot interoperate as easily as Open Source because engineers from Microsoft who need a feature in an Adobe product can't just jump into the code and make the change. They can't even go randomly looking around at Adobe's code to see what integration would look like - it's proprietary.

			In Open Source world, anyone working on any piece of OpenDevOps can work on them all, or they can talk with counterpart engineers in an open forum without having to sign NDAs, and with the ability to point to specific lines of code or revision diffs. Open Source encourages development of interoperability in a way that proprietary software cannot.

RobertBushman at 23:40, 25 January 2021

2021-01-25T23:40:22Z

← Older revision		Revision as of 23:40, 25 January 2021
Line 5:		Line 5:
	A DevOps ecosystem for remote teams includes a number of components:		A DevOps ecosystem for remote teams includes a number of components:

	1. Forum server, for discussing topics that evolve over days or weeks.		# Forum server, for discussing topics that evolve over days or weeks.
	1. Chat system, for immediate interaction.		# Chat system, for immediate interaction.
	1. Videoconferencing, for video interaction.		# Videoconferencing, for video interaction.
	1. Wiki server, for long-term evolving information provision.		# Wiki server, for long-term evolving information provision.
	1. Network-enabled office suite, for collaborative document development.		# Network-enabled office suite, for collaborative document development.
	1. Real office suite, for making high quality docs.		# Real office suite, for making high quality docs.
	1. Source code repository, for version control.		# Source code repository, for version control.
	1. Ticket tracker, for change requests.		# Ticket tracker, for change requests.
	1. Kanban board, for project tracking.		# Kanban board, for project tracking.

RobertBushman at 23:39, 25 January 2021

2021-01-25T23:39:54Z

← Older revision		Revision as of 23:39, 25 January 2021
Line 4:		Line 4:

	A DevOps ecosystem for remote teams includes a number of components:		A DevOps ecosystem for remote teams includes a number of components:

	1. Forum server, for discussing topics that evolve over days or weeks.		1. Forum server, for discussing topics that evolve over days or weeks.
	1. Chat system, for immediate interaction.		1. Chat system, for immediate interaction.

RobertBushman: Created page with "As software engineering has become increasingly complex, the Open Source ecosystem has evolved along with it. From the early days with an open source set of command line tools..."

2021-01-25T23:39:32Z

Created page with "As software engineering has become increasingly complex, the Open Source ecosystem has evolved along with it. From the early days with an open source set of command line tools..."

New page

As software engineering has become increasingly complex, the Open Source ecosystem has evolved along with it. From the early days with an open source set of command line tools, developer libraries, and an OS kernel, through the development of network services, and on to desktop applications like LibreOffice, GIMP, and KDEnlive. I think the next "most important battleground" is enterprise application development.

To develop enterprise grade software, you need a suite of applications that work together. To continue bringing engineers into Open Source development, the tools engineers are using on a day-to-day basis to be Open Source. If we cannot demonstrate, in the office, that Open Source produces viable software, it is hard to make the case that it is. Conversely, if engineers are using and relying on Open Source every day, they will be more inclined to see it is an important thing in their lives, and they will be more likely to contribute.

A DevOps ecosystem for remote teams includes a number of components:
1. Forum server, for discussing topics that evolve over days or weeks.
1. Chat system, for immediate interaction.
1. Videoconferencing, for video interaction.
1. Wiki server, for long-term evolving information provision.
1. Network-enabled office suite, for collaborative document development.
1. Real office suite, for making high quality docs.
1. Source code repository, for version control.
1. Ticket tracker, for change requests.
1. Kanban board, for project tracking.