<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.author-g-6e891apu12f1wgug
{mso-style-name:author-g-6e891apu12f1wgug;}
span.author-g-z122zgf3rd2w3w4mn7lz122z
{mso-style-name:author-g-z122zgf3rd2w3w4mn7lz122z;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>The titan pad isn’t the right place for discussions, so I’m moving that here:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>>We've never really cracked the modularisation problem, but it is possible to add new templates if you know what you're doing. It would be good to have an example / walk though of building a new template and adding it to the install.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:#7F7F7F;mso-style-textfill-fill-color:#7F7F7F;mso-style-textfill-fill-alpha:100.0%'>>Does the app store not do this? I thought it did? It downloads the code from github and sets it up (or it did)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:#7F7F7F;mso-style-textfill-fill-color:#7F7F7F;mso-style-textfill-fill-alpha:100.0%'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>My question to everyone is whether this is i) working and ii) well understood? Perhaps it is me that missed something?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>J<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Tenney Julian <br><b>Sent:</b> 09 February 2015 10:47<br><b>To:</b> For Xerte technical developers (xerte-dev@lists.nottingham.ac.uk)<br><b>Subject:</b> Development Plan for next release<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’d like to draw up a plan of all the work we need, or want, to complete before the next release – then we can figure out the current status of each piece of work, who is owning it, how much work remains and so on. There is a titanpad here: <a href="https://titanpad.com/xerteDev">https://titanpad.com/xerteDev</a>. I’ll write down as much as I can think of, but could you all check I’ve got everything you’re working on, and anything else you’d like to see added. I’ll then tidy it up into a more detailed plan before the end of this week if you can all put down your thoughts before end of Thursday?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We really want to get the release done in time for the Apereo conference in Baltimore: that is the first week in June, so we have something like 15 weeks to get the next release fixed up. Perhaps we need to work through a few phases: a good first phase would be to get a running install with the bleeding edge code running on it so we can all run the latest code; then to work to finish the development, and then we need to have a decent amount of time for testing and fixing up the final codebase.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It might also be sensible to break the work down into sub-projects and divide responsibility for those between us? I’m happy to put some effort behind managing the whole thing, and to put some time into testing – and to help out wherever I can as well, obviously,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Julian<o:p></o:p></p></div></body></html>