Websites/creativecommons.org - Revision history

CCID-georgeharipopescu: Corrected the link to Transifex

2016-11-28T13:55:11Z

Corrected the link to Transifex

← Older revision		Revision as of 13:55, 28 November 2016
Line 35:		Line 35:
	= Localization =		= Localization =

	String localization is done on [https://www.transifex.com/~~projects/p~~/CC~~/resource~~/deeds-choosers/ Transifex]. Please contact a team member if you need to get set-up.		String localization is done on [https://www.transifex.com/nkinkade/CC/deeds-choosers/ Transifex]. Please contact a team member if you need to get set-up.

	Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on Tuesday morning. These changes are visible for testing on the [https://staging.creativecommons.org staging] site.		Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on Tuesday morning. These changes are visible for testing on the [https://staging.creativecommons.org staging] site.

CCID-shinchpearson at 19:12, 7 February 2014

2014-02-07T19:12:06Z

← Older revision		Revision as of 19:12, 7 February 2014
Line 10:		Line 10:

	;Development		;Development
	: Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night, but CC will endeavor to make changes by end of the day Tuesday.		: Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night, but CC will endeavor to make changes to strings marked for localization by end of the day Tuesday where possible.

	;String Freeze		;String Freeze

CCID-shinchpearson at 17:33, 7 February 2014

2014-02-07T17:33:01Z

← Older revision		Revision as of 17:33, 7 February 2014
Line 1:		Line 1:
	The [https://creativecommons.org creativecommons.org] site is our main website, which has significant traffic (.5m/month).		The [https://creativecommons.org creativecommons.org] site is our main website, which has significant traffic (.5m/month).

	Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development, localization~~, and QA~~, which you can read about below.		Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development and localization, which you can read about below.

	= Release Schedule =		= Release Schedule =
Line 10:		Line 10:

	;Development		;Development
	: Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night.		: Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night, but CC will endeavor to make changes by end of the day Tuesday.

	;String Freeze		;String Freeze
	: At the end of Thursday (midnight Friday) the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators 3 full days (including the weekend) to work on translations.		: At the end of Thursday (midnight Friday) the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators a minimum of 3 full days (including the weekend) to work on translations, although as noted above, translators will typically have a full week to translate because CC will attempt to commit all changes to the English on Tuesdays.
	:~~Changes~~ which modify/add strings '''may''' land on a branch which can be merged at a later date (for a future release).		:Note: changes which modify/add strings '''may''' land on a branch which can be merged at a later date (for a future release).

	;~~Full Freeze~~		;Release
	:On Sunday night (midnight Monday) the source tree is locked down, and no changes are allowed. This gives us one day where we can QA the site by using the [https://staging.creativecommons.org staging] site, before releasing it to production on Tuesday morning		: Changes to the production site happen only on Tuesday mornings. Changes are not pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner).
	:Changes ~~'''may''' land on a branch which can be merged at a later date (for a future release).~~

	~~Note that changes~~ to the production site happen only on Tuesday mornings. ~~'''No changes'''~~ are pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner).

	~~However, changes can always (and often should) land on branches with which we can launch temporary servers for public testing~~.

	= Sources =		= Sources =
Line 42:		Line 37:
	String localization is done on [https://www.transifex.com/projects/p/CC/resource/deeds-choosers/ Transifex]. Please contact a team member if you need to get set-up.		String localization is done on [https://www.transifex.com/projects/p/CC/resource/deeds-choosers/ Transifex]. Please contact a team member if you need to get set-up.

	Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on ~~Sunday night~~. These changes are visible for testing on the [https://staging.creativecommons.org staging] site.		Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on Tuesday morning. These changes are visible for testing on the [https://staging.creativecommons.org staging] site.

Dan Mills at 06:55, 7 February 2014

2014-02-07T06:55:23Z

← Older revision		Revision as of 06:55, 7 February 2014
Line 27:		Line 27:

	Sources for the creativecommons.org site are available on [https://github.com/creativecommons/creativecommons.org GitHub]. Proposed changes can be submitted as pull requests to the appropriate module(s).		Sources for the creativecommons.org site are available on [https://github.com/creativecommons/creativecommons.org GitHub]. Proposed changes can be submitted as pull requests to the appropriate module(s).

			= Editing Guide =

			We've developed a [https://docs.google.com/a/creativecommons.org/document/d/1SJnLpEYR_Z6MlSSdCTDzW_ZIh3msvrCw3uZKUnLCd8c/edit#heading=h.87xn7dh4juh0 guide] explaining how to edit the website, step by step (assumes you have the necessary permissions to do so).

	= Issues =		= Issues =

Dan Mills: /* Issues */

2013-12-03T22:08:21Z

Issues

← Older revision		Revision as of 22:08, 3 December 2013
Line 31:		Line 31:

	All issues, including both bugs (problems) as well as desired changes must be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].		All issues, including both bugs (problems) as well as desired changes must be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].

			Issues are evaluated at the weekly triage meeting, where we decide what we will work on, and in what order.

	= Localization =		= Localization =

Dan Mills: /* Issues */

2013-12-03T22:04:11Z

Issues

← Older revision		Revision as of 22:04, 3 December 2013
Line 30:		Line 30:
	= Issues =		= Issues =

	~~Issues with creativecommons.org can~~ be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].		All issues, including both bugs (problems) as well as desired changes must be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].

	= Localization =		= Localization =

Dan Mills at 21:58, 3 December 2013

2013-12-03T21:58:53Z

← Older revision		Revision as of 21:58, 3 December 2013
Line 31:		Line 31:

	Issues with creativecommons.org can be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].		Issues with creativecommons.org can be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].

			= Localization =

			String localization is done on [https://www.transifex.com/projects/p/CC/resource/deeds-choosers/ Transifex]. Please contact a team member if you need to get set-up.

			Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on Sunday night. These changes are visible for testing on the [https://staging.creativecommons.org staging] site.

Dan Mills at 21:50, 3 December 2013

2013-12-03T21:50:58Z

← Older revision		Revision as of 21:50, 3 December 2013
Line 1:		Line 1:
	The [creativecommons.org] site is our main website, which has significant traffic (.5m/month).		The [https://creativecommons.org creativecommons.org] site is our main website, which has significant traffic (.5m/month).

	Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development, localization, and QA, which you can read about below.		Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development, localization, and QA, which you can read about below.
Line 13:		Line 13:

	;String Freeze		;String Freeze
	: At the end of Thursday the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators 3 full days (including the weekend) to work on translations. ~~Exceptions to the string freeze are~~ at ~~the discretion of the module owner, but generally not granted~~.		: At the end of Thursday (midnight Friday) the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators 3 full days (including the weekend) to work on translations.
			:Changes which modify/add strings '''may''' land on a branch which can be merged at a later date (for a future release).

	;Full Freeze		;Full Freeze
	:On Sunday night the source tree is locked down, and no changes are allowed. This gives us one day where we can QA the site before releasing it to production on Tuesday morning		:On Sunday night (midnight Monday) the source tree is locked down, and no changes are allowed. This gives us one day where we can QA the site by using the [https://staging.creativecommons.org staging] site, before releasing it to production on Tuesday morning
			:Changes '''may''' land on a branch which can be merged at a later date (for a future release).

	Note that changes to the production site happen ~~'''~~only~~'''~~ on Tuesday mornings. '''No changes''' are pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner).		Note that changes to the production site happen only on Tuesday mornings. '''No changes''' are pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner).

			However, changes can always (and often should) land on branches with which we can launch temporary servers for public testing.

			= Sources =

			Sources for the creativecommons.org site are available on [https://github.com/creativecommons/creativecommons.org GitHub]. Proposed changes can be submitted as pull requests to the appropriate module(s).

			= Issues =

			Issues with creativecommons.org can be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org].

Dan Mills at 21:37, 3 December 2013

2013-12-03T21:37:42Z

← Older revision		Revision as of 21:37, 3 December 2013
Line 1:		Line 1:
	creativecommons.org is our main website, ~~and~~ has many internal components that must inter-operate correctly for the site to function~~. The site has significant~~ traffic ~~(.5m/month)~~, ~~and so~~ the site must be ~~correctly tuned to withstand the load~~.		The [creativecommons.org] site is our main website, which has significant traffic (.5m/month).

			Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development, localization, and QA, which you can read about below.

	= Release Schedule =		= Release Schedule =
Line 5:		Line 7:
	All times in Pacific Time (GMT-8 or GMT-7, depending on daylight savings).		All times in Pacific Time (GMT-8 or GMT-7, depending on daylight savings).

	The ~~creativecommons.org site follows a weekly~~ release schedule~~, with different~~ stages ~~for development, localization, and QA. The different stages are~~:		The release schedule repeats these stages weekly:

	;Development		;Development

Dan Mills: Created page with "creativecommons.org is our main website, and has many internal components that must inter-operate correctly for the site to function. The site has significant traffic (.5m/mon..."

2013-12-03T21:33:52Z

Created page with "creativecommons.org is our main website, and has many internal components that must inter-operate correctly for the site to function. The site has significant traffic (.5m/mon..."

New page

creativecommons.org is our main website, and has many internal components that must inter-operate correctly for the site to function. The site has significant traffic (.5m/month), and so the site must be correctly tuned to withstand the load.

= Release Schedule =

All times in Pacific Time (GMT-8 or GMT-7, depending on daylight savings).

The creativecommons.org site follows a weekly release schedule, with different stages for development, localization, and QA. The different stages are:

;Development
: Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night.

;String Freeze
: At the end of Thursday the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators 3 full days (including the weekend) to work on translations. Exceptions to the string freeze are at the discretion of the module owner, but generally not granted.

;Full Freeze
:On Sunday night the source tree is locked down, and no changes are allowed. This gives us one day where we can QA the site before releasing it to production on Tuesday morning

Note that changes to the production site happen '''only''' on Tuesday mornings. '''No changes''' are pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner).