@Lewis I think my team was operating under some different assumptions regarding our ability to push our github docs pages that are currently posted on Draperlaboratory/github to apache. I'll round up with them RE Greg's email. I think we all have consensus on the effect we want, but maybe some disconnects in how we think we can get it done.
For clarity's sake, here is the schema of how our websites/documentation will be managed. Corporate Branding of SensSoft: softwareasasensor.com redirects to draper.com/softwareasasensor (note that we will still be compliant with Apache marketing and branding rules regarding incubator projects). This page will of course link to Apache community and repos. Apache Community: incubator.apache.org/projects/sensoft.html will be our home page for our Apache projects, this will connect to vm requested (INFRA-12671) and host demos. Links to documentation redirect to git.io pages, which we are trying to build on Apache git resources (currently built on draperlaboratory/git repos). If we can just push these into git-wip.a.o as Greg suggests, then that problem is solved. More soon... -----Original Message----- From: lewis john mcgibbney [mailto:lewi...@apache.org] Sent: Tuesday, October 04, 2016 5:57 PM To: dev@senssoft.incubator.apache.org Subject: Re: Access to apache.github repos to add github.io pages [SENSSOFT] @Josh, On Tue, Oct 4, 2016 at 1:24 PM, < dev-digest-h...@senssoft.incubator.apache.org> wrote: > > From: "Poore, Joshua C." <jpo...@draper.com> > To: "infrastruct...@apache.org" <infrastruct...@apache.org> > Cc: "Mcgibbney, Lewis J (398M)" <lewis.j.mcgibb...@jpl.nasa.gov>, > "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>, " > dev@senssoft.incubator.apache.org" <dev@senssoft.incubator.apache.org> > Date: Tue, 04 Oct 2016 20:07:42 +0000 > Subject: Access to apache.github repos to add github.io pages > [SENSSOFT] > Hello- > > We're incubating at Apache. We'd like to move our github.io docs pages > from our old repos to our apache.github mirrors to consolidate > documentation. How best/who best to ask for permissions to stand these up? > Ideally, we'd like to generate sphinx templates for all Apache > SensSoft documentation that would live in these repos. > This was previously open over on https://issues.apache.org/jira/browse/INFRA-12264 Essentially if we can decide on a strategy then we can open a ticket within the INFRA Jira ticket and request resources there. As Greg has mentioned, we can do most of this ourselves. Would you want INFRA to create a new, separate Git-based repository at something like https://git-wip-us.apache.org/repos/asf/incubator-senssoft-website.git ? We could then create all documentation in sphinx, build it locally and push the docs to the Website for deployment. Honestly to me it doesn't matter but it would be good to get some consensus. Lewis ________________________________ Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately destroy all copies of this email. ________________________________
