| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

FrontPage

Page history last edited by federicoaurora 2 days, 16 hours ago

EpiDoc Development Planning

 

Mission Statement

 

This wiki is used by EpiDoc developers to organize and prioritize the planning and preparation of future releases of software and documentation. If you are new to EpiDoc, and are seeking general information or orientation, please visit the EpiDoc website at https://epidoc.stoa.org/ or join the Markup list. Many of the issues listed in this wiki are organized and discussed more fully in the Feature Request tracker at Sourceforge.

 

Regular EpiDoc sprints: 2013–24

 

  • "EpiDoc Action Group" discuss specific issues, and work through SourceForge tickets

 

 

2024

2023 

2022  

2021  

2020  

2019 

2018 

2017 

2016 

2015 

2014 

2013 

 

Less structured developments

  • revisit site design and menu structure (EMy & GB) (2016)
  • spec for EFES tool (2016/17)
  • refactor internal/external apparatus code and parameters (ongoing)
  • refactor the way we use <g> (@ref rather than @type) (2017)
  • refactor Guidelines (e.g. use tunnel parms) (2017)
  • Epigraphic Ontology discussion (see OEDUc working group) (2018)

 

Guidelines Push: 2010-13 (version 8)

 

 

EpiDoc training discussions/requests:

 

 

Release Sprint: July 2010

 

 

Major Components

 

 

Guidelines Push: April 2008

 

 

New Roadmap push: May-June 2007

 

A series of IRC meetings to plan and execute GL improvement.

 

 

Roadmap Push: September 2006

 

We will use a series of events this month to establish priorities and milestones for EpiDoc development. All members of the EpiDoc community are welcome to participate, but there are certain deadlines that must be met:

 

 

Comments (0)

You don't have permission to comment on this page.