Re: Github pull requests

[Felix Cheung]

Re JIRA - the merge PR script in Spark closes the JIRA automatically..

_
From: Julian Hyde 
Sent: Wednesday, February 21, 2018 8:46 PM
Subject: Re: Github pull requests
To: Jonas Pfefferle 
Cc: , Patrick Stuedi 


I believe that there are tools to do git / CI / JIRA integration. Spark is one 
of the projects with the most integration. Search their lists and JIRA to find 
out how they did it.

Speaking for my own project: Calcite doesn’t have very much integration because 
we don’t have spare cycles to research and troubleshoot. A documented manual 
process suffices.

Julian


> On Feb 21, 2018, at 2:26 AM, Jonas Pfefferle  wrote:
>
> We just closed our first pull request and where wondering if there is also a 
> way to automatically close the corresponding JIRA ticket? Also is there a way 
> we can technically enforce that we have a certain amount of people who 
> approved the code? Or do we have to do this informally?
>
> Thanks,
> Jonas
>
> On Wed, 14 Feb 2018 10:53:04 -0800
> Julian Hyde  wrote:
>> The nice thing about git is that every git repo is capable of being a master 
>> / slave. (The ASF git repo is special only in that it gathers audit logs 
>> when people push to it, e.g. the IP address where the push came from. Those 
>> logs will be useful if the provenance of our IP is ever challenged.)
>> So, the merging doesn’t happen on the GitHub repo. It happens in the repo on 
>> your laptop. Before merging, you pull the latest from the apache master 
>> branch (it doesn’t matter whether this comes from the GitHub mirror or the 
>> ASF repo - it is bitwise identical, as the commit SHAs will attest), and you 
>> pull from a GitHub repo the commit(s) referenced in the GitHub PR. You 
>> append these commits to the commit chain, test, then push to the ASF master 
>> branch.
>> If you add ‘Close #NN’ to the commit comments (and you generally will), an 
>> ASF commit hook will close PR #NN at the time that the commit arrives in ASF 
>> git.
>> Julian
>>> On Feb 14, 2018, at 6:59 AM, Jonas Pfefferle  wrote:
>>> I think you are missing a 3rd option:
>>> Basically option 1) but we merge the pull request on github and push the 
>>> changes to the apache git. So no need to delete the PRs. However we have to 
>>> be careful to only commit changes to github to not get the histories out of 
>>> sync.
>>> Jonas
>>> On Wed, 14 Feb 2018 13:58:58 +0100
>>> Patrick Stuedi  wrote:
 Hi all,
 If the github repo is synced with git repo only in one direction, then
 what is the recommended way to handle new code contributions
 (including code reviews)? We see two options here:
 1) Code contributions are issued as PRs on the Crail Apache github
 (and reviewed there), then merged outside in a private repo and
 committed back to the Apache git repo (the PR may need to be deleted
 once the commit has happened), from where the Apache Crail github repo
 will again pick it up (sync).
 2) We don't use the git repo at all, only the github repo. PRs are
 reviewed and merged directly at the github level.
 Option (1) looks complicated, option (2) might not be according to the
 Apache policies (?). What is the recommended way?
 -Patrick
 On Mon, Feb 12, 2018 at 5:25 PM, Julian Hyde  
 wrote:
> No.
> Julian
>> On Feb 12, 2018, at 08:03, Jonas Pfefferle  wrote:
>> Hi @all,
>> Is the Apache Crail github repository synced both ways with the Apache 
>> Crail git? I.e. can we merge pull request in github?
>> Regards,
>> Jonas
>

Re: draft podling report

[Felix Cheung]

Great! I’ve added myself preemptively to the wiki and signed off the Crail 
report.

Could one you please add me on whimsy, if it makes sense, as mentor. Thanks



From: Luciano Resende 
Sent: Tuesday, December 4, 2018 2:01 PM
To: dev@crail.apache.org
Subject: Re: draft podling report

+1, have already signed off.

On Tue, Dec 4, 2018 at 9:30 AM Julian Hyde  wrote:
>
> Looks good. Thanks for doing this promptly. I'll sign off tomorrow
> after it is final.
>
> Felix, As a new mentor, feel free to add your name below the report,
> sign off, and add comments.
>
> Julian
>
> On Tue, Dec 4, 2018 at 9:18 AM bernard metzler  wrote:
> >
> > Dear all, I added a draft podling report for Crail to
> > https://wiki.apache.org/incubator/December2018. Please
> > check if it makes all sense. Dear mentors, as usual,
> > be frank if something looks suspicious or is inappropriate,
> > or missing. I think we can still edit until tomorrow
> > evening.
> >
> > Thanks a lot,
> > Bernard.



--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Felix Cheung]

Hi there - please see the notice below. I will kick this off as “discuss” thread

+1 for the move



From: Apache Infrastructure Team 
Sent: Thursday, January 3, 2019 5:19 AM
To: dev@crail.apache.org
Subject: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Hello, crail folks.
As stated earlier in 2018, all git repositories must be migrated from
the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
is being decommissioned. Your project is receiving this email because
you still have repositories on git-wip-us that needs to be migrated.

The following repositories on git-wip-us belong to your project:
- incubator-crail.git
- incubator-crail-website.git


We are now entering the mandated (coordinated) move stage of the roadmap,
and you are asked to please coordinate migration with the Apache
Infrastructure Team before February 7th. All repositories not migrated
on February 7th will be mass migrated without warning, and we'd appreciate
it if we could work together to avoid a big mess that day :-).

Moving to gitbox means you will get full write access on GitHub as well,
and be able to close/merge pull requests and much more.

To have your repositories moved, please follow these steps:

- Ensure consensus on the move (a link to a lists.apache.org thread will
suffice for us as evidence).
- Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA

Your migration should only take a few minutes. If you wish to migrate
at a specific time of day or date, please do let us know in the ticket.

As always, we appreciate your understanding and patience as we move
things around and work to provide better services and features for
the Apache Family.

Should you wish to contact us with feedback or questions, please do so
at: us...@infra.apache.org.


With regards,
Apache Infrastructure

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Felix Cheung]

Hi there - any more vote/comment?



From: Luciano Resende 
Sent: Friday, January 4, 2019 5:44 AM
To: dev@crail.apache.org
Subject: Re: [NOTICE] Mandatory migration of git repositories to 
gitbox.apache.org

Hey all, please use this thread if you have any concerns/questions
about this move, otherwise please create a INFRA Jira issue and
reference this thread.

On Thu, Jan 3, 2019 at 8:19 AM Apache Infrastructure Team
 wrote:
>
> Hello, crail folks.
> As stated earlier in 2018, all git repositories must be migrated from
> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> is being decommissioned. Your project is receiving this email because
> you still have repositories on git-wip-us that needs to be migrated.
>
> The following repositories on git-wip-us belong to your project:
> - incubator-crail.git
> - incubator-crail-website.git
>
>
> We are now entering the mandated (coordinated) move stage of the roadmap,
> and you are asked to please coordinate migration with the Apache
> Infrastructure Team before February 7th. All repositories not migrated
> on February 7th will be mass migrated without warning, and we'd appreciate
> it if we could work together to avoid a big mess that day :-).
>
> Moving to gitbox means you will get full write access on GitHub as well,
> and be able to close/merge pull requests and much more.
>
> To have your repositories moved, please follow these steps:
>
> - Ensure consensus on the move (a link to a lists.apache.org thread will
> suffice for us as evidence).
> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>
> Your migration should only take a few minutes. If you wish to migrate
> at a specific time of day or date, please do let us know in the ticket.
>
> As always, we appreciate your understanding and patience as we move
> things around and work to provide better services and features for
> the Apache Family.
>
> Should you wish to contact us with feedback or questions, please do so
> at: us...@infra.apache.org.
>
>
> With regards,
> Apache Infrastructure
>


--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Felix Cheung]

Great, thanks!

Could someone take the lead to create the Infra JIRA? (All it needs is to 
reference this mail thread from lists.apache.org)

It should be very simple - once that is done there’s a small step for 
committers to connect their accounts on gitbox, that’s it.



From: Patrick Stuedi 
Sent: Sunday, January 6, 2019 11:47 AM
To: dev@crail.apache.org
Subject: Re: [NOTICE] Mandatory migration of git repositories to 
gitbox.apache.org

+1 from me too, we should create the infra JIRA as Luciano suggested.
Jonas has interacted with the infra team in the past.

On Sun, Jan 6, 2019 at 8:09 PM Felix Cheung  wrote:
>
> Hi there - any more vote/comment?
>
>
> 
> From: Luciano Resende 
> Sent: Friday, January 4, 2019 5:44 AM
> To: dev@crail.apache.org
> Subject: Re: [NOTICE] Mandatory migration of git repositories to 
> gitbox.apache.org
>
> Hey all, please use this thread if you have any concerns/questions
> about this move, otherwise please create a INFRA Jira issue and
> reference this thread.
>
> On Thu, Jan 3, 2019 at 8:19 AM Apache Infrastructure Team
>  wrote:
> >
> > Hello, crail folks.
> > As stated earlier in 2018, all git repositories must be migrated from
> > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> > is being decommissioned. Your project is receiving this email because
> > you still have repositories on git-wip-us that needs to be migrated.
> >
> > The following repositories on git-wip-us belong to your project:
> > - incubator-crail.git
> > - incubator-crail-website.git
> >
> >
> > We are now entering the mandated (coordinated) move stage of the roadmap,
> > and you are asked to please coordinate migration with the Apache
> > Infrastructure Team before February 7th. All repositories not migrated
> > on February 7th will be mass migrated without warning, and we'd appreciate
> > it if we could work together to avoid a big mess that day :-).
> >
> > Moving to gitbox means you will get full write access on GitHub as well,
> > and be able to close/merge pull requests and much more.
> >
> > To have your repositories moved, please follow these steps:
> >
> > - Ensure consensus on the move (a link to a lists.apache.org thread will
> > suffice for us as evidence).
> > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> >
> > Your migration should only take a few minutes. If you wish to migrate
> > at a specific time of day or date, please do let us know in the ticket.
> >
> > As always, we appreciate your understanding and patience as we move
> > things around and work to provide better services and features for
> > the Apache Family.
> >
> > Should you wish to contact us with feedback or questions, please do so
> > at: us...@infra.apache.org.
> >
> >
> > With regards,
> > Apache Infrastructure
> >
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Felix Cheung]

Thanks!


From: Animesh Trivedi 
Sent: Monday, January 7, 2019 1:42:52 AM
To: dev@crail.apache.org
Subject: Re: [NOTICE] Mandatory migration of git repositories to 
gitbox.apache.org

Migration is finished.

On Mon, Jan 7, 2019 at 10:22 AM Animesh Trivedi 
wrote:

> Done: https://issues.apache.org/jira/browse/INFRA-17570
>
> Cheers,
> --
> Animesh
>
> On Sun, Jan 6, 2019 at 9:13 PM Felix Cheung 
> wrote:
>
>> Great, thanks!
>>
>> Could someone take the lead to create the Infra JIRA? (All it needs is to
>> reference this mail thread from lists.apache.org)
>>
>> It should be very simple - once that is done there’s a small step for
>> committers to connect their accounts on gitbox, that’s it.
>>
>>
>> 
>> From: Patrick Stuedi 
>> Sent: Sunday, January 6, 2019 11:47 AM
>> To: dev@crail.apache.org
>> Subject: Re: [NOTICE] Mandatory migration of git repositories to
>> gitbox.apache.org
>>
>> +1 from me too, we should create the infra JIRA as Luciano suggested.
>> Jonas has interacted with the infra team in the past.
>>
>> On Sun, Jan 6, 2019 at 8:09 PM Felix Cheung 
>> wrote:
>> >
>> > Hi there - any more vote/comment?
>> >
>> >
>> > 
>> > From: Luciano Resende 
>> > Sent: Friday, January 4, 2019 5:44 AM
>> > To: dev@crail.apache.org
>> > Subject: Re: [NOTICE] Mandatory migration of git repositories to
>> gitbox.apache.org
>> >
>> > Hey all, please use this thread if you have any concerns/questions
>> > about this move, otherwise please create a INFRA Jira issue and
>> > reference this thread.
>> >
>> > On Thu, Jan 3, 2019 at 8:19 AM Apache Infrastructure Team
>> >  wrote:
>> > >
>> > > Hello, crail folks.
>> > > As stated earlier in 2018, all git repositories must be migrated from
>> > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
>> service
>> > > is being decommissioned. Your project is receiving this email because
>> > > you still have repositories on git-wip-us that needs to be migrated.
>> > >
>> > > The following repositories on git-wip-us belong to your project:
>> > > - incubator-crail.git
>> > > - incubator-crail-website.git
>> > >
>> > >
>> > > We are now entering the mandated (coordinated) move stage of the
>> roadmap,
>> > > and you are asked to please coordinate migration with the Apache
>> > > Infrastructure Team before February 7th. All repositories not migrated
>> > > on February 7th will be mass migrated without warning, and we'd
>> appreciate
>> > > it if we could work together to avoid a big mess that day :-).
>> > >
>> > > Moving to gitbox means you will get full write access on GitHub as
>> well,
>> > > and be able to close/merge pull requests and much more.
>> > >
>> > > To have your repositories moved, please follow these steps:
>> > >
>> > > - Ensure consensus on the move (a link to a lists.apache.org thread
>> will
>> > > suffice for us as evidence).
>> > > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>> > >
>> > > Your migration should only take a few minutes. If you wish to migrate
>> > > at a specific time of day or date, please do let us know in the
>> ticket.
>> > >
>> > > As always, we appreciate your understanding and patience as we move
>> > > things around and work to provide better services and features for
>> > > the Apache Family.
>> > >
>> > > Should you wish to contact us with feedback or questions, please do so
>> > > at: us...@infra.apache.org.
>> > >
>> > >
>> > > With regards,
>> > > Apache Infrastructure
>> > >
>> >
>> >
>> > --
>> > Luciano Resende
>> > http://twitter.com/lresende1975
>> > http://lresende.blogspot.com/
>>
>

Re: New blog post: Call overhead Python -> C/C++

[Felix Cheung]

Very cool, Jonas!



From: Patrick Stuedi 
Sent: Friday, January 25, 2019 11:05 AM
To: dev@crail.apache.org
Subject: Re: New blog post: Call overhead Python -> C/C++

Done. Just posted a tweet.


On Fri, Jan 25, 2019 at 7:59 PM Julian Hyde  wrote:

> May I suggest you tweet a link to the blog post? Wes and I are active on
> twitter and can help bring Crail to a wider audience.
>
> > On Jan 25, 2019, at 4:48 AM, Jonas Pfefferle  wrote:
> >
> > Hi @all
> >
> >
> > We have been investigating the performance impact of calling C/C++
> functions from Python for a possible Python client API/library for Crail.
> Check out our new blog entry with the findings:
> http://crail.incubator.apache.org/blog/2019/01/python.html
> >
> > Cheers,
> > Jonas
>
>

Re: Podling Report Reminder - March 2019

[Felix Cheung]

Hello there -  a quick reminder a report is due for the project.



From: jmcl...@apache.org
Sent: Friday, March 1, 2019 2:35 PM
To: d...@crail.incubator.apache.org
Subject: Podling Report Reminder - March 2019

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 20 March 2019, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, March 06).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

* Your project name
* A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
* A list of the three most important issues to address in the move
towards graduation.
* Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
* How has the community developed since the last report
* How has the project developed since the last report.
* How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/March2019

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Incubator report

[Felix Cheung]

Looks good. Thanks Bernard.

Btw any way to get more traffic on dev@? Perhaps you can announce some of these 
news on it.



From: bernard metzler 
Sent: Tuesday, March 5, 2019 5:34 AM
To: dev@crail.apache.org; Julian Hyde
Subject: Re: Incubator report

On 3/5/2019 11:24, Julian Hyde wrote:
> Hi Crail PPMC,
>
> The March incubator report is due tomorrow. Is someone working on it?
>
> Julian
>
> https://wiki.apache.org/incubator/March2019 
> 
>
>
Hi all,

I added the draft report to https://wiki.apache.org/incubator/March2019

Dear mentors, please have a look.

Thanks very much!
Bernard.

Re: podling report June

[Felix Cheung]

About me - yes, it was discussed on list and I wasn’t able to change the roster 
myself at the time.




From: Justin Mclean 
Sent: Thursday, May 30, 2019 8:00 PM
To: dev@crail.apache.org
Subject: Re: podling report June

Hi,

Thanks for submitting the report early much appreciated and it makes my job 
easier.

 A few minor things that if you could fix it would be appreciated.
- You're missing an answer to "Any issues that the Incubator PMC (IPMC) or ASF 
Board wish/need to be aware of?" (Or rather I think markup is hiding your 
answer.)
- Felix is not listed as a mentor of your project in the roster [1]
- Make sure that each line under the ### headings starts with two spaces

Thanks,
Justin


1. https://whimsy.apache.org/roster/ppmc/crail

Re: Close PR right on Github page

[Felix Cheung]

Adrian, did you link your account? You should be able to close or merge PR once 
you have setup.

https://gitbox.apache.org/setup/


From: Adrian Schüpbach 
Sent: Tuesday, June 11, 2019 2:41:54 PM
To: dev@crail.apache.org
Subject: Re: Close PR right on Github page

Hi Julian

Thanks for your answer. Right, "Close #nnn" has worked for me,
in some cases I'd prefer that a PR, which we really can not accept,
does not even create a history, so a commit with "Close #nnn"
would not be the right approach in those cases.

I will ask INFRA how to set permissions. Since some of us
have the "Close" button on the GitHUB UI, it must be
possible somehow to configure this.


Thanks
Adrian


On 11.06.2019 19:48, Julian Hyde wrote:
> I suspect that closing a PR from the Github UI may be possible now we have 
> gitbox, if permissions are set correctly. But I don’t know how to set 
> permissions. You could try asking INFRA in hipchat.
>
> The method I use isn’t pretty but it has worked for a long time. Add a 
> comment ‘Close #nnn’ or ‘Closes #nnn’ or ‘Close apache/incubator-crail#nnn’ 
> on its own line in a commit message. When the commit is merged into master 
> the bot will close the PR.
>
> Julian
>
>
>> On Jun 11, 2019, at 1:05 AM, Adrian Schuepbach  wrote:
>>
>> Hi Julian
>>
>> It seems that I do not have the right to close (or merge) a PR. The
>> button just does not appear for me. I thought that when I linked my GitHub
>> account with my Apache ID I got the rights, but now I don't have them.
>>
>> Might those rights have been lost after migrating to gitbox?
>>
>> I am still able to merge changes via the command line. But it would
>> be great, if I could also close (or merge) PRs on the website.
>>
>> What should I do to get these rights again?
>>
>> Thanks
>> Adrian
>>
>>
>

Re: Re: Close PR right on Github page

[Felix Cheung]

Great!


From: Adrian Schuepbach 
Sent: Thursday, June 13, 2019 5:33:04 AM
To: dev@crail.apache.org
Subject: Re: Re: Close PR right on Github page

Hi Felix

Thanks a lot! It seem that I only linked the Apache ID with my account and
joined the Apache group, but did not follow the rest of the steps (I did
this before
migrating to gitbox).

I have done the steps now and wait until it is all synchronized and
assume/hope it will work then.


Thanks a lot, this was a very useful hint!
Adrian





From:   "Felix Cheung" 
To: "dev@crail.apache.org" 
Date:   06/13/2019 03:28 AM
Subject:[EXTERNAL] Re: Close PR right on Github page



Adrian, did you link your account? You should be able to close or merge PR
once you have setup.

https://urldefense.proofpoint.com/v2/url?u=https-3A__gitbox.apache.org_setup_&d=DwIF-g&c=jf_iaSHvJObTbx-siA1ZOg&r=pcxZvCQyESWay4DCuwO7dXLiJ4NahPw6YN0LJ8XEt6k&m=5OAdnPdjB7MWuNmwpl8rTeTgnssXSiZBDAdqBVIXN3Y&s=w_sdA4b0XbpDJEovGRfNhSfrLlIRAmwE56belivrBQU&e=



From: Adrian Schüpbach 
Sent: Tuesday, June 11, 2019 2:41:54 PM
To: dev@crail.apache.org
Subject: Re: Close PR right on Github page

Hi Julian

Thanks for your answer. Right, "Close #nnn" has worked for me,
in some cases I'd prefer that a PR, which we really can not accept,
does not even create a history, so a commit with "Close #nnn"
would not be the right approach in those cases.

I will ask INFRA how to set permissions. Since some of us
have the "Close" button on the GitHUB UI, it must be
possible somehow to configure this.


Thanks
Adrian


On 11.06.2019 19:48, Julian Hyde wrote:
> I suspect that closing a PR from the Github UI may be possible now we
have gitbox, if permissions are set correctly. But I don’t know how to set
permissions. You could try asking INFRA in hipchat.
>
> The method I use isn’t pretty but it has worked for a long time. Add a
comment ‘Close #nnn’ or ‘Closes #nnn’ or ‘Close
apache/incubator-crail#nnn’ on its own line in a commit message. When the
commit is merged into master the bot will close the PR.
>
> Julian
>
>
>> On Jun 11, 2019, at 1:05 AM, Adrian Schuepbach 
wrote:
>>
>> Hi Julian
>>
>> It seems that I do not have the right to close (or merge) a PR. The
>> button just does not appear for me. I thought that when I linked my
GitHub
>> account with my Apache ID I got the rights, but now I don't have them.
>>
>> Might those rights have been lost after migrating to gitbox?
>>
>> I am still able to merge changes via the command line. But it would
>> be great, if I could also close (or merge) PRs on the website.
>>
>> What should I do to get these rights again?
>>
>> Thanks
>> Adrian
>>
>>
>

Re: Podling Report Reminder - September 2019

[Felix Cheung]

Hi - reminder of the report due within a week.



From: jmcl...@apache.org 
Sent: Thursday, August 22, 2019 6:29:04 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Report Reminder - September 2019

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 September 2019, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2019

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Report Reminder - September 2019

[Felix Cheung]

Hello - reminder again. The report is due in 2 days


From: Felix Cheung 
Sent: Wednesday, August 28, 2019 12:07:53 PM
To: dev@crail.apache.org 
Subject: Re: Podling Report Reminder - September 2019

Hi - reminder of the report due within a week.



From: jmcl...@apache.org 
Sent: Thursday, August 22, 2019 6:29:04 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Report Reminder - September 2019

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 September 2019, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2019

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Report Reminder - September 2019

[Felix Cheung]

Thank you Bernard.


From: bernard metzler 
Sent: Tuesday, September 3, 2019 2:10:33 AM
To: dev@crail.apache.org ; Felix Cheung 

Subject: Re: Podling Report Reminder - September 2019

Hi Felix,

Thanks for the reminder!

I just did put in what I think happened since last
report. Basically it is a great presentation Patrick
gave on USENIX ATC'19, which is also online now. And
a few pull requests, which have been incorporated.
We are preparing for a new release, but are not yet
there. So it feels a little thin this
time - but since folks were out on summer vacation...

Best regards,
Bernard.

On 9/2/2019 18:25, Felix Cheung wrote:
> Hello - reminder again. The report is due in 2 days
>
> ____
> From: Felix Cheung 
> Sent: Wednesday, August 28, 2019 12:07:53 PM
> To: dev@crail.apache.org 
> Subject: Re: Podling Report Reminder - September 2019
>
> Hi - reminder of the report due within a week.
>
>
> 
> From: jmcl...@apache.org 
> Sent: Thursday, August 22, 2019 6:29:04 PM
> To: d...@crail.incubator.apache.org 
> Subject: Podling Report Reminder - September 2019
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 18 September 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, September 04).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>  the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>  towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>  aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Podling Crail Report Reminder - December 2019

[Felix Cheung]

Hello- reminder on the report this week. Thanks!



From: jmcl...@apache.org 
Sent: Saturday, November 30, 2019 3:49:40 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - December 2019

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 December 2019, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, December 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/December2019

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Crail Report Reminder - December 2019

[Felix Cheung]

Thanks. We could also report a release is ongoing.


From: bernard metzler 
Sent: Monday, December 2, 2019 9:24:04 AM
To: dev@crail.apache.org ; Felix Cheung 

Subject: Re: Podling Crail Report Reminder - December 2019

Hi Felix,

Sure we will do. Just trying to get another release in shape to
have something great to report ;) OK we will likely fail that
release before December 5th, but we will report!

Thanks
Bernard.


On 12/2/2019 18:04, Felix Cheung wrote:
> Hello- reminder on the report this week. Thanks!
>
>
> 
> From: jmcl...@apache.org 
> Sent: Saturday, November 30, 2019 3:49:40 PM
> To: d...@crail.incubator.apache.org 
> Subject: Podling Crail Report Reminder - December 2019
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 18 December 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, December 04).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>  the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>  towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>  aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/December2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Reminder March Incubator report

[Felix Cheung]

Re: Podling Crail Report Reminder - June 2020

[Felix Cheung]

Reminder on the podling  report


From: jmcl...@apache.org 
Sent: Friday, May 22, 2020 9:53 PM
To: d...@crail.incubator.apache.org
Subject: Podling Crail Report Reminder - June 2020

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 17 June 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 03).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/June2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Crail draft podling report June 2020

[Felix Cheung]

Thanks - The wiki is now using the same credentials as your Apache account - 
have you tried that?



From: bernard metzler 
Sent: Tuesday, June 2, 2020 2:04:00 AM
To: dev@crail.apache.org 
Subject: Crail draft podling report June 2020

Please find below a draft podling report for Crail,
subject to discussion, suggestions, changes, etc.

Initially I wanted to directly put that in at
https://cwiki.apache.org/confluence/display/INCUBATOR/June2020

to edit online with you. Unfortunately I lost my
Confluence password for login, and any attempt to reset
it ends up with "An internal error occurred when trying
to change your password." In the interest of time, and
assuming others on the list still have access, I'd ask
one of you to put it in later today if we agreed on the
content.

Thanks,
Bernard.


Here is what I have in mind as a report so far:

---
Crail

Crail is a storage platform for sharing performance critical data in 
distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.
- Three most important unfinished issues to address before graduating:

1. Grow developers community
2. Grow Crail use base
3. More steady release cycle

- Are there any issues that the IPMC or ASF Board need to be aware of?

no.

- How has the community developed since the last report?

We see increasing traffic on the dev mailing list from
Crail users. A recent proposal from Adrian to add elastic
scaling got positive feedback from other committers.

- How has the project developed since the last report?

Crail went through a phase of limited visible activities on
the code base. It is critical the Crail developers
community resumes to be more active to keep the project
making decent progress. Using Crail as an ephemeral data
store for serverless computing emerges as a very suitable
use case. Pushing this forward, aiming at inclusion
in a next release is of common interest among the
committers.

- How would you assess the podling's maturity?

  (Please feel free to add your own commentary.)

  Initial setup
  Working towards first release
  x   Community building
  Nearing graduation
  Other:

- Date of last release:

2020-01-14

- When were the last committers or PPMC members elected?

December 4th, 2018

- Have your mentors been helpful and responsive?

yes.

Re: Podling Crail Report Reminder - September 2020

[Felix Cheung]

Reminder on report


From: jmcl...@apache.org 
Sent: Saturday, August 29, 2020 6:55:15 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - September 2020

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 September 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Crail Report Reminder - September 2020

[Felix Cheung]

Actually I just saw it. Thanks for putting it together.

It is great to hear updates on (hopefully) generating more activities


From: Felix Cheung 
Sent: Tuesday, September 1, 2020 12:35:24 PM
To: dev@crail.apache.org ; 
d...@crail.incubator.apache.org 
Subject: Re: Podling Crail Report Reminder - September 2020

Reminder on report


From: jmcl...@apache.org 
Sent: Saturday, August 29, 2020 6:55:15 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - September 2020

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 September 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/September2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Crail Report Reminder - December 2020

[Felix Cheung]

Reminder :


From: jmcl...@apache.org 
Sent: Saturday, November 28, 2020 4:01:28 PM
To: d...@crail.incubator.apache.org 
Subject: Podling Crail Report Reminder - December 2020

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 December 2020.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, December 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/December2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC