At this point I’m willing to do the following with the Antora site effort:

- put the examples back into the Antora site
- find some way of including or referencing javadoc.
- figuring out how to relate to the  pypubsub system so the site is published 
through git.
- be the point of contact with infra.

What I’m not willing to do is try to have a two-builder site when AFAICT one 
part is distinctly inferior and less capable and no one will tell me anything 
about why it’s better or required or nice or ....
I’m also not willing to wait indefinitely for feedback.  If I proceed with this 
it will have to be commit-then-review, as my previous requests for review have 
generally been met with silence.

David Jencks

> On Aug 7, 2020, at 6:16 AM, Andrew Wetmore <andr...@apache.org> wrote:
> 
> Hi:
> 
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
> 
> There are several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
> 
> Please let me know whether your site is still on the Apache CMS and, if so,
> who will be the project point-of-contact with Infra for the migration.
> 
> Thank you!
> 
> 
> 
> 
> [1] https://infra.apache.org/project-site.html
> 
> [2]
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> 
> 
> -- 
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
> 
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Reply via email to