From Open Siddur Project Development Wiki

Contents 1 Development Goals by Version 1.1 v.0.1 1.1.1 Proof of concept tag (December 2008) 1.2 v. 0.3 1.2.1 v 0.3.0 (November 2009) 1.2.2 v. 0.3.1 (February 2010) 1.3 v. 0.4 1.3.1 v. 0.4.0 (January 2011) 1.3.2 v. 0.4.1 (May 2011) 1.3.3 v. 0.4.2 (May 2011) 1.3.4 v. 0.4.3 (July 2011) 1.3.5 v. 0.4.4 (September 2011) 1.3.6 v. 0.4.5 1.3.7 v. 0.4.6 1.4 v. 0.5 1.4.1 v. 0.5.0 1.4.2 v. 0.5.1 1.4.3 v. 0.5.2 1.4.4 v. 0.5.3 1.4.5 v. 0.5.4 1.5 v. 0.6 1.5.1 v. 0.6.0 1.5.2 v. 0.6.1 1.5.3 v. 0.6.2 1.5.4 v. 0.6.3 1.5.5 v. 0.6.4 (an alpha-quality release) 1.6 v 0.7 1.6.1 v. 0.7.0 1.6.2 v. 0.7.1 1.6.3 v. 0.7.2 1.6.4 v. 0.7.3 1.6.5 v. 0.7.4 1.7 v. 0.8 1.7.1 v. 0.8.0 1.8 v 0.9 1.8.1 v. 0.9.0 1.9 v. 0.10 1.9.1 v. 0.10.0 1.9.2 v. 0.10.1 1.9.3 v. 0.10.2 1.10 v. 0.11 1.10.1 v. 0.11.0 1.10.2 v 0.11.1 1.10.3 v. 0.11.2 1.11 v. 0.12 1.11.1 v. 0.12.0 1.11.2 v. 0.12.1 1.12 v. 0.13 1.12.1 v. 0.13.0 1.13 v. 0.14 1.13.1 v. 0.14.0 1.13.2 v. 0.14.1 1.14 v. 0.98 1.15 v. 0.99 1.16 v. 1.0 1.17 Features beyond 1.0 2 Texts 3 Contributed texts 4 Original text transcriptions 5 Encoded texts 6 Translations 7 Instructional material 8 Comments/essays 9 Non technical 9.1 Membership in the community 9.2 Documentation 9.2.1 Developer documentation 9.3 End-user documentation 9.4 Project management 9.5 Other testing 9.6 Communications

The web application the Open Siddur Project is developing is at an early alpha stage of development. This page lists the steps we need to complete the web application. If you're a coder, please consider volunteering your skills to help us reach these goals. If you are not a coder, please consider transcribing texts so we can have more texts ready for processing by this software.

In order to understand how the milestones fit into the whole project, please read about the project architecture.

This page is an ordered list of milestones (deliverables), organized by subproject. Continuous work should be listed separately. Development status updates are broadcast regularly on our technical discussion list and development blog. Click here to view them.

If you're interested in helping us reach any of these milestones, let us know!

Progress indicators:

• Unformatted text indicates TODO items
• bold indicates items that are considered complete
• italic indicates in-progress items
• bold italic indicates items that are partially complete.

Development Goals by Version

Note: This is the plan as of last edit. As development progresses, these goals will be evaluated. The version ordering may change and more minor versions may be added as new feature requests or difficulties emerge. Minor versions may also be added as bugfix releases or to improve look and feel of the UI without any major functionality changes. In general, development will be frozen on a released version and reported bugs will be fixed in subsequent versions.

v.0.1

Proof of concept tag (December 2008)

• Demonstrate conversion of a siddur to printable format

v. 0.3

v 0.3.0 (November 2009)

• Demonstrate web-based XHTML to JLPTEI transform (client side)

v. 0.3.1 (February 2010)

• Show bibliographic, contributor, and license information

v. 0.4

The focus of 0.4 is on allowing the arrangement of texts that are already in the database, and laying the infrastructure for the processing of new combinations of texts into printable formats.

v. 0.4.0 (January 2011)

• Move transform server side
• Cache concurrent hierarchy operations

v. 0.4.1 (May 2011)

• interactive user interface for user account login
  • Associate accounts with email addresses
• first "siddur" creation UI (using the WLC Tanach texts)
  • Individual title page information UI
  • UI to allow selection, combination, and ordering of pre-existing texts
• first web-accessible REST API

v. 0.4.2 (May 2011)

• Text indexing (backend)
• Search UI component integrated into text construction UI

v. 0.4.3 (July 2011)

• Background task scheduler (backend)
• Background caching (backend)
  • Find uncached/out of date resources and cache them at regular intervals

v. 0.4.4 (September 2011)

• Task status UI to show compilations in Queued, Processing, and Complete states

v. 0.4.5

• UI for partial selection of pre-existing texts
• Builder API adds contributor information to appropriate contributor lists and properly sets responsibility links within the file

v. 0.4.6

• UI for import of STML documents directly into the database

v. 0.5

The focus of 0.5 is on selection and display of parallel texts.

v. 0.5.0

• Background transliteration of in-db texts with an existing table
• Simple UI for table selection
• CSS for 2-way parallel texts

v. 0.5.1

• UI transliteration table editor

v. 0.5.2

• Integrate Raphael Finkel's qamats qatan detection code to backend
• Qamats qatan/sheva na decision XML finalization
• Qamats qatan/sheva na automation/correction UI

v. 0.5.3

• Conversion of 1917 JPS to JLPTEI
• XML verse-by-verse alignment of 1917 JPS to WLC
• Allow at least binary selection (yes/no) of 1917 JPS translation

v. 0.5.4

• Rudimentary style selection for 2- and 3-way parallel texts
• CSS to allow 3-way parallel texts

v. 0.6

The focus of 0.6 is on transcription and text entry. Not expected to have any new user-visible features until 0.6.3 or 0.6.4

v. 0.6.0

• Reusable licensing selector UI control
• Bibliography viewer (partially complete )
• Embeddable Item-by-item bibliography editor control
• Viewer for all public contributor information (allow editing/adding contributors who are not users)
  • Allow a user to adopt contributions as their own?

v. 0.6.1

• Define book-by-book mapping between page numbers (on the page) and URLs
• Editor for page mappings (if necessary)
• Embeddable scrollable (zoomable?) control to get a page image from a JLPTEI document (XQuery + UI)

v. 0.6.2

• Segment editor
• Virtual keyboard

v. 0.6.3

• First integrated transcription editor (segment editor + embedded view + components above)

v. 0.6.4 (an alpha-quality release)

• Multiple hierarchy markers in transcription editor
• Output to JLPTEI file

v 0.7

v. 0.7 will introduce a user interface for conditional inclusion and features that depend on the existence of the conditional system.

v. 0.7.0

• Conditional inclusion widget
  • make new conditional
  • search conditionals
  • apply conditional to selected text

v. 0.7.1

• Editor for default value dependent on other conditions

v. 0.7.2

• Translation alignment editor

v. 0.7.3

• Comment editor (apply out-of-line instructions and/or notes to text)

v. 0.7.4

• Annotation editor (apply meaningful out-of-line annotations to text)

v. 0.8

v. 0.8.0

• Finalize JLPTEI schemas
• Schematron assertions for otherwise unchecked conditions
• Add schema validation to editing workflow

v 0.9

v. 0.9.0

• Style editor UI
  • represent CSS as XML settings?
  • jQuery-based selectors to show changes in real time?

v. 0.10

v. 0.10 will focus on user identity and collaboration features

v. 0.10.0

• Allow authentication by OpenID (I think this doesn't involve storage of sensitive information)
• Merge user accounts and/or associate more than one OpenID with a given db identity?

v. 0.10.1

• Collaboration group console
  • Edit access to your own group
  • Add new groups
  • Admin groups
  • Join groups
  • Messaging within the group? Use email?

v. 0.10.2

• Sharing control in editors (self, group, all)

v. 0.11

v. 0.11 will focus on PDF output. The milestones that are displayed assume that we will be using XeLaTeX as a backend for converting XML to PDF.

v. 0.11.0

• XeTeX compilation server (this is an independent project)
  • Must support authentication from the db
  • Must be able to "call back" the db when the compilation is finished
  • May queue compilations if more than one cannot be done simultaneously

v 0.11.1

• Format transform for JLPTEI processed after the list compiler to TeXML
• Implement TeXML to TeX conversion in the XeTeX compilation server

v. 0.11.2

• Provide UI option for compilation to PDF
• Implement PDF compilation as a call to the XeTeX server
• Implement callback mechanism in the db app

v. 0.12

Security and e-commerce. The actual release plan of major/minor versions is not yet known.

v. 0.12.0

• Examination of security in the code
• Transition to production-grade security

v. 0.12.1

• Integrate one or more e-commerce systems
• Allow generated PDFs to be printed-on-demand through the Open Siddur platform

v. 0.13

v. 0.13.0

• Design and implementation of REST API for external usage
• Define canonical reference or indexing system

v. 0.14

This release focuses on Internationalization/Localization. Beyond having a framework, this depends on there being translators to translate the interface into at least one other language.

v. 0.14.0

• Localized string framework for UI

v. 0.14.1

• Localize strings to at least one other language (he? ru?)

v. 0.98

• Bugfix and testing release(s): alpha

v. 0.99

• Bugfix and testing release(s): beta

v. 1.0

1.0 Release! Yay!

Features beyond 1.0

• Page image upload or link by users
• Semantic grammatical tagging of words (interface with Open Scriptures MorphDB)
• Dictionaries (interface with Open Scriptures BDBMesh)

Texts

Summary of which base texts we need:

Nusaḥ (rite)	Siddur	Maḥzor	Haggadah	Seliḥot
Ashkenaz	Have	Need	Need	German rite: Have, Lithuanian Rite: Need
Ari/Lubavitch	Have	Partial	Have	Need
Edot Hamizraḥ	Need	Need	Need	Need
Italian (Benè Romì)	Need	Need	Need	Need
Romaniote (Greek)	Need	Need	Need	Need
Sepharadi/Spanish-Portuguese	Need	Need	Need	Need
Yemenite	Need	Need	Need	Need
Historical/Rav Saadyah	Need	Need	Need	Need
Appam (Needrthern Italy)	Need	Need	Need	Need
Persian	Need	Need	Need	Need
Provençal	Need	Need	Need	Need

Others that are different eNeedugh to warrant an additional base text?

• Texts from the Cairo Genizah
• Prayers composed by and for Jewish women, e.g. Sefer T'khines
• Songs of the Beta Israel (Ethiopian Jewry)
• the Karaite Siddur
• relevant prayers and poetry of other Bnei Noach(out of scope for Open Siddur Project, in scope for Platform? -- Efraim.feinstein 22:49, 13 December 2009 (UTC))

Contributed texts

Each contributed text needs to be converted to JLPTEI.

1. Reb Zalman Schachter Shalomi's Siddur

Original text transcriptions

Milestones by page can be tracked at Transcription.

1. Tanach
   1. Correct qamats qatan and sheva na marking.
2. For each nusach, define milestones by part of davening. Some milestones can be worked on in parallel.
   1. Mincha for weekdays
   2. Kabbalat Shabbat
   3. Maariv for weekdays
   4. Maariv for Shabbat
   5. Maariv for Yom Tov
   6. Mincha for Shabbat
   7. Pesukei D'zimrah (easy)
   8. Shacharit for weekdays (not Mon/Thurs)
   9. Torah reading for weekdays
   10. Shabbat z'mirot

Encoded texts

Translations

Instructional material

Comments/essays

Non technical

Membership in the community

Documentation

Developer documentation

1. Encoding tutorial for application developers
2. Introduction to hacking

End-user documentation

1. Software recommendations
   1. System Requirements
   2. keyboard layouts

Project management

• unified Mission Statement
• indicate development milestones
• Group tasks for reaching milestones in phases
• Develop team charter
• Recruit Advisory Board
• Develop project constitution
• Define QC Guidelines
• Recruit initial Core Content Group (CCG)
• Define how new members are inducted into CCG
• Assign volunteer manager(s) (currently shared among CCG)
• attain fiscal sponsorships
• plan use of resources
• Recruit board of directors (necessary for non-profit status)
• create Open Siddur Foundation non-profit

Other testing

• Automatic Transcription for Hebrew text (OCR) -- needs to be revisited every year or so

Communications

(These are more-or-less all constantly in-progress)

• documentation wiki
• discussion list
• development blog
• survey users--extend project community beyond core developer team
• Facebook
• Twitter
• interviews with media
• cultivate partnerships with collaborators
• regularly update