Communication & Marketing

November 8th 2016

Ryzom Wikis
Ryzom has several wikis: Ryzom wiki for the Lore, Ryzom Core and Ryzom Forge. We've got the project to gather all these various existing wikis into one single official one: the one of Ryzom Forge, which has the advantage of being multilanguage. The other wikis will remain open, but only the one of Ryzom Forge will receive the official articles. It will have a "Lore" part gathering all the Lore validated articles of the ryzom.wiki, but also a "Dev" part.
Here is a mock-up of the project:  http://forge.ryzom.com/wiki/Maquette (clic on the Gameplay and Lore test pages please).

Q: It's planned to integrate the RC wiki also?
A: Yes and no: we cannot close the Ryzom Core wiki (used by others than us), but the idea is to use the one of Ryzom Forge to consolidate there the Dev articles useful for Ryzom. And in priority, of course, the up-to-date articles by Ryzom Core. The aim of this project is to stop scattering and to concentrate on the same wiki everything that is about Ryzom.

Q: And what about the pages created by the players? (So not validated by the Lore)
A: The forge.ryzom.com wiki will remain an official-collaborative wiki, also in its Lore and Dev sections.
But since it's not possible (nor advisable) to migrate the whole content of the Ryzom Core wikis and the 3 DE, EN and FR wiki.ryzom.com, the simplest way will be to just migrate the up-to-date and working articles on Dev side, and the validated Lore articles on Lore side. And then, to restart all together in collaborative mode on forge.ryzom.com.

Q: The new core.ryzom.com wiki will remain? (clone of forge)
A: No. We thought that instead of creating a 4th wiki, it would be better to reduce their number. It will be a part of the forge.ryzom.com which will host the dev articles.

Q: I've got a question regarding the wiki: if we find a typo (typing error, wrong orthograph, error in translation...), we can fix it or we have to mention it somewhere?
A: You can fix it, of course!

21st of november 2016

1 Gaueko leaving
Gaueko, who acted as Communication assistant manager and Translation group co-leader, and who was also a member of the Lore group, a translator towards Spanish, and in charge of the marauders, has chosen to leave the Ryzom team. We thank him for his great commitment and we wish him the best for the rest.

2 Result of the 2 years of Ryzom/Khaganat collaboration (by Zatalyz)
I invite you to read the very interesting thread by Zatalyz on Ryzom forum: http://app.ryzom.com/app_forum/index.php?page=topic/view/26129.

3 Reorganization of Ryzom Teams
 We're currently working at reorganising the Ryzom Teams, in order to move towards:
- a maximum transparency between the internal teams (under NDA);
- a maximum transparency with the Ryzom Forge and Ryzom Core groups and with the players (not total however to avoid spoil: the events scenarios, for example, won't be shared);
- a reviewing of our working method, in order to increase our efficience without overloading ourselves;
- a reworking of the tools, in order not to depend anymore on external tools and their limits for the free versions: we're studying and testing currently their open source substitutes, which will be hosted on a Ryzom server.

4 New presenting for the "teams roadmap" on the WebIG in 2017
The "teams roadmap" on the WebIG ( http://app.ryzom.com/app_devroadmap/ ) is increasing and becomes difficult to read, especially as the various lignes cannot be sorted. That's why a new roadmap, clearer and easier to follow, will be proposed for 2017

Q: When do we all move to #Ryzom and stop spreading ourselves in all directions?
A: You can already keep only #ryzom, #ryzomforge and #ryzomsupport. To close the last two ones (especially the last one), we first have to announce it and change the links everywhere. (The link to #ryzomsupport is given in lots of places, it will have to be changed into #ryzom before we stop using the #ryzomsupport channel).
A Glorf: Normally you can create redirection on IRC, to send the ones who log on #ryzomsupport to #ryzom. I'll have a look for next time. I had written it somewhere but I cannot find it anymore.
Q: Cant a bot sit on channel and inform visitors about the change in the meantime? Or just a new welcome message on the channel?
A: Probably.
=>  I'll try to implement this quickly.

December 15th 2016

1 Change of the tools used by the Ryzom teams
As said during last meeting, we are working on a redesign of the tools, in order to no longer depend on external tools and their limitations in free version: we are currently studying and testing their open source replacements, which will be hosted on a Ryzom server.

The tools that will be replaced are:
- The internal chat (currently Slack)
- The task management software (currently Asana)
- The file sharing tool (currently Dropbox)
- The Collaborative Publishing Tool (currently Paper)

It will lead to a greater visibility, since the members or Ryzom, Ryzom Forge and Ryzom Core will share these tools and will be able to follow the whole of the ongoing projects. There will only be a restriction regarding the access to some documents related to these projects.

I will tell you more soon, as soon as this project is more advanced.

Hi guys. Maybe you should have a look at:

- matrix.org - decentralized, distributed and federated chat protocol with many bridges (gitter, irc, slack etc)
- taiga.io - one of the best project management out there
- nextcloud - file sharing and more
- nextcloud - with collabora/only office/etherpad for collaborative doc editing.

You could have all of those self hosted with ldap support to have all those services accessible with just one set of credentials. I'm hosting thos services, and more with https://disroot.org project, so I could help you setup your instance of you want, or you could use our services.