Re: Podling Report Reminder - June 2018
The pulsar community is aware that for convenience, they can continue to make releases using their pre-Apache process. As well as the caveat that any such releases are not hosted on ASF infrastructure, and are flagged with a prominent notice that such releases are not Apache releases. Many projects do this early in incubation to maintain their release rhythm. As a mentor I think all is good in that respect. I look forward to an Apache release, and it seems one is likely soon. -Taylor > On Jun 20, 2018, at 5:43 PM, Gian Merlino wrote: > > Hi Justin, > > As Julian said, he is active, and has been very helpful as a mentor. > (Thanks Julian!!) > > Thanks for checking up on us. We'll make sure not to miss next month's > report; we are aware they are a thing (we did a couple already -- Nishant > did one and I did one or two) but it looks like nobody noticed this one > until it was too late. About the non-ASF releases: I don't have a link > handy to the thread, but basically what is going on is that until recently > we didn't have the SGA sorted, which we understood to mean it was out of > the question to do ASF releases. Now it is sorted and we're looking to > migrate our git repos next. I think it is likely we'll want to do another > non-incubator minor release while that process is ongoing, but am still > optimistic that the next major release will be an incubator release. > > On Tue, Jun 19, 2018 at 6:00 PM Justin Mclean > wrote: > >> Hi, >> >> I noticed the podling has failed to report this month and so will need two >> report next month. You're a relatively new podling so I wonder are you just >> not aware of the process or is it that you need more help from your >> mentors? Are your mentors currently active? >> >> I also notice on your dev list a number of votes for non ASF releases. I >> can’t see (but may of missed it) any discussion to why these non ASF >> releases are needed or what is holding you up making an ASF release. It >> seems a little odd to me that you would vote on these and then not get the >> IPMC to look at them, so it may be good idea to have the IPMC look at these >> releases in the future, but hopefully your next release will be an ASF one >> and will be voted on by the IPMC. >> >> Thanks, >> Justin >> - >> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org >> For additional commands, e-mail: dev-h...@druid.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Podling Report Reminder - June 2018
Hi Justin, As Julian said, he is active, and has been very helpful as a mentor. (Thanks Julian!!) Thanks for checking up on us. We'll make sure not to miss next month's report; we are aware they are a thing (we did a couple already -- Nishant did one and I did one or two) but it looks like nobody noticed this one until it was too late. About the non-ASF releases: I don't have a link handy to the thread, but basically what is going on is that until recently we didn't have the SGA sorted, which we understood to mean it was out of the question to do ASF releases. Now it is sorted and we're looking to migrate our git repos next. I think it is likely we'll want to do another non-incubator minor release while that process is ongoing, but am still optimistic that the next major release will be an incubator release. On Tue, Jun 19, 2018 at 6:00 PM Justin Mclean wrote: > Hi, > > I noticed the podling has failed to report this month and so will need two > report next month. You're a relatively new podling so I wonder are you just > not aware of the process or is it that you need more help from your > mentors? Are your mentors currently active? > > I also notice on your dev list a number of votes for non ASF releases. I > can’t see (but may of missed it) any discussion to why these non ASF > releases are needed or what is holding you up making an ASF release. It > seems a little odd to me that you would vote on these and then not get the > IPMC to look at them, so it may be good idea to have the IPMC look at these > releases in the future, but hopefully your next release will be an ASF one > and will be voted on by the IPMC. > > Thanks, > Justin > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
Re: Podling Report Reminder - June 2018
Yes, the mentors are active and I’m one of them. As a mentor I am happy to give advice, and do so frequently. But I’m not going to nag the PPMC to file reports. They need to do that for themselves. Julian > On Jun 19, 2018, at 18:00, Justin Mclean wrote: > > Hi, > > I noticed the podling has failed to report this month and so will need two > report next month. You're a relatively new podling so I wonder are you just > not aware of the process or is it that you need more help from your mentors? > Are your mentors currently active? > > I also notice on your dev list a number of votes for non ASF releases. I > can’t see (but may of missed it) any discussion to why these non ASF releases > are needed or what is holding you up making an ASF release. It seems a little > odd to me that you would vote on these and then not get the IPMC to look at > them, so it may be good idea to have the IPMC look at these releases in the > future, but hopefully your next release will be an ASF one and will be voted > on by the IPMC. > > Thanks, > Justin > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Podling Report Reminder - June 2018
Hi, I noticed the podling has failed to report this month and so will need two report next month. You're a relatively new podling so I wonder are you just not aware of the process or is it that you need more help from your mentors? Are your mentors currently active? I also notice on your dev list a number of votes for non ASF releases. I can’t see (but may of missed it) any discussion to why these non ASF releases are needed or what is holding you up making an ASF release. It seems a little odd to me that you would vote on these and then not get the IPMC to look at them, so it may be good idea to have the IPMC look at these releases in the future, but hopefully your next release will be an ASF one and will be voted on by the IPMC. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Podling Report Reminder - June 2018
All, Please see below note. As an Apache podling, you are expected to provide a report on a quarterly basis. New podlings are expected to report their first 3 months. Report is past due to the IPMC. If you do not report, you will be asked to report again next month (if you are within the first 3 months, your schedule will get postponed). Reports are used to check project status and health. John On 2018/06/04 00:06:31, jmcl...@apache.org 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 June 2018, 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, June 06). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://wiki.apache.org/incubator/June2018 > > 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 > > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Podling Report Reminder - June 2018
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 June 2018, 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, June 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/June2018 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 - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Podling Report Reminder - June 2018
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 June 2018, 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, June 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/June2018 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 - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
