> I'm not sure what to do with
> https://cwiki.apache.org/confluence/display/WW/Migration+Guide - if
> this also should be migrated or not.


I would prefer to migrate it. Linked Version Notes and Release Notes, too.

Is this suitable for release workflow?


Regards,
Christoph



> From: Lukasz Lenart <lukaszlen...@apache.org>
> To: Struts Developers List <dev@struts.apache.org>, 
> Date: 18.09.2017 09:17
> Subject: Re: Documentation
> 
> 2017-09-15 11:09 GMT+02:00 Yasser Zamani <yasser.zam...@live.com>:
> > May I help you in documentation transition from Confluence ? If I had 
a
> > read-only version of *source code* of Confluence's docs, then I think 
I
> > may able write a convertor code then prepare it's output as a PR 
against
> > 'struts-site/master'.
> 
> There is converter in place that I have been using to convert the
> docs. What I thought to do is:
> - export 
https://cwiki.apache.org/confluence/display/WW/Tag+Developers+Guide
> - export https://cwiki.apache.org/confluence/display/WW/Plugin
> +Developers+Guide
> - remove content of the /docs folder and put simple index.html file
> that will point to different exported guides
> 
> after that, we can stop syncing Confluence wiki and mark it as
> deprecated. I'm not sure what to do with
> https://cwiki.apache.org/confluence/display/WW/Migration+Guide - if
> this also should be migrated or not.
> 
> Some parts will have to stay on Confluence like Security Bulletins as
> this allows control access to them. Also after migrating the docs I
> can move all the pages into a "Deprecated" space and leave only what
> we need to keep on Confluence.
> 
> 
> Regards
> -- 
> Ɓukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
> 

This Email was scanned by Sophos Anti Virus

Reply via email to