Re: installation documentation: which details do we need to specify?

That sounds like a good plan. We can also just add some language saying that these are platforms that are known to build, but that other platforms might also work given a compatible JDK. -David On Mon, Nov 23, 2015 at 3:44 PM, William Markito wrote: > Hi Karen, > > Indeed

Re: How can we get Geode docs viewable?

Thanks, Greg - we actually have a plan to move the hosted documentation to something like geode.docs.pivotal.io, but I'll be sure to update that link when the change is in place and older links are redirected. It turns out that Google indexing doesn't take place on any of the cfapps.io sites, so

Re: [VOTE] Grandfathering forgotten Geode contributors

+1 On Thursday, June 11, 2015, Dan Smith dsm...@pivotal.io wrote: +1 -Dan On Thu, Jun 11, 2015 at 4:19 PM, John Blum jb...@pivotal.io javascript:; wrote: +1 On Thu, Jun 11, 2015 at 4:18 PM, Wes Williams wwilli...@pivotal.io javascript:; wrote: +1 *Wes Williams |

Re: What should I do to correct documentation?

On Mon, Jun 8, 2015 at 10:06 AM, Greg Chase g...@gregchase.com wrote: Fabio - thanks for bringing these up. Please consider posting one or more JIRA's with your findings: https://issues.apache.org/jira/browse/GEODE/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel . Docs

Re: Bringing geode website into the project

On Thu, May 28, 2015 at 6:34 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: On Thu, May 28, 2015 at 8:53 AM, David Yozie dyo...@pivotal.io wrote: If we want to continue using the same publishing system we should probably manage the end-user docs source in a separate branch of whatever repo

Re: Bringing geode website into the project

On Wed, May 27, 2015 at 8:53 AM, Anthony Baker aba...@pivotal.io wrote: Aren’t we limited to a single repo during incubation? Pretty much. Within that repo we need to manage: - Source for geode components - Website source - Documentation source What are your thoughts for