Calendar:Module Ownership: Difference between revisions

Calendar:Module Ownership (view source)

19 bytes removed , 21 July 2007

no edit summary

278

edits

Revision as of 13:12, 21 July 2007 (view source) Ssitter (talk \| contribs) mNo edit summary ← Older edit		Revision as of 13:13, 21 July 2007 (view source) Ssitter (talk \| contribs) No edit summary Newer edit →
Line 189:		Line 189:
	If the module owner and their peers are all busy and don't have time to do a complete review, you can ask someone else to review the code. This must be 'known hacker', somebody who has done calendar work himself, but does not need to be a module owner or peer. If you have code review, you can ask a owner or peer of the module your code touches to give module-owner-approval. Giving this approval only means that the code is good from a high level point of view. Because this is a lot less work, it should be easier to get this approval.		If the module owner and their peers are all busy and don't have time to do a complete review, you can ask someone else to review the code. This must be 'known hacker', somebody who has done calendar work himself, but does not need to be a module owner or peer. If you have code review, you can ask a owner or peer of the module your code touches to give module-owner-approval. Giving this approval only means that the code is good from a high level point of view. Because this is a lot less work, it should be easier to get this approval.

	[[category:calendar\|Module Ownership ~~and Review Process~~]]		[[category:calendar\|Module Ownership]]