Re: Apache DLAB Issue Tracker - Clutch
Hi Dave, Thanks! Kind Regards, Furkan KAMACI On Fri, Aug 2, 2019 at 10:30 PM Dave Fisher wrote: > Hi Furkan, > > The clutch is looking at the Podling’s status xml and for DLab there is an > incorrect id attribute for the tracker url: > > Change: > > https://issues.apache.org/jira/projects/DLAB/;> > https://issues.apache.org/jira/projects/DLAB/ > > To: > > https://issues.apache.org/jira/projects/DLAB/;> > https://issues.apache.org/jira/projects/DLAB/ > > > Regards, > Dave > > > On Aug 2, 2019, at 12:21 PM, Furkan KAMACI > wrote: > > > > Hi All, > > > > Apache DLAB has an issue tracker [1] but clutch says that is has not [2]. > > Does anybody know what may be the reason for this? > > > > [1] https://issues.apache.org/jira/projects/DLAB/ > > [2] https://incubator.apache.org/clutch/ > > > > Kind Regards, > > Furkan KAMACI > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Apache DLAB Issue Tracker - Clutch
Hi Furkan, The clutch is looking at the Podling’s status xml and for DLab there is an incorrect id attribute for the tracker url: Change: https://issues.apache.org/jira/projects/DLAB/;>https://issues.apache.org/jira/projects/DLAB/ To: https://issues.apache.org/jira/projects/DLAB/;>https://issues.apache.org/jira/projects/DLAB/ Regards, Dave > On Aug 2, 2019, at 12:21 PM, Furkan KAMACI wrote: > > Hi All, > > Apache DLAB has an issue tracker [1] but clutch says that is has not [2]. > Does anybody know what may be the reason for this? > > [1] https://issues.apache.org/jira/projects/DLAB/ > [2] https://incubator.apache.org/clutch/ > > Kind Regards, > Furkan KAMACI - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Apache DLAB Issue Tracker - Clutch
Hi All, Apache DLAB has an issue tracker [1] but clutch says that is has not [2]. Does anybody know what may be the reason for this? [1] https://issues.apache.org/jira/projects/DLAB/ [2] https://incubator.apache.org/clutch/ Kind Regards, Furkan KAMACI
Re: Feedbacks and Questions about Podling Status Files and Incubator Website
Hi, Thanks for the answers Justin! Kind Regards, Furkan KAMACI On Fri, Aug 2, 2019 at 1:52 AM Justin Mclean wrote: > Hi, > > Take a look at the note at the bottom of [1] > > > I want to update podling status file and have some questions and > feedbacks: > > > > 1) https://incubator.apache.org/guides/website.html says that: > > > > Podling status files are maintained in SVN, and you should continue to > > maintain them at > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/ > > > > So, I've updated the XML file at SVN, is that enough (may not b enough > > according to question 5)? > > It depends on what you want updated. > > > 2) A mentor will also need to update it until others in the project’s > PPMC > > can update it. > > What are the requirements for PPMC can update it? > > From memory but I’ve not checked any IPMC member shod be able to edit that > file. > > > 4) This link doesn't work: > > https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/ > at > > here: > > The site was recently split into a 2 stage build process, so there’s two > jenkins jobs now one to build the clutch and one to build the site, > > > 5) https://incubator.apache.org/guides/ppmc.html#Project+Status+Updates > says > > that: > > > > Podling rosters are maintained in Whimsy. Going forward, the content in > > projects/$podling.xml is considered deprecated. > > Whimsey keeps rosters (and modifies the XML file) so there no need to > update rosters in that XML file manually. > > > So, how can I update here: https://whimsy.apache.org/roster/ppmc/flagon > (apart > > from modifying Mentor/PPMC list)? > > That will only update the roster. > > Thanks, > Justin > > 1. https://incubator.apache.org/clutch/ > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [MENTORS] IPMC Policy change work in progress disclaimer
On Fri, 2 Aug 2019 at 07:16, Paul King wrote: > Kudos for progressing this idea. I really like it. It should allow > improvements from the perspective of both podlings and reviewers. > > Cheers, Paul. > +1 - nice work.
Re: [VOTE] DataSketches-memory RC2
Hi, > I will do a thorough license search. Ask your mentor for help they will be able to help you with this. > I will try to locate the WIP Disclaimer ... do you have a link? Yes https://incubator.apache.org/policy/incubation.html#disclaimers. There also an email to this list today with the text in a more convenient form. > Right now I am struggling with pom issue related to the > maven-remote-resources-plugin. Hopefully someone with more maven experience than I can help you out here. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] DataSketches-memory RC2
HI, > [*INFO*] Exclude: **/test/resources/**/*.txt That missed one of the files in question, I found it by running rat manually. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] IPMC Policy change work in progress disclaimer
+1! 2 Ağu 2019 Cum, saat 09:29 tarihinde Sheng Wu şunu yazdı: > +1 from me. > > Sheng Wu > Apache Skywalking, ShardingSphere, Zipkin > > > > > 在 2019年8月2日，上午10:25，Justin Mclean 写道： > > > > Hi, > > > > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added > to the IPMC policy page. [1] > > > > Podlings can now select which disclaimer they want to use. If they want > to use the standard disclaimer then their releases must comply with all ASF > policy. If they want the incubator to be more lenient in voting on their > release or know that the release has some issues not in line with ASF > policy then the work in progress disclaimer can be used. > > > > Unless the release is simple and straightforward, I would recommend that > a podling uses the work in progress disclaimer for the first couple of > releases. > > > > For what is allowed under the work in progress disclaimer please see > this legal JIRA [2]. This allows a lot more in a release but not > everything. Certain things are required like having a LICENSE, NOTICE and > DISCLAIMER-WIP, and while it would be OK to include compiled code you still > need to comply with any licensing for that code. > > > > By the time a podling graduates it's expected that they are making > releases with the standard disclaimer. > > > > Here is the text of the DISCLAIMER-WIP where the Incubator is the > sponsor: > > > > Apache #Podling-Name# is an effort > > undergoing incubation at The Apache Software Foundation (ASF), > > sponsored by the Apache Incubator. Incubation is required of all > > newly accepted projects until a further review indicates that the > > infrastructure, communications, and decision making process have > > stabilized in a manner consistent with other successful ASF projects. > > While incubation status is not necessarily a reflection of the > > completeness or stability of the code, it does indicate that the > > project has yet to be fully endorsed by the ASF. > > > > Some of the incubating project's releases may not be fully compliant > > with ASF policy. For example, releases may have incomplete or > > un-reviewed licensing conditions. What follows is a list of known > > issues the project is currently aware of (note that this list, by > > definition, is likely to be incomplete): > > #List of known issues go here# > > > > If you are planning to incorporate this work into your > > product/project, please be aware that you will need to conduct a > > thorough licensing review to determine the overall implications of > > including this work. For the current status of this project through the > Apache > > Incubator visit: > > http://incubator.apache.org/project/#Podling-Name#.html > > > > > > Just fill in #Podling-Name# with your podling name and list the known > issues in the correct place. > > > > Thanks, > > Justin > > > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > > 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469 > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [MENTORS] IPMC Policy change work in progress disclaimer
+1 from me. Sheng Wu Apache Skywalking, ShardingSphere, Zipkin > 在 2019年8月2日，上午10:25，Justin Mclean 写道： > > Hi, > > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added to > the IPMC policy page. [1] > > Podlings can now select which disclaimer they want to use. If they want to > use the standard disclaimer then their releases must comply with all ASF > policy. If they want the incubator to be more lenient in voting on their > release or know that the release has some issues not in line with ASF policy > then the work in progress disclaimer can be used. > > Unless the release is simple and straightforward, I would recommend that a > podling uses the work in progress disclaimer for the first couple of releases. > > For what is allowed under the work in progress disclaimer please see this > legal JIRA [2]. This allows a lot more in a release but not everything. > Certain things are required like having a LICENSE, NOTICE and DISCLAIMER-WIP, > and while it would be OK to include compiled code you still need to comply > with any licensing for that code. > > By the time a podling graduates it's expected that they are making releases > with the standard disclaimer. > > Here is the text of the DISCLAIMER-WIP where the Incubator is the sponsor: > > Apache #Podling-Name# is an effort > undergoing incubation at The Apache Software Foundation (ASF), > sponsored by the Apache Incubator. Incubation is required of all > newly accepted projects until a further review indicates that the > infrastructure, communications, and decision making process have > stabilized in a manner consistent with other successful ASF projects. > While incubation status is not necessarily a reflection of the > completeness or stability of the code, it does indicate that the > project has yet to be fully endorsed by the ASF. > > Some of the incubating project's releases may not be fully compliant > with ASF policy. For example, releases may have incomplete or > un-reviewed licensing conditions. What follows is a list of known > issues the project is currently aware of (note that this list, by > definition, is likely to be incomplete): > #List of known issues go here# > > If you are planning to incorporate this work into your > product/project, please be aware that you will need to conduct a > thorough licensing review to determine the overall implications of > including this work. For the current status of this project through the Apache > Incubator visit: > http://incubator.apache.org/project/#Podling-Name#.html > > > Just fill in #Podling-Name# with your podling name and list the known issues > in the correct place. > > Thanks, > Justin > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469 > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] IPMC Policy change work in progress disclaimer
+1 On Thu, Aug 1, 2019 at 11:17 PM Paul King wrote: > Kudos for progressing this idea. I really like it. It should allow > improvements from the perspective of both podlings and reviewers. > > Cheers, Paul. > > On Fri, Aug 2, 2019 at 12:25 PM Justin Mclean > wrote: > > > Hi, > > > > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added > > to the IPMC policy page. [1] > > > > Podlings can now select which disclaimer they want to use. If they want > to > > use the standard disclaimer then their releases must comply with all ASF > > policy. If they want the incubator to be more lenient in voting on their > > release or know that the release has some issues not in line with ASF > > policy then the work in progress disclaimer can be used. > > > > Unless the release is simple and straightforward, I would recommend that > a > > podling uses the work in progress disclaimer for the first couple of > > releases. > > > > For what is allowed under the work in progress disclaimer please see this > > legal JIRA [2]. This allows a lot more in a release but not everything. > > Certain things are required like having a LICENSE, NOTICE and > > DISCLAIMER-WIP, and while it would be OK to include compiled code you > still > > need to comply with any licensing for that code. > > > > By the time a podling graduates it's expected that they are making > > releases with the standard disclaimer. > > > > Here is the text of the DISCLAIMER-WIP where the Incubator is the > sponsor: > > > > Apache #Podling-Name# is an effort > > undergoing incubation at The Apache Software Foundation (ASF), > > sponsored by the Apache Incubator. Incubation is required of all > > newly accepted projects until a further review indicates that the > > infrastructure, communications, and decision making process have > > stabilized in a manner consistent with other successful ASF projects. > > While incubation status is not necessarily a reflection of the > > completeness or stability of the code, it does indicate that the > > project has yet to be fully endorsed by the ASF. > > > > Some of the incubating project's releases may not be fully compliant > > with ASF policy. For example, releases may have incomplete or > > un-reviewed licensing conditions. What follows is a list of known > > issues the project is currently aware of (note that this list, by > > definition, is likely to be incomplete): > > #List of known issues go here# > > > > If you are planning to incorporate this work into your > > product/project, please be aware that you will need to conduct a > > thorough licensing review to determine the overall implications of > > including this work. For the current status of this project through the > > Apache > > Incubator visit: > > http://incubator.apache.org/project/#Podling-Name#.html > > > > > > Just fill in #Podling-Name# with your podling name and list the known > > issues in the correct place. > > > > Thanks, > > Justin > > > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > > 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469 > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [MENTORS] IPMC Policy change work in progress disclaimer
Kudos for progressing this idea. I really like it. It should allow improvements from the perspective of both podlings and reviewers. Cheers, Paul. On Fri, Aug 2, 2019 at 12:25 PM Justin Mclean wrote: > Hi, > > The work in progress progress disclaimer (DISCLAIMER-WIP) has been added > to the IPMC policy page. [1] > > Podlings can now select which disclaimer they want to use. If they want to > use the standard disclaimer then their releases must comply with all ASF > policy. If they want the incubator to be more lenient in voting on their > release or know that the release has some issues not in line with ASF > policy then the work in progress disclaimer can be used. > > Unless the release is simple and straightforward, I would recommend that a > podling uses the work in progress disclaimer for the first couple of > releases. > > For what is allowed under the work in progress disclaimer please see this > legal JIRA [2]. This allows a lot more in a release but not everything. > Certain things are required like having a LICENSE, NOTICE and > DISCLAIMER-WIP, and while it would be OK to include compiled code you still > need to comply with any licensing for that code. > > By the time a podling graduates it's expected that they are making > releases with the standard disclaimer. > > Here is the text of the DISCLAIMER-WIP where the Incubator is the sponsor: > > Apache #Podling-Name# is an effort > undergoing incubation at The Apache Software Foundation (ASF), > sponsored by the Apache Incubator. Incubation is required of all > newly accepted projects until a further review indicates that the > infrastructure, communications, and decision making process have > stabilized in a manner consistent with other successful ASF projects. > While incubation status is not necessarily a reflection of the > completeness or stability of the code, it does indicate that the > project has yet to be fully endorsed by the ASF. > > Some of the incubating project's releases may not be fully compliant > with ASF policy. For example, releases may have incomplete or > un-reviewed licensing conditions. What follows is a list of known > issues the project is currently aware of (note that this list, by > definition, is likely to be incomplete): > #List of known issues go here# > > If you are planning to incorporate this work into your > product/project, please be aware that you will need to conduct a > thorough licensing review to determine the overall implications of > including this work. For the current status of this project through the > Apache > Incubator visit: > http://incubator.apache.org/project/#Podling-Name#.html > > > Just fill in #Podling-Name# with your podling name and list the known > issues in the correct place. > > Thanks, > Justin > > 1. https://incubator.apache.org/policy/incubation.html#disclaimers > 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469 > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
