Re: Proposals - wiki required?

2014-11-24 Thread Roman Shaposhnik
On Sun, Nov 23, 2014 at 8:20 AM, Marvin Humphrey mar...@rectangular.com wrote:
 IMO, it doesn’t matter so long as the original vote to accept the proposal
 includes the entire proposal.

 It would be inconvenient if people don't use the wiki or some other form where
 the evolution of the proposal can be inspected using diffs.  Close reading of
 proposal text is costly; serious flaws can hide in small crevices.  We don't
 want those weighing a proposal to have to perform careful review a second time
 for the VOTE thread.

Huge +1 to this consideration. The way it works for me: when anybody is asking
me to do work for that person (read proposal, formulate opinion, vote)
the easiest
way to get that work done is to make it *easier* for *me* to do it.
You don't have
to, of course. Just like I don't *have* to vote on every single proposal.

May be I'm in the minority, but tracking proposal evolution on a wiki-like
medium makes it easier for me.

The call, of course, belongs to the one who actually wants the proposal
to be accepted.

Thanks,
Roman.

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



Mail command to allow marvin emails

2014-11-24 Thread John D. Ament
All,

Does anyone know the mail command to send out to allow marvin emails
to get to a list without moderation?

John

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



Re: Mail command to allow marvin emails

2014-11-24 Thread Tim Ellison
On 24/11/14 14:35, John D. Ament wrote:
 Does anyone know the mail command to send out to allow marvin emails
 to get to a list without moderation?

If the mail hits moderation then I/some other mod will allow it through
and add Marvin to the allowed senders' list.

Tim


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



Re: Mail command to allow marvin emails

2014-11-24 Thread Alan D. Cabrera
It’s too bad that this can’t be automated when a podling is added.  I have a 
ticket waiting in INFRA to add a REST API to Hermes to allow such a thing. 

https://issues.apache.org/jira/browse/INFRA-8006

Maybe people can up-vote it?  :)


Regards,
Alan


On Nov 24, 2014, at 7:28 AM, Tim Ellison t.p.elli...@gmail.com wrote:

 On 24/11/14 14:35, John D. Ament wrote:
 Does anyone know the mail command to send out to allow marvin emails
 to get to a list without moderation?
 
 If the mail hits moderation then I/some other mod will allow it through
 and add Marvin to the allowed senders' list.
 
 Tim
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 



Re: Mail command to allow marvin emails

2014-11-24 Thread John D. Ament
On Mon Nov 24 2014 at 10:29:02 AM Tim Ellison t.p.elli...@gmail.com wrote:

 On 24/11/14 14:35, John D. Ament wrote:
  Does anyone know the mail command to send out to allow marvin emails
  to get to a list without moderation?

 If the mail hits moderation then I/some other mod will allow it through
 and add Marvin to the allowed senders' list.


Are you referring to general@ or something else? I'm specifically referring
to dev@tamaya.i.a.o and I was hoping to white list marvin (the board report
email reminder).  I can't seem to find instructions on how to white list
people anywhere.

If you're saying that only you can white list Marvin.. please white list
Marvin on the listed mail alias.

Tim


John




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




Re: Mail command to allow marvin emails

2014-11-24 Thread Alex Harui
Are you looking for the dev-allow-subscribe command?

On 11/24/14, 9:39 AM, John D. Ament johndam...@apache.org wrote:

On Mon Nov 24 2014 at 10:29:02 AM Tim Ellison t.p.elli...@gmail.com
wrote:

 On 24/11/14 14:35, John D. Ament wrote:
  Does anyone know the mail command to send out to allow marvin emails
  to get to a list without moderation?

 If the mail hits moderation then I/some other mod will allow it through
 and add Marvin to the allowed senders' list.


Are you referring to general@ or something else? I'm specifically
referring
to dev@tamaya.i.a.o and I was hoping to white list marvin (the board
report
email reminder).  I can't seem to find instructions on how to white list
people anywhere.

If you're saying that only you can white list Marvin.. please white list
Marvin on the listed mail alias.

Tim


John




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





Re: [VOTE] accept NiFi into the incubator

2014-11-24 Thread Sergio Fernández

+1 (binding)

On 23/11/14 03:00, John D. Ament wrote:

Ok, as long as there's no more editing going on, I'm +1.



On Sat, Nov 22, 2014 at 5:17 PM, Sean Busbey bus...@cloudera.com wrote:


On Sat, Nov 22, 2014 at 3:42 PM, John D. Ament john.d.am...@gmail.com
wrote:


Is it me or has the proposal changed since the vote went out? Ideally we
want the proposal to be final before sending the vote.



This is why the vote includes the proposal text or a specific wiki
revision. I believe Benson sent the proposal text for the vote as a follow
up to the original call.

  On Sat, Nov 22, 2014 at 3:55 PM, Joe Witt joe.w...@gmail.com wrote:


John,

I've added the volunteering mentors. Updated the IPMC membership status

of

the mentors.  Updated the CLA status of the contributors.  I'll stop

doing

so now though to avoid any confusion.



Joe, usually when there are things to change that don't impact the vote
itself, they're noted by the champion as follow ons and then taken care of
after the vote in the podling docs rather than the proposal.

Easy mistake, not a big deal.

--
Sean





--
Sergio Fernández
Senior Researcher
Knowledge and Media Technologies
Salzburg Research Forschungsgesellschaft mbH
Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
T: +43 662 2288 318 | M: +43 660 2747 925
sergio.fernan...@salzburgresearch.at
http://www.salzburgresearch.at

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



Re: [VOTE] accept NiFi into the incubator

2014-11-24 Thread Sergio Fernández

+1 (binding)

On 23/11/14 03:00, John D. Ament wrote:

Ok, as long as there's no more editing going on, I'm +1.



On Sat, Nov 22, 2014 at 5:17 PM, Sean Busbey bus...@cloudera.com wrote:


On Sat, Nov 22, 2014 at 3:42 PM, John D. Ament john.d.am...@gmail.com
wrote:


Is it me or has the proposal changed since the vote went out? Ideally we
want the proposal to be final before sending the vote.



This is why the vote includes the proposal text or a specific wiki
revision. I believe Benson sent the proposal text for the vote as a follow
up to the original call.

  On Sat, Nov 22, 2014 at 3:55 PM, Joe Witt joe.w...@gmail.com wrote:


John,

I've added the volunteering mentors. Updated the IPMC membership status

of

the mentors.  Updated the CLA status of the contributors.  I'll stop

doing

so now though to avoid any confusion.



Joe, usually when there are things to change that don't impact the vote
itself, they're noted by the champion as follow ons and then taken care of
after the vote in the podling docs rather than the proposal.

Easy mistake, not a big deal.

--
Sean





--
Sergio Fernández
Senior Researcher
Knowledge and Media Technologies
Salzburg Research Forschungsgesellschaft mbH
Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
T: +43 662 2288 318 | M: +43 660 2747 925
sergio.fernan...@salzburgresearch.at
http://www.salzburgresearch.at

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



[PROPOSAL] [DISCUSSION] Corinthia for Incubation.

2014-11-24 Thread jan i
Hi all,

On behalf of the project team I  would like to propose Corinthia as an
Apache Incubator project. The complete proposal can be found at:
https://github.com/uxproductivity/Corinthia/wiki/Incubator-proposal

We will move the proposal to incubator wiki, if it gets accepted and all
project members have r/w access.

I would like to point out, that we really would like a second mentor, who
are familiar with all the paperwork and can help give a second opinion
from the outside since I am also involved in the project.

The project team hope for a good discussion and hope to get feedback.

Remark I have added all initial committers to this mail, since not all are
subscribed to general@.

Please find the complete text below:

On behalf of the Corinthia team
jan I.

== COPY ===
## Proposal
The goal of Corinthia is to provide a responsive design editor (converter?
Or complete program? I suggest just using, “program”, a term used next
paragraph) as well as a toolkit that enacts a defined conversion between
different office document formats. Responsive design fits the layout as
needed, tablet or desktop. The editor is a lightweight editor - an
extension and not a replacement for the desktop editor.

Many office document programs claim to read/write to the ISO open standards
for office documents, OpenDocument Format (ODF) and Open Office XML
(OOXML), but do not document which parts are left unimplemented.
Furthermore, the standards have a large number of implementation defined
parts, making real-world congruence chancy. The Corinthia toolkit wants to
put this unacknowledged aspect into the open and provide compliance
sheets for document formats, as known from industry computer protocols.

Corinthia aims at generating a large set of test documents, which can be
used to verify the compliance sheets. The code can work as test case for
other applications (or entities tendering for OOXML/ODF based systems) as
well.

The base of Corinthia and its toolkit is the library DocFormats, which
converts between different office document file formats. Currently it
supports .docx (part of the OOXML specification), HTML, and LaTeX
(export-only).

The design  of DocFormats is based on on the idea of bidirectional
transformation (BDT), in which a specific document (the original file in
its source format) is converted into an abstract document (in the
destination format). A modified version of the abstract document can then
be used to update the specific document in a non-destructive manner,
keeping intact all parts of the file which are not supported in the
abstract format by modifying the original file rather than replacing it.

Descriptions of BDT can be found in:

Aaron Bohannon, J. Nathan Foster, Benjamin C. Pierce et. al. Boomerang:
Resourceful Lenses for String Data. Technical Report MS-CIS-07-15
Department of Computer and Information Science University of Pennsylvania.
November 2007. [boomerang.pdf](
http://www.cis.upenn.edu/~bcpierce/papers/boomerang.pdf)

Benjamin Pierce. Foundations for Bidirectional Programming. ICMT2009 -
International Conference on Model Transformation. June 2009.
[icmt-2009-slides.pdf](
http://www.cis.upenn.edu/~bcpierce/papers/icmt-2009-slides.pdf)

The short term goal of the project is to have an easy-to-integrate library
that any application can use to embed support for a range of different file
formats, and use the parsing, serialisation, and conversion facilities for
various purposes. These include editors, batch conversion tools, web
publishing systems, document analysis tools, and content management
systems. By abstracting over different file formats and using HTML as a
common intermediate format, one can just code an application to that end,
and let DocFormats take care of conversion to other formats.

The medium term goal of the project is to have a series of end-user
applications (separate from the library itself), including an editor and
file conversion tool. These will serve as examples of how the libraries can
be used.

And ultimately to have a touch based UI for office documents.

It is also a goal to cooperate with other open source projects, in terms of
getting input from them as well as providing APIs for their use. Corinthia
is meant to be easy to understand and work with, making it more
approachable for a range of projects.

## Background
DocFormats has been shipping as part of UX Write on the iOS app store since
February 2013. From this perspective, it is a stable, mature library that
works for the most commonly-used features of .docx formats. As an open
source project, it is completely new, and from this perspective is very
much in its early stages. We are currently exploring the best way to
leverage the existing work that has been done to make it easier to
integrate in other projects, as well as support more file formats.

## Rationale
Apache's mission to produce software for the public good, fits with
Corinthia's idea of providing an editor and thoroughly documented

Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.

2014-11-24 Thread jan i
Hi.

Sorry, somebody hit me with the big GIT hammer !! I did something with git
that should not be done.

The correct text is:
= COPY ==
## Proposal
The goal of Corinthia is to provide a responsive design editor as well as a
toolkit that enacts a defined conversion between different office document
formats. Responsive design fits the layout as needed, tablet or desktop.
The editor is a lightweight editor - an extension and not a replacement for
the desktop editor.

Many office document programs claim to read/write to the ISO open standards
for office documents, OpenDocument Format (ODF) and Open Office XML
(OOXML), but do not document which parts are left unimplemented.
Furthermore, the standards have a large number of implementation defined
parts, making real-world congruence chancy. The Corinthia toolkit wants to
put this unacknowledged aspect into the open and provide compliance
sheets for document formats, as known from industry computer protocols.

Corinthia aims at generating a large set of test documents, which can be
used to verify the compliance sheets. The code can work as test case for
other applications (or entities tendering for OOXML/ODF based systems) as
well.

The base of Corinthia and its toolkit is the library DocFormats, which
converts between different office document file formats. Currently it
supports .docx (part of the OOXML specification), HTML, and LaTeX
(export-only).

The design  of DocFormats is based on on the idea of bidirectional
transformation (BDT), in which a specific document (the original file in
its source format) is converted into an abstract document (in the
destination format). A modified version of the abstract document can then
be used to update the specific document in a non-destructive manner,
keeping intact all parts of the file which are not supported in the
abstract format by modifying the original file rather than replacing it.

Descriptions of BDT can be found in:

Aaron Bohannon, J. Nathan Foster, Benjamin C. Pierce et. al. Boomerang:
Resourceful Lenses for String Data. Technical Report MS-CIS-07-15
Department of Computer and Information Science University of Pennsylvania.
November 2007. [boomerang.pdf](
http://www.cis.upenn.edu/~bcpierce/papers/boomerang.pdf)

Benjamin Pierce. Foundations for Bidirectional Programming. ICMT2009 -
International Conference on Model Transformation. June 2009.
[icmt-2009-slides.pdf](
http://www.cis.upenn.edu/~bcpierce/papers/icmt-2009-slides.pdf)

The short term goal of the project is to have an easy-to-integrate library
that any application can use to embed support for a range of different file
formats, and use the parsing, serialisation, and conversion facilities for
various purposes. These include editors, batch conversion tools, web
publishing systems, document analysis tools, and content management
systems. By abstracting over different file formats and using HTML as a
common intermediate format, one can just code an application to that end,
and let DocFormats take care of conversion to other formats.

The medium term goal of the project is to have a series of end-user
applications (separate from the library itself), including an editor and
file conversion tool. These will serve as examples of how the libraries can
be used.

And ultimately to have a touch based UI for office documents.

It is also a goal to cooperate with other open source projects, in terms of
getting input from them as well as providing APIs for their use. Corinthia
is meant to be easy to understand and work with, making it more
approachable for a range of projects.

## Background
DocFormats has been shipping as part of UX Write on the iOS app store since
February 2013. From this perspective, it is a stable, mature library that
works for the most commonly-used features of .docx formats. As an open
source project, it is completely new, and from this perspective is very
much in its early stages. We are currently exploring the best way to
leverage the existing work that has been done to make it easier to
integrate in other projects, as well as support more file formats.

## Rationale
Apache's mission to produce software for the public good, fits with
Corinthia's idea of providing an editor and thoroughly documented
conversion of office documents, thereby hopefully show that implementations
can and should be documented especially where the standards offer options,
which will help to ensure interoperability.

We strongly believe the project has potential to grow by cooperating with
other projects and offers something mature projects cannot offer, a chance
to take advantage of new architectures and design philosophies, as well as
also to learn from, and not just reproduce, history.

We have found that Apache committers are loyal to Apache, and more likely
to take part in Corinthia.incubator than Corinthia.GitHub.


## Initial Goals
The initial and most important goal is to enlarge the community consisting
of developers, testers, 

Re: Wrong release name - Argus Ranger

2014-11-24 Thread Balaji Ganesan
Infra made the move from Argus website/mailing list to Ranger last week as
part of this JIRA https://issues.apache.org/jira/browse/INFRA-8471.

The ranger mailing lists was not working post the change. I believe there
was INFRA JIRA created for this
https://issues.apache.org/jira/browse/INFRA-8693



On Sat, Nov 22, 2014 at 7:33 PM, John D. Ament john.d.am...@gmail.com
wrote:

 Ok, I had to dig into mail archives to figure out what's going on.

 Currently anything @argus.i.a.o is bouncing.  Switching to the ranger
 mail alias to see if it goes through.

 John

 On Sat, Nov 22, 2014 at 10:22 PM, John D. Ament john.d.am...@gmail.com
 wrote:
  Hi Argus,
 
  I was compiling the release list and noticed that yours wasn't named
 properly.
 
  /release/incubator/argus/0.4.0/ranger-0.4.0.tar.gz
 
  Per incubation requirements, it needs to be named -incubating  -
  please see
 http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
 
  Can you fix this?

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



-- 
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: [RESULT] [VOTE] accept NiFi into the incubator

2014-11-24 Thread Benson Margulies
The vote for NiFi incubation has passed. I will go start turning cranks.


Nonbinding +1:

Sean Busaby
Brock Noland
Ryan Blue
Joey Echeverria


Binding +1:

Tim Williams
Chris Mattmann
Suresh Srinivas
Chris Douglas
John D Ament
Benson Margulies
Jake Farrell
Andrew Purtell
Bertrand Delacretaz
Advind Prabhakar
Alan D. Cabrera
Ted Dunning
j...@apache.org
Sergio Fernández


Using Twiki in Website

2014-11-24 Thread Balaji Ganesan
Can anyone share their experience around using twiki in their website, for
user content or other purposes? The good and the bad?

-- 
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: Wrong release name - Argus Ranger

2014-11-24 Thread John D. Ament
On Mon Nov 24 2014 at 4:27:38 PM Balaji Ganesan bgane...@hortonworks.com
wrote:

 Infra made the move from Argus website/mailing list to Ranger last week as
 part of this JIRA https://issues.apache.org/jira/browse/INFRA-8471.

 The ranger mailing lists was not working post the change. I believe there
 was INFRA JIRA created for this
 https://issues.apache.org/jira/browse/INFRA-8693



Thanks for the update.  Do you mind if I include these details in the
incubator's monthly report?



 On Sat, Nov 22, 2014 at 7:33 PM, John D. Ament john.d.am...@gmail.com
 wrote:

  Ok, I had to dig into mail archives to figure out what's going on.
 
  Currently anything @argus.i.a.o is bouncing.  Switching to the ranger
  mail alias to see if it goes through.
 
  John
 
  On Sat, Nov 22, 2014 at 10:22 PM, John D. Ament john.d.am...@gmail.com
  wrote:
   Hi Argus,
  
   I was compiling the release list and noticed that yours wasn't named
  properly.
  
   /release/incubator/argus/0.4.0/ranger-0.4.0.tar.gz
  
   Per incubation requirements, it needs to be named -incubating  -
   please see
  http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
  
   Can you fix this?
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 

 --
 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: Wrong release name - Argus Ranger

2014-11-24 Thread Balaji Ganesan
John, please do. Thanks again for your help in overseeing this.

P.S: Please note that d...@ranger.incubator.apache.org will continue to
bounce till we fix the issue with Infra. I have taken it off from cc

On Mon, Nov 24, 2014 at 1:33 PM, John D. Ament johndam...@apache.org
wrote:

 On Mon Nov 24 2014 at 4:27:38 PM Balaji Ganesan bgane...@hortonworks.com
 wrote:

  Infra made the move from Argus website/mailing list to Ranger last week
 as
  part of this JIRA https://issues.apache.org/jira/browse/INFRA-8471.
 
  The ranger mailing lists was not working post the change. I believe there
  was INFRA JIRA created for this
  https://issues.apache.org/jira/browse/INFRA-8693
 
 
 
 Thanks for the update.  Do you mind if I include these details in the
 incubator's monthly report?


 
  On Sat, Nov 22, 2014 at 7:33 PM, John D. Ament john.d.am...@gmail.com
  wrote:
 
   Ok, I had to dig into mail archives to figure out what's going on.
  
   Currently anything @argus.i.a.o is bouncing.  Switching to the ranger
   mail alias to see if it goes through.
  
   John
  
   On Sat, Nov 22, 2014 at 10:22 PM, John D. Ament 
 john.d.am...@gmail.com
   wrote:
Hi Argus,
   
I was compiling the release list and noticed that yours wasn't named
   properly.
   
/release/incubator/argus/0.4.0/ranger-0.4.0.tar.gz
   
Per incubation requirements, it needs to be named -incubating  -
please see
   http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
   
Can you fix this?
  
   -
   To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
   For additional commands, e-mail: general-h...@incubator.apache.org
  
  
 
  --
  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.


Incubator website guide

2014-11-24 Thread Benson Margulies
Following http://incubator.apache.org/guides/website.html, I ran 'ant' (and
also build.sh) after adding nifi to podlings.xml and added the nifi.xml
fille. It didn't produce any changed files to commit.

Is the guide behind? Am I confused?


NiFi setup

2014-11-24 Thread Benson Margulies
One message here to make progress in public before we have NiFi mailing lists:

I've added nifi to podlings.xml and I've created nifi.xml.

I've opened INFRA-8706  for the mailing lists.

I plan to write one other JIRA for a git repo; after that, we need
discussion on the list to be sure of what we want.

Once we have some mailing lists, we can coordinate next steps. Initial
committers can get/keep those ICLA cards and letters coming in.

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



Re: Incubator website guide

2014-11-24 Thread Alan D. Cabrera

On Nov 24, 2014, at 1:49 PM, Benson Margulies bimargul...@gmail.com wrote:

 Following http://incubator.apache.org/guides/website.html, I ran 'ant' (and
 also build.sh) after adding nifi to podlings.xml and added the nifi.xml
 fille. It didn't produce any changed files to commit.
 
 Is the guide behind? Am I confused?


python3 clutch.py
ant
svn ci -m Run clutch.
ssh -t a...@people.apache.org publish.pl incubator adc

works for me.


Regards,
Alan



Re: Incubator website guide

2014-11-24 Thread John D. Ament
On Mon, Nov 24, 2014 at 5:46 PM, Alan D. Cabrera l...@toolazydogs.com wrote:

 On Nov 24, 2014, at 1:49 PM, Benson Margulies bimargul...@gmail.com wrote:

 Following http://incubator.apache.org/guides/website.html, I ran 'ant' (and
 also build.sh) after adding nifi to podlings.xml and added the nifi.xml
 fille. It didn't produce any changed files to commit.

 Is the guide behind? Am I confused?


 python3 clutch.py
 ant
 svn ci -m Run clutch.
 ssh -t a...@people.apache.org publish.pl incubator adc

 works for me.

So then the clutch is missing from the page Benson mentioned, no?



 Regards,
 Alan


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



Fwd: [jira] [Closed] (INFRA-8696) Access to Jenkins

2014-11-24 Thread Edward J. Yoon
Mentors, if incubator project can use the Jenkins, Please add fegaras and
moon to Jenkins.

-- Forwarded message --
From: David Nalley (JIRA) j...@apache.org
Date: Mon, Nov 24, 2014 at 11:10 PM
Subject: [jira] [Closed] (INFRA-8696) Access to Jenkins
To: edwardy...@apache.org



 [
https://issues.apache.org/jira/browse/INFRA-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Nalley closed INFRA-8696.
---
Resolution: Not a Problem

Granting access to Jenkins is not an infra task. Please talk to your PMC
Chair and refer him/her to:
http://wiki.apache.org/general/Jenkins#How_do_I_get_an_account


 Access to Jenkins
 -

 Key: INFRA-8696
 URL: https://issues.apache.org/jira/browse/INFRA-8696
 Project: Infrastructure
  Issue Type: Wish
  Components: Jenkins
Reporter: Edward J. Yoon

 Can someone please add fegaras and moon to Jenkins.



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



-- 
Best Regards, Edward J. Yoon


Re: Incubator website guide

2014-11-24 Thread Benson Margulies
On Mon, Nov 24, 2014 at 6:24 PM, John D. Ament johndam...@apache.org wrote:
 On Mon, Nov 24, 2014 at 5:46 PM, Alan D. Cabrera l...@toolazydogs.com wrote:

 On Nov 24, 2014, at 1:49 PM, Benson Margulies bimargul...@gmail.com wrote:

 Following http://incubator.apache.org/guides/website.html, I ran 'ant' (and
 also build.sh) after adding nifi to podlings.xml and added the nifi.xml
 fille. It didn't produce any changed files to commit.

 Is the guide behind? Am I confused?


 python3 clutch.py
 ant
 svn ci -m Run clutch.
 ssh -t a...@people.apache.org publish.pl incubator adc

 works for me.

 So then the clutch is missing from the page Benson mentioned, no?

Yes it is, which is ironic, given that I wrote some of the code of it.

I did fix the reference to discuss target/site which is where the
content actually lands.

I'm going to do something about git, too.




 Regards,
 Alan


 -
 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



DeviceMap podling status page looks wrong

2014-11-24 Thread sebb
The DeviceMap podling status page [1] looks wrong to me.
The News section is all but empty, and does not mention graduation.

The entries under Incubation work items are all listed as having
been completed on 2014-09-29.
Is that really correct?

[1] http://incubator.apache.org/projects/devicemap.html

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