You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by Billie Rinaldi <bi...@gmail.com> on 2014/05/02 17:44:14 UTC
slider website
Regarding the imminent creation of our Slider website, it seems that CMS is
capable of building a site using Maven:
https://www.apache.org/dev/cmsref.html#external-build
http://svn.apache.org/repos/asf/maven/site/trunk/content
which is great, because that means we'd be able to edit markdown using CMS
and the buildbot would automatically regenerate the site.
So, what are people's thoughts on moving the site materials out of trunk
into site versus making a copy of them or generating them into site? I
think it would be easier to maintain the site if we just moved it, but I
don't know if we'd lose anything by not having the site documentation in
the source tree.
Billie
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
Thanks - this is starting to make more sense. I didn’t realize that the slider site files would reside in the infra website repo.
This seems like a viable approach. I’ll take a stab at implementation to see what it yields.
— Jon
On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>
> This is the actually nuts-and-bolts for how the CMS builds the site from Markdown. Very useful when you want to do some design locally and see some results. ASF also has more info on it you can read up on (make sure to catch the Python and Perl mod dependencies):
>
> https://www.apache.org/dev/cmsref.html#faq-build-tools
>
> Personally, I've really grown into the CMS and like it quite a bit, but I also enjoy all the documentation information that the maven site provides. Maybe there's some middle ground that we can do that we can reach that encapsulates some of the existing documentation from Github?
>
> On 5/2/14, 12:52 PM, Jon Maron wrote:
>> The other alternative is to forego the CMS and:
>>
>> 1) Manually login to people.apache.org
>> 2) create the web root directory for the project
>> 3) use svn to checkout the generated site (which I imagine would require us to add the generated files to svn)
>> 4) From that point on essentially use 'svn update' to update the site when sources are changed
>>
>> I think I like the idea of using the CMS approach, I'm just not certain how it's actually implemented (the one sentence indicating providing the correct args to the perl script gives no indication as to how that process actually works - do we invoke the script to build a new site, do we somehow configure CMS to execute the script periodically or manually, etc)
>>
>> -- Jon
>>
>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com> wrote:
>>
>>> Regarding the imminent creation of our Slider website, it seems that CMS is
>>> capable of building a site using Maven:
>>>
>>> https://www.apache.org/dev/cmsref.html#external-build
>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>>
>>> which is great, because that means we'd be able to edit markdown using CMS
>>> and the buildbot would automatically regenerate the site.
>>>
>>> So, what are people's thoughts on moving the site materials out of trunk
>>> into site versus making a copy of them or generating them into site? I
>>> think it would be easier to maintain the site if we just moved it, but I
>>> don't know if we'd lose anything by not having the site documentation in
>>> the source tree.
>>>
>>> Billie
>>
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Billie Rinaldi <bi...@gmail.com>.
They've changed the website urls, but not all of the documentation yet.
The right url should be slider.i.a.o.
On Mon, May 5, 2014 at 2:23 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
> On May 5, 2014, at 4:33 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
> > I’ve made some updates to the current site code in its current location.
> Given that CMS/infra is expecting the site source to be in
> https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear
> that this directory would require someone to create a local commit that:
> >
> > 1) adds a pom.xml file to the root (slider/site)
> > 2) Adds a content sub-directory (slider/site/content)
> > 3) moves current markdown files to either “content” or a
> “content/markdown” sub-directory (slider/site/content/markdown)
> > 4) mv site.xml to “content”
> > 5) move current resource dir to “content/resources”
> >
> > this all assumes that we can use the maven approach to building the site
> (setting maven as the external build approach). Is that something we file
> a JIRA for?
> >
> > Related question: is the only reason we don’t have a current site, even
> though there is a file in “slider/site” (index.html) in that root
> directory? For the time being I even tried mimicking the published content
> directory (i.e. I moved index.html to site/content/index.html) but still
> get a 404 from the website (incubator.apache.org/slider/), so I have very
> little confidence in undertaking the more extensive move outlined above.
>
> Did find an active site at http://slider.incubator.apache.org/, so the
> move to content folder appears a step in the right direction (as far as
> understanding site structure)
>
> >
> > — Jon
> >
> > On May 5, 2014, at 12:21 PM, Jon Maron <jm...@hortonworks.com> wrote:
> >
> >>
> >> On May 5, 2014, at 11:47 AM, Josh Elser <jo...@gmail.com> wrote:
> >>
> >>> On 5/5/14, 11:30 AM, Jon Maron wrote:
> >>>> On May 5, 2014, at 11:09 AM, Josh Elser<jo...@gmail.com> wrote:
> >>>>
> >>>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for starters?
> >>>> I’ve been iterating through this as well and made some changes:
> >>>>
> >>>> - announcement.html - doesn’t actually exist. for the time being I
> replaced it with a modified version of the getting_started doc we provided
> with the release last week
> >>>> - client_cofifguration.html - doesn’t exist. remove it?
> >>>> - cluster_descriptions - doesn’t exist. remove for now?
> >>>> - logging - same
> >>>>
> >>>> In addition, there was a bunch of stuff missing from pom to complete
> some of the standard menu items - <scm> update to svn settings, top level
> <url>, <mailingLists>, <distributionManagement>..
> >>>>
> >>>> Did you make similar changes or should I commit them so you can
> review?
> >>>>
> >>>
> >>> I made one content change (a newline) to make doxia work on trunk
> as-is, and updated a maven plugin to silence some errors coming out of
> Aether.
> >>>
> >>> Apparently I don't have commit rights though (or something is still
> hosed for me post-HB resets). I IM'ed Billie and she said she thinks she
> has the karma to verify that for me.
> >>>
> >>> In short, I was going to commit, but it's of no consequence for you to
> wait around for me to get there :). Fire away.
> >>
> >> Cool. Some of the changes will have to be modified when we move to git:
> >>
> >> <scm>
> >> <url>https://svn.apache.org/repos/asf/incubator/slider/</url>
> >> <connection>scm:svn:
> https://svn.apache.org/repos/asf/incubator/slider/
> >> </connection>
> >> <developerConnection>
> >> scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
> >> </developerConnection>
> >> </scm>
> >>
> >> — Jon
> >>
> >
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
On May 5, 2014, at 4:33 PM, Jon Maron <jm...@hortonworks.com> wrote:
> I’ve made some updates to the current site code in its current location. Given that CMS/infra is expecting the site source to be in https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that this directory would require someone to create a local commit that:
>
> 1) adds a pom.xml file to the root (slider/site)
> 2) Adds a content sub-directory (slider/site/content)
> 3) moves current markdown files to either “content” or a “content/markdown” sub-directory (slider/site/content/markdown)
> 4) mv site.xml to “content”
> 5) move current resource dir to “content/resources”
>
> this all assumes that we can use the maven approach to building the site (setting maven as the external build approach). Is that something we file a JIRA for?
>
> Related question: is the only reason we don’t have a current site, even though there is a file in “slider/site” (index.html) in that root directory? For the time being I even tried mimicking the published content directory (i.e. I moved index.html to site/content/index.html) but still get a 404 from the website (incubator.apache.org/slider/), so I have very little confidence in undertaking the more extensive move outlined above.
Did find an active site at http://slider.incubator.apache.org/, so the move to content folder appears a step in the right direction (as far as understanding site structure)
>
> — Jon
>
> On May 5, 2014, at 12:21 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
>>
>> On May 5, 2014, at 11:47 AM, Josh Elser <jo...@gmail.com> wrote:
>>
>>> On 5/5/14, 11:30 AM, Jon Maron wrote:
>>>> On May 5, 2014, at 11:09 AM, Josh Elser<jo...@gmail.com> wrote:
>>>>
>>>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for starters?
>>>> I’ve been iterating through this as well and made some changes:
>>>>
>>>> - announcement.html - doesn’t actually exist. for the time being I replaced it with a modified version of the getting_started doc we provided with the release last week
>>>> - client_cofifguration.html - doesn’t exist. remove it?
>>>> - cluster_descriptions - doesn’t exist. remove for now?
>>>> - logging - same
>>>>
>>>> In addition, there was a bunch of stuff missing from pom to complete some of the standard menu items - <scm> update to svn settings, top level <url>, <mailingLists>, <distributionManagement>..
>>>>
>>>> Did you make similar changes or should I commit them so you can review?
>>>>
>>>
>>> I made one content change (a newline) to make doxia work on trunk as-is, and updated a maven plugin to silence some errors coming out of Aether.
>>>
>>> Apparently I don't have commit rights though (or something is still hosed for me post-HB resets). I IM'ed Billie and she said she thinks she has the karma to verify that for me.
>>>
>>> In short, I was going to commit, but it's of no consequence for you to wait around for me to get there :). Fire away.
>>
>> Cool. Some of the changes will have to be modified when we move to git:
>>
>> <scm>
>> <url>https://svn.apache.org/repos/asf/incubator/slider/</url>
>> <connection>scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
>> </connection>
>> <developerConnection>
>> scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
>> </developerConnection>
>> </scm>
>>
>> — Jon
>>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
On May 5, 2014, at 4:33 PM, Jon Maron <jm...@hortonworks.com> wrote:
> I’ve made some updates to the current site code in its current location. Given that CMS/infra is expecting the site source to be in https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that this directory would require someone to create a local commit that:
>
> 1) adds a pom.xml file to the root (slider/site)
> 2) Adds a content sub-directory (slider/site/content)
> 3) moves current markdown files to either “content” or a “content/markdown” sub-directory (slider/site/content/markdown)
> 4) mv site.xml to “content”
> 5) move current resource dir to “content/resources”
>
> this all assumes that we can use the maven approach to building the site (setting maven as the external build approach). Is that something we file a JIRA for?
Assuming that a JIRA can be filed indicating a maven based site to CMS, I have a local commit that has the following (hanging off the https://svn.apache.org/repos/asf/incubator/slider/site/ repository root):
HW10386:slider-site jmaron$ svn status
D content/index.html
A content/markdown
A content/markdown/architecture
A content/markdown/architecture/architecture.md
A content/markdown/architecture/index.md
A content/markdown/architecture/rolehistory.md
A content/markdown/client-configuration.md
A content/markdown/configuration
A content/markdown/configuration/core.md
A content/markdown/configuration/example-app_configuration-resolved.json
A content/markdown/configuration/example-app_configuration.json
A content/markdown/configuration/example-empty.json
A content/markdown/configuration/example-internal.json
A content/markdown/configuration/example-overridden-resolved.json
A content/markdown/configuration/example-overridden.json
A content/markdown/configuration/example-resources.json
A content/markdown/configuration/index-markdown.md
A content/markdown/configuration/index.md
A content/markdown/configuration/original-hbase.json
A content/markdown/configuration/proposed-hbase.json
A content/markdown/configuration/redesign.md
A content/markdown/configuration/resolved-resources.json
A content/markdown/configuration/specification.md
A content/markdown/debugging.md
A content/markdown/developing
A content/markdown/developing/building.md
A content/markdown/developing/functional_tests.md
A content/markdown/developing/index.md
A content/markdown/developing/manual_testing.md
A content/markdown/developing/releasing.md
A content/markdown/developing/testing.md
A content/markdown/examples.md
A content/markdown/exitcodes.md
A content/markdown/getting_started.md
A content/markdown/index.md
A content/markdown/manpage.md
A content/markdown/registry
A content/markdown/registry/a_YARN_service_registry.md
A content/markdown/registry/index.md
A content/markdown/registry/initial_registry_design.md
A content/markdown/registry/p2p_service_registries.md
A content/markdown/registry/references.md
A content/markdown/registry/registry-model.md
A content/markdown/registry/service_registry_end_to_end_scenario.md
A content/markdown/registry/the_YARN_application_registration_and_binding_problem.md
A content/markdown/release_notes
A content/markdown/release_notes/release-0.22.0.md
A content/markdown/release_notes/release-0.24.0.md
A content/markdown/security.md
A content/markdown/slider_specs
A content/markdown/slider_specs/application_configuration.md
A content/markdown/slider_specs/application_definition.md
A content/markdown/slider_specs/application_instance_configuration.md
A content/markdown/slider_specs/application_needs.md
A content/markdown/slider_specs/application_package.md
A content/markdown/slider_specs/canonical_scenarios.md
A content/markdown/slider_specs/creating_app_definitions.md
A content/markdown/slider_specs/index.md
A content/markdown/slider_specs/resource_specification.md
A content/markdown/slider_specs/writing_app_command_scripts.md
A content/markdown/specification
A content/markdown/specification/cli-actions.md
A content/markdown/specification/index.md
A content/markdown/specification/slider-model.md
A content/markdown/troubleshooting.md
A content/resources
A content/resources/hoya_am_architecture.png
A content/resources/images
A content/resources/images/app_config_folders_01.png
A content/resources/images/app_package_sample_04.png
A content/resources/images/image_0.png
A content/resources/images/image_1.png
A content/resources/images/managed_client.png
A content/resources/images/slider-container.png
A content/resources/images/unmanaged_client.png
A content/site.xml
A pom.xml
The pom assumes that the site is built into the target/site directory (Is that what CMS expects?). If I move forward with this commit, we should probably remove the original markdown and site files from their current location (hanging off of https://svn.apache.org/repos/asf/incubator/slider/trunk/src/site).
>
> Related question: is the only reason we don’t have a current site, even though there is a file in “slider/site” (index.html) in that root directory? For the time being I even tried mimicking the published content directory (i.e. I moved index.html to site/content/index.html) but still get a 404 from the website (incubator.apache.org/slider/), so I have very little confidence in undertaking the more extensive move outlined above.
>
> — Jon
>
> On May 5, 2014, at 12:21 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
>>
>> On May 5, 2014, at 11:47 AM, Josh Elser <jo...@gmail.com> wrote:
>>
>>> On 5/5/14, 11:30 AM, Jon Maron wrote:
>>>> On May 5, 2014, at 11:09 AM, Josh Elser<jo...@gmail.com> wrote:
>>>>
>>>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for starters?
>>>> I’ve been iterating through this as well and made some changes:
>>>>
>>>> - announcement.html - doesn’t actually exist. for the time being I replaced it with a modified version of the getting_started doc we provided with the release last week
>>>> - client_cofifguration.html - doesn’t exist. remove it?
>>>> - cluster_descriptions - doesn’t exist. remove for now?
>>>> - logging - same
>>>>
>>>> In addition, there was a bunch of stuff missing from pom to complete some of the standard menu items - <scm> update to svn settings, top level <url>, <mailingLists>, <distributionManagement>..
>>>>
>>>> Did you make similar changes or should I commit them so you can review?
>>>>
>>>
>>> I made one content change (a newline) to make doxia work on trunk as-is, and updated a maven plugin to silence some errors coming out of Aether.
>>>
>>> Apparently I don't have commit rights though (or something is still hosed for me post-HB resets). I IM'ed Billie and she said she thinks she has the karma to verify that for me.
>>>
>>> In short, I was going to commit, but it's of no consequence for you to wait around for me to get there :). Fire away.
>>
>> Cool. Some of the changes will have to be modified when we move to git:
>>
>> <scm>
>> <url>https://svn.apache.org/repos/asf/incubator/slider/</url>
>> <connection>scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
>> </connection>
>> <developerConnection>
>> scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
>> </developerConnection>
>> </scm>
>>
>> — Jon
>>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
I’ve made some updates to the current site code in its current location. Given that CMS/infra is expecting the site source to be in https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that this directory would require someone to create a local commit that:
1) adds a pom.xml file to the root (slider/site)
2) Adds a content sub-directory (slider/site/content)
3) moves current markdown files to either “content” or a “content/markdown” sub-directory (slider/site/content/markdown)
4) mv site.xml to “content”
5) move current resource dir to “content/resources”
this all assumes that we can use the maven approach to building the site (setting maven as the external build approach). Is that something we file a JIRA for?
Related question: is the only reason we don’t have a current site, even though there is a file in “slider/site” (index.html) in that root directory? For the time being I even tried mimicking the published content directory (i.e. I moved index.html to site/content/index.html) but still get a 404 from the website (incubator.apache.org/slider/), so I have very little confidence in undertaking the more extensive move outlined above.
— Jon
On May 5, 2014, at 12:21 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
> On May 5, 2014, at 11:47 AM, Josh Elser <jo...@gmail.com> wrote:
>
>> On 5/5/14, 11:30 AM, Jon Maron wrote:
>>> On May 5, 2014, at 11:09 AM, Josh Elser<jo...@gmail.com> wrote:
>>>
>>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for starters?
>>> I’ve been iterating through this as well and made some changes:
>>>
>>> - announcement.html - doesn’t actually exist. for the time being I replaced it with a modified version of the getting_started doc we provided with the release last week
>>> - client_cofifguration.html - doesn’t exist. remove it?
>>> - cluster_descriptions - doesn’t exist. remove for now?
>>> - logging - same
>>>
>>> In addition, there was a bunch of stuff missing from pom to complete some of the standard menu items - <scm> update to svn settings, top level <url>, <mailingLists>, <distributionManagement>..
>>>
>>> Did you make similar changes or should I commit them so you can review?
>>>
>>
>> I made one content change (a newline) to make doxia work on trunk as-is, and updated a maven plugin to silence some errors coming out of Aether.
>>
>> Apparently I don't have commit rights though (or something is still hosed for me post-HB resets). I IM'ed Billie and she said she thinks she has the karma to verify that for me.
>>
>> In short, I was going to commit, but it's of no consequence for you to wait around for me to get there :). Fire away.
>
> Cool. Some of the changes will have to be modified when we move to git:
>
> <scm>
> <url>https://svn.apache.org/repos/asf/incubator/slider/</url>
> <connection>scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
> </connection>
> <developerConnection>
> scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
> </developerConnection>
> </scm>
>
> — Jon
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
On May 5, 2014, at 11:47 AM, Josh Elser <jo...@gmail.com> wrote:
> On 5/5/14, 11:30 AM, Jon Maron wrote:
>> On May 5, 2014, at 11:09 AM, Josh Elser<jo...@gmail.com> wrote:
>>
>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for starters?
>> I’ve been iterating through this as well and made some changes:
>>
>> - announcement.html - doesn’t actually exist. for the time being I replaced it with a modified version of the getting_started doc we provided with the release last week
>> - client_cofifguration.html - doesn’t exist. remove it?
>> - cluster_descriptions - doesn’t exist. remove for now?
>> - logging - same
>>
>> In addition, there was a bunch of stuff missing from pom to complete some of the standard menu items - <scm> update to svn settings, top level <url>, <mailingLists>, <distributionManagement>..
>>
>> Did you make similar changes or should I commit them so you can review?
>>
>
> I made one content change (a newline) to make doxia work on trunk as-is, and updated a maven plugin to silence some errors coming out of Aether.
>
> Apparently I don't have commit rights though (or something is still hosed for me post-HB resets). I IM'ed Billie and she said she thinks she has the karma to verify that for me.
>
> In short, I was going to commit, but it's of no consequence for you to wait around for me to get there :). Fire away.
Cool. Some of the changes will have to be modified when we move to git:
<scm>
<url>https://svn.apache.org/repos/asf/incubator/slider/</url>
<connection>scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
</connection>
<developerConnection>
scm:svn:https://svn.apache.org/repos/asf/incubator/slider/
</developerConnection>
</scm>
— Jon
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Josh Elser <jo...@gmail.com>.
On 5/5/14, 11:30 AM, Jon Maron wrote:
> On May 5, 2014, at 11:09 AM, Josh Elser<jo...@gmail.com> wrote:
>
>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for starters?
> I’ve been iterating through this as well and made some changes:
>
> - announcement.html - doesn’t actually exist. for the time being I replaced it with a modified version of the getting_started doc we provided with the release last week
> - client_cofifguration.html - doesn’t exist. remove it?
> - cluster_descriptions - doesn’t exist. remove for now?
> - logging - same
>
> In addition, there was a bunch of stuff missing from pom to complete some of the standard menu items - <scm> update to svn settings, top level <url>, <mailingLists>, <distributionManagement>..
>
> Did you make similar changes or should I commit them so you can review?
>
I made one content change (a newline) to make doxia work on trunk as-is,
and updated a maven plugin to silence some errors coming out of Aether.
Apparently I don't have commit rights though (or something is still
hosed for me post-HB resets). I IM'ed Billie and she said she thinks she
has the karma to verify that for me.
In short, I was going to commit, but it's of no consequence for you to
wait around for me to get there :). Fire away.
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
On May 5, 2014, at 11:09 AM, Josh Elser <jo...@gmail.com> wrote:
> Ah, ok. How does http://people.apache.org/~elserj/slider/site/ look for starters?
I’ve been iterating through this as well and made some changes:
- announcement.html - doesn’t actually exist. for the time being I replaced it with a modified version of the getting_started doc we provided with the release last week
- client_cofifguration.html - doesn’t exist. remove it?
- cluster_descriptions - doesn’t exist. remove for now?
- logging - same
In addition, there was a bunch of stuff missing from pom to complete some of the standard menu items - <scm> update to svn settings, top level <url>, <mailingLists>, <distributionManagement>..
Did you make similar changes or should I commit them so you can review?
>
> There's one oddity I found when poking at this that the doxia markdown converter (or Pegdown rather, as that's what's used underneath) and some issues with the Maven aether classdefnotfound issues that are easy to resolve.
>
> If we set the SVN info to the site element in distributionManangement in the top-level pom, will that auto update the repo (avoiding `mvn site:site` locally with a manual copy and `svn ci`)? If that's so, I believe once we get there, svnpubsub/buildbot/cms will take care of building/staging and we can review publish the site.
>
> On 5/5/14, 4:57 AM, Steve Loughran wrote:
>> I'd assumed that the slider site would be built the same way we do it for
>> other projects.
>>
>> -The content build just publishes into /site (that's mvn site:site
>> -DskipTests) for now
>> -we check it in
>> -something at apache triggers a site rebuild
>>
>> We can use the markdown content in src/site/markdown; these get turned into
>> html relative to the root dir, and means we can keep all the site source in
>> svn in sync with the actual releases
>>
>>
>>
>> On 2 May 2014 21:23, Billie Rinaldi <bi...@gmail.com> wrote:
>>
>>> On Fri, May 2, 2014 at 1:16 PM, Jon Maron <jm...@hortonworks.com> wrote:
>>>
>>>> Yeah - I just came to the same conclusion.
>>>>
>>>> The process would be to essentially create a separate maven project for
>>>> the web site - site.xml, md files, pom.xml etc. I think once created
>>> we’d
>>>> file a JIRA to enable the CMS integration (my guess is they are
>>> responsible
>>>> for enabling the “external build”, though there is a procedure for
>>> enabling
>>>> the process on a local box for testing)
>>>>
>>>> Any thoughts? Given its wide use, the CMS may the appropriate way to
>>>> proceed.
>>>>
>>>
>>> I think it's a good idea, but let's see how Steve feels about moving the
>>> docs out of the main project.
>>>
>>>
>>>>
>>>> — Jon
>>>>
>>>> On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com>
>>>> wrote:
>>>>
>>>>> I think that we create and populate the directory, then put in an INFRA
>>>>> request when it's ready to be hooked up to CMS.
>>>>>
>>>>>
>>>>> On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com>
>>>> wrote:
>>>>>
>>>>>> I’m not sure if I’m missing something, but it appears that there is a
>>>> need
>>>>>> to have infra create the initial SVN directory for CMS (e.g.
>>>>>> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
>>>>>>
>>>>>> — Jon
>>>>>>
>>>>>> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
>>>>>>
>>>>>>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>>>>>>>
>>>>>>> This is the actually nuts-and-bolts for how the CMS builds the site
>>>> from
>>>>>> Markdown. Very useful when you want to do some design locally and see
>>>> some
>>>>>> results. ASF also has more info on it you can read up on (make sure to
>>>>>> catch the Python and Perl mod dependencies):
>>>>>>>
>>>>>>> https://www.apache.org/dev/cmsref.html#faq-build-tools
>>>>>>>
>>>>>>> Personally, I've really grown into the CMS and like it quite a bit,
>>> but
>>>>>> I also enjoy all the documentation information that the maven site
>>>>>> provides. Maybe there's some middle ground that we can do that we can
>>>> reach
>>>>>> that encapsulates some of the existing documentation from Github?
>>>>>>>
>>>>>>> On 5/2/14, 12:52 PM, Jon Maron wrote:
>>>>>>>> The other alternative is to forego the CMS and:
>>>>>>>>
>>>>>>>> 1) Manually login to people.apache.org
>>>>>>>> 2) create the web root directory for the project
>>>>>>>> 3) use svn to checkout the generated site (which I imagine would
>>>>>> require us to add the generated files to svn)
>>>>>>>> 4) From that point on essentially use 'svn update' to update the
>>> site
>>>>>> when sources are changed
>>>>>>>>
>>>>>>>> I think I like the idea of using the CMS approach, I'm just not
>>>> certain
>>>>>> how it's actually implemented (the one sentence indicating providing
>>> the
>>>>>> correct args to the perl script gives no indication as to how that
>>>> process
>>>>>> actually works - do we invoke the script to build a new site, do we
>>>> somehow
>>>>>> configure CMS to execute the script periodically or manually, etc)
>>>>>>>>
>>>>>>>> -- Jon
>>>>>>>>
>>>>>>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <
>>> billie.rinaldi@gmail.com
>>>>>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Regarding the imminent creation of our Slider website, it seems
>>> that
>>>>>> CMS is
>>>>>>>>> capable of building a site using Maven:
>>>>>>>>>
>>>>>>>>> https://www.apache.org/dev/cmsref.html#external-build
>>>>>>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>>>>>>>>
>>>>>>>>> which is great, because that means we'd be able to edit markdown
>>>> using
>>>>>> CMS
>>>>>>>>> and the buildbot would automatically regenerate the site.
>>>>>>>>>
>>>>>>>>> So, what are people's thoughts on moving the site materials out of
>>>>>> trunk
>>>>>>>>> into site versus making a copy of them or generating them into
>>> site?
>>>> I
>>>>>>>>> think it would be easier to maintain the site if we just moved it,
>>>> but
>>>>>> I
>>>>>>>>> don't know if we'd lose anything by not having the site
>>> documentation
>>>>>> in
>>>>>>>>> the source tree.
>>>>>>>>>
>>>>>>>>> Billie
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> CONFIDENTIALITY NOTICE
>>>>>> NOTICE: This message is intended for the use of the individual or
>>>> entity to
>>>>>> which it is addressed and may contain information that is
>>> confidential,
>>>>>> privileged and exempt from disclosure under applicable law. If the
>>>> reader
>>>>>> of this message is not the intended recipient, you are hereby notified
>>>> that
>>>>>> any printing, copying, dissemination, distribution, disclosure or
>>>>>> forwarding of this communication is strictly prohibited. If you have
>>>>>> received this communication in error, please contact the sender
>>>> immediately
>>>>>> and delete it from your system. Thank You.
>>>>>>
>>>>
>>>>
>>>> --
>>>> CONFIDENTIALITY NOTICE
>>>> NOTICE: This message is intended for the use of the individual or entity
>>> to
>>>> which it is addressed and may contain information that is confidential,
>>>> privileged and exempt from disclosure under applicable law. If the reader
>>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>>> any printing, copying, dissemination, distribution, disclosure or
>>>> forwarding of this communication is strictly prohibited. If you have
>>>> received this communication in error, please contact the sender
>>> immediately
>>>> and delete it from your system. Thank You.
>>>>
>>>
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Josh Elser <jo...@gmail.com>.
Ah, ok. How does http://people.apache.org/~elserj/slider/site/ look for
starters?
There's one oddity I found when poking at this that the doxia markdown
converter (or Pegdown rather, as that's what's used underneath) and some
issues with the Maven aether classdefnotfound issues that are easy to
resolve.
If we set the SVN info to the site element in distributionManangement in
the top-level pom, will that auto update the repo (avoiding `mvn
site:site` locally with a manual copy and `svn ci`)? If that's so, I
believe once we get there, svnpubsub/buildbot/cms will take care of
building/staging and we can review publish the site.
On 5/5/14, 4:57 AM, Steve Loughran wrote:
> I'd assumed that the slider site would be built the same way we do it for
> other projects.
>
> -The content build just publishes into /site (that's mvn site:site
> -DskipTests) for now
> -we check it in
> -something at apache triggers a site rebuild
>
> We can use the markdown content in src/site/markdown; these get turned into
> html relative to the root dir, and means we can keep all the site source in
> svn in sync with the actual releases
>
>
>
> On 2 May 2014 21:23, Billie Rinaldi <bi...@gmail.com> wrote:
>
>> On Fri, May 2, 2014 at 1:16 PM, Jon Maron <jm...@hortonworks.com> wrote:
>>
>>> Yeah - I just came to the same conclusion.
>>>
>>> The process would be to essentially create a separate maven project for
>>> the web site - site.xml, md files, pom.xml etc. I think once created
>> we’d
>>> file a JIRA to enable the CMS integration (my guess is they are
>> responsible
>>> for enabling the “external build”, though there is a procedure for
>> enabling
>>> the process on a local box for testing)
>>>
>>> Any thoughts? Given its wide use, the CMS may the appropriate way to
>>> proceed.
>>>
>>
>> I think it's a good idea, but let's see how Steve feels about moving the
>> docs out of the main project.
>>
>>
>>>
>>> — Jon
>>>
>>> On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com>
>>> wrote:
>>>
>>>> I think that we create and populate the directory, then put in an INFRA
>>>> request when it's ready to be hooked up to CMS.
>>>>
>>>>
>>>> On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com>
>>> wrote:
>>>>
>>>>> I’m not sure if I’m missing something, but it appears that there is a
>>> need
>>>>> to have infra create the initial SVN directory for CMS (e.g.
>>>>> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
>>>>>
>>>>> — Jon
>>>>>
>>>>> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
>>>>>
>>>>>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>>>>>>
>>>>>> This is the actually nuts-and-bolts for how the CMS builds the site
>>> from
>>>>> Markdown. Very useful when you want to do some design locally and see
>>> some
>>>>> results. ASF also has more info on it you can read up on (make sure to
>>>>> catch the Python and Perl mod dependencies):
>>>>>>
>>>>>> https://www.apache.org/dev/cmsref.html#faq-build-tools
>>>>>>
>>>>>> Personally, I've really grown into the CMS and like it quite a bit,
>> but
>>>>> I also enjoy all the documentation information that the maven site
>>>>> provides. Maybe there's some middle ground that we can do that we can
>>> reach
>>>>> that encapsulates some of the existing documentation from Github?
>>>>>>
>>>>>> On 5/2/14, 12:52 PM, Jon Maron wrote:
>>>>>>> The other alternative is to forego the CMS and:
>>>>>>>
>>>>>>> 1) Manually login to people.apache.org
>>>>>>> 2) create the web root directory for the project
>>>>>>> 3) use svn to checkout the generated site (which I imagine would
>>>>> require us to add the generated files to svn)
>>>>>>> 4) From that point on essentially use 'svn update' to update the
>> site
>>>>> when sources are changed
>>>>>>>
>>>>>>> I think I like the idea of using the CMS approach, I'm just not
>>> certain
>>>>> how it's actually implemented (the one sentence indicating providing
>> the
>>>>> correct args to the perl script gives no indication as to how that
>>> process
>>>>> actually works - do we invoke the script to build a new site, do we
>>> somehow
>>>>> configure CMS to execute the script periodically or manually, etc)
>>>>>>>
>>>>>>> -- Jon
>>>>>>>
>>>>>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <
>> billie.rinaldi@gmail.com
>>>>
>>>>> wrote:
>>>>>>>
>>>>>>>> Regarding the imminent creation of our Slider website, it seems
>> that
>>>>> CMS is
>>>>>>>> capable of building a site using Maven:
>>>>>>>>
>>>>>>>> https://www.apache.org/dev/cmsref.html#external-build
>>>>>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>>>>>>>
>>>>>>>> which is great, because that means we'd be able to edit markdown
>>> using
>>>>> CMS
>>>>>>>> and the buildbot would automatically regenerate the site.
>>>>>>>>
>>>>>>>> So, what are people's thoughts on moving the site materials out of
>>>>> trunk
>>>>>>>> into site versus making a copy of them or generating them into
>> site?
>>> I
>>>>>>>> think it would be easier to maintain the site if we just moved it,
>>> but
>>>>> I
>>>>>>>> don't know if we'd lose anything by not having the site
>> documentation
>>>>> in
>>>>>>>> the source tree.
>>>>>>>>
>>>>>>>> Billie
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> CONFIDENTIALITY NOTICE
>>>>> NOTICE: This message is intended for the use of the individual or
>>> entity to
>>>>> which it is addressed and may contain information that is
>> confidential,
>>>>> privileged and exempt from disclosure under applicable law. If the
>>> reader
>>>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>>>> any printing, copying, dissemination, distribution, disclosure or
>>>>> forwarding of this communication is strictly prohibited. If you have
>>>>> received this communication in error, please contact the sender
>>> immediately
>>>>> and delete it from your system. Thank You.
>>>>>
>>>
>>>
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity
>> to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified
>> that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender
>> immediately
>>> and delete it from your system. Thank You.
>>>
>>
>
Re: slider website
Posted by Josh Elser <jo...@gmail.com>.
On 5/5/14, 11:16 AM, Josh Elser wrote:
> On 5/5/14, 11:08 AM, Jon Maron wrote:
>>
>> On May 5, 2014, at 10:40 AM, Josh Elser <jo...@gmail.com> wrote:
>>
>>> On 5/5/14, 9:52 AM, Jon Maron wrote:
>>>> On May 5, 2014, at 9:19 AM, Steve Loughran<st...@hortonworks.com>
>>>> wrote:
>>>>
>>>>>> OK, to make life more complicated, we can't use svnpubsub and
>>>>>> git, so if
>>>>>> we switch to git, then we have to use CMS
>>>>>>
>>>>>> Having been back in svn for a couple of days, I'm missing some of
>>>>>> the git
>>>>>> features, not just in the Atlassian SourceTree tool, but in the
>>>>>> difficultly
>>>>>> in switching branches, and of selectively committing bits of a
>>>>>> source file.
>>>>>> This makes it a lot fiddlier to work on short-lived feature
>>>>>> branches, and
>>>>>> to isolate changes into individual commits.
>>>>>>
>>>>>> I'm going to propose filing an INFRA ticket to move the svn repo
>>>>>> to git
>>>>>> -the svn commit gives us the donation of source, the git give us a
>>>>>> git-based dev process. Which implies CMS for content
>>>> Which implies a separation of the two sources (code source and web
>>>> site source), correct? Should I simply proceed with creating a
>>>> separate CMS repo based markdown source project?
>>>>
>>>
>>> Bingo, the site would be in SVN with code in Git. When we do the
>>> transition, we'd just leave
>>> http://svn.apache.org/repos/asf/incubator/slider/site/ still intact.
>>>
>>> We've been operating that way in Accumulo for some time without
>>> issue. I'd have no reservations against doing it here.
>>
>> Given our use for the maven site building approach, it looks like the
>> structure for http://svn.apache.org/repos/asf/incubator/slider/site/
>> would be:
>>
>> trunk/
>> pom.xml - pom with site building info, plugin etc
>> content/
>> site.xml
>> markdow/
>> - *.md files
>> resources/
>> /images
>>
>> I imagine at that point we just file a JIRA indicating the site repo
>> is ready and is a maven based build.
>>
>> — Jon
>>
>
> I don't think the site would be a full-fledged repo on its own. We could
> either maintain our own site with the markdown files we have or we could
> just publish what `mvn site:site` generates for us, along with ASF
> incubating required docs.
>
> The former gives us much more freedom over designing a website with
> branding for the project, while the latter lets us just write docs and
> we get what maven (and the chosen skin) gives us and lets the docs be
> co-located with the source.
>
> I could go either way. I'll commit in the fixes I made to get the site
> building locally -- don't take that as me asserting that we must use the
> maven-generated site though :)
ps. sorry, I missed Billie initial email because I wasn't subscribed
quick enough. My apologies - I didn't see her "CMS is capable of
building a site using Maven" before.
Re: slider website
Posted by Josh Elser <jo...@gmail.com>.
On 5/5/14, 11:08 AM, Jon Maron wrote:
>
> On May 5, 2014, at 10:40 AM, Josh Elser <jo...@gmail.com> wrote:
>
>> On 5/5/14, 9:52 AM, Jon Maron wrote:
>>> On May 5, 2014, at 9:19 AM, Steve Loughran<st...@hortonworks.com> wrote:
>>>
>>>>> OK, to make life more complicated, we can't use svnpubsub and git, so if
>>>>> we switch to git, then we have to use CMS
>>>>>
>>>>> Having been back in svn for a couple of days, I'm missing some of the git
>>>>> features, not just in the Atlassian SourceTree tool, but in the difficultly
>>>>> in switching branches, and of selectively committing bits of a source file.
>>>>> This makes it a lot fiddlier to work on short-lived feature branches, and
>>>>> to isolate changes into individual commits.
>>>>>
>>>>> I'm going to propose filing an INFRA ticket to move the svn repo to git
>>>>> -the svn commit gives us the donation of source, the git give us a
>>>>> git-based dev process. Which implies CMS for content
>>> Which implies a separation of the two sources (code source and web site source), correct? Should I simply proceed with creating a separate CMS repo based markdown source project?
>>>
>>
>> Bingo, the site would be in SVN with code in Git. When we do the transition, we'd just leave http://svn.apache.org/repos/asf/incubator/slider/site/ still intact.
>>
>> We've been operating that way in Accumulo for some time without issue. I'd have no reservations against doing it here.
>
> Given our use for the maven site building approach, it looks like the structure for http://svn.apache.org/repos/asf/incubator/slider/site/ would be:
>
> trunk/
> pom.xml - pom with site building info, plugin etc
> content/
> site.xml
> markdow/
> - *.md files
> resources/
> /images
>
> I imagine at that point we just file a JIRA indicating the site repo is ready and is a maven based build.
>
> — Jon
>
I don't think the site would be a full-fledged repo on its own. We could
either maintain our own site with the markdown files we have or we could
just publish what `mvn site:site` generates for us, along with ASF
incubating required docs.
The former gives us much more freedom over designing a website with
branding for the project, while the latter lets us just write docs and
we get what maven (and the chosen skin) gives us and lets the docs be
co-located with the source.
I could go either way. I'll commit in the fixes I made to get the site
building locally -- don't take that as me asserting that we must use the
maven-generated site though :)
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
On May 5, 2014, at 10:40 AM, Josh Elser <jo...@gmail.com> wrote:
> On 5/5/14, 9:52 AM, Jon Maron wrote:
>> On May 5, 2014, at 9:19 AM, Steve Loughran<st...@hortonworks.com> wrote:
>>
>>> >OK, to make life more complicated, we can't use svnpubsub and git, so if
>>> >we switch to git, then we have to use CMS
>>> >
>>> >Having been back in svn for a couple of days, I'm missing some of the git
>>> >features, not just in the Atlassian SourceTree tool, but in the difficultly
>>> >in switching branches, and of selectively committing bits of a source file.
>>> >This makes it a lot fiddlier to work on short-lived feature branches, and
>>> >to isolate changes into individual commits.
>>> >
>>> >I'm going to propose filing an INFRA ticket to move the svn repo to git
>>> >-the svn commit gives us the donation of source, the git give us a
>>> >git-based dev process. Which implies CMS for content
>> Which implies a separation of the two sources (code source and web site source), correct? Should I simply proceed with creating a separate CMS repo based markdown source project?
>>
>
> Bingo, the site would be in SVN with code in Git. When we do the transition, we'd just leave http://svn.apache.org/repos/asf/incubator/slider/site/ still intact.
>
> We've been operating that way in Accumulo for some time without issue. I'd have no reservations against doing it here.
Given our use for the maven site building approach, it looks like the structure for http://svn.apache.org/repos/asf/incubator/slider/site/ would be:
trunk/
pom.xml - pom with site building info, plugin etc
content/
site.xml
markdow/
- *.md files
resources/
/images
I imagine at that point we just file a JIRA indicating the site repo is ready and is a maven based build.
— Jon
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Josh Elser <jo...@gmail.com>.
On 5/5/14, 9:52 AM, Jon Maron wrote:
> On May 5, 2014, at 9:19 AM, Steve Loughran<st...@hortonworks.com> wrote:
>
>> >OK, to make life more complicated, we can't use svnpubsub and git, so if
>> >we switch to git, then we have to use CMS
>> >
>> >Having been back in svn for a couple of days, I'm missing some of the git
>> >features, not just in the Atlassian SourceTree tool, but in the difficultly
>> >in switching branches, and of selectively committing bits of a source file.
>> >This makes it a lot fiddlier to work on short-lived feature branches, and
>> >to isolate changes into individual commits.
>> >
>> >I'm going to propose filing an INFRA ticket to move the svn repo to git
>> >-the svn commit gives us the donation of source, the git give us a
>> >git-based dev process. Which implies CMS for content
> Which implies a separation of the two sources (code source and web site source), correct? Should I simply proceed with creating a separate CMS repo based markdown source project?
>
Bingo, the site would be in SVN with code in Git. When we do the
transition, we'd just leave
http://svn.apache.org/repos/asf/incubator/slider/site/ still intact.
We've been operating that way in Accumulo for some time without issue.
I'd have no reservations against doing it here.
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
On May 5, 2014, at 9:19 AM, Steve Loughran <st...@hortonworks.com> wrote:
> OK, to make life more complicated, we can't use svnpubsub and git, so if
> we switch to git, then we have to use CMS
>
> Having been back in svn for a couple of days, I'm missing some of the git
> features, not just in the Atlassian SourceTree tool, but in the difficultly
> in switching branches, and of selectively committing bits of a source file.
> This makes it a lot fiddlier to work on short-lived feature branches, and
> to isolate changes into individual commits.
>
> I'm going to propose filing an INFRA ticket to move the svn repo to git
> -the svn commit gives us the donation of source, the git give us a
> git-based dev process. Which implies CMS for content
Which implies a separation of the two sources (code source and web site source), correct? Should I simply proceed with creating a separate CMS repo based markdown source project?
>
>
>
>
> On 5 May 2014 09:57, Steve Loughran <st...@hortonworks.com> wrote:
>
>> I'd assumed that the slider site would be built the same way we do it for
>> other projects.
>>
>> -The content build just publishes into /site (that's mvn site:site
>> -DskipTests) for now
>> -we check it in
>> -something at apache triggers a site rebuild
>>
>> We can use the markdown content in src/site/markdown; these get turned
>> into html relative to the root dir, and means we can keep all the site
>> source in svn in sync with the actual releases
>>
>>
>>
>> On 2 May 2014 21:23, Billie Rinaldi <bi...@gmail.com> wrote:
>>
>>> On Fri, May 2, 2014 at 1:16 PM, Jon Maron <jm...@hortonworks.com> wrote:
>>>
>>>> Yeah - I just came to the same conclusion.
>>>>
>>>> The process would be to essentially create a separate maven project for
>>>> the web site - site.xml, md files, pom.xml etc. I think once created
>>> we’d
>>>> file a JIRA to enable the CMS integration (my guess is they are
>>> responsible
>>>> for enabling the “external build”, though there is a procedure for
>>> enabling
>>>> the process on a local box for testing)
>>>>
>>>> Any thoughts? Given its wide use, the CMS may the appropriate way to
>>>> proceed.
>>>>
>>>
>>> I think it's a good idea, but let's see how Steve feels about moving the
>>> docs out of the main project.
>>>
>>>
>>>>
>>>> — Jon
>>>>
>>>> On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com>
>>>> wrote:
>>>>
>>>>> I think that we create and populate the directory, then put in an
>>> INFRA
>>>>> request when it's ready to be hooked up to CMS.
>>>>>
>>>>>
>>>>> On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com>
>>>> wrote:
>>>>>
>>>>>> I’m not sure if I’m missing something, but it appears that there is a
>>>> need
>>>>>> to have infra create the initial SVN directory for CMS (e.g.
>>>>>> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
>>>>>>
>>>>>> — Jon
>>>>>>
>>>>>> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
>>>>>>
>>>>>>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>>>>>>>
>>>>>>> This is the actually nuts-and-bolts for how the CMS builds the site
>>>> from
>>>>>> Markdown. Very useful when you want to do some design locally and see
>>>> some
>>>>>> results. ASF also has more info on it you can read up on (make sure
>>> to
>>>>>> catch the Python and Perl mod dependencies):
>>>>>>>
>>>>>>> https://www.apache.org/dev/cmsref.html#faq-build-tools
>>>>>>>
>>>>>>> Personally, I've really grown into the CMS and like it quite a bit,
>>> but
>>>>>> I also enjoy all the documentation information that the maven site
>>>>>> provides. Maybe there's some middle ground that we can do that we can
>>>> reach
>>>>>> that encapsulates some of the existing documentation from Github?
>>>>>>>
>>>>>>> On 5/2/14, 12:52 PM, Jon Maron wrote:
>>>>>>>> The other alternative is to forego the CMS and:
>>>>>>>>
>>>>>>>> 1) Manually login to people.apache.org
>>>>>>>> 2) create the web root directory for the project
>>>>>>>> 3) use svn to checkout the generated site (which I imagine would
>>>>>> require us to add the generated files to svn)
>>>>>>>> 4) From that point on essentially use 'svn update' to update the
>>> site
>>>>>> when sources are changed
>>>>>>>>
>>>>>>>> I think I like the idea of using the CMS approach, I'm just not
>>>> certain
>>>>>> how it's actually implemented (the one sentence indicating providing
>>> the
>>>>>> correct args to the perl script gives no indication as to how that
>>>> process
>>>>>> actually works - do we invoke the script to build a new site, do we
>>>> somehow
>>>>>> configure CMS to execute the script periodically or manually, etc)
>>>>>>>>
>>>>>>>> -- Jon
>>>>>>>>
>>>>>>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <
>>> billie.rinaldi@gmail.com
>>>>>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Regarding the imminent creation of our Slider website, it seems
>>> that
>>>>>> CMS is
>>>>>>>>> capable of building a site using Maven:
>>>>>>>>>
>>>>>>>>> https://www.apache.org/dev/cmsref.html#external-build
>>>>>>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>>>>>>>>
>>>>>>>>> which is great, because that means we'd be able to edit markdown
>>>> using
>>>>>> CMS
>>>>>>>>> and the buildbot would automatically regenerate the site.
>>>>>>>>>
>>>>>>>>> So, what are people's thoughts on moving the site materials out of
>>>>>> trunk
>>>>>>>>> into site versus making a copy of them or generating them into
>>> site?
>>>> I
>>>>>>>>> think it would be easier to maintain the site if we just moved it,
>>>> but
>>>>>> I
>>>>>>>>> don't know if we'd lose anything by not having the site
>>> documentation
>>>>>> in
>>>>>>>>> the source tree.
>>>>>>>>>
>>>>>>>>> Billie
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> CONFIDENTIALITY NOTICE
>>>>>> NOTICE: This message is intended for the use of the individual or
>>>> entity to
>>>>>> which it is addressed and may contain information that is
>>> confidential,
>>>>>> privileged and exempt from disclosure under applicable law. If the
>>>> reader
>>>>>> of this message is not the intended recipient, you are hereby
>>> notified
>>>> that
>>>>>> any printing, copying, dissemination, distribution, disclosure or
>>>>>> forwarding of this communication is strictly prohibited. If you have
>>>>>> received this communication in error, please contact the sender
>>>> immediately
>>>>>> and delete it from your system. Thank You.
>>>>>>
>>>>
>>>>
>>>> --
>>>> CONFIDENTIALITY NOTICE
>>>> NOTICE: This message is intended for the use of the individual or
>>> entity to
>>>> which it is addressed and may contain information that is confidential,
>>>> privileged and exempt from disclosure under applicable law. If the
>>> reader
>>>> of this message is not the intended recipient, you are hereby notified
>>> that
>>>> any printing, copying, dissemination, distribution, disclosure or
>>>> forwarding of this communication is strictly prohibited. If you have
>>>> received this communication in error, please contact the sender
>>> immediately
>>>> and delete it from your system. Thank You.
>>>>
>>>
>>
>>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Steve Loughran <st...@hortonworks.com>.
OK, to make life more complicated, we can't use svnpubsub and git, so if
we switch to git, then we have to use CMS
Having been back in svn for a couple of days, I'm missing some of the git
features, not just in the Atlassian SourceTree tool, but in the difficultly
in switching branches, and of selectively committing bits of a source file.
This makes it a lot fiddlier to work on short-lived feature branches, and
to isolate changes into individual commits.
I'm going to propose filing an INFRA ticket to move the svn repo to git
-the svn commit gives us the donation of source, the git give us a
git-based dev process. Which implies CMS for content
On 5 May 2014 09:57, Steve Loughran <st...@hortonworks.com> wrote:
> I'd assumed that the slider site would be built the same way we do it for
> other projects.
>
> -The content build just publishes into /site (that's mvn site:site
> -DskipTests) for now
> -we check it in
> -something at apache triggers a site rebuild
>
> We can use the markdown content in src/site/markdown; these get turned
> into html relative to the root dir, and means we can keep all the site
> source in svn in sync with the actual releases
>
>
>
> On 2 May 2014 21:23, Billie Rinaldi <bi...@gmail.com> wrote:
>
>> On Fri, May 2, 2014 at 1:16 PM, Jon Maron <jm...@hortonworks.com> wrote:
>>
>> > Yeah - I just came to the same conclusion.
>> >
>> > The process would be to essentially create a separate maven project for
>> > the web site - site.xml, md files, pom.xml etc. I think once created
>> we’d
>> > file a JIRA to enable the CMS integration (my guess is they are
>> responsible
>> > for enabling the “external build”, though there is a procedure for
>> enabling
>> > the process on a local box for testing)
>> >
>> > Any thoughts? Given its wide use, the CMS may the appropriate way to
>> > proceed.
>> >
>>
>> I think it's a good idea, but let's see how Steve feels about moving the
>> docs out of the main project.
>>
>>
>> >
>> > — Jon
>> >
>> > On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com>
>> > wrote:
>> >
>> > > I think that we create and populate the directory, then put in an
>> INFRA
>> > > request when it's ready to be hooked up to CMS.
>> > >
>> > >
>> > > On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com>
>> > wrote:
>> > >
>> > >> I’m not sure if I’m missing something, but it appears that there is a
>> > need
>> > >> to have infra create the initial SVN directory for CMS (e.g.
>> > >> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
>> > >>
>> > >> — Jon
>> > >>
>> > >> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
>> > >>
>> > >>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>> > >>>
>> > >>> This is the actually nuts-and-bolts for how the CMS builds the site
>> > from
>> > >> Markdown. Very useful when you want to do some design locally and see
>> > some
>> > >> results. ASF also has more info on it you can read up on (make sure
>> to
>> > >> catch the Python and Perl mod dependencies):
>> > >>>
>> > >>> https://www.apache.org/dev/cmsref.html#faq-build-tools
>> > >>>
>> > >>> Personally, I've really grown into the CMS and like it quite a bit,
>> but
>> > >> I also enjoy all the documentation information that the maven site
>> > >> provides. Maybe there's some middle ground that we can do that we can
>> > reach
>> > >> that encapsulates some of the existing documentation from Github?
>> > >>>
>> > >>> On 5/2/14, 12:52 PM, Jon Maron wrote:
>> > >>>> The other alternative is to forego the CMS and:
>> > >>>>
>> > >>>> 1) Manually login to people.apache.org
>> > >>>> 2) create the web root directory for the project
>> > >>>> 3) use svn to checkout the generated site (which I imagine would
>> > >> require us to add the generated files to svn)
>> > >>>> 4) From that point on essentially use 'svn update' to update the
>> site
>> > >> when sources are changed
>> > >>>>
>> > >>>> I think I like the idea of using the CMS approach, I'm just not
>> > certain
>> > >> how it's actually implemented (the one sentence indicating providing
>> the
>> > >> correct args to the perl script gives no indication as to how that
>> > process
>> > >> actually works - do we invoke the script to build a new site, do we
>> > somehow
>> > >> configure CMS to execute the script periodically or manually, etc)
>> > >>>>
>> > >>>> -- Jon
>> > >>>>
>> > >>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <
>> billie.rinaldi@gmail.com
>> > >
>> > >> wrote:
>> > >>>>
>> > >>>>> Regarding the imminent creation of our Slider website, it seems
>> that
>> > >> CMS is
>> > >>>>> capable of building a site using Maven:
>> > >>>>>
>> > >>>>> https://www.apache.org/dev/cmsref.html#external-build
>> > >>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>> > >>>>>
>> > >>>>> which is great, because that means we'd be able to edit markdown
>> > using
>> > >> CMS
>> > >>>>> and the buildbot would automatically regenerate the site.
>> > >>>>>
>> > >>>>> So, what are people's thoughts on moving the site materials out of
>> > >> trunk
>> > >>>>> into site versus making a copy of them or generating them into
>> site?
>> > I
>> > >>>>> think it would be easier to maintain the site if we just moved it,
>> > but
>> > >> I
>> > >>>>> don't know if we'd lose anything by not having the site
>> documentation
>> > >> in
>> > >>>>> the source tree.
>> > >>>>>
>> > >>>>> Billie
>> > >>>>
>> > >>>>
>> > >>
>> > >>
>> > >> --
>> > >> CONFIDENTIALITY NOTICE
>> > >> NOTICE: This message is intended for the use of the individual or
>> > entity to
>> > >> which it is addressed and may contain information that is
>> confidential,
>> > >> privileged and exempt from disclosure under applicable law. If the
>> > reader
>> > >> of this message is not the intended recipient, you are hereby
>> notified
>> > that
>> > >> any printing, copying, dissemination, distribution, disclosure or
>> > >> forwarding of this communication is strictly prohibited. If you have
>> > >> received this communication in error, please contact the sender
>> > immediately
>> > >> and delete it from your system. Thank You.
>> > >>
>> >
>> >
>> > --
>> > CONFIDENTIALITY NOTICE
>> > NOTICE: This message is intended for the use of the individual or
>> entity to
>> > which it is addressed and may contain information that is confidential,
>> > privileged and exempt from disclosure under applicable law. If the
>> reader
>> > of this message is not the intended recipient, you are hereby notified
>> that
>> > any printing, copying, dissemination, distribution, disclosure or
>> > forwarding of this communication is strictly prohibited. If you have
>> > received this communication in error, please contact the sender
>> immediately
>> > and delete it from your system. Thank You.
>> >
>>
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Steve Loughran <st...@hortonworks.com>.
I'd assumed that the slider site would be built the same way we do it for
other projects.
-The content build just publishes into /site (that's mvn site:site
-DskipTests) for now
-we check it in
-something at apache triggers a site rebuild
We can use the markdown content in src/site/markdown; these get turned into
html relative to the root dir, and means we can keep all the site source in
svn in sync with the actual releases
On 2 May 2014 21:23, Billie Rinaldi <bi...@gmail.com> wrote:
> On Fri, May 2, 2014 at 1:16 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
> > Yeah - I just came to the same conclusion.
> >
> > The process would be to essentially create a separate maven project for
> > the web site - site.xml, md files, pom.xml etc. I think once created
> we’d
> > file a JIRA to enable the CMS integration (my guess is they are
> responsible
> > for enabling the “external build”, though there is a procedure for
> enabling
> > the process on a local box for testing)
> >
> > Any thoughts? Given its wide use, the CMS may the appropriate way to
> > proceed.
> >
>
> I think it's a good idea, but let's see how Steve feels about moving the
> docs out of the main project.
>
>
> >
> > — Jon
> >
> > On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com>
> > wrote:
> >
> > > I think that we create and populate the directory, then put in an INFRA
> > > request when it's ready to be hooked up to CMS.
> > >
> > >
> > > On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com>
> > wrote:
> > >
> > >> I’m not sure if I’m missing something, but it appears that there is a
> > need
> > >> to have infra create the initial SVN directory for CMS (e.g.
> > >> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
> > >>
> > >> — Jon
> > >>
> > >> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
> > >>
> > >>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
> > >>>
> > >>> This is the actually nuts-and-bolts for how the CMS builds the site
> > from
> > >> Markdown. Very useful when you want to do some design locally and see
> > some
> > >> results. ASF also has more info on it you can read up on (make sure to
> > >> catch the Python and Perl mod dependencies):
> > >>>
> > >>> https://www.apache.org/dev/cmsref.html#faq-build-tools
> > >>>
> > >>> Personally, I've really grown into the CMS and like it quite a bit,
> but
> > >> I also enjoy all the documentation information that the maven site
> > >> provides. Maybe there's some middle ground that we can do that we can
> > reach
> > >> that encapsulates some of the existing documentation from Github?
> > >>>
> > >>> On 5/2/14, 12:52 PM, Jon Maron wrote:
> > >>>> The other alternative is to forego the CMS and:
> > >>>>
> > >>>> 1) Manually login to people.apache.org
> > >>>> 2) create the web root directory for the project
> > >>>> 3) use svn to checkout the generated site (which I imagine would
> > >> require us to add the generated files to svn)
> > >>>> 4) From that point on essentially use 'svn update' to update the
> site
> > >> when sources are changed
> > >>>>
> > >>>> I think I like the idea of using the CMS approach, I'm just not
> > certain
> > >> how it's actually implemented (the one sentence indicating providing
> the
> > >> correct args to the perl script gives no indication as to how that
> > process
> > >> actually works - do we invoke the script to build a new site, do we
> > somehow
> > >> configure CMS to execute the script periodically or manually, etc)
> > >>>>
> > >>>> -- Jon
> > >>>>
> > >>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <
> billie.rinaldi@gmail.com
> > >
> > >> wrote:
> > >>>>
> > >>>>> Regarding the imminent creation of our Slider website, it seems
> that
> > >> CMS is
> > >>>>> capable of building a site using Maven:
> > >>>>>
> > >>>>> https://www.apache.org/dev/cmsref.html#external-build
> > >>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
> > >>>>>
> > >>>>> which is great, because that means we'd be able to edit markdown
> > using
> > >> CMS
> > >>>>> and the buildbot would automatically regenerate the site.
> > >>>>>
> > >>>>> So, what are people's thoughts on moving the site materials out of
> > >> trunk
> > >>>>> into site versus making a copy of them or generating them into
> site?
> > I
> > >>>>> think it would be easier to maintain the site if we just moved it,
> > but
> > >> I
> > >>>>> don't know if we'd lose anything by not having the site
> documentation
> > >> in
> > >>>>> the source tree.
> > >>>>>
> > >>>>> Billie
> > >>>>
> > >>>>
> > >>
> > >>
> > >> --
> > >> CONFIDENTIALITY NOTICE
> > >> NOTICE: This message is intended for the use of the individual or
> > entity to
> > >> which it is addressed and may contain information that is
> confidential,
> > >> privileged and exempt from disclosure under applicable law. If the
> > reader
> > >> of this message is not the intended recipient, you are hereby notified
> > that
> > >> any printing, copying, dissemination, distribution, disclosure or
> > >> forwarding of this communication is strictly prohibited. If you have
> > >> received this communication in error, please contact the sender
> > immediately
> > >> and delete it from your system. Thank You.
> > >>
> >
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Billie Rinaldi <bi...@gmail.com>.
On Fri, May 2, 2014 at 1:16 PM, Jon Maron <jm...@hortonworks.com> wrote:
> Yeah - I just came to the same conclusion.
>
> The process would be to essentially create a separate maven project for
> the web site - site.xml, md files, pom.xml etc. I think once created we’d
> file a JIRA to enable the CMS integration (my guess is they are responsible
> for enabling the “external build”, though there is a procedure for enabling
> the process on a local box for testing)
>
> Any thoughts? Given its wide use, the CMS may the appropriate way to
> proceed.
>
I think it's a good idea, but let's see how Steve feels about moving the
docs out of the main project.
>
> — Jon
>
> On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com>
> wrote:
>
> > I think that we create and populate the directory, then put in an INFRA
> > request when it's ready to be hooked up to CMS.
> >
> >
> > On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com>
> wrote:
> >
> >> I’m not sure if I’m missing something, but it appears that there is a
> need
> >> to have infra create the initial SVN directory for CMS (e.g.
> >> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
> >>
> >> — Jon
> >>
> >> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
> >>
> >>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
> >>>
> >>> This is the actually nuts-and-bolts for how the CMS builds the site
> from
> >> Markdown. Very useful when you want to do some design locally and see
> some
> >> results. ASF also has more info on it you can read up on (make sure to
> >> catch the Python and Perl mod dependencies):
> >>>
> >>> https://www.apache.org/dev/cmsref.html#faq-build-tools
> >>>
> >>> Personally, I've really grown into the CMS and like it quite a bit, but
> >> I also enjoy all the documentation information that the maven site
> >> provides. Maybe there's some middle ground that we can do that we can
> reach
> >> that encapsulates some of the existing documentation from Github?
> >>>
> >>> On 5/2/14, 12:52 PM, Jon Maron wrote:
> >>>> The other alternative is to forego the CMS and:
> >>>>
> >>>> 1) Manually login to people.apache.org
> >>>> 2) create the web root directory for the project
> >>>> 3) use svn to checkout the generated site (which I imagine would
> >> require us to add the generated files to svn)
> >>>> 4) From that point on essentially use 'svn update' to update the site
> >> when sources are changed
> >>>>
> >>>> I think I like the idea of using the CMS approach, I'm just not
> certain
> >> how it's actually implemented (the one sentence indicating providing the
> >> correct args to the perl script gives no indication as to how that
> process
> >> actually works - do we invoke the script to build a new site, do we
> somehow
> >> configure CMS to execute the script periodically or manually, etc)
> >>>>
> >>>> -- Jon
> >>>>
> >>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <billie.rinaldi@gmail.com
> >
> >> wrote:
> >>>>
> >>>>> Regarding the imminent creation of our Slider website, it seems that
> >> CMS is
> >>>>> capable of building a site using Maven:
> >>>>>
> >>>>> https://www.apache.org/dev/cmsref.html#external-build
> >>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
> >>>>>
> >>>>> which is great, because that means we'd be able to edit markdown
> using
> >> CMS
> >>>>> and the buildbot would automatically regenerate the site.
> >>>>>
> >>>>> So, what are people's thoughts on moving the site materials out of
> >> trunk
> >>>>> into site versus making a copy of them or generating them into site?
> I
> >>>>> think it would be easier to maintain the site if we just moved it,
> but
> >> I
> >>>>> don't know if we'd lose anything by not having the site documentation
> >> in
> >>>>> the source tree.
> >>>>>
> >>>>> Billie
> >>>>
> >>>>
> >>
> >>
> >> --
> >> CONFIDENTIALITY NOTICE
> >> NOTICE: This message is intended for the use of the individual or
> entity to
> >> which it is addressed and may contain information that is confidential,
> >> privileged and exempt from disclosure under applicable law. If the
> reader
> >> of this message is not the intended recipient, you are hereby notified
> that
> >> any printing, copying, dissemination, distribution, disclosure or
> >> forwarding of this communication is strictly prohibited. If you have
> >> received this communication in error, please contact the sender
> immediately
> >> and delete it from your system. Thank You.
> >>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
Yeah - I just came to the same conclusion.
The process would be to essentially create a separate maven project for the web site - site.xml, md files, pom.xml etc. I think once created we’d file a JIRA to enable the CMS integration (my guess is they are responsible for enabling the “external build”, though there is a procedure for enabling the process on a local box for testing)
Any thoughts? Given its wide use, the CMS may the appropriate way to proceed.
— Jon
On May 2, 2014, at 3:38 PM, Billie Rinaldi <bi...@gmail.com> wrote:
> I think that we create and populate the directory, then put in an INFRA
> request when it's ready to be hooked up to CMS.
>
>
> On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com> wrote:
>
>> I’m not sure if I’m missing something, but it appears that there is a need
>> to have infra create the initial SVN directory for CMS (e.g.
>> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
>>
>> — Jon
>>
>> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
>>
>>> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>>>
>>> This is the actually nuts-and-bolts for how the CMS builds the site from
>> Markdown. Very useful when you want to do some design locally and see some
>> results. ASF also has more info on it you can read up on (make sure to
>> catch the Python and Perl mod dependencies):
>>>
>>> https://www.apache.org/dev/cmsref.html#faq-build-tools
>>>
>>> Personally, I've really grown into the CMS and like it quite a bit, but
>> I also enjoy all the documentation information that the maven site
>> provides. Maybe there's some middle ground that we can do that we can reach
>> that encapsulates some of the existing documentation from Github?
>>>
>>> On 5/2/14, 12:52 PM, Jon Maron wrote:
>>>> The other alternative is to forego the CMS and:
>>>>
>>>> 1) Manually login to people.apache.org
>>>> 2) create the web root directory for the project
>>>> 3) use svn to checkout the generated site (which I imagine would
>> require us to add the generated files to svn)
>>>> 4) From that point on essentially use 'svn update' to update the site
>> when sources are changed
>>>>
>>>> I think I like the idea of using the CMS approach, I'm just not certain
>> how it's actually implemented (the one sentence indicating providing the
>> correct args to the perl script gives no indication as to how that process
>> actually works - do we invoke the script to build a new site, do we somehow
>> configure CMS to execute the script periodically or manually, etc)
>>>>
>>>> -- Jon
>>>>
>>>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com>
>> wrote:
>>>>
>>>>> Regarding the imminent creation of our Slider website, it seems that
>> CMS is
>>>>> capable of building a site using Maven:
>>>>>
>>>>> https://www.apache.org/dev/cmsref.html#external-build
>>>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>>>>
>>>>> which is great, because that means we'd be able to edit markdown using
>> CMS
>>>>> and the buildbot would automatically regenerate the site.
>>>>>
>>>>> So, what are people's thoughts on moving the site materials out of
>> trunk
>>>>> into site versus making a copy of them or generating them into site? I
>>>>> think it would be easier to maintain the site if we just moved it, but
>> I
>>>>> don't know if we'd lose anything by not having the site documentation
>> in
>>>>> the source tree.
>>>>>
>>>>> Billie
>>>>
>>>>
>>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Billie Rinaldi <bi...@gmail.com>.
I think that we create and populate the directory, then put in an INFRA
request when it's ready to be hooked up to CMS.
On Fri, May 2, 2014 at 12:22 PM, Jon Maron <jm...@hortonworks.com> wrote:
> I’m not sure if I’m missing something, but it appears that there is a need
> to have infra create the initial SVN directory for CMS (e.g.
> http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
>
> — Jon
>
> On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
> >
> > This is the actually nuts-and-bolts for how the CMS builds the site from
> Markdown. Very useful when you want to do some design locally and see some
> results. ASF also has more info on it you can read up on (make sure to
> catch the Python and Perl mod dependencies):
> >
> > https://www.apache.org/dev/cmsref.html#faq-build-tools
> >
> > Personally, I've really grown into the CMS and like it quite a bit, but
> I also enjoy all the documentation information that the maven site
> provides. Maybe there's some middle ground that we can do that we can reach
> that encapsulates some of the existing documentation from Github?
> >
> > On 5/2/14, 12:52 PM, Jon Maron wrote:
> >> The other alternative is to forego the CMS and:
> >>
> >> 1) Manually login to people.apache.org
> >> 2) create the web root directory for the project
> >> 3) use svn to checkout the generated site (which I imagine would
> require us to add the generated files to svn)
> >> 4) From that point on essentially use 'svn update' to update the site
> when sources are changed
> >>
> >> I think I like the idea of using the CMS approach, I'm just not certain
> how it's actually implemented (the one sentence indicating providing the
> correct args to the perl script gives no indication as to how that process
> actually works - do we invoke the script to build a new site, do we somehow
> configure CMS to execute the script periodically or manually, etc)
> >>
> >> -- Jon
> >>
> >> On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com>
> wrote:
> >>
> >>> Regarding the imminent creation of our Slider website, it seems that
> CMS is
> >>> capable of building a site using Maven:
> >>>
> >>> https://www.apache.org/dev/cmsref.html#external-build
> >>> http://svn.apache.org/repos/asf/maven/site/trunk/content
> >>>
> >>> which is great, because that means we'd be able to edit markdown using
> CMS
> >>> and the buildbot would automatically regenerate the site.
> >>>
> >>> So, what are people's thoughts on moving the site materials out of
> trunk
> >>> into site versus making a copy of them or generating them into site? I
> >>> think it would be easier to maintain the site if we just moved it, but
> I
> >>> don't know if we'd lose anything by not having the site documentation
> in
> >>> the source tree.
> >>>
> >>> Billie
> >>
> >>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
I’m not sure if I’m missing something, but it appears that there is a need to have infra create the initial SVN directory for CMS (e.g. http://svn.apache.org/repos/asf/slider/site/trunk/). Is that true?
— Jon
On May 2, 2014, at 1:12 PM, Josh Elser <jo...@gmail.com> wrote:
> Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
>
> This is the actually nuts-and-bolts for how the CMS builds the site from Markdown. Very useful when you want to do some design locally and see some results. ASF also has more info on it you can read up on (make sure to catch the Python and Perl mod dependencies):
>
> https://www.apache.org/dev/cmsref.html#faq-build-tools
>
> Personally, I've really grown into the CMS and like it quite a bit, but I also enjoy all the documentation information that the maven site provides. Maybe there's some middle ground that we can do that we can reach that encapsulates some of the existing documentation from Github?
>
> On 5/2/14, 12:52 PM, Jon Maron wrote:
>> The other alternative is to forego the CMS and:
>>
>> 1) Manually login to people.apache.org
>> 2) create the web root directory for the project
>> 3) use svn to checkout the generated site (which I imagine would require us to add the generated files to svn)
>> 4) From that point on essentially use 'svn update' to update the site when sources are changed
>>
>> I think I like the idea of using the CMS approach, I'm just not certain how it's actually implemented (the one sentence indicating providing the correct args to the perl script gives no indication as to how that process actually works - do we invoke the script to build a new site, do we somehow configure CMS to execute the script periodically or manually, etc)
>>
>> -- Jon
>>
>> On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com> wrote:
>>
>>> Regarding the imminent creation of our Slider website, it seems that CMS is
>>> capable of building a site using Maven:
>>>
>>> https://www.apache.org/dev/cmsref.html#external-build
>>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>>
>>> which is great, because that means we'd be able to edit markdown using CMS
>>> and the buildbot would automatically regenerate the site.
>>>
>>> So, what are people's thoughts on moving the site materials out of trunk
>>> into site versus making a copy of them or generating them into site? I
>>> think it would be easier to maintain the site if we just moved it, but I
>>> don't know if we'd lose anything by not having the site documentation in
>>> the source tree.
>>>
>>> Billie
>>
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: slider website
Posted by Josh Elser <jo...@gmail.com>.
Jon, check out: https://svn.apache.org/repos/infra/websites/cms/
This is the actually nuts-and-bolts for how the CMS builds the site from
Markdown. Very useful when you want to do some design locally and see
some results. ASF also has more info on it you can read up on (make sure
to catch the Python and Perl mod dependencies):
https://www.apache.org/dev/cmsref.html#faq-build-tools
Personally, I've really grown into the CMS and like it quite a bit, but
I also enjoy all the documentation information that the maven site
provides. Maybe there's some middle ground that we can do that we can
reach that encapsulates some of the existing documentation from Github?
On 5/2/14, 12:52 PM, Jon Maron wrote:
> The other alternative is to forego the CMS and:
>
> 1) Manually login to people.apache.org
> 2) create the web root directory for the project
> 3) use svn to checkout the generated site (which I imagine would require us to add the generated files to svn)
> 4) From that point on essentially use 'svn update' to update the site when sources are changed
>
> I think I like the idea of using the CMS approach, I'm just not certain how it's actually implemented (the one sentence indicating providing the correct args to the perl script gives no indication as to how that process actually works - do we invoke the script to build a new site, do we somehow configure CMS to execute the script periodically or manually, etc)
>
> -- Jon
>
> On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com> wrote:
>
>> Regarding the imminent creation of our Slider website, it seems that CMS is
>> capable of building a site using Maven:
>>
>> https://www.apache.org/dev/cmsref.html#external-build
>> http://svn.apache.org/repos/asf/maven/site/trunk/content
>>
>> which is great, because that means we'd be able to edit markdown using CMS
>> and the buildbot would automatically regenerate the site.
>>
>> So, what are people's thoughts on moving the site materials out of trunk
>> into site versus making a copy of them or generating them into site? I
>> think it would be easier to maintain the site if we just moved it, but I
>> don't know if we'd lose anything by not having the site documentation in
>> the source tree.
>>
>> Billie
>
>
Re: slider website
Posted by Billie Rinaldi <bi...@gmail.com>.
On Fri, May 2, 2014 at 9:52 AM, Jon Maron <jm...@hortonworks.com> wrote:
> The other alternative is to forego the CMS and:
>
> 1) Manually login to people.apache.org
> 2) create the web root directory for the project
> 3) use svn to checkout the generated site (which I imagine would require
> us to add the generated files to svn)
> 4) From that point on essentially use 'svn update' to update the site
> when sources are changed
>
> I think I like the idea of using the CMS approach, I'm just not certain
> how it's actually implemented (the one sentence indicating providing the
> correct args to the perl script gives no indication as to how that process
> actually works - do we invoke the script to build a new site, do we somehow
> configure CMS to execute the script periodically or manually, etc)
>
My guess is that either it automatically detects that the site should be
built with maven, or that INFRA configures that when the site is set up --
I don't see any special configuration for CMS in Maven's site. CMS is
configured to build whenever a change is made in svn. Changes can be made
through svn or the CMS GUI. The site is built to a staging area first, so
you can inspect the changes, and then you can publish to the production
site.
>
> -- Jon
>
> On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com>
> wrote:
>
> > Regarding the imminent creation of our Slider website, it seems that CMS
> is
> > capable of building a site using Maven:
> >
> > https://www.apache.org/dev/cmsref.html#external-build
> > http://svn.apache.org/repos/asf/maven/site/trunk/content
> >
> > which is great, because that means we'd be able to edit markdown using
> CMS
> > and the buildbot would automatically regenerate the site.
> >
> > So, what are people's thoughts on moving the site materials out of trunk
> > into site versus making a copy of them or generating them into site? I
> > think it would be easier to maintain the site if we just moved it, but I
> > don't know if we'd lose anything by not having the site documentation in
> > the source tree.
> >
> > Billie
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: slider website
Posted by Jon Maron <jm...@hortonworks.com>.
The other alternative is to forego the CMS and:
1) Manually login to people.apache.org
2) create the web root directory for the project
3) use svn to checkout the generated site (which I imagine would require us to add the generated files to svn)
4) From that point on essentially use 'svn update' to update the site when sources are changed
I think I like the idea of using the CMS approach, I'm just not certain how it's actually implemented (the one sentence indicating providing the correct args to the perl script gives no indication as to how that process actually works - do we invoke the script to build a new site, do we somehow configure CMS to execute the script periodically or manually, etc)
-- Jon
On May 2, 2014, at 11:44 AM, Billie Rinaldi <bi...@gmail.com> wrote:
> Regarding the imminent creation of our Slider website, it seems that CMS is
> capable of building a site using Maven:
>
> https://www.apache.org/dev/cmsref.html#external-build
> http://svn.apache.org/repos/asf/maven/site/trunk/content
>
> which is great, because that means we'd be able to edit markdown using CMS
> and the buildbot would automatically regenerate the site.
>
> So, what are people's thoughts on moving the site materials out of trunk
> into site versus making a copy of them or generating them into site? I
> think it would be easier to maintain the site if we just moved it, but I
> don't know if we'd lose anything by not having the site documentation in
> the source tree.
>
> Billie
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.