[WIU] Weekly Incubator Update: 2017, Week 20.
@Phase 1 courses' volunteers: If you want your self-computed progress to be displayed in the future WIUs, please contact me (jrikhal) in the incubator.
Note: Data retrieved on 2017/05/21 at 08:44 (UTC).
I. Phase 1 Courses
- Exits (Courses reaching BETA Phase):
- Japanese from English (currently only on iOS). See here for details.
Please, ask THERE any question related to that course, not in this WIU, thanks.
- Japanese from English (currently only on iOS). See here for details.
- Entries (Courses entering the Incubator): None.
I.B. Completion Summary
Right-click on the image then select "Open in a new tab" to enlarge the image
(A) This week's value automatically generated from Duolingo's statistics.
(S) This week's value self-reported by the team of volunteers working on the course.
\/!\ Lacking data: see at bottom. \/!\
II. Latest News from Course Volunteers (All Phases)
Course "Czech from English" (Phase 1)
By nueby on 2017/05/21
End in sight?
95%. This may be the last percentage update based on the 2000 word target. There will most likely be more words than that in the course, as needed to provide as much closure as possible.
Course "Japanese from English" (Phase 1)
Japanese beta course available on iOS!
We are thrilled to announce that our Japanese course is now available on iOS. It's coming to ...
Course "High Valyrian from English" (Phase 1)
By Dedalvs on 2017/05/17
Second Checkpoint Cleared!
We've cleared the second checkpoint, and as we go, are getting closer to clearing out the old Russian words in the lesson. Slow but steady!
Course "Irish from English" (Phase 3)
Update on the development of the new tree.
It has been a long time since our last update and we would like to apologise for th...
Course "Italian from Portuguese" (Phase 1)
Infelizmente somos forçados a adiar a data de lançamento do curso, ainda não foi liberado pelo Du...
III. Previous Weekly Incubator Updates
See this index of WIUs.
Explanation of the data
Lack of previous data
Progress is displayed for two and three weeks ago only if the weekly values were self-reported to us by the teams. Our automatic progress calculation for non-self-reporting courses cannot be performed retroactively because we lack the necessary data. (But each week's values will be available the following week, and so the charts will populate soon.)
Since it's the first WIU automatically generated with our code, here some details about it.
Our calculation does not just copy the official course completion percentage, and this is why some of our status figures deviate from the previous WIUs, in some cases significantly.
- We enforce the minimum "total words" target of 1500 to reduce the impact of partial trees on the calculation.
- We only use the completion of localization strings for courses that are the first to teach from the given language, and even then only at one-sixth the weight of the word completion progress.
- We ignore the completion of images.
24 Comments This discussion is locked.
Wow, I didn't the Irish team had given an update. Best of luck to them in creating the tree 2.0, I'm eagerly awaiting it.
This part in particular is really exciting:
"Our new course will focus on the bringing out the Irishness in the language by introducing aspects of Irish culture into the course and also by focusing on the use of the language in everyday situations as well as more Irish specific vocabulary. We hope to enrich the course by including idiomatic expressions/phrases and more dialectical elements of the language. Additionally, we want to include bonus skills related to niche aspects of Irish culture and history as well as modern life."
Would it be possible for you to include the full text of news from course volunteers in future updates rather than the abbreviated ones in this update?
The texts are abbreviated on purpose in order to have a "not too long"(*) WIU.
The idea is that everyone can see
at glance if there has been an update for a course they're interested into. When it's the case, the direct link to the (full) update is provided so that one can easily go read the full update.
So... sorry but no, it's on purpose. ;)
(*) and this one is already too long due to the "DISCLAIMER" and the "Explanation of the data" (which will not be in next WIUs).
The script I wrote(*) retrieving the data already displays full text on very short updates: when less than 100 characters(**).
(*) in order for the WIU to be created within 2min each week.
(**) which happens
Update: I changed the code (and this week WIU) so that
- if the update's text is less than 200 characters long, it displays it entirely
- otherwise, it displays the 100 first characters and a link to the full update.
Thank you for this. If you don't mind me making a suggestion, can you include the actual percentage numbers of completion next to the course names in the graph? The lines are very thin and as you get towards the top of the graph it's not easy to work out what percentage each one represents.
if you know how to do so on a Google Spreadsheet graph, my ears and eyes are widely open!
I wanted to do things like you described, how jitengore was doing it, but despite some researches I couldn't find how to do that on a Google Spreadsheet (don't want to use something else: it needs to be online to be sharable with other contributors).
Oh... I indeed probably totally misread.
However, IMO, the (precise) percentage is quite irrelevant. Mainly because (at least for (A) ones) it's in any case not more accurate/precise than what can be "read" on a graph (+-1%).
On the other hand, what is relevant/accurate is
- dynamic of each course progress
- what courses may arrive first in beta (even if reaching first 100% doesn't mean you'll be next released(*))
Therefore, I'll keep promoting those "focuses" on the graph. ;)
That said, I could make the vertical lines "darker" for the next WIU to answer the remark
he lines are very thin and as you get towards the top of the graph it's not easy to work out what percentage each one represents.
(*) Cf. for example IT-PT that the volunteers brought to 100% more than one month ago and since then are waiting. While JA-EN was released few hours/days after reaching "completion"...
I have brought this up a few times already but I think it is important. Are they going to specify which devices will get each course? Or try to release them at similar times? With Japanese as far as I know all they have said is some time this year for web, while other devices have a more specific prediction. I don't get the feeling they are in any rush to release it for the web. If they keep releasing courses and then telling people sorry not for you at the last minute, it will be pretty off-putting to users.
Are they going to specify which devices will get each course?
I am afraid we the volunteers will only know along with the regular users, but we can speculate.
The typical procedure was to release on the web, followed on meeting certain error report criteria by a release on mobile apps. Japanese put this in some doubt, arguably for technical reasons. So let's watch what happens with Italian for Portuguese, one would hope very soon. No special excuses appear to exist for deviating from the old sequence in its case. If all is as expected, great. We will know what to expect for whoever is next.