Volunteer:Development

From Gospel Translations

Revision as of 21:06, 25 August 2008 (view source) Mahra (Talk | contribs) ← Older edit		Current revision as of 15:39, 10 August 2010 (view source) JoyaTeemer (Talk | contribs) m (Protected "Volunteer:Development" ([edit=sysop] (indefinite) [move=sysop] (indefinite)))
(14 intermediate revisions not shown)
Line 1:		Line 1:
-	The scoop on what we use, and projects we need help tackling.	+	__NOTOC__
		+	==== Getting Started ====
		+	Thanks for your interest in the technology that keeps Gospel Translations running. You can get involved with any of the projects below by [[Special:Contact|enrolling]] as a volunteer. (We're also very open to your own ideas for how to make the site better or more efficient.) For ease of maintenance, right now we prefer all code to be PHP--but just ask if you think we should make an exception for a particular project.
		+
		+
		+	== Current projects ==
		+	=== Completed ===
		+
		+	*[[Gospel Translations:Technology/Multi-wiki project|Multi-wiki automation]] - Using automated processes to launch and maintain separate wikis for each language that Gospel Translation works in. '''(Assigned to Nick F.)'''
		+	*[[Gospel Translations:Technology/BrowseTranslations extension|BrowseTranslations extension]] - Create a [http://www.mediawiki.org/wiki/Manual:Special_pages SpecialPage] that allows drilldown browsing of our translation library.
		+
		+	===Unassigned===
		+	* Formatting bot - Write an automation script to check for formatting errors on the wiki and correct them.
		+	* Facebook app - This FB plugin would let people display the translation they're currently working on, how many contributions they've made in total, a "member since" date, etc. Still needs brainstorming.
		+	* Email this page to a friend - Write a MediaWiki extension that makes it easy to send a particular article to a friend in proper formatting.
		+	* Show/hide original - Write a script that would allow readers to show/hide the original (English) text next to translated text on foreign-language pages. This would allow side-by-side review in an easy manner.
		+	* Glossary highlight extension - Write a MediaWiki extension that will (in English articles) highlight words that appear in our glossaries, so that translators will have an easy time identifying words that should be standardized in their translations.
		+	* Page protection bot - Write a script to check for all pages marked as category "Final Version" and protect them.
		+
	== Software ==		== Software ==
Line 14:		Line 32:
	* [[Project:Technology/DabbleDB integration|How DabbleDB integrates with the GospelTranslations wiki]]		* [[Project:Technology/DabbleDB integration|How DabbleDB integrates with the GospelTranslations wiki]]
-
-	==Project: Multiple wiki automation==
-
-	'''Goal:''' to have a separate wiki for every language we support
-
-	'''Requirements:'''
-	* Code base written in PHP
-	* For each language ''X'', copy over every ''X'' article from this English wiki to a target wiki, http://''X''.gospeltranslations.org
-
-	'''Technical process'''
-
-	This is the basic process that could be used to accomplish the multi-wiki setup and updates. There are some underlying techniques not spelled out here, so feel free to ask questions if something isn't connecting for you.
-	# <font color="green">[working]</font> Cronjob imports up-to-date info DabbleDB database and stores it in local PHP array ([[Project:Technology/DabbleDB_export_structure|see structure]])
-	# <font color="orange">[unassigned]</font> Automating bot ([http://wikisum.com/w/User:Adam/Creating_MediaWiki_bots_in_PHP how to make one])
-	## reads local PHP array to find all entries for language ''X''
-	## for each entry, gets translated title off of the English wiki (i.e., for [[Gospel_Implications/es]], it finds the title ''Consecuencias del evangelio'')
-	## for each entry, creates a page on the target wiki, i.e., http://fr.gospeltranslations.org/wiki/ENTRY_TRANSLATED_TITLE
-	## on each page created, writes in transclusion code: <code><nowiki>{{:gt_en:ENTRY_ENGLISH_NAME}}</nowiki></code>
-	# <font color="green">[working]</font> Non-English wiki uses transclusion code to pull article text from English wiki. For example, the code <code><nowiki>{{:gt_en:Gospel_Implications/es}}</nowiki></code> will grab the entire article text from [[Gospel_Implications/es]]
-
-	Obviously, what is missing from the functionality right now is a working automation bot.
	[[Category:Tech admin]]		[[Category:Tech admin]]

---

Current revision as of 15:39, 10 August 2010

Getting Started

Thanks for your interest in the technology that keeps Gospel Translations running. You can get involved with any of the projects below by enrolling as a volunteer. (We're also very open to your own ideas for how to make the site better or more efficient.) For ease of maintenance, right now we prefer all code to be PHP--but just ask if you think we should make an exception for a particular project.

Current projects

Completed

• Multi-wiki automation - Using automated processes to launch and maintain separate wikis for each language that Gospel Translation works in. (Assigned to Nick F.)
• BrowseTranslations extension - Create a SpecialPage that allows drilldown browsing of our translation library.

Unassigned

• Formatting bot - Write an automation script to check for formatting errors on the wiki and correct them.
• Facebook app - This FB plugin would let people display the translation they're currently working on, how many contributions they've made in total, a "member since" date, etc. Still needs brainstorming.
• Email this page to a friend - Write a MediaWiki extension that makes it easy to send a particular article to a friend in proper formatting.
• Show/hide original - Write a script that would allow readers to show/hide the original (English) text next to translated text on foreign-language pages. This would allow side-by-side review in an easy manner.
• Glossary highlight extension - Write a MediaWiki extension that will (in English articles) highlight words that appear in our glossaries, so that translators will have an easy time identifying words that should be standardized in their translations.
• Page protection bot - Write a script to check for all pages marked as category "Final Version" and protect them.

Software

Gospel Translations relies on a few basic pieces of software to run smoothly.

MediaWiki is our wiki engine, and is the same software used by Wikipedia. It was chosen for it's proven scalability, excellent support for multiple languages, and it's easy extensibility. The fact that it has such excellent community support was also a big factor when we chose it. MediaWiki runs on PHP and MySQL.

• User manual
• Writing extensions
• Technical documentation

DabbleDB is our online database provider, helping us keep information about all of our publishers, articles, volunteers, and translations organized in one central place. Better still, it has good API support, so we've been able to tie the data their directly into wiki articles--when you visit a page and see the blue box listing Author, Translator, and so forth (see example), you are seeing MediaWiki and DabbleDB work together.

• How DabbleDB integrates with the GospelTranslations wiki