Projects/Write: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (Activities/Write moved to Projects/Write: proj)
(.)
Line 1: Line 1:
<noinclude>{{activity-summary-header}}
<noinclude>{{project-summary-header}}
</noinclude>{{Activity-summary
</noinclude>{{project-summary
|simplename = write
|simplename = write
|packagename = Write
|packagename = Write
Line 17: Line 17:
|comments = version 20+; added collaboration; journal integration added
|comments = version 20+; added collaboration; journal integration added
}}<noinclude>
}}<noinclude>
{{activity-summary-footer}}
{{project-summary-footer}}
</noinclude>
</noinclude>

Revision as of 04:37, 10 January 2008

To create an activity summary, add {{subst:Project-summary-pg|}} to a new page.


icon for write Write : A multimedia word processor edit
version 20+; added collaboration; journal integration added 
Maintainers: J.M. Maurer  ·  License: unknown  ·  Mime types: text/plain .txt .doc, .abw, .rtf, .xhtml, .html, odt
Download v.32 · source
Tested in: all (trac)
Translate: ·    

Key:

New activities should use the project-pre-summary template, including:

prettyname - the display name for the activity, such as Comic Maker. 
description - a few sentences describing the activity and its audience
categories - any keywords that match your activity and its use.  
   see the activities grid for examples.
maintainers - people actively working on the activity, with links to 
   their userpages or ways to contact them.
image - title of an uploaded image that may make a suitable icon
port-notes - notes on other platforms and potential or in-progress ports
mimetypes - mime types that the activity can read and launch.
comments - general comments about development.
l10n-notes - comments about localization, including links for translating
   existing related projects.
license - the name of the license[s] your activity uses, with a link
   to its full text.
status - from 0 to 6.  0:idea, 1:stub, 2:immature, 3:active development,
   4:beta, 5:stable, 6:finishing touches

Testable projects should review the style guide and use the project-summary template, also including:

simplename - a simple name for the activity: it should contain only lowercase 
   letters, numbers, hyphens, underscores.  Determines the name of some source files.
packagename - the name used for project bundles; it should not contain spaces.
   It can be the same as simplename (best option) or a CamelCase version of it 
   (some existing activities do this). 
license - the name of the license[s] your activity uses, with a link
   to its full text.
status - from 0 to 6.  0:idea, 1:stub, 2:immature, 3:active development,
   4:beta, 5:stable, 6:finishing touches
version - the version number of the latest build.
source-url - a raw url for the source repository .
builds - latest builds in which the activity has been tested.
l10n-url - url and title of a place to go to translate the activity.
   common options are {{pootle|xo_core}} and {{pootle|xo_bundled}}.