Re: [PROPOSAL] [DISCUSSION] Corinthia Abstract

2014-11-29 Thread Ian C
Hi All,

I am intrigued by this project. And will sign up once it becomes available
a real Apache project.

Same as for everyone, making time is the killer...

As something of an amusing sideline I created a document in Google Drive
and downloaded it as an odt. Looking inside, eeks, each word is in its own
span?
Opening and saving in OpenOffice seems to restore some sanity. I did the
same in docx ... This project will have its work cut out...

Even more interested now...

On Sun, Nov 30, 2014 at 3:55 AM, Dennis E. Hamilton  wrote:

> I put together an abstract in the Corinthia Podling Proposal.  It is a bit
> lengthy and requires review that it captures the essence of what Corinthia
> is for without over/under-stepping.
>
> Here is the text also added to <
> https://wiki.apache.org/incubator/CorinthiaProposal>,
>
> """
> Corinthia converts among document file formats via transformation through
> an HTML-grounded intermediary.  The selection of document file formats is
> expandable by addition of import and export plugins.
>
> Editing in Corinthia is via a responsive editor, implemented in JavaScript
> and HTML (CSS), that works on the web, in the cloud, and also adapts across
> device form factors for practical use on mobile devices, tablets, and
> touch-enabled as well as keyboard-oriented interfaces.  Corinthia document
> viewing and editing is on the intermediate form, limited to common,
> widely-supported features. Corinthia is not a comprehensive substitute for
> format-specific authoring, editing, and final-form printing/production
> software.
>
> To avoid irreversible loss of features from imported documents, Corinthia
> encapsulates unsupported feature occurrences in a form that can be
> recovered from the intermediate as part of subsequent export to the same or
> different format.
>
> Identification and confirmation of inter-convertible features of different
> formats for dependable import and export involves development of extensive
> test documents in the different formats.  There is profiling of the extent
> to which standardized formats are supported in practice, with
> identification of deviations and implementation-dependent choices that
> impact convertibility.
>
> All of the Corinthia test cases, profiling, plugin development, libraries,
> and utilities are reusable resources to other projects.  All development of
> source-code for binaries is in portable C Language for multi-platform
> compilation as well as API "wrapping" for delivery to other programming
> models, such as for Python, .NET, Java, and Node.js.  Document format file
> import and export plugins may be adaptable as import-export extensions used
> with other document-processing software.
> """
>
> -Original Message-
> From: jan i [mailto:j...@apache.org]
> Sent: Wednesday, November 26, 2014 03:13
> To: general@incubator.apache.org
> Subject: Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.
>
> Hi all.
>
> We, at the project, hope that the lack of discussion is not a negative sign
> !
>
> In the meantime, we have been working behind the scenes, and a couple of
> things have happened:
>
> - The proposal is now on the incubator wiki / corinthiaProposal
> 
>
> - Dennis Hamilton (incubator, aoo committer) joined the initial committer
> list. His expertise in especially document formats will be of great value
> to the project, Dennis is also providing a lot of good feedback on our open
> issues.
>
> - Daniel Gruno (Humbedooh) has volunteered to be mentor for the project. We
> look forward to guidance in all the tricky "paper work".
>
> - Talks are being prepared for ACNA.
>
>
> We are more than happy to answer any questions and make requested changes.
>
> on behalf of the project
> jan i
>
>
> On 24 November 2014 at 22:14, Ross Gardler (MS OPEN TECH) <
> ross.gard...@microsoft.com> wrote:
>
> > There are some passing similarities with Forrest here. I'm not suggesting
> > any changes to the proposal, just flagging that the intermediate format
> > approach described here is the approach Forrest takes. The focus for
> > Forrest was not on document format conversion but there is a lot of
> > experience there in using intermediate formats.
> >
> > Microsoft Open Technologies, Inc.
> > A subsidiary of Microsoft Corporation
> >
> > -Original Message-
> > From: jan i [mailto:j...@apache.org]
> > Sent: Monday, November 24, 2014 12:37 PM
> > To: jan i
> > Cc: general@incubator.apache.org
> > Subject: Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.
> >
> > Hi.
> >
> > Sorry, somebody hit me with the big GIT hammer !! I did something with
> git
> > that should not be done.
> >
> > The correct text is:
> [ ... ]
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Cheers,

Ian C


[ANNOUNCE] Brock Noland joins the IPMC

2014-11-29 Thread Roman Shaposhnik
Hi!

an ASF member Brock Noland has
volunteered recently to join the Incubator PMC.

Welcome, Brock! Great to have you on board!

Please make sure to subscribed yourself to the
IPMC MLs and also feel free to let us know a
surprising thing or two about yourself.

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[ANNOUNCE] Thejas Nair joins the IPMC

2014-11-29 Thread Roman Shaposhnik
Hi!

an ASF member Thejas Nair has
volunteered recently to join the Incubator PMC.

Welcome, Thejas! Great to have you on board!

Please make sure to subscribed yourself to the
IPMC MLs and also feel free to let us know a
surprising thing or two about yourself.

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[ANNOUNCE] Andrew L. Farris joins the IPMC

2014-11-29 Thread Roman Shaposhnik
Hi!

an ASF member Andrew L. Farris has
volunteered recently to join the Incubator PMC.

Welcome, Andrew! Great to have you on board!

Please make sure to subscribed yourself to the
IPMC MLs and also feel free to let us know a
surprising thing or two about yourself.

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



RE: [PROPOSAL] [DISCUSSION] Corinthia Abstract

2014-11-29 Thread Dennis E. Hamilton
I put together an abstract in the Corinthia Podling Proposal.  It is a bit 
lengthy and requires review that it captures the essence of what Corinthia is 
for without over/under-stepping.

Here is the text also added to 
,

"""
Corinthia converts among document file formats via transformation through an 
HTML-grounded intermediary.  The selection of document file formats is 
expandable by addition of import and export plugins.  

Editing in Corinthia is via a responsive editor, implemented in JavaScript and 
HTML (CSS), that works on the web, in the cloud, and also adapts across device 
form factors for practical use on mobile devices, tablets, and touch-enabled as 
well as keyboard-oriented interfaces.  Corinthia document viewing and editing 
is on the intermediate form, limited to common, widely-supported features. 
Corinthia is not a comprehensive substitute for format-specific authoring, 
editing, and final-form printing/production software.

To avoid irreversible loss of features from imported documents, Corinthia 
encapsulates unsupported feature occurrences in a form that can be recovered 
from the intermediate as part of subsequent export to the same or different 
format.

Identification and confirmation of inter-convertible features of different 
formats for dependable import and export involves development of extensive test 
documents in the different formats.  There is profiling of the extent to which 
standardized formats are supported in practice, with identification of 
deviations and implementation-dependent choices that impact convertibility.  

All of the Corinthia test cases, profiling, plugin development, libraries, and 
utilities are reusable resources to other projects.  All development of 
source-code for binaries is in portable C Language for multi-platform 
compilation as well as API "wrapping" for delivery to other programming models, 
such as for Python, .NET, Java, and Node.js.  Document format file import and 
export plugins may be adaptable as import-export extensions used with other 
document-processing software.
"""

-Original Message-
From: jan i [mailto:j...@apache.org] 
Sent: Wednesday, November 26, 2014 03:13
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.

Hi all.

We, at the project, hope that the lack of discussion is not a negative sign
!

In the meantime, we have been working behind the scenes, and a couple of
things have happened:

- The proposal is now on the incubator wiki / corinthiaProposal


- Dennis Hamilton (incubator, aoo committer) joined the initial committer
list. His expertise in especially document formats will be of great value
to the project, Dennis is also providing a lot of good feedback on our open
issues.

- Daniel Gruno (Humbedooh) has volunteered to be mentor for the project. We
look forward to guidance in all the tricky "paper work".

- Talks are being prepared for ACNA.


We are more than happy to answer any questions and make requested changes.

on behalf of the project
jan i


On 24 November 2014 at 22:14, Ross Gardler (MS OPEN TECH) <
ross.gard...@microsoft.com> wrote:

> There are some passing similarities with Forrest here. I'm not suggesting
> any changes to the proposal, just flagging that the intermediate format
> approach described here is the approach Forrest takes. The focus for
> Forrest was not on document format conversion but there is a lot of
> experience there in using intermediate formats.
>
> Microsoft Open Technologies, Inc.
> A subsidiary of Microsoft Corporation
>
> -Original Message-
> From: jan i [mailto:j...@apache.org]
> Sent: Monday, November 24, 2014 12:37 PM
> To: jan i
> Cc: general@incubator.apache.org
> Subject: Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.
>
> Hi.
>
> Sorry, somebody hit me with the big GIT hammer !! I did something with git
> that should not be done.
>
> The correct text is:
[ ... ]


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Website for Tamaya - need help

2014-11-29 Thread Benson Margulies
I had incorrectly inferred pubsub from the prior email thread.

On Sat, Nov 29, 2014 at 11:22 AM, John D. Ament  wrote:
> Thanks for your help Drew!
>
> I missed devicemap.  I think I was looking for newer podlings (johnzon or
> batchee or usergrid) none of whom had sites.  It's possible they're not
> going through CMS though.
>
> John
>
> On Sat Nov 29 2014 at 11:15:54 AM Drew Farris  wrote:
>
>> On Sat, Nov 29, 2014 at 9:58 AM, John D. Ament 
>> wrote:
>> > One other thing (sorry!)
>> >
>> > I notice on the cms.apache.org landing page, none of the podlings are
>> > listed.  How do podlings publish?
>>
>> Actually, it looks like there are podlings listed in [export], and on
>> cms.apache.org proper (e.g: devicemap). I'm going to assume that will
>> be or can be modified once the site is set up properly.
>>
>> [export] https://svn.apache.org/repos/infra/websites/cms/webgui/
>> content/export.json
>>
>> > On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament 
>> > wrote:
>> >
>> >> Drew,
>> >>
>> >> "default-perl" would make the most sense.  They're going to manage the
>> >> asciidoc files within standard source, use a site plugin to publish the
>> >> html to the SVN directory.  This should end up being very similar to
>> >> batchee's [setup].
>> >>
>> >> Thanks!
>> >>
>> >> John
>> >>
>> >> [setup]:
>> >> https://git-wip-us.apache.org/repos/asf/infrastructure-
>> puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=
>> fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427
>> >>
>> >> On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris  wrote:
>> >>
>> >>> John,
>> >>>
>> >>> I just took a quick look at this. It appears the options are svnpubsub
>> >>> or Apache CMS. For CMS, you have a choice of 'cms build type':
>> >>> default-perl, maven, ant, or shell.
>> >>>
>> >>> It sounds like you want Apache CMS, do you have any thoughts about the
>> >>> 'cms build type' option?
>> >>>
>> >>> Drew
>> >>>
>> >>> --
>> >>> Drew Farris
>> >>> drew.far...@gmail.com
>> >>> d...@apache.org
>> >>>
>> >>>
>> >>> On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament > >
>> >>> wrote:
>> >>> > Benson,
>> >>> >
>> >>> > Thanks.  So I don't know what that page is expecting since I can't
>> >>> actually
>> >>> > see it.
>> >>> >
>> >>> > If you require a temporary index.html, I can upload one.  In which
>> case,
>> >>> > the full URL would be
>> >>> > https://svn.apache.org/repos/asf/incubator/tamaya/site/
>> trunk/index.html
>> >>> for
>> >>> > the staging site to read from.
>> >>> >
>> >>> > I think we're expecting staging/production via Apache CMS (
>> >>> cms.apache.org).
>> >>> >
>> >>> > John
>> >>> >
>> >>> > On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies <
>> >>> bimargul...@gmail.com>
>> >>> > wrote:
>> >>> >
>> >>> >> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament <
>> johndam...@apache.org>
>> >>> >> wrote:
>> >>> >> > https://infra.apache.org/officers/webreq
>> >>> >>
>> >>> >> I tried:
>> >>> >>
>> >>> >> Missing
>> >>> https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
>> >>> >>
>> >>> >> 
>> -
>> >>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>> >>
>> >>> >>
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >>> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>>
>> >>>
>> >>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[jira] [Commented] (INCUBATOR-127) Project name still shows as Apache Argus - It should be Apache Ranger.

2014-11-29 Thread John D. Ament (JIRA)

[ 
https://issues.apache.org/jira/browse/INCUBATOR-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228859#comment-14228859
 ] 

John D. Ament commented on INCUBATOR-127:
-

[~sneethiraj] You need to have one of your mentors update podlings.xml - or 
better yet you can probably do it yourself.

> Project name still shows as Apache Argus - It should be Apache Ranger.
> --
>
> Key: INCUBATOR-127
> URL: https://issues.apache.org/jira/browse/INCUBATOR-127
> Project: Incubator
>  Issue Type: Bug
>  Components: site
>Reporter: Selvamohan Neethiraj
>
> Project name in Apache Incubator site is still showing up as Argus (after it 
> got renamed as Ranger)
> http://incubator.apache.org/
>- In the List of all current Incubator projects



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Website for Tamaya - need help

2014-11-29 Thread John D. Ament
Thanks for your help Drew!

I missed devicemap.  I think I was looking for newer podlings (johnzon or
batchee or usergrid) none of whom had sites.  It's possible they're not
going through CMS though.

John

On Sat Nov 29 2014 at 11:15:54 AM Drew Farris  wrote:

> On Sat, Nov 29, 2014 at 9:58 AM, John D. Ament 
> wrote:
> > One other thing (sorry!)
> >
> > I notice on the cms.apache.org landing page, none of the podlings are
> > listed.  How do podlings publish?
>
> Actually, it looks like there are podlings listed in [export], and on
> cms.apache.org proper (e.g: devicemap). I'm going to assume that will
> be or can be modified once the site is set up properly.
>
> [export] https://svn.apache.org/repos/infra/websites/cms/webgui/
> content/export.json
>
> > On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament 
> > wrote:
> >
> >> Drew,
> >>
> >> "default-perl" would make the most sense.  They're going to manage the
> >> asciidoc files within standard source, use a site plugin to publish the
> >> html to the SVN directory.  This should end up being very similar to
> >> batchee's [setup].
> >>
> >> Thanks!
> >>
> >> John
> >>
> >> [setup]:
> >> https://git-wip-us.apache.org/repos/asf/infrastructure-
> puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=
> fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427
> >>
> >> On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris  wrote:
> >>
> >>> John,
> >>>
> >>> I just took a quick look at this. It appears the options are svnpubsub
> >>> or Apache CMS. For CMS, you have a choice of 'cms build type':
> >>> default-perl, maven, ant, or shell.
> >>>
> >>> It sounds like you want Apache CMS, do you have any thoughts about the
> >>> 'cms build type' option?
> >>>
> >>> Drew
> >>>
> >>> --
> >>> Drew Farris
> >>> drew.far...@gmail.com
> >>> d...@apache.org
> >>>
> >>>
> >>> On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament  >
> >>> wrote:
> >>> > Benson,
> >>> >
> >>> > Thanks.  So I don't know what that page is expecting since I can't
> >>> actually
> >>> > see it.
> >>> >
> >>> > If you require a temporary index.html, I can upload one.  In which
> case,
> >>> > the full URL would be
> >>> > https://svn.apache.org/repos/asf/incubator/tamaya/site/
> trunk/index.html
> >>> for
> >>> > the staging site to read from.
> >>> >
> >>> > I think we're expecting staging/production via Apache CMS (
> >>> cms.apache.org).
> >>> >
> >>> > John
> >>> >
> >>> > On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies <
> >>> bimargul...@gmail.com>
> >>> > wrote:
> >>> >
> >>> >> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament <
> johndam...@apache.org>
> >>> >> wrote:
> >>> >> > https://infra.apache.org/officers/webreq
> >>> >>
> >>> >> I tried:
> >>> >>
> >>> >> Missing
> >>> https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
> >>> >>
> >>> >> 
> -
> >>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>> >>
> >>> >>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: Website for Tamaya - need help

2014-11-29 Thread Drew Farris
On Sat, Nov 29, 2014 at 9:58 AM, John D. Ament  wrote:
> One other thing (sorry!)
>
> I notice on the cms.apache.org landing page, none of the podlings are
> listed.  How do podlings publish?

Actually, it looks like there are podlings listed in [export], and on
cms.apache.org proper (e.g: devicemap). I'm going to assume that will
be or can be modified once the site is set up properly.

[export] 
https://svn.apache.org/repos/infra/websites/cms/webgui/content/export.json

> On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament 
> wrote:
>
>> Drew,
>>
>> "default-perl" would make the most sense.  They're going to manage the
>> asciidoc files within standard source, use a site plugin to publish the
>> html to the SVN directory.  This should end up being very similar to
>> batchee's [setup].
>>
>> Thanks!
>>
>> John
>>
>> [setup]:
>> https://git-wip-us.apache.org/repos/asf/infrastructure-puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427
>>
>> On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris  wrote:
>>
>>> John,
>>>
>>> I just took a quick look at this. It appears the options are svnpubsub
>>> or Apache CMS. For CMS, you have a choice of 'cms build type':
>>> default-perl, maven, ant, or shell.
>>>
>>> It sounds like you want Apache CMS, do you have any thoughts about the
>>> 'cms build type' option?
>>>
>>> Drew
>>>
>>> --
>>> Drew Farris
>>> drew.far...@gmail.com
>>> d...@apache.org
>>>
>>>
>>> On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament 
>>> wrote:
>>> > Benson,
>>> >
>>> > Thanks.  So I don't know what that page is expecting since I can't
>>> actually
>>> > see it.
>>> >
>>> > If you require a temporary index.html, I can upload one.  In which case,
>>> > the full URL would be
>>> > https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html
>>> for
>>> > the staging site to read from.
>>> >
>>> > I think we're expecting staging/production via Apache CMS (
>>> cms.apache.org).
>>> >
>>> > John
>>> >
>>> > On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies <
>>> bimargul...@gmail.com>
>>> > wrote:
>>> >
>>> >> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament 
>>> >> wrote:
>>> >> > https://infra.apache.org/officers/webreq
>>> >>
>>> >> I tried:
>>> >>
>>> >> Missing
>>> https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>>> >>
>>> >>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[jira] [Created] (INCUBATOR-127) Project name still shows as Apache Argus - It should be Apache Ranger.

2014-11-29 Thread Selvamohan Neethiraj (JIRA)
Selvamohan Neethiraj created INCUBATOR-127:
--

 Summary: Project name still shows as Apache Argus - It should be 
Apache Ranger.
 Key: INCUBATOR-127
 URL: https://issues.apache.org/jira/browse/INCUBATOR-127
 Project: Incubator
  Issue Type: Bug
  Components: site
Reporter: Selvamohan Neethiraj


Project name in Apache Incubator site is still showing up as Argus (after it 
got renamed as Ranger)

http://incubator.apache.org/
   - In the List of all current Incubator projects





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Website for Tamaya - need help

2014-11-29 Thread Drew Farris
John,

Ok, request successfully submitted, from the output: "Next steps: We
will create the web site and email private@tamaya once we have done
that. There is no need to file a JIRA."

It is not entirely clear to me how to publish a podling via CMS. I
wasn't able to find docs and permutations of cms.apache.org weren't
useful. It doesn't appear that there is
(podling).staging.incubator.apache.org, where the staging version of
the site can be viewed. This leads me to believe that publishing the
podling site is managed independently from the incubator site proper.

Drew
--
drew.far...@gmail.com
d...@apache.org

On Sat, Nov 29, 2014 at 9:58 AM, John D. Ament  wrote:
> One other thing (sorry!)
>
> I notice on the cms.apache.org landing page, none of the podlings are
> listed.  How do podlings publish?
>
> On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament 
> wrote:
>
>> Drew,
>>
>> "default-perl" would make the most sense.  They're going to manage the
>> asciidoc files within standard source, use a site plugin to publish the
>> html to the SVN directory.  This should end up being very similar to
>> batchee's [setup].
>>
>> Thanks!
>>
>> John
>>
>> [setup]:
>> https://git-wip-us.apache.org/repos/asf/infrastructure-puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427
>>
>> On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris  wrote:
>>
>>> John,
>>>
>>> I just took a quick look at this. It appears the options are svnpubsub
>>> or Apache CMS. For CMS, you have a choice of 'cms build type':
>>> default-perl, maven, ant, or shell.
>>>
>>> It sounds like you want Apache CMS, do you have any thoughts about the
>>> 'cms build type' option?
>>>
>>> Drew
>>>
>>> --
>>> Drew Farris
>>> drew.far...@gmail.com
>>> d...@apache.org
>>>
>>>
>>> On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament 
>>> wrote:
>>> > Benson,
>>> >
>>> > Thanks.  So I don't know what that page is expecting since I can't
>>> actually
>>> > see it.
>>> >
>>> > If you require a temporary index.html, I can upload one.  In which case,
>>> > the full URL would be
>>> > https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html
>>> for
>>> > the staging site to read from.
>>> >
>>> > I think we're expecting staging/production via Apache CMS (
>>> cms.apache.org).
>>> >
>>> > John
>>> >
>>> > On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies <
>>> bimargul...@gmail.com>
>>> > wrote:
>>> >
>>> >> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament 
>>> >> wrote:
>>> >> > https://infra.apache.org/officers/webreq
>>> >>
>>> >> I tried:
>>> >>
>>> >> Missing
>>> https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>>> >>
>>> >>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Website for Tamaya - need help

2014-11-29 Thread John D. Ament
One other thing (sorry!)

I notice on the cms.apache.org landing page, none of the podlings are
listed.  How do podlings publish?

On Sat, Nov 29, 2014 at 9:55 AM, John D. Ament 
wrote:

> Drew,
>
> "default-perl" would make the most sense.  They're going to manage the
> asciidoc files within standard source, use a site plugin to publish the
> html to the SVN directory.  This should end up being very similar to
> batchee's [setup].
>
> Thanks!
>
> John
>
> [setup]:
> https://git-wip-us.apache.org/repos/asf/infrastructure-puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427
>
> On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris  wrote:
>
>> John,
>>
>> I just took a quick look at this. It appears the options are svnpubsub
>> or Apache CMS. For CMS, you have a choice of 'cms build type':
>> default-perl, maven, ant, or shell.
>>
>> It sounds like you want Apache CMS, do you have any thoughts about the
>> 'cms build type' option?
>>
>> Drew
>>
>> --
>> Drew Farris
>> drew.far...@gmail.com
>> d...@apache.org
>>
>>
>> On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament 
>> wrote:
>> > Benson,
>> >
>> > Thanks.  So I don't know what that page is expecting since I can't
>> actually
>> > see it.
>> >
>> > If you require a temporary index.html, I can upload one.  In which case,
>> > the full URL would be
>> > https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html
>> for
>> > the staging site to read from.
>> >
>> > I think we're expecting staging/production via Apache CMS (
>> cms.apache.org).
>> >
>> > John
>> >
>> > On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies <
>> bimargul...@gmail.com>
>> > wrote:
>> >
>> >> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament 
>> >> wrote:
>> >> > https://infra.apache.org/officers/webreq
>> >>
>> >> I tried:
>> >>
>> >> Missing
>> https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>


Re: Website for Tamaya - need help

2014-11-29 Thread John D. Ament
Drew,

"default-perl" would make the most sense.  They're going to manage the
asciidoc files within standard source, use a site plugin to publish the
html to the SVN directory.  This should end up being very similar to
batchee's [setup].

Thanks!

John

[setup]:
https://git-wip-us.apache.org/repos/asf/infrastructure-puppet/repo?p=incubator-batchee.git;a=blob;f=pom.xml;h=fdad006cb0335098bd801b1159a1390334436161;hb=HEAD#l427

On Sat, Nov 29, 2014 at 9:50 AM, Drew Farris  wrote:

> John,
>
> I just took a quick look at this. It appears the options are svnpubsub
> or Apache CMS. For CMS, you have a choice of 'cms build type':
> default-perl, maven, ant, or shell.
>
> It sounds like you want Apache CMS, do you have any thoughts about the
> 'cms build type' option?
>
> Drew
>
> --
> Drew Farris
> drew.far...@gmail.com
> d...@apache.org
>
>
> On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament 
> wrote:
> > Benson,
> >
> > Thanks.  So I don't know what that page is expecting since I can't
> actually
> > see it.
> >
> > If you require a temporary index.html, I can upload one.  In which case,
> > the full URL would be
> > https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html
> for
> > the staging site to read from.
> >
> > I think we're expecting staging/production via Apache CMS (
> cms.apache.org).
> >
> > John
> >
> > On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies  >
> > wrote:
> >
> >> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament 
> >> wrote:
> >> > https://infra.apache.org/officers/webreq
> >>
> >> I tried:
> >>
> >> Missing
> https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: Website for Tamaya - need help

2014-11-29 Thread Drew Farris
John,

I just took a quick look at this. It appears the options are svnpubsub
or Apache CMS. For CMS, you have a choice of 'cms build type':
default-perl, maven, ant, or shell.

It sounds like you want Apache CMS, do you have any thoughts about the
'cms build type' option?

Drew

--
Drew Farris
drew.far...@gmail.com
d...@apache.org


On Sat, Nov 29, 2014 at 9:18 AM, John D. Ament  wrote:
> Benson,
>
> Thanks.  So I don't know what that page is expecting since I can't actually
> see it.
>
> If you require a temporary index.html, I can upload one.  In which case,
> the full URL would be
> https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html for
> the staging site to read from.
>
> I think we're expecting staging/production via Apache CMS (cms.apache.org).
>
> John
>
> On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies 
> wrote:
>
>> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament 
>> wrote:
>> > https://infra.apache.org/officers/webreq
>>
>> I tried:
>>
>> Missing https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Website for Tamaya - need help

2014-11-29 Thread John D. Ament
Benson,

Thanks.  So I don't know what that page is expecting since I can't actually
see it.

If you require a temporary index.html, I can upload one.  In which case,
the full URL would be
https://svn.apache.org/repos/asf/incubator/tamaya/site/trunk/index.html for
the staging site to read from.

I think we're expecting staging/production via Apache CMS (cms.apache.org).

John

On Fri, Nov 28, 2014 at 8:05 PM, Benson Margulies 
wrote:

> On Fri, Nov 28, 2014 at 6:13 PM, John D. Ament 
> wrote:
> > https://infra.apache.org/officers/webreq
>
> I tried:
>
> Missing https://svn.apache.org/repos/asf/incubator/tamaya/site/index.html
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>