Github user keith-turner commented on the issue:
    > Also, this raises the question... do we really need apidocs published on 
our site
    Personally, I like having the javadocs on the Fluo website.  However I am 
not opposed to dropping it from our website.     I like that it will be less 
work for us.  Also, does not currently have any advertisements.   I 
looked at the source for, they seem to track using google analytics 
which is ok w/ me.  
    We could put a base javadoc url in _config.yml.  Then we can update all 
javadoc links to use this base.  This will allow use to easily switch in the 
future if the website goes away or starts being sleazy in some way.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to