[TYPO3-team-core-v5] TYPO3 Phoenix Scrum Meeting Notes - 21.07.2011

Robert Lemke robert at typo3.org
Thu Jul 21 13:26:35 CEST 2011


Hi Francois,

Am 21.07.2011 um 13:13 schrieb François Suter:

>> ✔ Discovered problems in current and future workflow with DocBook
>> ✔ checked if using Restructured Text would be feasible
>> ✔ did research on toolchain and other implications for using ReSt
>> ➜ continue writing quickstart in ReSt
> 
> What's up? What problems do you encounter? Remember that the Doc Team is working hard on transitioning to DocBook.

yes, I know – and that's also why I as very reluctant to check out alternatives. On the other hand there was this apparent feeling most in the time had for some time now that writing and handling DocBook might be too heavy.

Anyway, I guess nothing is really lost. DocBook is still, from a technical perspective, a very capable format. On the other hand, Restructured Text is a lot easier to learn, does not require a special edit and has a few advantages when it comes to collaboration (DIFFs are more readable, chunks of text can easily be shared in chats or be edited by multiple persons simultaneously in tools like Etherpad).

I am very aware of what hassle and maybe also disappointment a last-minute-switch could cause. On the other hand I think that the FLOW3 / Phoenix team should take a test ride and discover the real implications of using that format. There are, by the way, tools to convert from / to DocBook. I haven't tried them yet, but they might help us in the process.

So, I suggest that I try this out and we stay in touch about it. All the work your team has done regarding structuring and laying out documentation (including visual design), is not lost at all. If we really switch to Restructed Text, it would "only" be all the thought work which went into the DocBook specifics which went down the drain.

I'll get back to you as soon as I have more insights!

Thanks for taking care,
Robert



More information about the TYPO3-team-core-v5 mailing list