You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@amaterasu.apache.org by Yaniv Rodenski <ya...@shinto.io> on 2019/01/01 15:11:51 UTC
[DISCUSS] podling report
Hi All,
I propose the following report to be submitted.
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?
How has the community developed since the last report?
Two new contributors have contributed code that have been merged. In
addition, we are actively looking for more use cases and organizations to
use Amaterasu.
How has the project developed since the last report?
* 5 pull requests have been opened since the last report and 4 have been
merged
* Since last report 9 more issues have been created and 4 out of them
have been assigned
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:
[](amaterasu) Jean-Baptiste Onofré
[](amaterasu) Olivier Lamy
[](amaterasu) Davor Bonaci
--
Yaniv Rodenski
Re: [DISCUSS] podling report
Posted by Davor Bonaci <db...@gmail.com>.
>
> 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 <ya...@gmail.com> 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
> <ki...@gmail.com> and @eyalb@apache.org <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: [DISCUSS] podling report
Posted by Yaniv Rodenski <ya...@shinto.io>.
Hi Davor,
The report was made in a rush and a bit from memory as I am traveling. I
will rectify, please see below:
> Two new contributors have contributed code that have been merged.
This was from my memory, @Yariv Triffon <ya...@gmail.com> 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.
> 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
<ki...@gmail.com> and @eyalb@apache.org <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.
> * 5 pull requests have been opened
You are correct, as I said this report was done in a rush I will fix this
in the report.
I understand that you are not trying to be difficult, and if you and the
other mentors think we should retire we can discuss that, but also, 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 (and I'm not speaking about graduation yet).
I will also add a comment in the report regarding this discussion.
Cheers,
Yaniv
On Sun, Jan 6, 2019 at 8:39 AM Davor Bonaci <da...@apache.org> wrote:
> 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
>
--
Yaniv Rodenski
+61 477 778 405
yaniv@shinto.io
Re: [DISCUSS] podling report
Posted by Davor Bonaci <da...@apache.org>.
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: [DISCUSS] podling report
Posted by Olivier Lamy <ol...@apache.org>.
lgtm
On Fri, 4 Jan 2019 at 20:43, Nadav Har Tzvi <na...@gmail.com> wrote:
> Yeah, I give it a +1
>
> Cheers,
> Nadav
>
>
>
> On Tue, 1 Jan 2019 at 17:12, Yaniv Rodenski <ya...@shinto.io> wrote:
>
> > Hi All,
> >
> > I propose the following report to be submitted.
> >
> > 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?
> >
> >
> > How has the community developed since the last report?
> >
> >
> > Two new contributors have contributed code that have been merged. In
> > addition, we are actively looking for more use cases and organizations to
> > use Amaterasu.
> >
> >
> > How has the project developed since the last report?
> >
> >
> > * 5 pull requests have been opened since the last report and 4 have
> been
> > merged
> >
> > * Since last report 9 more issues have been created and 4 out of them
> > have been assigned
> >
> >
> > 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:
> >
> >
> > [](amaterasu) Jean-Baptiste Onofré
> >
> > [](amaterasu) Olivier Lamy
> >
> > [](amaterasu) Davor Bonaci
> >
> > --
> > Yaniv Rodenski
> >
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [DISCUSS] podling report
Posted by Nadav Har Tzvi <na...@gmail.com>.
Yeah, I give it a +1
Cheers,
Nadav
On Tue, 1 Jan 2019 at 17:12, Yaniv Rodenski <ya...@shinto.io> wrote:
> Hi All,
>
> I propose the following report to be submitted.
>
> 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?
>
>
> How has the community developed since the last report?
>
>
> Two new contributors have contributed code that have been merged. In
> addition, we are actively looking for more use cases and organizations to
> use Amaterasu.
>
>
> How has the project developed since the last report?
>
>
> * 5 pull requests have been opened since the last report and 4 have been
> merged
>
> * Since last report 9 more issues have been created and 4 out of them
> have been assigned
>
>
> 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:
>
>
> [](amaterasu) Jean-Baptiste Onofré
>
> [](amaterasu) Olivier Lamy
>
> [](amaterasu) Davor Bonaci
>
> --
> Yaniv Rodenski
>