To provide another data point,   we toot for the initial work on Papyrus for 
Real Time, with the final user/toolsmith documentation placed in the project’s 
wiki. We also took a similar approach for the definition of the content for the 
upcoming Papyrus UML Light.


Regards,

Charles Rivet
Senior Product Manager, Papyrus-RT product leader
char...@zeligsoft.com <mailto:char...@zeligsoft.com>

> On 2018-11-30, at 15:47 , Wayne Beaton <wayne.bea...@eclipse-foundation.org 
> <mailto:wayne.bea...@eclipse-foundation.org>> wrote:
> 
> There is no plan. Frankly, we've been just using the tools that we have 
> available. In the case of Google Docs, collaboration is the killer feature.
> 
> Google Docs are a useful means of doing initial collaboration. IMHO, 
> independent of any access issues, management of documents becomes pretty 
> unwieldy pretty quickly. My personal practice is to use Google Docs for that 
> initial rapid-paced collaboration and then move content into Asciidoc+Git for 
> ongoing development and maintenance (e.g. the Eclipse Foundation 
> Specification Process). This is not official Eclipse Foundation policy. It's 
> also not a good solution for non-technical collaborators.
> 
> I'm not quite sure what channel is the right channel to discuss options. 
> Perhaps you can open a bug against Community and we can start there.
> 
> Wayne
> 
> 
> 
> On Wed, Nov 28, 2018 at 3:06 AM Markus Tiede <markus.ti...@open-co.de 
> <mailto:markus.ti...@open-co.de>> wrote:
> Hi all,
> 
> just a (hopefully) quick question: are there any plans on moving away from 
> sharing information (e.g. links to documents on various mailing lists) via 
> Google-Docs? For us (Baloise) and probably others (behind corporate proxies 
> that block content / domains like these) it‘s not possible accessing these 
> documents / information (at work) at all.
> 
> It would be helpful getting some feedback whether others also face this issue 
> and if so how you handle it for now.
> 
> It‘d also be nice having something @eclipse that allows sharing these 
> documents!
> 
> ---
> Thanks in advance and with best regards,
> Markus Tiede
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> <mailto:cross-project-issues-dev@eclipse.org>
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>
> 
> -- 
> Wayne Beaton
> Director of Open Source Projects | Eclipse Foundation, Inc.
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 
> <mailto:cross-project-issues-dev@eclipse.org>
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to