What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. Zipkin has been incubating since 2018-08-29. ### Three most important unfinished issues to address before graduating: 1. Release all migrated components under Apache Incubator umbrella 2. Migrate the inter-component dependencies to the ones released under Apache Incubator 3. Finalize and polish all repositories to have no outstanding (minor) issues with respect to release policies and processes ### 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? There have been 2 community events which has happend in April and May respectively: - UX workshop and Lens GA planning at LINE Fukuoka - Zipkin Pow-wow Both events have been quite successful and contributed new interesting ideas regarding the project's current and future developments. ### How has the project developed since the last report? All designated repositories have been migrated under Apache organization. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2019-06-02 ### When were the last committers or PPMC members elected? 2019-03-15 ### Have your mentors been helpful? No answer. ### Signed-off-by: - [ ] (zipkin) Michael Semb Wever Comments: - [ ] (zipkin) John D. Ament Comments: - [X] (zipkin) Willem Ning Jiang Comments: - [X] (zipkin) Andriy Redko Comments: Very good pace with releases, really glad to see things moving. - [x] (zipkin) Sheng Wu Comments: Zipkin has released most of components in incubator, by different release managers. New PPMC members are selected. Near graduation. ### IPMC/Shepherd notes: Dave Fisher: Podling suitable name search is needed. Also a download page on the website.
Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. Zipkin has been incubating since 2018-08-29. Three most important issues to address in the move towards graduation: 1. Finalize the first release of the Apache Zipkin (incubating) for Apache Karaf 2. Migrate other repositories to ASF Github organization 3. Work towards releasing more Apache Zipkin (incubating) components once migration is completed Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The first release was very challenging. The Zipkin community found The Apache Incubator established practices to be somewhat hostile and unwelcoming for the newcomers. The community felt frustration and demotivation to the the point that the issues had been raised for the attention of the board. How has the community developed since the last report? A lot of work has been done to get the first release out, by all means a great achievement. The team and community is looking forward to see the positive changes within Apache Incubator with respect to the feedback provided. How has the project developed since the last report? The team has mastered the Apache CI/CD infrastructure and was able to quickly do the switch over for the first migrated repository. Also, the team better understands how the incubation process works and what to watch for. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [X] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2019-02-26 When were the last committers or PPMC members elected? 2019-02-26 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. Signed-off-by: [X](zipkin) Michael Semb Wever Comments: [X](zipkin) John D. Ament Comments: [X](zipkin) Willem Ning Jiang Comments: [X](zipkin) Andriy Redko Comments: [x](zipkin) Sheng Wu Comments: IPMC/Shepherd notes:
Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. Zipkin has been incubating since 2018-08-29. Three most important issues to address in the move towards graduation: 1. Finalize the migration of the GitHub repositories 2. Wrap up and agree upon release process, the draft discussion has been started already 3. Plan to integrate one of the repositories (zipkin-karaf) with Apache CI (Jenkins) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The podling is presently blocked on INFRA-16989 however from the ASF side all concerns are cleared out. How has the community developed since the last report? The workshop regarding major Zipkin UI rework in planned on 3-7 of December, 2018. How has the project developed since the last report? Not much progress to report since the repositories have not been migrated yet. The new mentor, Sheng Wu, has joined the project. Also, the team has established a process to reflect project updates which is to create a wiki at the same time as the incubator reports (called LastMonthInZipkin). How would you assess the podling's maturity? Please feel free to add your own commentary. [X] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: N/A When were the last committers or PPMC members elected? 2018-11-16 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. Not much involvement from the mentors for the past month. Signed-off-by: [X](zipkin) Michael Semb Wever Comments: [ ](zipkin) John D. Ament Comments: [ ](zipkin) Willem Ning Jiang Comments: [X](zipkin) Andriy Redko Comments: [x](zipkin) Sheng Wu Comments: IPMC/Shepherd notes: }}}
Zipkin is a distributed tracing system. It helps gather timing data needed
to troubleshoot latency problems in microservice architectures.
Zipkin has been incubating since 2018-08-29.
Three most important issues to address in the move towards graduation:
1. Finalize the migration of the GitHub repositories
2. Finalize the migration of website
3. Assess the migration to Apache CI infrastructure (Jenkins)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The podling is presently blocked on INFRA-16989.
How has the community developed since the last report?
The workshop has been held on 29th of October, 2018.
How has the project developed since the last report?
The team started to look at Apache CI infrastructure (Jenkins) and assess
the fit to the project needs (comparing to Travis CI). The Zipkin web
site has been already migrated to Jenkins job and automatically rebuilds
in case of changes.
How would you assess the podling's maturity?
The IP rights/SGA and Git repository migration are still ongoing.
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
2018-09-24
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.
Mick was instrumental in getting us "in the nick of time" progressed on
the otherwise block on SGA. He encouraged me towards sending a message
to the secretary and escalated later which allowed a last minute progress.
Andriy helped with keeping spirit alive on dev list, review of wiki
content and also progressed our new committer Raja towards steps needed
for committership.
Signed-off-by:
[X](zipkin) Michael Semb Wever
Comments: I would have listed the blockage on migrating the code
(INFRA-16989) under "issues that the Incubator PMC (IPMC) or ASF
Board wish/need to be aware of" as even though it's moving again,
this podling has barely moved for months because of it.
[X](zipkin) John D. Ament
Comments: I agree with the issues around the code import and don't
understand how we can help them move past it. It seems that infra has
suddenly put a burden on secretary that isn't typical.
[X](zipkin) Willem Ning Jiang
Comments: As we already get iCLAs and SGA, can we move the code in to
Apache?
[X](zipkin) Andriy Redko
Comments: The project struggles for a few months now to get the SGA
approved or/and accepted
(https://issues.apache.org/jira/browse/INFRA-16989)
by Apache. This is a significant source of frustration among the PPMCs
and community in general as the any further efforts are blocked.
IPMC/Shepherd notes:
Zipkin is a distributed tracing system. It helps gather timing data needed
to troubleshoot latency problems in microservice architectures.
Zipkin has been incubating since 2018-08-29.
Three most important issues to address in the move towards graduation:
1. Finalize the migration of the GitHub repositories
2. Finalize the migration of website
3. Assess the migration to Apache CI infrastructure (Jenkins)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The podling is presently blocked on INFRA-16989.
How has the community developed since the last report?
The workshop has been held on 29th of October, 2018.
How has the project developed since the last report?
The team started to look at Apache CI infrastructure (Jenkins) and assess
the fit to the project needs (comparing to Travis CI). The Zipkin web
site has been already migrated to Jenkins job and automatically rebuilds
in case of changes.
How would you assess the podling's maturity?
The IP rights/SGA and Git repository migration are still ongoing.
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
2018-09-24
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.
Mick was instrumental in getting us "in the nick of time" progressed on
the otherwise block on SGA. He encouraged me towards sending a message
to the secretary and escalated later which allowed a last minute progress.
Andriy helped with keeping spirit alive on dev list, review of wiki
content and also progressed our new committer Raja towards steps needed
for committership.
Signed-off-by:
[X](zipkin) Michael Semb Wever
Comments: I would have listed the blockage on migrating the code
(INFRA-16989) under "issues that the Incubator PMC (IPMC) or ASF
Board wish/need to be aware of" as even though it's moving again,
this podling has barely moved for months because of it.
[X](zipkin) John D. Ament
Comments: I agree with the issues around the code import and don't
understand how we can help them move past it. It seems that infra has
suddenly put a burden on secretary that isn't typical.
[X](zipkin) Willem Ning Jiang
Comments: As we already get iCLAs and SGA, can we move the code in to
Apache?
[X](zipkin) Andriy Redko
Comments: The project struggles for a few months now to get the SGA
approved or/and accepted
(https://issues.apache.org/jira/browse/INFRA-16989)
by Apache. This is a significant source of frustration among the PPMCs
and community in general as the any further efforts are blocked.
IPMC/Shepherd notes:
Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. Zipkin has been incubating since 2018-08-29. Three most important issues to address in the move towards graduation: 1. Finalize committers ICLAs 2. Migrate GitHub repositories 3. Migrate website 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? The workshop has been held on 20th of September, 2018. The existing community is slowly getting used to the new Zipkin home. How has the project developed since the last report? The Confluence space has been created and large amount of content already published, including designs, features and workshops. The discussions around establishing the CI/CD processes are ongoing but currently on hold due to Git repositories migration. How would you assess the podling's maturity? Currently in progress are conversations to finalize the IP rights and Git repository migration. The number of core PPMC members have been added, a few more ICLAs are on the way. [X] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: N/A When were the last committers or PPMC members elected? 2018-09-24 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. The team is quite happy with mentors involvement so far. Signed-off-by: [X](zipkin) Michael Semb Wever Comments: [X](zipkin) John D. Ament Comments: The podling is struggling to get their code repos moved over to the ASF. Presently blocked on a requirement to have all ICLAs and SGA present, which isn't the norm for existing open source (non-commercially donated) entities. Granted, we do this very infrequent but it may be time for the foundation to formalize this process a bit better so that other podlings don't run into similar issues. [X](zipkin) Willem Ning Jiang Comments: [X](zipkin) Andriy Redko Comments: IPMC/Shepherd notes: }}}
Zipkin has been incubating since 2018-08-30 Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data. Zipkin’s design is based on the Google Dapper paper. Three most important issues to address in the move towards graduation. 1. Initial committers ICLAs 2. Migrate GitHub repositories 3. Migrate website Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: none How has the community developed since the last report? N/A How has the project developed since the last report? N/A How would you assess the podling's maturity? Zipkin only entered the Incubator just over a week ago. The project DNS and mailing lists have been setup. Currently in progress is git repository migration. Otherwise the community is still handing in ICLAs and learning up on ASF. [X] Initial setup [ ] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Building initial designs and re-writing donated code Date of last release: N/A When were the last committers or PPMC members elected? N/A Signed-off-by: [X](zipkin) Mick Semb Wever Comments: [X](zipkin) Andriy Redko Comments: [X](zipkin) John D. Ament Comments: [ ](zipkin) Willem Ning Jiang Comments: IPMC/Shepherd notes: }}}