Re: Podling Report Reminder - July 2019

[Davor Bonaci]

FYI only: my stats come from GitHub's insights page [1] for the last 3
months. The methodology is "contributions to master, excluding merge
commits". 9 commits merged from 3 contributors. (I have no idea how would
this get to a hundred, however you slice it.)

Davor

[1]
https://github.com/apache/incubator-amaterasu/graphs/contributors?from=2019-03-22&to=2019-06-22&type=c

On Sun, Jun 23, 2019 at 6:20 PM Yaniv Rodenski  wrote:

> Hi Davor,
>
> That seems wrong to me. According to GitHub, just in the last month we had
> 8 PRs 5 of which are already merged and 3 are waiting for fixes based on
> review. In the last 3 months I believe we are getting closer to 100
> commits, I'll get the exact count for the report soon.
>
> Also, this is from our GitHub pulse for the last month - Excluding merges,
> *3
> authors* have pushed *22 commits* to master and *22 commits* to all
> branches. On master, *130 files* have changed and there have been *1,567*
> *additions* and *5,829* *deletions*
> <
> https://github.com/apache/incubator-amaterasu/compare/master@%7B1558659799%7D...master
> >.
>
>
> As for the release, we are very close to finishing our next release that
> includes another major milestone, the documentation. out of 38 issues, 33
> are done and two are in progress. I believe this is a matter of a couple of
> weeks before we can start voting on it.
>
> In addition 2 PRs ware opened for the next version.
>
> Once we have the documentation out (we are hoping for a public use-case by
> than as well) I think we can start test the community growth, but that my
> opinion, happy to have that discussion.
>
> Cheers,
> Yaniv
>
> On Sun, Jun 23, 2019 at 7:45 AM Davor Bonaci  wrote:
>
> > Hey everybody --
> > what's the current view on the state of the project?
> >
> > I see a few commits in the last 3 months (9 commits, 3 contributors), ~no
> > mailing list activity, ~no community growth since the start of the
> project,
> > no releases in a year, and no plans of one.
> >
> > Davor
> >
> > On Fri, Jun 21, 2019 at 7:30 PM  wrote:
> >
> > > 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 July 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, July 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/July2019
> > >
> > > 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
> > >
> >
>
>
> --
> Yaniv Rodenski
>
> +61 477 778 405
> ya...@shinto.io
>

Re: Podling Report Reminder - July 2019

[Davor Bonaci]

Hey everybody --
what's the current view on the state of the project?

I see a few commits in the last 3 months (9 commits, 3 contributors), ~no
mailing list activity, ~no community growth since the start of the project,
no releases in a year, and no plans of one.

Davor

On Fri, Jun 21, 2019 at 7:30 PM  wrote:

> 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 July 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, July 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/July2019
>
> 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: [Discuss] April report draft

[Davor Bonaci]

Congratulations, Nadav! That's a really big deal.

I signed off on the report. No additional comments (but my opinion has not
particularly changed).

On Mon, Apr 1, 2019 at 8:35 PM Yaniv Rodenski  wrote:

> Hi All
>
>
> First of all, a big congrats to Nadav and wife or the birth of their first
> child two days ago. While it is major progress, it did not make it to this
> months report :)
>
>
> Please see below the suggested report:
>
>
> Amaterasu
>
>
> Apache Amaterasu is a framework providing configuration management and
>
> deployment for Big Data Pipelines.
>
>
> It provides the following capabilities:
>
> Continuous integration tools to package pipelines and run tests.
>
> A repository to store those packaged applications: the applications
>
> repository.
>
> A repository to store the pipelines, and engine configuration (for
>
> instance, the location of the Spark master, etc.): per environment - the
>
> configuration repository.
>
> A dashboard to monitor the pipelines.
>
> A DSL and integration hooks allowing third parties to easily integrate.
>
>
> Amaterasu has been incubating since 2017-09.
>
>
> Three most important issues to address in the move towards graduation:
>
>
>   1. Grow up user and contributor communities
>
>   2. Prepare documentation
>
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
>
> of?
>
>
>   There is still concern regarding the progress of the project. The
> community tries to address this by making the project more accessible. The
> first major step is releasing the documentation and simplifying the install
> process. In addition, we are working closely with some of the newer
> contributors to mentor them and help them be more productive.
>
>
> How has the community developed since the last report?
>
>
>   Since the last report, we have been focusing on the next release with
> strong focus building the documentation which we hope will help with
> adoption. We are still working with a couple of organization on their use
> case, hopefully, those could become a public use cases soon.
>
>
> How has the project developed since the last report?
>
>
>   * 11 pull requests by 4 contributors have been opened since the last
> report. Out of those 2 have been closed, 2 are awaiting review/fixes and
> the rest have been merged
>
>   * Documentation has been progressing and is due for the upcoming release.
>
>
> Date of the last release:
>
>
>   12 July 2018
>
>
> When were the last committers or PMC members elected?
>
>
>   N/A
>
>
> Have your mentors been helpful and responsive or are things falling through
> the cracks? In the latter case, please list any open issues that need to be
> addressed
>
> .
>
>
>   N/A
>
>
> Signed-off-by:
>
>
>   [X](amaterasu) Jean-Baptiste Onofré
>
>  Comments:
>
>   [X](amaterasu) Olivier Lamy
>
>  Comments:
>
>   [X](amaterasu) Davor Bonaci
>
>  Comments:
>
>
>
> IPMC/Shepherd notes:
>

Re: Podling Report Reminder - April 2019

[Davor Bonaci]

Hi guys --
What do we think about the project status these days?

Davor

On Fri, Mar 29, 2019 at 4:07 PM  wrote:

> 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 April 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, April 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://wiki.apache.org/incubator/April2019
>
> 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: [DISCUSS] podling report

[Davor Bonaci]

>
> The report was made in a rush and a bit from memory as I am traveling.


In such cases, it is totally okay to miss the report and report the
following month -- not a big deal. I'd much rather see a good report next
month compared to an incorrect report with false data.

But, also, the incubation report is not Yaniv's personal responsibility.
What about everybody else in the PPMC?

> Two new contributors have contributed code that have been merged.
> This was from my memory, @Yariv Triffon  did start
> committing (he is working on AMATERASU-54), but also, he helped me and
> pushed to by branch during this iteration (@Yariv, correct me if I'm
> wrong). It does seem that those changes did not make it at the end (or I
> might have redone them manually) but I will remove him from the report.
>

SG. Also, for all metrics, I'd love to see both absolute numbers and
relevant difference from the previous report.

For example:
*During the past 3 months, there were X pull
requests/commits/contributors/dev@ threads/issues opened/resolved,
inclusive of X from first-time contributors. This compares to X and X in
the previous reporting period, respectively.*


> > In addition, we are actively looking for more use cases and organizations
> > to use Amaterasu.
> This is done by having direct discussions with different organizations, in
> fact, most of my efforts in the last months have been around trying to find
> use cases for Amaterasu, and I have been spending a lot of time approaching
> organizations (with some help from @Kirupagaran Devarajan
>  and @ey...@apache.org ).
>
> I think this is key to the success of the project no less than the number
> of commits, but it takes time, especially for a small project.
>

So, how many '*yes*'/'*no*'/'*in progress*' are there? What did you learn
from every 'no'? Is there any analysis or discussion what can be done to
improve things based on that feedback?


> if you and the other mentors think we should retire we can discuss that


Aside: telling somebody to give up on something should carry extreme
responsibility. Whoever tells somebody else to give up should better be
extremely confident and understand many of the implications, both personal
and professional. Many people easily advise others to give up because they
aren't capable of it themselves -- be careful to find your path. But, there
are also those who understand what they are saying and why, and you should
take them seriously. You are welcome to put me in either bucket; that is up
to you.

I tried to be clear previously that retirement != failure. Simply put, not
all communities are best fitted for the ASF. Joining ASF gives you rights
and responsibilities. For some communities, they receive more than they
give. For others, it is the other way around and it simply is not the right
fit. I am very confident to say Amaterasu is not the right fit, at least
for the foreseeable future. You'd be better off as a standalone project on
GitHub, or potentially part of Apache Labs [1]. In either case, you
wouldn't need to worry about reporting, releasing, growing committers --
all of which is now lacking -- and could focus on what you really need:
iterating in understanding and solving user pain.

I wanted to know if maybe there are things you and the rest of the mentors
> think you can do to help us pass this rough patch and get the project to
> the next level
>

I commented on this many times over: the value proposition is not
resonating with users, you need to focus on understanding user pain better
and solving it. Incubation mentors cannot do this for you.

Davor

[1] http://labs.apache.org/

Re: Podling Report Reminder - January 2019

[Davor Bonaci]

Thanks Justin for stepping in; much appreciated.

Yaniv et al, this thread needs attention.

Also, maybe the mentors do have ideas on how to make progress on this
> front? in your experience, ware there any tactics that worked in such
> scenarios?
>

We already discussed this. The problem isn't tactical execution on
community growth, it is the value proposition. Mentors will not be able to
help you on these issues.

Re: [DISCUSS] podling report

[Davor Bonaci]

The report doesn't have my sign-off in the current form.


> Two new contributors have contributed code that have been merged.


Can you please clarify who are those? From what I can tell [1], the code
activity includes past contributors Yaniv (11 commits, 1.5k lines) and
anonymousGiraffe (50 lines). The (only) new contributor seems to be ebarten
at 40 lines.


> In addition, we are actively looking for more use cases and organizations
> to use Amaterasu.
>

Can you please clarify what exactly has been done here? Links and evidence
would be super helpful.


> * 5 pull requests have been opened


I can see four (#34 - #37). #33 was opened in early August. Which is the
fifth one?

Firstly, I don't think it matters whether there are 1 or 2 new
contributors, 4 or 5 pull requests, but it does bother me the accuracy of
the report. Please be accurate when reporting statistics and possibly quote
the source if there's any doubt about them, otherwise you easily lose all
credibility and appear disrespectful to your audience. Please.

Secondly, I think it is safe to assume that everybody understands that the
project is dormant and not making any progress towards graduation. Should
the report at least mention it? Even after being explicitly asked by Justin?

Please note that I'm not trying to be difficult here, but things cannot
continue this way.

Davor

[1]
https://github.com/apache/incubator-amaterasu/graphs/contributors?from=2018-10-05&to=2019-01-05&type=c

Re: Podling Report Reminder - January 2019

[Davor Bonaci]

Any comments?

On Fri, Dec 21, 2018 at 5:48 PM Justin Mclean  wrote:

> Hi,
>
>  In your last report it was mentioned that:
> "A concern was raised by Davor Bonaci (mentor) that the community is too
> small and not active enough and that Amaterasu should consider retiring.
> currently, the community voted on trying to address those issues and
> reconsider in a few months."
>
> Has any progress / decision been made? I was not able to find any further
> discussion about this other than the initial thread. Please include in your
> report how the PPMC is addressing this issue.
>
> Thanks,
> Justin
>

Re: [DISCUSS] podling report

[Davor Bonaci]

>
>   A concern was raised by Davor Bonaci (mentor) that the community is too
>
small and not active enough and that Amaterasu should consider retiring.
> currently, the community voted on trying to address those issues and
> reconsider in a few months.
>

"a mentor" or "mentors". (We generally avoid naming individuals in reports.)

Remove "community voted", there was no vote yet. Please rephrase as "We did
a roll call, and identified a total of 4 individuals willing to contribute
as volunteers. We'll keep tracking the activity and reassess whether to
retire within a few months."

How has the community developed since the last report?
>
>   * One additional contributor has been added to the community, he is still
> working on his first commit with the help of one PPMC
>

No evidence on the mailing list. You could compare activity on the mailing
list, PRs, etc. compared to the previous quarter.

How has the project developed since the last report?
>
>   * Since the last report Amaterasu had its first release as an Apache
> Project.
>

Emphasize -- this is a big milestone.

Re: Project status

[Davor Bonaci]

Okay; it seems there 4 people interested and willing to work on the
project. Option #2 it is.

Some other comments:

- Please don't apologize for any lack of contribution at any given time --
this is a volunteer led organization and we totally understand and
appreciate volunteer efforts as, when and if they are made.

- There are many ways of growing the community; the best one is by
increasing usage and adoption ("user fit"). Obviously, this is a hard
problem, requiring lot of time, user development, and improving the
technology. Alternatively, if there's no organic growth, companies often
get paid developers regardless in hopes that those people can solve the
problem with user fit and jump start the organic growth. There are no easy
answers, perhaps similar to the book The Hard Thing About Hard Things. You
have to work like crazy on it, there's no recipe.

- You should discuss the goals so that there are no moving goalposts. Think
about some metrics that you want to accomplish now, and then measure
yourself against them in 3 months. All four of you should drive this
discussion -- and JB and I should just be the observers. And, please, make
sure you start those conversations again to check on the progress. (Please
don't wait for me to do it.)

On Tue, Oct 2, 2018 at 4:39 AM Kirupa Devarajan 
wrote:

> Hi All,
>
> I would like the project to remain in podling too. My workload is becoming
> less and I will start contributing too.
>
> -Kirupa
>
> On Tue., 2 Oct. 2018, 6:26 pm Jean-Baptiste Onofré, 
> wrote:
>
> > Hi,
> >
> > I second Davor here. I think it makes sense to think about retiring the
> > podling. I don't see large community around the project (both dev and
> > user).
> >
> > Regards
> > JB
> >
> > On 02/10/2018 09:27, Davor Bonaci wrote:
> > > Any comments? Anyone?
> > >
> > > Option 1: start a vote to retire the podling and move the project into
> > your
> > > own repository.
> > > Option 2: keep things as-is for a few months and re-assess.
> > >
> > > I'd say Option 2 requires a minimum of 3 people explicitly saying that
> > they
> > > want to continue trying and contributing.
> > >
> > > On Sun, Sep 23, 2018 at 8:13 PM Davor Bonaci  wrote:
> > >
> > >> Thanks Yaniv for your comments.
> > >>
> > >>- After the release of 0.2.0 the community became very quiet. I
> think
> > >>>that at this point in the life of the project it is natural, as we
> > all
> > >>>doing this in our free time and the release was a major effort
> that
> > >>> all of
> > >>>us (after talking to members in the community) had to compensate
> for
> > >>> in our
> > >>>day jobs and families.
> > >>>With that said, we shouldn't have gone so quiet. I think we can
> all
> > >>>agree this is not acceptable for so long (if at all).
> > >>>
> > >>
> > >> Not sure I agree: it is not natural for projects in the Incubator to
> be
> > >> quiet. It does happen to projects that are getting
> obsolete/irrelevant,
> > >> often after many years as TLPs. The release usually *increases*
> activity
> > >> around the project as new users come, ask questions, start
> contributing,
> > >> etc.
> > >>
> > >> On the other hand, totally fine for people to go quiet. The problem
> > isn't
> > >> around anybody going quiet, but the fact of nobody new arriving. Is
> > there
> > >> any evidence of any usage of the release? Anybody hitting any problem?
> > Any
> > >> lack of documentation? Any bugfixes? That's the core of the problem.
> > >>
> > >>
> > >>>- It is very critical at this point to grow the community. Going
> > back
> > >>> to
> > >>>my first point, as long as we are such a small community, efforts
> > like
> > >>>releasing a version will set us back, and the last release is a
> good
> > >>>example for that danger.
> > >>>
> > >>
> > >> Not sure I agree: releases usually pick up the activity, pick up new
> > >> users, as new features now make the project more attractive. I don't
> > think
> > >> I've ever seen an argument where "releasing a version sets us back".
> > >> Especially the *first* one.
> > >>
> > >>- Grow the community. BTW I think this is one reason w

Re: Project status

[Davor Bonaci]

Any comments? Anyone?

Option 1: start a vote to retire the podling and move the project into your
own repository.
Option 2: keep things as-is for a few months and re-assess.

I'd say Option 2 requires a minimum of 3 people explicitly saying that they
want to continue trying and contributing.

On Sun, Sep 23, 2018 at 8:13 PM Davor Bonaci  wrote:

> Thanks Yaniv for your comments.
>
>- After the release of 0.2.0 the community became very quiet. I think
>>that at this point in the life of the project it is natural, as we all
>>doing this in our free time and the release was a major effort that
>> all of
>>us (after talking to members in the community) had to compensate for
>> in our
>>day jobs and families.
>>With that said, we shouldn't have gone so quiet. I think we can all
>>agree this is not acceptable for so long (if at all).
>>
>
> Not sure I agree: it is not natural for projects in the Incubator to be
> quiet. It does happen to projects that are getting obsolete/irrelevant,
> often after many years as TLPs. The release usually *increases* activity
> around the project as new users come, ask questions, start contributing,
> etc.
>
> On the other hand, totally fine for people to go quiet. The problem isn't
> around anybody going quiet, but the fact of nobody new arriving. Is there
> any evidence of any usage of the release? Anybody hitting any problem? Any
> lack of documentation? Any bugfixes? That's the core of the problem.
>
>
>>- It is very critical at this point to grow the community. Going back
>> to
>>my first point, as long as we are such a small community, efforts like
>>releasing a version will set us back, and the last release is a good
>>example for that danger.
>>
>
> Not sure I agree: releases usually pick up the activity, pick up new
> users, as new features now make the project more attractive. I don't think
> I've ever seen an argument where "releasing a version sets us back".
> Especially the *first* one.
>
>- Grow the community. BTW I think this is one reason we should consider
>>staying an Apache project, I think that with the release, we should
>> also
>>shift some focus to growing the community. This is an issue I see other
>>projects struggling with, this includes TLPs such as Apache Arrow (in a
>>recent thread on their dev list) and I don't think there is one answer
>> on
>>how to do it, and I spent some time on other lists to see if they have
>>solutions. I think we can do many things to fix this, and it's more of
>> a
>>trial and error process for most projects. Things we can (and should
>> start
>>doing immediately) includes doing more public presentations (and I
>> have to
>>give a shout-out @Nadav Har Tzvi  that
>> presented
>>in two conferences recently), write blog posts, and we should all
>> invest
>>time in doing so. But one thing we also need to do is actively looking
>> for
>>more contributors. If anyone here has someone they think is a good fit,
>>let's try to get them onboard.
>>
>
> Outreach (blogs, talks, etc.) can help, but they help you *scale*. I think
> the project hasn't demonstrated early user fit -- and trying to scale
> before establishing that often doesn't yield results. For example, if you
> were to throw Amaterasu in front of 1000 people, how many would join the
> community? If only a few, it is probably a bad idea to do it. (I worry it
> is less than a few.)
>
> The problem is likely with the user fit, and can be solved only by user
> development -- most of which often happens before scaling, before building
> the community, and before joining the Incubator.
>
> It is really, really, really hard to build the community before early user
> fit.
>
> I think that the next few months are more about staying in the incubating
>> or not, it is do-or-die for Amaterasu. We need to fix the situation so I
>> wouldn't rush in this situation to consider retiring quite yet.
>>
>
> I'm totally fine with leaving things as-is for a few more months. But, I
> don't think it is realistic to expect changes to the degree necessary to
> graduate. As a result, I think you can use *your time* better.
>
> * * *
>
> I'm really sorry to be the messenger of bad news. I don't want to paint
> Amaterasu (or your work) in any bad way. I do want you and the project to
> be most successful as possible.
>
> Please note that I don't gain anything by driving this conversation. In
> fact, I lose a lot. Time is a precious resource of everyone -- and I'd like
> to make sure that the time *you* have for the project is spent in a way
> that is likely to yield results, not trying to achieve various ASF goals
> that may not achievable. (If this is not obvious now, I trust that over
> time direct feedback and tough conversations will be appreciated, instead
> of letting you waste time for something unrealistic -- which is what most
> people in my shoes would do.)
>

Re: Project status

[Davor Bonaci]

Thanks Yaniv for your comments.

   - After the release of 0.2.0 the community became very quiet. I think
>that at this point in the life of the project it is natural, as we all
>doing this in our free time and the release was a major effort that all
> of
>us (after talking to members in the community) had to compensate for in
> our
>day jobs and families.
>With that said, we shouldn't have gone so quiet. I think we can all
>agree this is not acceptable for so long (if at all).
>

Not sure I agree: it is not natural for projects in the Incubator to be
quiet. It does happen to projects that are getting obsolete/irrelevant,
often after many years as TLPs. The release usually *increases* activity
around the project as new users come, ask questions, start contributing,
etc.

On the other hand, totally fine for people to go quiet. The problem isn't
around anybody going quiet, but the fact of nobody new arriving. Is there
any evidence of any usage of the release? Anybody hitting any problem? Any
lack of documentation? Any bugfixes? That's the core of the problem.


>- It is very critical at this point to grow the community. Going back to
>my first point, as long as we are such a small community, efforts like
>releasing a version will set us back, and the last release is a good
>example for that danger.
>

Not sure I agree: releases usually pick up the activity, pick up new users,
as new features now make the project more attractive. I don't think I've
ever seen an argument where "releasing a version sets us back". Especially
the *first* one.

   - Grow the community. BTW I think this is one reason we should consider
>staying an Apache project, I think that with the release, we should also
>shift some focus to growing the community. This is an issue I see other
>projects struggling with, this includes TLPs such as Apache Arrow (in a
>recent thread on their dev list) and I don't think there is one answer
> on
>how to do it, and I spent some time on other lists to see if they have
>solutions. I think we can do many things to fix this, and it's more of a
>trial and error process for most projects. Things we can (and should
> start
>doing immediately) includes doing more public presentations (and I have
> to
>give a shout-out @Nadav Har Tzvi  that
> presented
>in two conferences recently), write blog posts, and we should all invest
>time in doing so. But one thing we also need to do is actively looking
> for
>more contributors. If anyone here has someone they think is a good fit,
>let's try to get them onboard.
>

Outreach (blogs, talks, etc.) can help, but they help you *scale*. I think
the project hasn't demonstrated early user fit -- and trying to scale
before establishing that often doesn't yield results. For example, if you
were to throw Amaterasu in front of 1000 people, how many would join the
community? If only a few, it is probably a bad idea to do it. (I worry it
is less than a few.)

The problem is likely with the user fit, and can be solved only by user
development -- most of which often happens before scaling, before building
the community, and before joining the Incubator.

It is really, really, really hard to build the community before early user
fit.

I think that the next few months are more about staying in the incubating
> or not, it is do-or-die for Amaterasu. We need to fix the situation so I
> wouldn't rush in this situation to consider retiring quite yet.
>

I'm totally fine with leaving things as-is for a few more months. But, I
don't think it is realistic to expect changes to the degree necessary to
graduate. As a result, I think you can use *your time* better.

* * *

I'm really sorry to be the messenger of bad news. I don't want to paint
Amaterasu (or your work) in any bad way. I do want you and the project to
be most successful as possible.

Please note that I don't gain anything by driving this conversation. In
fact, I lose a lot. Time is a precious resource of everyone -- and I'd like
to make sure that the time *you* have for the project is spent in a way
that is likely to yield results, not trying to achieve various ASF goals
that may not achievable. (If this is not obvious now, I trust that over
time direct feedback and tough conversations will be appreciated, instead
of letting you waste time for something unrealistic -- which is what most
people in my shoes would do.)

Project status

[Davor Bonaci]

I continue to be concerned about the project's ability to graduate from the
Incubator.

Right now, the last commit was ~1.5 months ago. Since July 1, there was
just a single contributor to the project. There were no substantive
discussions on the dev@ mailing list since June. I can confidently say that
the chances of ever graduating are very slim.

In my mind, the issue is "fit" between the project and the Foundation. The
Foundation imposes on a lot of requirements on the project. Those make
sense for some category of projects. I believe the tradeoffs here are not
in favor of Amaterasu -- you need to give a lot, and receive a little --
ultimately decreasing the chance of Amaterasu being successful.

Nobody should perceive that as a failure -- simply an issue of a fit. The
project is good, provides value, and has some interest around it. This is
not pass/fail test for the project.

My opinion is that the best path forward is to the retire Amaterasu
podling, and enable the project to thrive as a standalone project, without
any of the encumbrances imposed on the project right now.

Thoughts?

(I know this is something that nobody wants. Again, it is not a failure of
any kind -- just an issue of fit.)

Davor

Re: [DISCUSS] podling report

[Davor Bonaci]

+1

"have been released" --> "have been built and voted upon"

On Fri, Jul 6, 2018 at 12:51 AM, Yaniv Rodenski  wrote:

> Hi All,
>
> Sorry for doing this late again, but I propose the following report to be
> submitted:
>
> "
> Apache Amaterasu is a framework providing configuration management and
> deployment for Big Data Pipelines.
>
> It provides the following capabilities:
>
> Continuous integration tools to package pipelines and run tests.
> A repository to store those packaged applications: the applications
> repository.
> A repository to store the pipelines, and engine configuration (for
> instance, the location of the Spark master, etc.): per environment - the
> configuration repository.
> A dashboard to monitor the pipelines.
> A DSL and integration hooks allowing third parties to easily integrate.
>
> Amaterasu has been incubating since 2017-09.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Prepare the first release
>   2. Grow up user and contributor communities
>   3. Prepare documentation
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   * Two conference talks have been delivered (PyCon il and SDP)
>   * Initial documentation has been created, targeted for Amaterasu's next
> release
>
> How has the project developed since the last report?
>
>   * since the last report 4 release candidates have been released, at the
> time of this report the last RC is being voted on in the general@incubator
> mailing list
>   * Two additional contributors started contributing to the code base
>   * One more organization we are aware of have started a POC with Amaterasu
>
> Date of the last release:
>
>   N/A
>
> When were the last committers or PMC members elected?
>
>   N/A
> "
>
> If there are no objections I will update the wiki.
>
> Cheers,
> Yaniv
>

Re: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 (rc4)

[Davor Bonaci]

+1 (binding)

Checked standard things; all clear improvements.

On Tue, Jun 26, 2018 at 1:37 PM, Eyal Ben-Ivri 
wrote:

> +1
>
>
> On 24. June 2018 at 12:00:12, Arun Manivannan (a...@arunma.com) wrote:
>
> Clean built. Testcases run fine. Ran it on HDP and HDP 2.6.5.0-292 with
> minor change on the leader AM. Works perfect.
>
> +1
>
> Cheers,
> Arun
>
> On Sun, Jun 24, 2018 at 5:10 PM guy peleg  wrote:
>
> > Downloaded the source code and the artifact, everything looks good on my
> > side.
> > +1
> >
> > Guy
> >
> > On Sun, Jun 24, 2018, 19:09 Kirupa Devarajan 
> > wrote:
> >
> > > gradle build and assemble successful on the branch
> > > version-0.2.0-incubating-rc4
> > > <
> > >
> > https://github.com/apache/incubator-amaterasu/tree/
> version-0.2.0-incubating-rc4
> > > >
> > > .
> > >
> > > +1
> > >
> > > Regards,
> > > Kirupa
> > >
> > >
> > > On Sun, Jun 24, 2018 at 6:57 PM, Nadav Har Tzvi <
> nadavhart...@gmail.com>
> > > wrote:
> > >
> > > > Tested on standalone Mesos, EMR and HDP.
> > > > Spark-Scala and PySpark both work on each of the environments.
> > > > Thus, I vote +1
> > > >
> > > > Cheers,
> > > > Nadav
> > > >
> > > >
> > > >
> > > > On Sat, 23 Jun 2018 at 15:35, Yaniv Rodenski 
> wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > After cancelling the vote in the general@ list we've fixed the
> > > > following:
> > > > > * Headers added to all non-code files where applicable as remarked
> by
> > > > Davor
> > > > > * Sources now match the released version + no keys are present
> > > > > * The gradle-wrapper.jar was removed and instructions ware added
> to
> > the
> > > > > readme.md file on how to add it.
> > > > > * Missing licenses found by Justin Mclean during the general@
> vote
> > > ware
> > > > > added when applicable.
> > > > >
> > > > > So, hoping for the best, please review and vote on the release
> > > candidate
> > > > #4
> > > > > for the version 0.2.0-incubating, as follows
> > > > >
> > > > > [ ] +1, Approve the release
> > > > > [ ] -1, Do not approve the release (please provide specific
> comments)
> > > > >
> > > > > The complete staging area is available for your review, which
> > includes:
> > > > >
> > > > > * JIRA release notes [1],
> > > > > * the official Apache source release to be deployed to
> > dist.apache.org
> > > > > [2],
> > > > > which is signed with the key with fingerprint [3],
> > > > > * source code tag "version-0.2.0-incubating-rc4" [4],
> > > > > * Java artifacts were built with Gradle 3.1 and OpenJDK/Oracle JDK
> > > > > 1.8.0_151
> > > > >
> > > > > The vote will be open for at least 72 hours. It is adopted by
> > majority
> > > > > approval, with at least 3 PMC affirmative votes.
> > > > >
> > > > > Thanks,
> > > > > Yaniv
> > > > >
> > > > > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> > > > > rojectId=12321521&version=12342793
> > > > > [2]
> > > https://dist.apache.org/repos/dist/dev/incubator/amaterasu/0.2.0rc4/
> > > > > [3] https://dist.apache.org/repos/dist/dev/incubator/amaterasu/
> KEYS
> > > > > [4] https://github.com/apache/incubator-amaterasu/tags
> > > > >
> > > > > Thanks everyone
> > > > > Yaniv
> > > > >
> > > >
> > >
> >
>

Re: Cancelling the vote in the @general mailing list

[Davor Bonaci]

Quick comments; will look into more details later.

Gradle wrapper jar
>

I'm of the opinion that this is fine, but others may disagree. Other
projects do it. It is a standard Gradle approach. I suggest following up
with Justin, and understanding what his concerns may be.


> the existence of PySpark in the resources of the executor/test folder


The redistribution of this file is fine. I thought that Justin found that
the header is missing. If so, just the header should be added, and that's
it.

3. Justin had a strange remark about an MIT licenced file which I think
> refers to codegen.py which is a BSD licensed file, I realize I need to add
> the original license of the project to the licenses folder, however,
> codegen doesn't have one. what can we do in that case?


We cannot distribute components with unknown license. If it is MIT/BSD,
there's a standard approach we use. If it is public domain, there are
typically options as well. I suggest understanding the genesis of software
in question.

Re: Vote at the general@ mailing list

[Davor Bonaci]

Please ping the thread. I'd prefer that the usual suspects also take a peek.

On Sun, Jun 17, 2018 at 9:04 PM, Yaniv Rodenski  wrote:

> Hi Mentors,
>
> Just a quick etiquette question, as we are over 72 hours into the vote and
> only JB has voted, what (and when) would be the best way to request more
> votes?
>
> I understand people are busy, when do we consider a vote to be "forgotten"
> and in need of a reminder?
>
> Cheers,
> --
> Yaniv Rodenski
>
> +61 477 778 405
> ya...@shinto.io
>

Re: [VOTE] Amaterasu release 0.2.0-incubating, release candidate #3

[Davor Bonaci]

>
> Based on what I've seen in other projects, it seems common to release bot
> the binaries (in Amaterasu those are released in the .tar file) as well as
> a source (which are in the -source.tar.gz file)
> The main question is if we do or do not need to release both.
>

Sorry, my mistake. It is perfectly fine to release convenience binaries in
addition to source code. You may want to name them better and refer to both
from the vote email, however ;-)

Re: [VOTE] Amaterasu release 0.2.0-incubating, release candidate #3

[Davor Bonaci]

No problem with .tar.gz. But, you don't need .tar then.

On Fri, Jun 1, 2018 at 12:04 AM, Yaniv Rodenski  wrote:

> One thing to clarify, the tar.gz is the source code as I've seen this is
> released in other projects. if that is not needed I'm happy to drop it from
> future releases.
>
> On Fri, Jun 1, 2018 at 5:01 PM, Yaniv Rodenski  wrote:
>
> > Thanks Davor,
> >
> > We will fix those for the next release.
> >
> > Cheers,
> > Yaniv
> >
> > On Fri, Jun 1, 2018 at 7:23 AM, Davor Bonaci  wrote:
> >
> >> Great improvement!
> >>
> >> license/notice/disclaimer: ok
> >> headers: ~fine (missing in some non-code files, it would be great to add
> >> those -- non-blocking)
> >> binaries: there's a gradle binary, but that may be ruled as acceptable
> >> (non-blocking from me)
> >>
> >> Not sure why we need both .tar and .tar.gz. I'd get rid of one of them.
> >> Also, shipping private keys in the distribution looks weird as well.
> >>
> >> For the first release, this is good. So, +1 to send onwards for an
> >> Incubator review, and polish a few of these things for a subsequent
> >> release.
> >>
> >> On Wed, May 30, 2018 at 7:12 PM, Yaniv Rodenski 
> wrote:
> >>
> >> > Hi All,
> >> >
> >> > Just a kind reminder for our mentors, we need your vote on this one :)
> >> >
> >> > Cheers,
> >> > Yaniv
> >> >
> >> > On Wed, May 30, 2018 at 3:25 PM, Arun Manivannan 
> >> wrote:
> >> >
> >> > > Thanks a lot, Nadav. Will get home and spend some more time on
> this. I
> >> > was
> >> > > in a rush and did this poor workaround. My VM is just 8 GB.
> >> > >
> >> > > Cheers
> >> > > Arun
> >> > >
> >> > > On Wed, May 30, 2018, 12:27 Nadav Har Tzvi 
> >> > wrote:
> >> > >
> >> > > > Yaniv and I just tested it. It worked flawlessly on my end (HDP
> >> docker
> >> > on
> >> > > > AWS). Both Spark-Scala and PySpark.
> >> > > > It worked on Yaniv's HDP cluster as well.
> >> > > > Worth noting:
> >> > > > 1. HDP 2.6.4
> >> > > > 2. Cluster has total of 32GB memory available
> >> > > > 3. Each container is allocated 1G memory.
> >> > > > 4. Amaterasu.properties:
> >> > > >
> >> > > > zk=sandbox-hdp.hortonworks.com
> >> > > > version=0.2.0-incubating-rc3
> >> > > > master=192.168.33.11
> >> > > > user=root
> >> > > > mode=yarn
> >> > > > webserver.port=8000
> >> > > > webserver.root=dist
> >> > > > spark.version=2.6.4.0-91
> >> > > > yarn.queue=default
> >> > > > yarn.jarspath=hdfs:///apps/amaterasu
> >> > > > spark.home=/usr/hdp/current/spark2-client
> >> > > >
> >> > > > #spark.home=/opt/cloudera/parcels/SPARK2-2.1.0.
> >> > cloudera2-1.cdh5.7.0.p0.
> >> > > 171658/lib/spark2
> >> > > > yarn.hadoop.home.dir=/etc/hadoop
> >> > > > spark.opts.spark.yarn.am.extraJavaOptions="-Dhdp.version=2.
> >> 6.4.0-91"
> >> > > > spark.opts.spark.driver.extraJavaOptions="-Dhdp.
> version=2.6.4.0-91"
> >> > > >
> >> > > >
> >> > > > Arun, please share:
> >> > > > 1. YARN memory configurations
> >> > > > 2. amaterasu.properties content
> >> > > > 3. HDP version.
> >> > > >
> >> > > > Cheers,
> >> > > > Nadav
> >> > > >
> >> > > >
> >> > > > On 30 May 2018 at 07:11, Arun Manivannan  wrote:
> >> > > >
> >> > > > > The pmem disabling is just temporary. I'll do a detailed
> analysis
> >> and
> >> > > get
> >> > > > > back with a proper solution.
> >> > > > >
> >> > > > > Any hints on this front is highly appreciated.
> >> > > > >
> >> > > > > Cheers
> >> > > > > Arun
> >> > > > >
> >> > > > > On Wed, May 30, 2018, 01:10 Nadav Har Tzvi &

Re: [VOTE] Amaterasu release 0.2.0-incubating, release candidate #3

[Davor Bonaci]

Great improvement!

license/notice/disclaimer: ok
headers: ~fine (missing in some non-code files, it would be great to add
those -- non-blocking)
binaries: there's a gradle binary, but that may be ruled as acceptable
(non-blocking from me)

Not sure why we need both .tar and .tar.gz. I'd get rid of one of them.
Also, shipping private keys in the distribution looks weird as well.

For the first release, this is good. So, +1 to send onwards for an
Incubator review, and polish a few of these things for a subsequent release.

On Wed, May 30, 2018 at 7:12 PM, Yaniv Rodenski  wrote:

> Hi All,
>
> Just a kind reminder for our mentors, we need your vote on this one :)
>
> Cheers,
> Yaniv
>
> On Wed, May 30, 2018 at 3:25 PM, Arun Manivannan  wrote:
>
> > Thanks a lot, Nadav. Will get home and spend some more time on this. I
> was
> > in a rush and did this poor workaround. My VM is just 8 GB.
> >
> > Cheers
> > Arun
> >
> > On Wed, May 30, 2018, 12:27 Nadav Har Tzvi 
> wrote:
> >
> > > Yaniv and I just tested it. It worked flawlessly on my end (HDP docker
> on
> > > AWS). Both Spark-Scala and PySpark.
> > > It worked on Yaniv's HDP cluster as well.
> > > Worth noting:
> > > 1. HDP 2.6.4
> > > 2. Cluster has total of 32GB memory available
> > > 3. Each container is allocated 1G memory.
> > > 4. Amaterasu.properties:
> > >
> > > zk=sandbox-hdp.hortonworks.com
> > > version=0.2.0-incubating-rc3
> > > master=192.168.33.11
> > > user=root
> > > mode=yarn
> > > webserver.port=8000
> > > webserver.root=dist
> > > spark.version=2.6.4.0-91
> > > yarn.queue=default
> > > yarn.jarspath=hdfs:///apps/amaterasu
> > > spark.home=/usr/hdp/current/spark2-client
> > >
> > > #spark.home=/opt/cloudera/parcels/SPARK2-2.1.0.
> cloudera2-1.cdh5.7.0.p0.
> > 171658/lib/spark2
> > > yarn.hadoop.home.dir=/etc/hadoop
> > > spark.opts.spark.yarn.am.extraJavaOptions="-Dhdp.version=2.6.4.0-91"
> > > spark.opts.spark.driver.extraJavaOptions="-Dhdp.version=2.6.4.0-91"
> > >
> > >
> > > Arun, please share:
> > > 1. YARN memory configurations
> > > 2. amaterasu.properties content
> > > 3. HDP version.
> > >
> > > Cheers,
> > > Nadav
> > >
> > >
> > > On 30 May 2018 at 07:11, Arun Manivannan  wrote:
> > >
> > > > The pmem disabling is just temporary. I'll do a detailed analysis and
> > get
> > > > back with a proper solution.
> > > >
> > > > Any hints on this front is highly appreciated.
> > > >
> > > > Cheers
> > > > Arun
> > > >
> > > > On Wed, May 30, 2018, 01:10 Nadav Har Tzvi 
> > > wrote:
> > > >
> > > > > Yaniv, Eyal, this might be related to the same issue you faced with
> > > HDP.
> > > > > Can you confirm?
> > > > >
> > > > > On Tue, May 29, 2018, 17:58 Arun Manivannan 
> wrote:
> > > > >
> > > > > > +1 from me
> > > > > >
> > > > > > Unit Tests and Build ran fine.
> > > > > >
> > > > > > Tested on HDP (VM) but had trouble allocating containers (didn't
> > have
> > > > > that
> > > > > > before).  Apparently Centos VMs are known to have this problem.
> > > > Disabled
> > > > > > physical memory check  (yarn.nodemanager.pmem-check-enabled) and
> > ran
> > > > jobs
> > > > > > successfully.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, May 29, 2018 at 10:42 PM Kirupa Devarajan <
> > > > > kirupagara...@gmail.com
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Unit tests passing and build was successful on the branch
> > > > > > > "version-0.2.0-incubating-rc3"
> > > > > > >
> > > > > > > +1 from me
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Kirupa
> > > > > > >
> > > > > > >
> > > > > > > On Tue, May 29, 2018 at 3:06 PM, guy peleg  >
> > > > wrote:
> > > > > > >
> > > > > > > > +1 looks good to me
> > > > > > > >
> > > > > > > > On Tue, May 29, 2018, 14:39 Nadav Har Tzvi <
> > > nadavhart...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 approve. Tested multiple times and after a long round of
> > > > fixing
> > > > > > and
> > > > > > > > > testing over and over.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Nadav
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 29 May 2018 at 07:38, Yaniv Rodenski 
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi everyone,
> > > > > > > > > >
> > > > > > > > > > We have fixed the legal issues, as well as a bug found by
> > > > @Nadav
> > > > > > > please
> > > > > > > > > > review and vote on the release candidate #3 for the
> version
> > > > > > > > > > 0.2.0-incubating, as follows
> > > > > > > > > >
> > > > > > > > > > [ ] +1, Approve the release
> > > > > > > > > > [ ] -1, Do not approve the release (please provide
> specific
> > > > > > comments)
> > > > > > > > > >
> > > > > > > > > > The complete staging area is available for your review,
> > which
> > > > > > > includes:
> > > > > > > > > >
> > > > > > > > > > * JIRA release notes [1],
> > > > > > > > > > * the official Apache source release to be deployed to
> > > > > > > dist.apache.org
> > > > > > > > > > [2],
> > > > > > > > > > which

Re: License questions for RC3

[Davor Bonaci]

>
>1. I've had to add the following exclusions from the plugin:
>["**/build/**", '**/.gradle/**', '**/gradle/**', '**/.idea/**',
>'**/.ruby-version/**', '**/repo/**', '**/resources/**', '**/*.iml/**']
>Is that a valid configuration?
>

Usually, "rat" is configured to run on a clean codebase, so (most)
temporary files don't cause false positives.

It is fine to add manual exclusions, but please make sure that any
exclusions (1) aren't part of the release, and (2) are not required for the
project in some environment.

   2. Looking at the built output, we currently have one dependency
>packaged which is the codegen python package which has a BSD license. Is
>that an issue?


Not an issue. Please follow LICENSE/NOTICE requirements. Typically, the
license text including the copyright statement needs to be added to the
LICENSE file.

if so, an alternative approach would be to install it via
>pip during Amaterasu's setup stage, is that a valid solution?
>

On the policy standpoint, there's no difference between the approaches. In
both cases, the dependencies must satisfy the same requirements. Between
the two, please pick the approach that you prefer. (There's a likely small
difference in crafting the LICENSE/NOTICE files between these two cases.)

Re: [VOTE] Amaterasu release 0.2.0-incubating, release candidate #2

[Davor Bonaci]

>
> BTW, did you get to check if the signatures are valid?


I did not. I also didn't check POMs, dependencies compliance, no binaries,
and similar things.

Just asking because it's my first time doing this.


No worries. This will take a number of tries -- completely normal.

Re: [VOTE] Amaterasu release 0.2.0-incubating, release candidate #2

[Davor Bonaci]

-1 (binding)

Good start, but please go through the Apache release policy. The legal
stuff is blocking for now.

legal:
* I failed to find LICENSE, NOTICE and DISCLAIMER files.

KEYS:
* Should support multiple release managers. See example how to format it
[1].

dist:
* No need for *.tar and *.tar.gz. Just use the latter one, but name
"apache-amaterasu-0.2.0-incubating.tar.gz".

Davor

[1] https://dist.apache.org/repos/dist/dev/beam/KEYS

On Mon, Apr 30, 2018 at 2:39 PM, Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> I'm just back from vacation. I will review the release.
>
> Regards
> JB
>
> On 04/29/2018 12:44 PM, Yaniv Rodenski wrote:
> > Hi Mentors,
> >
> > In order to progress with the vote, can any of you check the release
> > signatures? it is the first time I release s signed artifact in Apache
> and
> > would like to make sure I'm doing it right.
> > Also, I believe we need all three mentors to vote in order to promote the
> > vote to the general@ mailing list, are you OK to vote at this time?
> >
> > Thanks,
> > Yaniv
> >
> > On Thu, Apr 26, 2018 at 10:26 AM, Nadav Har Tzvi 
> wrote:
> >
> >> +1 looks good.
> >>
> >> On Thu, Apr 26, 2018, 01:50 guy peleg  wrote:
> >>
> >>> +1 everything indicates that the previous issues were resolved , in
> >>> addition we need short feedback loop from users.
> >>>
> >>> On Thu, Apr 26, 2018, 08:48 Kirupa Devarajan 
> >>> wrote:
> >>>
>  +1 - Test and Build successful for release candidate #2
> 
>  On Wed, 25 Apr 2018, 13:32 Yaniv Rodenski,  wrote:
> 
> > Hi everyone,
> >
> > After fixing issues with the build found in RC1 please review and
> >> vote
> >>> on
> > the release candidate #2 for the version 0.2.0-incubating, as
> >> follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which
> >> includes:
> >
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> >> dist.apache.org
> > [2],
> > which is signed with the key with fingerprint [3],
> > * source code tag "version-0.2.0-incubating-rc2" [4],
> > * Java artifacts were built with Gradle 3.1 and OpenJDK/Oracle JDK
> > 1.8.0_151
> >
> > The vote will be open for at least 72 hours. It is adopted by
> >> majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> >
> > Yaniv Rodenski
> >
> > [1]
> >
> >
> 
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12321521&version=12342793
> >
> > [2]
> >>> https://dist.apache.org/repos/dist/dev/incubator/amaterasu/0.2.0rc2/
> > [3] https://dist.apache.org/repos/dist/dev/incubator/amaterasu/KEYS
> > [4] https://github.com/apache/incubator-amaterasu/tags
> >
> > --
> > Yaniv Rodenski
> >
> > +61 477 778 405
> > ya...@shinto.io
> >
> 
> >>>
> >>
> >
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [DISCUSS] podling report

[Davor Bonaci]

Signed off.

On Mon, Apr 2, 2018 at 3:51 PM, Kirupa Devarajan 
wrote:

> Good Job Yaniv. Looks good.
>
> Regards,
> Kirupa.
>
> On Tue, 3 Apr 2018, 02:51 Davor Bonaci,  wrote:
>
> > Sounds good to me.
> >
> > (I'd remove the speaker names from the report; not necessary.)
> >
> > On Mon, Apr 2, 2018 at 7:24 AM, Nadav Har Tzvi 
> wrote:
> >
> > > Hey,
> > >
> > > I don't have confirmation for the SDP yet. It might be deferred to the
> > next
> > > SDP (December 2018 instead of June 2018).
> > >
> > > On 2 April 2018 at 13:45, Yaniv Rodenski  wrote:
> > >
> > > > Hi All,
> > > >
> > > > We have two days for submitting this report, and I hope we will have
> > some
> > > > additions but for now, I suggest the following report:
> > > >
> > > > "
> > > > Apache Amaterasu is a framework providing configuration management
> and
> > > > deployment for Big Data Pipelines.
> > > >
> > > > It provides the following capabilities:
> > > >
> > > > Continuous integration tools to package pipelines and run tests.
> > > > A repository to store those packaged applications: the applications
> > > > repository.
> > > > A repository to store the pipelines, and engine configuration (for
> > > > instance, the location of the Spark master, etc.): per environment -
> > the
> > > > configuration repository.
> > > > A dashboard to monitor the pipelines.
> > > > A DSL and integration hooks allowing third parties to easily
> integrate.
> > > >
> > > > Amaterasu has been incubating since 2017-09.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > >   1. Prepare the first release
> > > >   2. Grow up user and contributor communities
> > > >   3. Prepare documentation
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > > aware of?
> > > >
> > > >   None
> > > >
> > > > How has the community developed since the last report?
> > > >
> > > >   * Two conference talks are scheduled in the near future, Voxxed
> Days
> > > > Melbourne (Yaniv Rodenski) and SDP in Tel-Aviv (Nadav Har-Tzvi)
> > > >
> > > > How has the project developed since the last report?
> > > >
> > > >   * since the last report 12 PRs were opened and 11 are merged
> > > >   * One additional contributor started contributing to the code base
> > > >   * One organization we are aware of have started a POC with
> Amaterasu
> > > >   * We are in the process of automating the release process as
> > > > preparation for the first release in the incubator.
> > > >
> > > > Date of last release:
> > > >
> > > >   N/A
> > > >
> > > > When were the last committers or PMC members elected?
> > > >
> > > >   N/A
> > > > "
> > > >
> > > > If there are no objections I will update the wiki.
> > > >
> > > > Cheers,
> > > > --
> > > > Yaniv Rodenski
> > > >
> > > > +61 477 778 405
> > > > ya...@shinto.io
> > > >
> > >
> > >
> > >
> > > --
> > > =
> > > Nadav Har Tzvi
> > > Committer@Amaterasu
> > >
> >
>

Re: [DISCUSS] podling report

[Davor Bonaci]

Sounds good to me.

(I'd remove the speaker names from the report; not necessary.)

On Mon, Apr 2, 2018 at 7:24 AM, Nadav Har Tzvi  wrote:

> Hey,
>
> I don't have confirmation for the SDP yet. It might be deferred to the next
> SDP (December 2018 instead of June 2018).
>
> On 2 April 2018 at 13:45, Yaniv Rodenski  wrote:
>
> > Hi All,
> >
> > We have two days for submitting this report, and I hope we will have some
> > additions but for now, I suggest the following report:
> >
> > "
> > Apache Amaterasu is a framework providing configuration management and
> > deployment for Big Data Pipelines.
> >
> > It provides the following capabilities:
> >
> > Continuous integration tools to package pipelines and run tests.
> > A repository to store those packaged applications: the applications
> > repository.
> > A repository to store the pipelines, and engine configuration (for
> > instance, the location of the Spark master, etc.): per environment - the
> > configuration repository.
> > A dashboard to monitor the pipelines.
> > A DSL and integration hooks allowing third parties to easily integrate.
> >
> > Amaterasu has been incubating since 2017-09.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Prepare the first release
> >   2. Grow up user and contributor communities
> >   3. Prepare documentation
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >
> >   * Two conference talks are scheduled in the near future, Voxxed Days
> > Melbourne (Yaniv Rodenski) and SDP in Tel-Aviv (Nadav Har-Tzvi)
> >
> > How has the project developed since the last report?
> >
> >   * since the last report 12 PRs were opened and 11 are merged
> >   * One additional contributor started contributing to the code base
> >   * One organization we are aware of have started a POC with Amaterasu
> >   * We are in the process of automating the release process as
> > preparation for the first release in the incubator.
> >
> > Date of last release:
> >
> >   N/A
> >
> > When were the last committers or PMC members elected?
> >
> >   N/A
> > "
> >
> > If there are no objections I will update the wiki.
> >
> > Cheers,
> > --
> > Yaniv Rodenski
> >
> > +61 477 778 405
> > ya...@shinto.io
> >
>
>
>
> --
> =
> Nadav Har Tzvi
> Committer@Amaterasu
>

Re: Project status

[Davor Bonaci]

To close the loop on this...

Without going too deep... just two individuals responding on this thread in
10 days is way too little, given 5 PPMC members and 6 months in incubation.

One thing worth clarifying -- to succeed as an Apache project, yes, a lot
of change is needed. However, I'm *not* saying that there's anything wrong
with the project. Just I'm not sure that the project and the foundation are
the right fit at this moment. Nothing wrong with that -- there are many,
many ways to succeed as a project.

I continue to be enthusiastic about this space and continue to be happy to
help, as appropriate. That said, I'll revive this thread in 1-2 months to
check on the progress. If there's no evidence of progress, it may be best
to rethink the path forward then.

On Thu, Mar 29, 2018 at 12:42 AM, Eyal Ben-Ivri 
wrote:

> Hi to all,
>
> Sorry for not replying sooner, but I have been following the thread
> closely.
>
> It is quite obvious we need to find more people that will be active in the
> Amaterasu project.
> Yaniv and myself are often communicating through private channels (and I
> believe other developers are doing the same), and as an improvement, we
> need to make Amaterasu related discussions through this mailing list.
> A lot of the features and milestones discussions (some of them are
> mentioned here like the Travis build) should be discussed here, and that is
> something all of the active developers of the project should start to do,
> in my opinion.
>
> Besides that, i agree with all the points raised here, and do think that
> the main “beyond-the-code” goal should be growing the community around
> Amaterasu.
>
> Thank you,
> Eyal
>
>
>
> On 27. March 2018 at 07:12:04, Davor Bonaci (da...@apache.org) wrote:
>
> Anybody else?
>
> On Tue, Mar 20, 2018 at 5:06 PM, Yaniv Rodenski  wrote:
>
> > Thanks Davor,
> >
> > Points taken, we will learn and improve on those.
> >
> > Just one clearification, I was not blaming the mentor I myself was more
> > focused on working with Guy on automating the build than following up.
> > Rereading my own response I can see that was unclear.
> >
> >
> > On Wed, 21 Mar 2018 at 11:02 am, Davor Bonaci  wrote:
> >
> > > Thanks for a great response. Some comments inline.
> > >
> > > * In the last month we have been working on automating the release
> > process
> > > > via Travis, we are still trying to enable Travis build for the
> > Amaterasu
> > > > repo, which is taking ridiculously long. We need one of the mentors
> to
> > > just
> > > > enable it via their account (I've already talked a couple of times to
> > one
> > > > of the mentors about it).
> > > >
> > >
> > > Searching for 'travis' in the mailing list archives doesn't yield any
> > > discussion threads.
> > >
> > > Mentors don't have permission to do this themselves. Infra JIRA is the
> > way
> > > to do it, but I couldn't find such JIRA ticket filed.
> > >
> > > Emailing one mentor directly (or any other community member) isn't a
> way
> > to
> > > build the community. Things need to be discussed in public whenever
> > > possible.
> > >
> > > Given the above, blaming a mentor (whomever you may be referring to)
> > > doesn't make sense.
> > >
> > > * We are ready to release version 0.2.0-incubating, the reason it took
> > us a
> > > > month to initiate the process is the above automated build, which I
> > > > suggested in prior discussion and had no rejections. We will complete
> > > this
> > > > once build is enabled.
> > > >
> > >
> > > The release itself is a great milestone, but not the purpose to itself.
> > >
> > >
> > > > * as for community growth, we are working with two organizations on
> > > running
> > > > POCs (which will hopefully grow the user base) one of them is due to
> > > start
> > > > very soon. I don't want to name them (first of all it's too early,
> and
> > > also
> > > > it is for them to decide if they want to share) but a representative
> > from
> > > > at least one of those organisations is on the list and is welcomed to
> > > share
> > > > :)
> > > >
> > >
> > > Great!
> > >
> > >
> > > > * This year I've seen contributions from 4 contributors (not much
> more
> > > than
> > > > 3, I know) but one of them is new (Guy Peleg) and AFAIK additional
> > > > longer-term work is done by one more contributor on his local fork
> > (Nadav
> > > > Har-Tzvi)
> > > >
> > >
> > > I think this is the crux of the problem. Why is longer-term work going
> on
> > > in a local fork?
> > >
> > >
> > > > * We should be presenting more, and growing the community more which
> is
> > > > hard to do starting out as a tiny community. Any advice given there
> > would
> > > > be appreciated.
> > > >
> > >
> > > The first thing has to be do the basics well: on-list communication,
> open
> > > discussions, no side channels, etc.
> > >
> > --
> > Yaniv Rodenski
> >
> > +61 477 778 405
> > ya...@shinto.io
> >
>

Re: Project status

[Davor Bonaci]

Anybody else?

On Tue, Mar 20, 2018 at 5:06 PM, Yaniv Rodenski  wrote:

> Thanks Davor,
>
> Points taken, we will learn and improve on those.
>
> Just one clearification, I was not blaming the mentor I myself was more
> focused on working with Guy on automating the build than following up.
> Rereading my own response I can see that was unclear.
>
>
> On Wed, 21 Mar 2018 at 11:02 am, Davor Bonaci  wrote:
>
> > Thanks for a great response. Some comments inline.
> >
> > * In the last month we have been working on automating the release
> process
> > > via Travis, we are still trying to enable Travis build for the
> Amaterasu
> > > repo, which is taking ridiculously long. We need one of the mentors to
> > just
> > > enable it via their account (I've already talked a couple of times to
> one
> > > of the mentors about it).
> > >
> >
> > Searching for 'travis' in the mailing list archives doesn't yield any
> > discussion threads.
> >
> > Mentors don't have permission to do this themselves. Infra JIRA is the
> way
> > to do it, but I couldn't find such JIRA ticket filed.
> >
> > Emailing one mentor directly (or any other community member) isn't a way
> to
> > build the community. Things need to be discussed in public whenever
> > possible.
> >
> > Given the above, blaming a mentor (whomever you may be referring to)
> > doesn't make sense.
> >
> > * We are ready to release version 0.2.0-incubating, the reason it took
> us a
> > > month to initiate the process is the above automated build, which I
> > > suggested in prior discussion and had no rejections. We will complete
> > this
> > > once build is enabled.
> > >
> >
> > The release itself is a great milestone, but not the purpose to itself.
> >
> >
> > > * as for community growth, we are working with two organizations on
> > running
> > > POCs (which will hopefully grow the user base) one of them is due to
> > start
> > > very soon. I don't want to name them (first of all it's too early, and
> > also
> > > it is for them to decide if they want to share) but a representative
> from
> > > at least one of those organisations is on the list and is welcomed to
> > share
> > > :)
> > >
> >
> > Great!
> >
> >
> > > * This year I've seen contributions from 4 contributors (not much more
> > than
> > > 3, I know) but one of them is new (Guy Peleg) and AFAIK additional
> > > longer-term work is done by one more contributor on his local fork
> (Nadav
> > > Har-Tzvi)
> > >
> >
> > I think this is the crux of the problem. Why is longer-term work going on
> > in a local fork?
> >
> >
> > > * We should be presenting more, and growing the community more which is
> > > hard to do starting out as a tiny community. Any advice given there
> would
> > > be appreciated.
> > >
> >
> > The first thing has to be do the basics well: on-list communication, open
> > discussions, no side channels, etc.
> >
> --
> Yaniv Rodenski
>
> +61 477 778 405
> ya...@shinto.io
>

Re: Project status

[Davor Bonaci]

Thanks for a great response. Some comments inline.

* In the last month we have been working on automating the release process
> via Travis, we are still trying to enable Travis build for the Amaterasu
> repo, which is taking ridiculously long. We need one of the mentors to just
> enable it via their account (I've already talked a couple of times to one
> of the mentors about it).
>

Searching for 'travis' in the mailing list archives doesn't yield any
discussion threads.

Mentors don't have permission to do this themselves. Infra JIRA is the way
to do it, but I couldn't find such JIRA ticket filed.

Emailing one mentor directly (or any other community member) isn't a way to
build the community. Things need to be discussed in public whenever
possible.

Given the above, blaming a mentor (whomever you may be referring to)
doesn't make sense.

* We are ready to release version 0.2.0-incubating, the reason it took us a
> month to initiate the process is the above automated build, which I
> suggested in prior discussion and had no rejections. We will complete this
> once build is enabled.
>

The release itself is a great milestone, but not the purpose to itself.


> * as for community growth, we are working with two organizations on running
> POCs (which will hopefully grow the user base) one of them is due to start
> very soon. I don't want to name them (first of all it's too early, and also
> it is for them to decide if they want to share) but a representative from
> at least one of those organisations is on the list and is welcomed to share
> :)
>

Great!


> * This year I've seen contributions from 4 contributors (not much more than
> 3, I know) but one of them is new (Guy Peleg) and AFAIK additional
> longer-term work is done by one more contributor on his local fork (Nadav
> Har-Tzvi)
>

I think this is the crux of the problem. Why is longer-term work going on
in a local fork?


> * We should be presenting more, and growing the community more which is
> hard to do starting out as a tiny community. Any advice given there would
> be appreciated.
>

The first thing has to be do the basics well: on-list communication, open
discussions, no side channels, etc.

Project status

[Davor Bonaci]

Hi everyone --
I'd like to start a thread to discuss the project status and the progress
made over the last 6 months.

Very superficially, here are some ballpark, non-scientific statistics:

* 1 (non auto-generated) email thread on dev@ per month. The last (only?)
non-report discussion was on January 1, nearly 3 months ago.
* 13 lifetime pull requests
* 18 lifetime JIRA issues
* 3 contributors this year
* No evidence of community growth
* Little (visible) progress on the first release

I'd say we are not on the right path towards a successful open source
project, and graduation from Incubator seems hard right now.

I know this may be difficult, but I think it is better to talk about these
things openly and investigate what can be done and/or whether the project
would be better served as a standalone project in GitHub.

Thoughts?

Davor

Re: [DISCUSS] release procedure

[Davor Bonaci]

>
>2. As far as I can figure out, after voting on the incubator dev@ list
>we need to initiate a vote on the incubator general@ list, I have left
>an empty section for that, *can any of the mentors help fill that out*?
>

Vote first here on dev@amaterasu, then general@incubator.


>3. Additional question for our mentors, I have stated that the release
>requires the approval of 3 IPMC members, is that correct?
>

3 PPMC should approve before presenting to Incubator. 3 IPMC members then
to release.

Re: [DISCUSS] Monthly report and getting ready to release 0.2.0 incubating

[Davor Bonaci]

>
> Mentors - What are our next steps to release the version once development
> is done?
>

I generally advise to develop a project release policy / procedure along
with the first release and publish it.

See example [1]. You have some flexibility in figuring out what works well
for the project, however, you have to follow normative policies [2], [3].

As for the monthly report, I suggest the following
>

I think there's no need to report this time around. Normally, projects
report monthly for the first 3 months, then quarterly thereafter, unless
there's a special circumstance.

Davor

[1] https://beam.apache.org/contribute/release-guide/
[2] http://www.apache.org/legal/release-policy.html
[3] http://www.apache.org/dev/release-distribution

Re: Podling report

[Davor Bonaci]

Signed off.

On Wed, Jan 3, 2018 at 9:46 AM, Jean-Baptiste Onofré 
wrote:

> Hi,
>
> I posted and signed off the report on the incubator wiki.
>
> Regards
> JB
>
>
> On 02/01/2018 12:32, Yaniv Rodenski wrote:
>
>> Hi All,
>>
>> Happy 2018 everyone, I'm trying to start the year with an on-time report
>> :)
>>
>> ''
>> Apache Amaterasu is a framework providing continuous deployment for Big
>> Data Pipelines.
>>
>> It provides the following capabilities:
>>
>> Continuous integration tools to package pipelines and run tests.
>> A repository to store those packaged applications: the applications
>> repository.
>> A repository to store the pipelines, and engine configuration (for
>> instance, the location of the Spark master, etc.): per environment - the
>> configuration repository.
>> A dashboard to monitor the pipelines.
>> A DSL and integration hooks allowing third parties to easily integrate.
>>
>> Amaterasu has been incubating since 2017-09.
>>
>> Three most important issues to address in the move towards graduation:
>>
>>1. Prepare the first release
>>2. Grow up user and contributor communities
>>3. Prepare documentation
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>>None
>>
>> How has the community developed since the last report?
>>
>>* A planning meeting for the next version was held online and most
>> tasks
>> have been assigned to contributors
>>   * Tow new contributors have started setting up their dev environment and
>> are getting support from the community
>>
>> How has the project developed since the last report?
>>
>>* YARN support is almost completed and a PR is planned to be issued
>> within the next couple of weeks
>>* The Amaterasu cli tools for version 0.2.0-incubating is awaiting YARN
>> support to be completed for integration
>>* the above tasks are the last two outstanding issues before releasing
>> version 0.2.0 and the community is getting ready for its first release in
>> the incubator
>>
>> Date of last release:
>>
>>N/A
>>
>> When were the last committers or PMC members elected?
>>
>>N/A
>> "
>>
>> If there are no objections I will need help updating the wiki looks like
>> the user I've re-created recently got deleted again :(
>>
>> Cheers,
>>
>>

Re: Podling report

[Davor Bonaci]

+1

On Tue, Jan 2, 2018 at 4:26 AM, Jean-Baptiste Onofré 
wrote:

> Hi Yaniv,
>
> it looks good to me.
>
> I think the next step is really the release preparation as you mentioned.
>
> I will start the global review (especially legal, etc).
>
> Regards
> JB
>
>
> On 01/02/2018 12:32 PM, Yaniv Rodenski wrote:
>
>> Hi All,
>>
>> Happy 2018 everyone, I'm trying to start the year with an on-time report
>> :)
>>
>> ''
>> Apache Amaterasu is a framework providing continuous deployment for Big
>> Data Pipelines.
>>
>> It provides the following capabilities:
>>
>> Continuous integration tools to package pipelines and run tests.
>> A repository to store those packaged applications: the applications
>> repository.
>> A repository to store the pipelines, and engine configuration (for
>> instance, the location of the Spark master, etc.): per environment - the
>> configuration repository.
>> A dashboard to monitor the pipelines.
>> A DSL and integration hooks allowing third parties to easily integrate.
>>
>> Amaterasu has been incubating since 2017-09.
>>
>> Three most important issues to address in the move towards graduation:
>>
>>1. Prepare the first release
>>2. Grow up user and contributor communities
>>3. Prepare documentation
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>>None
>>
>> How has the community developed since the last report?
>>
>>* A planning meeting for the next version was held online and most
>> tasks
>> have been assigned to contributors
>>   * Tow new contributors have started setting up their dev environment and
>> are getting support from the community
>>
>> How has the project developed since the last report?
>>
>>* YARN support is almost completed and a PR is planned to be issued
>> within the next couple of weeks
>>* The Amaterasu cli tools for version 0.2.0-incubating is awaiting YARN
>> support to be completed for integration
>>* the above tasks are the last two outstanding issues before releasing
>> version 0.2.0 and the community is getting ready for its first release in
>> the incubator
>>
>> Date of last release:
>>
>>N/A
>>
>> When were the last committers or PMC members elected?
>>
>>N/A
>> "
>>
>> If there are no objections I will need help updating the wiki looks like
>> the user I've re-created recently got deleted again :(
>>
>> Cheers,
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Next steps?

[Davor Bonaci]

Assuming you've tried multiple times, with multiple email addresses, the
account might be locked by a large number of attempts.

Please email general@incubator mailing list for further steps on this
issue, and hopefully one of the administrators might be able to help.

On Wed, Dec 27, 2017 at 4:52 PM, Yaniv Rodenski  wrote:

> Hi Davor,
>
> I'm getting the login issue from
> https://wiki.apache.org/incubator/FrontPage?action=login which is odd
> because I used to be able to log in using that address, also, the reset
> password doesn't send me the reset token email.
>
> Cheers,
> Yaniv
>
> On Thu, Dec 28, 2017 at 11:47 AM, Davor Bonaci  wrote:
>
> > >
> > > I can't login to the wiki anymore (I'm getting Invalid
> > > username or password).
> > > I've tried resetting my password but that doesn't work either.
> >
> >
> > Account "YanivRodensky" currently has access to the wiki. Remember that
> > Incubator Wiki account is different than the ASF account or ASF Jira
> > account. Please double-check that you are trying to reset the password
> for
> > the right account.
> >
> > >> JIRA:
> > > >>- Non of the PPMC members can’t assign tasks.
> > > >>- We also can’t create Scrum boards.
> > >
> >
> > JB, can you check whether you can add Yaniv to the PMC group in Jira?
> >
> >
> > > >> Travis CI
> > > >>- we would like to add Amaterasu too Travis, when I connect to
> > Travis
> > > >> my
> > > >> GitHub account Amaterasu doesn’t come up.
> > >
> >
> > Please file a new JIRA ticket against Infra, akin to INFRA-12202 [1],
> > cc-ing mentors.
> >
> >
> > > >>- we would like to
> > > >> run integration tests on different Hadoop distros. So we would need
> to
> > > >> setup some clusters in the cloud, is there anyway to get a cloud
> > account
> > > >> from the ASF for that?
> > >
> >
> > I'd say this sounds unlikely in the near term. Testing priority should
> > probably be against Apache Hadoop releases, and we should look to set
> that
> > up through the Infra-supported tooling (Travis, Jenkins, Appveyor,
> > buildbot, etc.). Once we have this in place, we can look into further
> > steps.
> >
> > Davor
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-12202
> >
>
>
>
> --
> Yaniv Rodenski
>

Re: Next steps?

[Davor Bonaci]

>
> I can't login to the wiki anymore (I'm getting Invalid
> username or password).
> I've tried resetting my password but that doesn't work either.


Account "YanivRodensky" currently has access to the wiki. Remember that
Incubator Wiki account is different than the ASF account or ASF Jira
account. Please double-check that you are trying to reset the password for
the right account.

>> JIRA:
> >>- Non of the PPMC members can’t assign tasks.
> >>- We also can’t create Scrum boards.
>

JB, can you check whether you can add Yaniv to the PMC group in Jira?


> >> Travis CI
> >>- we would like to add Amaterasu too Travis, when I connect to Travis
> >> my
> >> GitHub account Amaterasu doesn’t come up.
>

Please file a new JIRA ticket against Infra, akin to INFRA-12202 [1],
cc-ing mentors.


> >>- we would like to
> >> run integration tests on different Hadoop distros. So we would need to
> >> setup some clusters in the cloud, is there anyway to get a cloud account
> >> from the ASF for that?
>

I'd say this sounds unlikely in the near term. Testing priority should
probably be against Apache Hadoop releases, and we should look to set that
up through the Infra-supported tooling (Travis, Jenkins, Appveyor,
buildbot, etc.). Once we have this in place, we can look into further steps.

Davor

[1] https://issues.apache.org/jira/browse/INFRA-12202

Next steps?

[Davor Bonaci]

Happy holidays everyone!

Most volunteers, myself included, often have more time during the holidays,
so I wanted to check if I there are any outstanding issues that might need
mentor attention.

Otherwise, the report is due 1/3. Yaniv, do you have everything you need
there?

Thanks!

Davor

Re: podling report

[Davor Bonaci]

Post the report?

On Mon, Dec 11, 2017 at 11:20 AM, Davor Bonaci  wrote:

>   * A planning meeting for the next version was held online and most tasks
>> have been assigned to contributors
>>
>
> ... held online, with minutes reported back to the list, and most ...
>
> Ok to push to the report.
>

Re: Write access to the incubator-amaterasu @ GitHub

[Davor Bonaci]

I've confirmed that I seem to be able to merge pull requests. I've also
confirmed you (Yaniv) are in the incubator committer list.

I observed that PPMC/committer roster is empty, so I populated it from the
project status page (modulo Karel, who doesn't seem to have an account).
This might solve the problem -- can you try again?

On Mon, Dec 11, 2017 at 4:00 AM, Yaniv Rodenski  wrote:

> Hi Davor,
>
> No, this is not resolved.
> I am linked to the ASF and can see on gitbox that I do have write access,
> but GitHub doesn't agree :(
>
> Should I open a ticket with infra?
>
> On Mon, Dec 11, 2017 at 8:21 PM, Davor Bonaci  wrote:
>
> > Is this resolved?
> >
> > If not, make sure you've linked your GitHub and ASF accounts at
> > https://gitbox.apache.org/.
> >
> > On Sun, Nov 26, 2017 at 12:47 AM, Yaniv Rodenski 
> wrote:
> >
> > > Hi JB,
> > >
> > > I get the following in GitHub:
> > > This branch has no conflicts with the base branchOnly those with write
> > > access
> > > <https://help.github.com/articles/what-are-the-
> > > different-access-permissions> to
> > > this repository can merge pull requests
> > >
> > >
> > > On Sun, Nov 26, 2017 at 4:14 PM, Jean-Baptiste Onofré  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > we can't see image on the mailing list. Can you send the actual
> > message ?
> > > >
> > > > As we are on gitbox, github or github should work.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 11/26/2017 02:40 AM, Yaniv Rodenski wrote:
> > > >
> > > >> Hi Mentors,
> > > >>
> > > >> I'm trying to merge a PR via GitHub and seeing this message:Inline
> > > image 1
> > > >>
> > > >> It looks like that while I do have access to gitbox I have no write
> > > >> access to the GitHub mirror. How can I get it?
> > > >>
> > > >> Cheers,
> > > >> --
> > > >> Yaniv Rodenski
> > > >>
> > > >
> > > > --
> > > > Jean-Baptiste Onofré
> > > > jbono...@apache.org
> > > > http://blog.nanthrax.net
> > > > Talend - http://www.talend.com
> > > >
> > >
> > >
> > >
> > > --
> > > Yaniv Rodenski
> > >
> >
>
>
>
> --
> Yaniv Rodenski
>

Re: podling report

[Davor Bonaci]

>
>   * A planning meeting for the next version was held online and most tasks
> have been assigned to contributors
>

... held online, with minutes reported back to the list, and most ...

Ok to push to the report.

Re: Write access to the incubator-amaterasu @ GitHub

[Davor Bonaci]

Is this resolved?

If not, make sure you've linked your GitHub and ASF accounts at
https://gitbox.apache.org/.

On Sun, Nov 26, 2017 at 12:47 AM, Yaniv Rodenski  wrote:

> Hi JB,
>
> I get the following in GitHub:
> This branch has no conflicts with the base branchOnly those with write
> access
>  different-access-permissions> to
> this repository can merge pull requests
>
>
> On Sun, Nov 26, 2017 at 4:14 PM, Jean-Baptiste Onofré 
> wrote:
>
> > Hi,
> >
> > we can't see image on the mailing list. Can you send the actual message ?
> >
> > As we are on gitbox, github or github should work.
> >
> > Regards
> > JB
> >
> > On 11/26/2017 02:40 AM, Yaniv Rodenski wrote:
> >
> >> Hi Mentors,
> >>
> >> I'm trying to merge a PR via GitHub and seeing this message:Inline
> image 1
> >>
> >> It looks like that while I do have access to gitbox I have no write
> >> access to the GitHub mirror. How can I get it?
> >>
> >> Cheers,
> >> --
> >> Yaniv Rodenski
> >>
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
> Yaniv Rodenski
>

Re: Podling Report Reminder - December 2017

[Davor Bonaci]

Anybody?

The deadline has passed for the report to Incubator. We may or may not be
able to get it into the official report, but it is still worth preparing it.

On Tue, Dec 5, 2017 at 3:38 AM,  wrote:

> 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 December 2017, 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 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.
>
> 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/December2017
>
> 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: Apache Amaterasu planning meeting notes - actions required

[Davor Bonaci]

>
> > > It seems that none of the committers is able to create a Kanban board
> nor
> > > can we assign tasks - Mentors, how do we fix that? do we issue a
> request
> > > for permissions with infra?
>

I've checked, and I don't have access to administer this project's JIRA
(yet), so cannot help you directly.

Please file an Infra ticket to add one of the PPMC members in the project's
JIRA PMC group, and then that person can add remaining PPMC members and
mentors to the list.

> > which brings up a question to the mentors, how do we treat contributions
> > on
> > > Amaterasu from contributors who are non-committers? do we just not
> assign
> > > them on JIRA?
>

Once you have proper JIRA access, add any contributors to the JIRA's
contributor group. At that point, you'll be able to assign issues directly
to non-committers.

Re: Next steps - Planning

[Davor Bonaci]

Happy to see progress!

I'd just ask that the meeting notes are taken during the meeting, and
posted to the dev@ list as soon as practical after the meeting.

On Wed, Nov 22, 2017 at 3:16 AM, Yaniv Rodenski  wrote:

> Hi All,
>
> Just one last reminder, if you can answer the poll we would really like to
> have as many of us at the meeting as possible
>
> Cheers
> Yaniv
>
> On Sat, Nov 18, 2017 at 11:16 AM, Yaniv Rodenski  wrote:
>
> > Hi All,
> >
> > As you can probably see, I've started migrating tasks from our old Trello
> > to JIRA.
> > A few things to note:
> >
> > We currently have two tasks that are pending for version 0.2.0-incubating
> > and started on JIRA - YARN support and the completion of SparkSQL. I
> don't
> > see the need to migrate those, but rather finish 0.2.0-incubating and
> start
> > freshly on 0..3.0-incubating. the only tasks for 0.2.0 that is in JIRA
> are
> > for the CLI and they started after we had the JIRA so we didn't see the
> > point to track them in Trello.
> >
> > We actually have a large backlog and some of those tasks ware created a
> > while back so it makes sense to revisit them before moving forward. I
> > suggest doing an hour planning session next week. Because some of us live
> > literally @ the end of the world (I'm looking @ you @davor) so I've
> created
> > a doodle poll: https://doodle.com/poll/bp8xra64wztf9nz2 to try and
> > schedule it.
> >
> > If you are interested in joining please fill this poll by Monday midday
> so
> > we can get the word out in time.
> >
> > Happy weekend everyone!
> > Yaniv
> >
>
>
>
> --
> Yaniv Rodenski
>

Re: podling report

[Davor Bonaci]

Signed-off.

On Mon, Nov 6, 2017 at 4:54 AM, Jean-Baptiste Onofré 
wrote:

> Hi,
>
> I just updated the wiki with the Amaterasu report.
>
> Regards
> JB
>
> On 11/05/2017 02:54 PM, John D. Ament wrote:
>
>> Ping, do you plan to post this to the wiki?
>>
>> On 2017-10-30 03:11, Yaniv Rodenski  wrote:
>>
>>> Absolutely.
>>> I was thinking about doing a planning meeting on hangouts and get our
>>> backlog in place in JIRA. I know most projects do it via the mailing
>>> list,
>>> but some (I know of Arrow) are having online syncs and I think it's a
>>> good
>>> way to speed things up.
>>>
>>> any thoughts on that?
>>>
>>> On Mon, Oct 30, 2017 at 5:41 PM, Jean-Baptiste Onofré 
>>>
>>> wrote:
>>>
>>> It looks good to me.

 By the way, I propose to really move forward next week.

 Thanks
 Regards
 JB

 On Oct 30, 2017, 07:39, at 07:39, Yaniv Rodenski 
 wrote:

> Hi All,
>
> A bit late I know, but I suggest the following report for this month:
>
> "
> Apache Amaterasu is a framework providing continuous deployment for Big
> Data Pipelines.
>
> It provides the following capabilities:
>
> Continuous integration tools to package pipelines and run tests.
> A repository to store those packaged applications: the applications
> repository.
> A repository to store the pipelines, and engine configuration (for
> instance, the location of the Spark master, etc.): per environment -
> the
> configuration repository.
> A dashboard to monitor the pipelines.
> A DSL and integration hooks allowing third parties to easily integrate.
>
> Amaterasu has been incubating since 2017-09.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Prepare the first release
>   2. Grow up user and contributor communities
>   3. Prepare documentation
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   * Talks have been given in different events to promote and give
> visibility to Amaterasu
>
> How has the project developed since the last report?
>
>   * Code based was moved to the ASFs git box
>   * One new pull request was issued
>
> Date of last release:
>
>   N/A
>
> When were the last committers or PMC members elected?
>
>   N/A
> "
>
> If there are no objections I will update the wiki.
>
> Cheers,
> --
> Yaniv Rodenski
>


>>>
>>>
>>> --
>>> Yaniv Rodenski
>>>
>>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Moving forward

[Davor Bonaci]

Many options -- you can simply compare two repositories, and issue a pull
request in the GitHub UI.

Alternatively, you can create a fork, clone it locally, set up multiple
remotes (to both old and new repositories), rebase and push.

On Wed, Oct 25, 2017 at 1:17 AM, Yaniv Rodenski  wrote:

> Hi Davor,
>
> looks like something worth our while.
> One question though, how do we issue a PR from a non-forked repo?
>
> Cheers,
> Yaniv
>
> On Tue, Oct 24, 2017 at 6:47 PM, Davor Bonaci  wrote:
>
> > (You are also welcome to retain any source history that the original
> > repository has -- feel free to push a pull request containing all
> commits.
> > See Beam's pull request #1 as an example.)
> >
> > On Sun, Oct 22, 2017 at 5:29 PM, Yaniv Rodenski  wrote:
> >
> > > Thanks Olivier!
> > > I prefer doing things myself, I’ll push it today.
> > >
> > > On Mon, 23 Oct 2017 at 11:25 am, Olivier Lamy 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > On 23 October 2017 at 11:20, Yaniv Rodenski  wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > The Podling Report reminder is a really great motivation for moving
> > > > forward
> > > > > with Amaterasu :)
> > > > > I think that on the bootstrapping end we still need to move the
> repo
> > to
> > > > the
> > > > > ASF one.
> > > > >
> > > > > Mentors, do I just do this manually (push local clone) or is there
> a
> > > way
> > > > to
> > > > > pull it directly from github?
> > > >
> > > >
> > > > You can do it yourself (i.e push the branches you want to save to ASF
> > > > repo).
> > > > Or create an INFRA ticket if you want to pull it directly from
> github.
> > > >
> > > >
> > > > >
> > > > >
> > > > Also we are very close to version 0.2.0-incubating.
> > > > > not a lot of open tasks, but I think we should also get our JIRA in
> > > > order,
> > > > > I can port everything we have on our old trello, but maybe a
> hangouts
> > > > sync
> > > > > to go over the open tasks is a good way to push things forward?
> > > > >
> > > > > Cheers,
> > > > > --
> > > > > Yaniv Rodenski
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > >
> > > --
> > > Yaniv Rodenski
> > >
> >
>
>
>
> --
> Yaniv Rodenski
>

Re: Moving forward

[Davor Bonaci]

(You are also welcome to retain any source history that the original
repository has -- feel free to push a pull request containing all commits.
See Beam's pull request #1 as an example.)

On Sun, Oct 22, 2017 at 5:29 PM, Yaniv Rodenski  wrote:

> Thanks Olivier!
> I prefer doing things myself, I’ll push it today.
>
> On Mon, 23 Oct 2017 at 11:25 am, Olivier Lamy  wrote:
>
> > Hi,
> >
> > On 23 October 2017 at 11:20, Yaniv Rodenski  wrote:
> >
> > > Hi All,
> > >
> > > The Podling Report reminder is a really great motivation for moving
> > forward
> > > with Amaterasu :)
> > > I think that on the bootstrapping end we still need to move the repo to
> > the
> > > ASF one.
> > >
> > > Mentors, do I just do this manually (push local clone) or is there a
> way
> > to
> > > pull it directly from github?
> >
> >
> > You can do it yourself (i.e push the branches you want to save to ASF
> > repo).
> > Or create an INFRA ticket if you want to pull it directly from github.
> >
> >
> > >
> > >
> > Also we are very close to version 0.2.0-incubating.
> > > not a lot of open tasks, but I think we should also get our JIRA in
> > order,
> > > I can port everything we have on our old trello, but maybe a hangouts
> > sync
> > > to go over the open tasks is a good way to push things forward?
> > >
> > > Cheers,
> > > --
> > > Yaniv Rodenski
> > >
> >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> --
> Yaniv Rodenski
>

Re: Bootstrapping follow up

[Davor Bonaci]

(Report signed-off.)

On Sun, Oct 8, 2017 at 9:03 AM, John D. Ament  wrote:

> Yaniv,
>
> That is the correct way to request access.  From the top of the wiki:
>
> To edit pages, first sign up for a Wiki user account (note: account names
> are NOT shared across Wikis). Then send your Wiki username - note: this is
> case-sensitive, be sure to provide the exact name - to general@incubator
> so that we can grant you write access by adding your account to the
> ContributorsGroup. Once your account is set up, just login and start making
> changes. Notifications of all changes you make will be sent to the
> cvs@incubator mailing list.
>
> On 2017-10-05 01:17, Yaniv Rodenski  wrote:
> > I do, and I’m on the general list
> >
> > I saw people asking for wiki access in the list so I was wandering if
> > that’s the best way getting access.
> >
> > Cheers,
> > Yaniv
> >
> > On Thu, 5 Oct 2017 at 3:48 pm, Jean-Baptiste Onofré 
> wrote:
> >
> > > Hi,
> > >
> > > I updated the wiki with the board report and signed if off.
> > >
> > > For the general incubator mailing list, you just have to subscribe
> using
> > > general-subscr...@incubator.apache.org
> > >
> > > Do you have an account on the wiki ?
> > >
> > > Regards
> > > JB
> > >
> > > On 10/05/2017 04:29 AM, Yaniv Rodenski wrote:
> > > > Hi Davor,
> > > >
> > > > I think I have no access (I see the report as an immutable page),
> anyway
> > > JB
> > > > said hell take care of it this time.
> > > > Noob question, going forward, do I just need to request access in to
> > > > Incubator mailing list?
> > > >
> > > > Cheers,
> > > > Yaniv
> > > >
> > > > On Thu, Oct 5, 2017 at 4:45 AM, Davor Bonaci 
> wrote:
> > > >
> > > >> The report should be posted in Wiki. Yaniv?
> > > >>
> > > >> On Sun, Oct 1, 2017 at 4:07 PM, Yaniv Rodenski 
> wrote:
> > > >>
> > > >>> Hi JB,
> > > >>>
> > > >>> Report looks good to me.
> > > >>> As for moving the Git repo, I'm happy to move forward, but does
> anyone
> > > >> has
> > > >>> any issues going forward? Anyone want's to issue a PR before we
> move
> > > (not
> > > >>> that there should be a difference)?
> > > >>>
> > > >>> Yaniv
> > > >>>
> > > >>> On Mon, Oct 2, 2017 at 3:41 AM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > > >>> wrote:
> > > >>>
> > > >>>> Hi Yaniv and others,
> > > >>>>
> > > >>>> The github integration should be OK as well.
> > > >>>>
> > > >>>> For the user mailing list, it seems related to spamd:
> > > >>>>
> > > >>>> spamd2-us-west.apache.org (ASF Mail Server at
> > > >> spamd2-us-west.apache.org)
> > > >>>>
> > > >>>> We have to create a Jira to INFRA about that. I will do it.
> > > >>>>
> > > >>>> For the code migration, I worked on a branch for the packages
> rename,
> > > >>>> legal, etc. I will rebase with master and we can start from this
> > > point.
> > > >>>>
> > > >>>> For the podling report, I propose the following:
> > > >>>>
> > > >>>> "
> > > >>>> Apache Amaterasu is a framework providing continuous deployment
> for
> > > Big
> > > >>>> Data pipelines.
> > > >>>>
> > > >>>> It provides the following capabilities:
> > > >>>>
> > > >>>> Continuous integration tools to package pipelines and run tests.
> > > >>>> A repository to store those packaged applications: the
> applications
> > > >>>> repository.
> > > >>>> A repository to store the pipelines, and engine configuration (for
> > > >>>> instance, location of the Spark master, etc.): per environment -
> the
> > > >>>> configuration repository.
> > > >>>> A dashboard to monitor the pipelines.
> > > >>>> A DSL and integration hooks allowing third parties to easily
> > > integrate.
> >

Re: Bootstrapping follow up

[Davor Bonaci]

The report should be posted in Wiki. Yaniv?

On Sun, Oct 1, 2017 at 4:07 PM, Yaniv Rodenski  wrote:

> Hi JB,
>
> Report looks good to me.
> As for moving the Git repo, I'm happy to move forward, but does anyone has
> any issues going forward? Anyone want's to issue a PR before we move (not
> that there should be a difference)?
>
> Yaniv
>
> On Mon, Oct 2, 2017 at 3:41 AM, Jean-Baptiste Onofré 
> wrote:
>
> > Hi Yaniv and others,
> >
> > The github integration should be OK as well.
> >
> > For the user mailing list, it seems related to spamd:
> >
> > spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org)
> >
> > We have to create a Jira to INFRA about that. I will do it.
> >
> > For the code migration, I worked on a branch for the packages rename,
> > legal, etc. I will rebase with master and we can start from this point.
> >
> > For the podling report, I propose the following:
> >
> > "
> > Apache Amaterasu is a framework providing continuous deployment for Big
> > Data pipelines.
> >
> > It provides the following capabilities:
> >
> > Continuous integration tools to package pipelines and run tests.
> > A repository to store those packaged applications: the applications
> > repository.
> > A repository to store the pipelines, and engine configuration (for
> > instance, location of the Spark master, etc.): per environment - the
> > configuration repository.
> > A dashboard to monitor the pipelines.
> > A DSL and integration hooks allowing third parties to easily integrate.
> >
> > Amaterasu has been incubating since 2017-09.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Prepare first release
> >   2. Grow up user and contributor communities
> >   3. Prepare documentation
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >
> >   * Talks have been given in different events to promote and give
> > visibility to Amaterasu
> >
> > How has the project developed since the last report?
> >
> >   * Resources creation is in progress (website, Jira, git & github
> mirror,
> > ...)
> >   * The code donation is in preparation (rename packages, check legal,
> ...)
> >   * The website has been published and is online.
> >
> > Date of last release:
> >
> >   N/A
> >
> > When were the last committers or PMC members elected?
> >
> >   N/A
> > "
> >
> > For the Jira backlog, how do you want to proceed ? Do you want the filter
> > some Jira ?
> >
> > Big +1 to add Davor. I already updated the proposal.
> >
> > Regards
> > JB
> >
> >
> > On 10/01/2017 12:24 PM, Yaniv Rodenski wrote:
> >
> >> Dear Mentors,
> >>
> >> Following up on the discussion with our mentors @davor and @jb on
> private
> >> email, we need to finalize the boot strapping process.
> >>
> >> As far as I understand the following steps are completed:
> >> 1. Mailing lists are partially set up (user is still returning an error
> >> when subscribing)
> >> 2. Website is up and running (W00t!)
> >> 3. The Amaterasu git repo is ready
> >>
> >> Need to be completed:
> >> 1. Fix the user-subscribe@ email
> >> 2. Migrate the Amaterasu repo to the ASFs incubator-amaterasu repo
> >> 3. Start working on our first report
> >> 4. Migrate the Amaterasu backlog from our old trello to JIRA
> >> 5. Add Davor officially to the project's mentors list
> >>
> >> Anything else we should be across at this stage?
> >>
> >> Cheers,
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
> Yaniv Rodenski
>

Re: Bootstrapping follow up

[Davor Bonaci]

Great progress on the setting up the code repository and the website!

For the user mailing list, it seems related to spamd:
>
> spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org)
>
> We have to create a Jira to INFRA about that. I will do it.
>

I think the mailing list is not yet created, hence the error.

FYI, there are some in the Incubator community saying that podlings should
have dev@ and private@, and only create user@ at a later point -- usually
once dev@ starts getting too much traffic. There's merit to that (e.g.,
fragmentation), but it is not a rule of any kind.

I think this is trivially fixed through Infra's self-service, but I don't
think this is critical for the time being.

2. Migrate the Amaterasu repo to the ASFs incubator-amaterasu repo
>>
>
I suggest to work on this next.

How are things from the legal perspective? Does any company perhaps own any
rights to the current code? Any SGAs needed?

3. Start working on our first report
>>
>
Yup! Does everyone have wiki access?


> 4. Migrate the Amaterasu backlog from our old trello to JIRA
>>
>
Do you plan to do this manually or automatically through some tool?