Adam Hyde + Kathi Fletcher - Revision history

Marcin: /* OSE */

2012-03-30T17:13:33Z

OSE

← Older revision		Revision as of 17:13, 30 March 2012
Line 37:		Line 37:
	*Cnx.org - repository. How to do versioning?		*Cnx.org - repository. How to do versioning?
	*Mediawiki - control center for OSE projects		*Mediawiki - control center for OSE projects
	*Open CAD/CAM solution?		*Open CAD/CAM solution?
			*Run on server.
			*Get an account on sourcefabric

			=Civilization Starter Kit Publishing=

Marcin: /* Adam - South Africa */

2012-03-30T17:03:16Z

Adam - South Africa

← Older revision		Revision as of 17:03, 30 March 2012
Line 20:		Line 20:
	*Does have a version history. Versioning - does have - Postgref and diffs are allowed		*Does have a version history. Versioning - does have - Postgref and diffs are allowed
	*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.		*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.
			*Use attribution wherever possible.

	=Kathi=		=Kathi=

Marcin: /* Adam - South Africa */

2012-03-30T17:01:21Z

Adam - South Africa

← Older revision		Revision as of 17:01, 30 March 2012
Line 18:		Line 18:
	*Booktype - limit of book paradigm from wiki. Base format of HTML, restricted set? No, allows extensions. Back end uses CSS and rendering. Rendering is separate from input. Allows Java for control. Based on [[Webkit]]. Controls styling with CSS. Uses [https://www.djangoproject.com/ Django]		*Booktype - limit of book paradigm from wiki. Base format of HTML, restricted set? No, allows extensions. Back end uses CSS and rendering. Rendering is separate from input. Allows Java for control. Based on [[Webkit]]. Controls styling with CSS. Uses [https://www.djangoproject.com/ Django]
	*Wikibooks - not gaining traction		*Wikibooks - not gaining traction
	*Versioning - does have - Postgref and diffs are allowed		*Does have a version history. Versioning - does have - Postgref and diffs are allowed
	*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.		*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.

Marcin: /* Adam - South Africa */

2012-03-30T17:00:38Z

Adam - South Africa

← Older revision		Revision as of 17:00, 30 March 2012
Line 18:		Line 18:
	*Booktype - limit of book paradigm from wiki. Base format of HTML, restricted set? No, allows extensions. Back end uses CSS and rendering. Rendering is separate from input. Allows Java for control. Based on [[Webkit]]. Controls styling with CSS. Uses [https://www.djangoproject.com/ Django]		*Booktype - limit of book paradigm from wiki. Base format of HTML, restricted set? No, allows extensions. Back end uses CSS and rendering. Rendering is separate from input. Allows Java for control. Based on [[Webkit]]. Controls styling with CSS. Uses [https://www.djangoproject.com/ Django]
	*Wikibooks - not gaining traction		*Wikibooks - not gaining traction
	*Postgref and diffs are allowed		*Versioning - does have - Postgref and diffs are allowed
	*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.		*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.

	~~Authoring and Social aspect -~~

	~~Versioning system -~~

	=Kathi=		=Kathi=

Marcin: /* Adam - South Africa */

2012-03-30T16:58:56Z

Adam - South Africa

← Older revision		Revision as of 16:58, 30 March 2012
Line 19:		Line 19:
	*Wikibooks - not gaining traction		*Wikibooks - not gaining traction
	*Postgref and diffs are allowed		*Postgref and diffs are allowed
	*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires		*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires how you will expose this to users. Most users don't know how to use GIT.

	Authoring and Social aspect -		Authoring and Social aspect -

Marcin: /* Adam - South Africa */

2012-03-30T16:58:14Z

Adam - South Africa

← Older revision		Revision as of 16:58, 30 March 2012
Line 19:		Line 19:
	*Wikibooks - not gaining traction		*Wikibooks - not gaining traction
	*Postgref and diffs are allowed		*Postgref and diffs are allowed
			*Not GIThub - closed source online repo for open source projects, but use GIT - a repo manager, open source, to fork and merge branches easily. So give every book its own GIT repository. Advantage of GIT is that you can trace legacy of files, and then merge them. Requires

	Authoring and Social aspect -		Authoring and Social aspect -

Marcin: /* Adam - South Africa */

2012-03-30T16:55:42Z

Adam - South Africa

← Older revision		Revision as of 16:55, 30 March 2012
Line 18:		Line 18:
	*Booktype - limit of book paradigm from wiki. Base format of HTML, restricted set? No, allows extensions. Back end uses CSS and rendering. Rendering is separate from input. Allows Java for control. Based on [[Webkit]]. Controls styling with CSS. Uses [https://www.djangoproject.com/ Django]		*Booktype - limit of book paradigm from wiki. Base format of HTML, restricted set? No, allows extensions. Back end uses CSS and rendering. Rendering is separate from input. Allows Java for control. Based on [[Webkit]]. Controls styling with CSS. Uses [https://www.djangoproject.com/ Django]
	*Wikibooks - not gaining traction		*Wikibooks - not gaining traction
			*Postgref and diffs are allowed

	Authoring and Social aspect -		Authoring and Social aspect -

Marcin: /* Kathi */

2012-03-30T16:55:20Z

Kathi

← Older revision		Revision as of 16:55, 30 March 2012
Line 31:		Line 31:
	*In CNX.org - CAD drawings good for repository		*In CNX.org - CAD drawings good for repository
	*Modules are versioned - will version with the documentation. For large things - an ecology where large things go in archive or such		*Modules are versioned - will version with the documentation. For large things - an ecology where large things go in archive or such
			*National Instruments - does have a circuit displayer. Painful. Only HTML 5 content.
			*

	=OSE=		=OSE=

Marcin: /* Kathi */

2012-03-30T16:52:55Z

Kathi

← Older revision		Revision as of 16:52, 30 March 2012
Line 30:		Line 30:
	*Kathi - sprints for software and development? 2 Days.		*Kathi - sprints for software and development? 2 Days.
	*In CNX.org - CAD drawings good for repository		*In CNX.org - CAD drawings good for repository
			*Modules are versioned - will version with the documentation. For large things - an ecology where large things go in archive or such

	=OSE=		=OSE=

Marcin: /* Kathi */

2012-03-30T16:49:45Z

Kathi

← Older revision		Revision as of 16:49, 30 March 2012
Line 29:		Line 29:
	*Mark Horner - like Life Sciences textbook in a weekend - with Siyavula. Friday evening to Sunday. Advertises as a book in a weekend, but really a couple of weekends + editing		*Mark Horner - like Life Sciences textbook in a weekend - with Siyavula. Friday evening to Sunday. Advertises as a book in a weekend, but really a couple of weekends + editing
	*Kathi - sprints for software and development? 2 Days.		*Kathi - sprints for software and development? 2 Days.
			*In CNX.org - CAD drawings good for repository

	=OSE=		=OSE=