<div dir="ltr">Hi guys!<div><br></div><div>I want to point out just a couple of things.</div><div><br></div><div><ul><li><b>remove_exts</b> branch could be merge but it will generate conflicts. During the sprint I start to lay the foundation of a new extension named EasyLink. Martina thought it was useless and she removed the directory from /extensions. Since we are going to move to VisualEditor I don't know if my extension will be only a VisualEditor gadget. In conclusion, if we decide to merge and resolve conflicts is better to keep the directory like it is in master. I will see to remove it if we'll not need.<br><br></li><li>We must fix Node.js dependencies into OCG before release. I had already talked about that with Cristian and Luca. We made a big jump forward (0.1 to 4 LTS), and we must consider that upstream doesn't support that. Service, Bundler and Texter aren't forked and I had to "play" with their dependencies in order to build successfull on dev environment. It could be my fault, but we have to investigate.</li></ul><div>Bye,</div><div><br></div><div>Alessandro</div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-16 17:48 GMT+01:00 <span dir="ltr"><<a href="mailto:wikitolearn-tech-request@kde.org" target="_blank">wikitolearn-tech-request@kde.org</a>></span>:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Date: Wed, 16 Mar 2016 15:57:13 +0100<br>
From: Cristian Baldi <<a href="mailto:bld.cris.96@gmail.com">bld.cris.96@gmail.com</a>><br>
To: WikiToLearn-Tech <<a href="mailto:WikiToLearn-Tech@kde.org">WikiToLearn-Tech@kde.org</a>><br>
Subject: [WikiToLearn Tech] Plans for the next release and related<br>
projects<br>
Message-ID:<br>
<CANW7w+PBNmVV_9jwiUed5tR8PFSRYB-V2v29=<a href="mailto:qQEQi0N9vJB_g@mail.gmail.com">qQEQi0N9vJB_g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hey guys!<br>
<br>
I decided to wrote this to discuss a bit about the next release and to<br>
gather some informations about the ongoing projects.<br>
<br>
At the sprint we achieved a lot but we have yet to put in<br>
production/user-side most of the work we produced there.<br>
<br>
I (and I guess you too) would like to see many new stuff coming with the<br>
next release.<br>
<br>
I will try to sum up the status of the ongoing projects I know, and if we<br>
could use them for the next release.<br>
<br>
*WikiToLearn *(the website)<br>
We are working on 3 different feature branches:<br>
<br>
- liquid2flow, I am in the process of migrating from LiquidThreads to<br>
Flow (for the talk pages), things didn't go as planned, we have a few<br>
problems with the migration. I contacted upstream and they gave me a few<br>
possible fixes, I have yet to try them, there is hop. If we need this fast<br>
or if we can't fix it for real we might need to lose all the discussions<br>
(or at least the User discussions, which are problematic)<br>
<br>
- remove_exts, Martina while at the sprint started the process of<br>
cleaning up and updating extensions and also updating/fixing the<br>
LocalSettings.php as well as adding a few quick fixes for extensions<br>
related development (error reporting for example). We have to do some<br>
testing and then we can merge this without many problems, I think.<br>
<br>
- dev-wtl-home, the sysadmins created this branch to begin the process<br>
of migrating from the old wtl setup to the new WikiToLearnHome one. More in<br>
the dedicated secton.<br>
<br>
All these 3 are blocking for the next release (IMO).<br>
<br>
*WikiToLearnHome*<br>
This is the new repo we (Luca, Dario, Davide and me) created to get the<br>
best possible WikiToLearn environment up and running as quickly and<br>
painlessly as possible, both in production and on development machines. We<br>
set the basis for it (we can run a local instance, but not in the clean way<br>
we would like) and are in the process of writing the last part of this new<br>
project. The idea is to have the WikiToLearn repo as free as possible from<br>
scripts and at the same time improve the experience for the developers,<br>
sysadmins, users.<br>
The objective is to end this as soon as possible, and get at least the<br>
local instance/development scripts ready in the next weeks (2?).<br>
<br>
I think this is blocking for the next release, it has to be working; open<br>
to discuss this. It won't change anything on the user/editor/reader side.<br>
<br>
*texla*<br>
Texla is the latex parser developed at the sprint (and in the weeks before<br>
it) by Davide with the help of a few other people. The plan is to have a<br>
web interface where a user can upload latex files and convert/upload them<br>
to WikiToLearn, painlessly. We still have quite a lot work to do on this<br>
and I think we can release without it.<br>
<br>
*OCG/Collection*<br>
Alessandro, Irene and me updated the system to the newer version of nodejs<br>
(it was running one from 4 years ago). Work is still going on for the<br>
conversion of tables. Need more details to know if everything is working or<br>
what needs to be fixed or if we can release. (We can release without the<br>
tables)<br>
We also worked on our fork of the collection extensions, improving the user<br>
experience, this is already merged in master.<br>
<br>
*Neverland*<br>
Let's wait for Gianluca, I don't know enough in the detail about what was<br>
done at the sprint. (New features?, fixes?)<br>
<br>
<br>
*VisualEditor*<br>
Gianluca managed to make VisualEditor run on WikiToLearn! It has some bugs<br>
and problems we have to fix, but I think we can release without it (unless<br>
something was fixed in the last few days)?<br>
<br>
*PDFCheck*<br>
Currently powered off, I have a simple bug to fix, we don't care for the<br>
release.<br>
<br>
*Infrastructure*<br>
We are planning the move to the new servers. Luca wants this for the next<br>
release.<br>
<br>
<br>
*Content Referencing*<br>
I don't know enough. I am sure we don't have this ready and won't need in<br>
the release.<br>
<br>
*Other Stuff*<br>
Cross Wiki Notification (who is working on that?) Not in this release? How<br>
much work is needed?<br>
Skin for the Blog (Andrea Zanini is working on that, we got some feedback<br>
from KDE's VDG). Non blocking.<br>
BotsForEditors (I am planning to work on that, soon).<br>
<br>
Waiting to get your opinion on everything,<br>
<br>
Cristian<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.kde.org/pipermail/wikitolearn-tech/attachments/20160316/1a2a4d33/attachment-0001.html" rel="noreferrer" target="_blank">http://mail.kde.org/pipermail/wikitolearn-tech/attachments/20160316/1a2a4d33/attachment-0001.html</a>><br></blockquote></div></div></div></div></div>