Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name
+1 not binding from wilfreds On 2024/05/08 00:31:23 tison wrote: > Hi, > > Following the discussion thread [1], I'd start a vote on the following > proposals: > > 1. Establish a consensus to allow and finally converge podling's GitHub repo > to > have a name without the incubator- prefix. > 2. Allow existing ongoing podlings to ask the INFRA to drop their > incubator- prefix by now, not MUST during the graduation. > 3. Update the docs on incubator.apache.org everywhere if the description > can conflict with this consensus. > 4. Update the docs on incubator.apache.org to guide how to describe > podling's incubating status on the GitHub repo (namely, including > "incubating" in the repo description and README, point to the DISCLAIMER > content). > > [1] https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok > > +1 allow podling's GitHub repo to have a name without the incubator- > prefix, and other items above > +0 do not care strongly > -1 disagree the proposals above, because ... > > Please vote with your ASF ID followed by (binding) if you are a member of > the Incubator PMC or (not binding) if not. > > Vote will be open for at least 72 hours. > > Best, > tison. > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
> https://github.com/apache/incubator-fury/pull/1574/commits/2ac9d808af75d17c0ea74a9755fe165b13de15f2 > > That is, keep the first and most prominent uses in form "Apache Foo > (incubating)" and add a hyperlink to "incubating" to the DISCLAIMER. This > should be a shorter solution and at least as good as the incubator- prefix. > Ensuring the repo description contain "incubating" can help. > that looks good and compensates for the loss of incubating in the name easily. Wilfred - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
For Go based projects dropping the incubator reference in the git repo makes things easier also when graduating. Packages and dependencies are referenced based on the repository name. Renaming the repository either requires changes throughout the code base to remove the incubator reference or the packages will always have the incubator reference in them. Wilfred On 2024/04/23 01:22:02 tison wrote: > Hi, > > Recently, the new added podlings, namely Amoro and Hertzbeat, have their > GitHub repo in the names: > > * https://github.com/apache/amoro > * https://github.com/apache/hertzbeat > > ... which is different to the other 20+ podlings and 200+ repos [1] > existing (this number counts retired ones and those for the Incubator PMC > itself, but it's approximate). > > [1] > https://github.com/orgs/apache/repositories?language==incubator-==all > > My opinion is to agree that generally: > > 1. The incubator prefix comes from the SVN days where all podlings were under > the incubator SVN tree. > 2. Dropping the incubator- prefix for podling's GitHub repo can reduce some > graduation tasks (although it's somewhat a milestone and ceremony for the > podling, and INFRA does not find it a large job, as well as it won't break > downstream almost due to redirections). > 3. It's still significant to make it clear that a podling is in the > incubating status and thus a DISCLAIMER to protect the ASF branding. > > With these premises, I started this thread with the following proposals and > questions. > > 1. Establish a consensus to allow podling's GitHub repo to have a name > without incubator- prefix. > 2. Allow other podlings to ask the INFRA to drop their incubator- prefix by > now, not MUST during the graduation. > 3. Update the docs on incubator.apache.org everywhere if the description > can conflict with this consensus. > 4. However, find a way to clarify that a repo belongs to a podling. > > For 4, I'd propose to add the "incubating" words to each repo's README. > This can be regarded as treating those READMEs a homepage for the repo and, > > 1. Name the project as "Apache Foo (Incubating)" in its first and most > prominent uses, hopefully and H1 heading. > 2. Add a footer including the Incubator logo and DISCLAIMER, like the > current footer of Apache Answer (Incubating) [3] > > [3] https://answer.apache.org/ > > This method, however, can be a new chore for podlings that have many > satellite repos that may previously claim their incubating status by naming > the repos incubator-foo-satellite. But it's just another template to > follow, so it won't be a big deal. > > Looking forward to your thoughts on this proposal and any suggestions to > improve the implementation part. > > Best, > tison. > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1 (Round2)
On 2024/01/03 08:24:10 tison wrote: > > go.mod could have an apache header > > go.mod doesn't seems something creative but a bookkeeping index. I > wonder if we should add license header for such files. go.mod is part of the project and lists the import and versions. It is maintained mostly by hand, partially via tools (layout and indirect ref etc), I would agree with adding a header. go.sum on the other hand is maintained by tools only based on the go.mod content. No header in that file as it causes issues, Wilfred > > Best, > tison. > > Christofer Dutz 于2024年1月3日周三 16:19写道： > > > > +1 (binding) > > > > However, I did find, that it seems to be impossible to build from sources, > > if the sources are unpacked from the src-archive instead of checked out. > > This should be addressed in future releases. > > > > Chris > > > > [OK] Download all staged artifacts under the url specified in the release > > vote email. > > [OK] Verify the signature is correct. > > [OK] Check if the signature references an Apache email address. > > [OK] Verify the SHA512 hashes. > > [OK] Unzip the archive. > > [OK] Verify the artifacts have “apache” and “incubating” in their names > > [OK] Verify the existence of LICENSE, NOTICE, README, DISCLAIMER files in > > the extracted source bundle. > > [OK] Verify the content of LICENSE, NOTICE, README, DISCLAIMER files in the > > extracted source bundle. > > > > * Using non-WIP disclaimer, doing the thorough checks. > > * NOTICE contains 2023, but as the RC was created 2023, no issue > > [OK] Run RAT externally to ensure there are no surprises. > > > > * go.mod could have an apache header > > * docs/img/logo.svg could have an apache header > > * ui/src/assets/images/default-avatar.svg could have an apache header > > [OK] Search for SNAPSHOT references > > [OK] Search for Copyright references, and if they are in headers, make sure > > these files containing them are mentioned in the LICENSE file. > > [MINOR] Build the project according to the information in the README.md > > file. > > > > * Readme could use an addition to add mockgen to the prerequisites > > * When building the second part “make build” I’m getting a fatal error: > > * “fatal: not a git repository (or any of the parent directories): > > .git” > > > > > > Von: Justin Mclean > > Datum: Mittwoch, 27. Dezember 2023 um 06:26 > > An: incubator general apache > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1 (Round2) > > Hi, > > > > +1 (binding) > > > > In the source release, I checked: > > - incubating in artifacts name > > - signatures and hashes are correct > > - LICENSE and NOTICE are fine > > - DISCLAIMER exists > > - all files have ASF headers > > - no unexpected binary files > > - my system isn't setup to compile it > > > > In the REDME.md it suggests that people run the latest non-released > > version; please don't do this. [1] > > > > Kind Regards, > > Justin > > > > 1. https://www.apache.org/legal/release-policy.html#what > > - > 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: clutch analysis part 1 failing: status pages not updating
Thank you Dave, I am not in a hurry either just wanted to make sure it was known. I looked at the code which seems complicated enough to break things badly. My python knowledge is limited, and I am not going to attempt to fix this for you. Cheers, Wilfred > On 5 Jan 2022, at 11:06, Dave Fisher wrote: > > Hi - > > This broke because clutch2.py needs to be updated to use lists.apache.org. > > # Currently prefer these, but consider switch to lists.apache.org > > MAIL_LIST_URL = "http://mail-archives.apache.org/mod_mbox/“ > > The code is here: > https://svn.apache.org/repos/asf/incubator/public/trunk/clutch2.py - it’s > large and the mailing list stuff is complicated. > > The equivalent new url looks like > https://lists.apache.org/api/preferences.lua which provides a json structure > which can be reused in a good way. It’s just that there will be additional > work. > > I doubt I’ll have time to address this before the weekend. > > Regards, > Dave > >> On Jan 4, 2022, at 1:36 PM, Wilfred Spiegelenburg >> wrote: >> >> I was trying to figure out why my update to the status page for YuniKorn was >> not showing up. >> I can see that the clutch data had not been updated for a couple of days >> also [1]. >> The build emails [2] point to a failure since build 808 [3]. The news added >> to the Inlong status page before my YuniKorn change has not been published >> either. >> >> Could someone please have a look that understands more of this build. I >> could not find a data change that could have triggered this failure. >> >> Wilfred >> >> [1] https://incubator.apache.org/clutch/ >> [2] https://lists.apache.org/thread/oylx5jp8m1xpvs1m32kq7o1otsrbb9cj >> [3] >> https://ci-builds.apache.org/job/Incubator/job/Incubator-SVN-Clutch-Analysis-part-1/808/console >> - >> 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 > Wilfred Spiegelenburg Senior Staff Software Engineer <https://www.cloudera.com/>
clutch analysis part 1 failing: status pages not updating
I was trying to figure out why my update to the status page for YuniKorn was not showing up. I can see that the clutch data had not been updated for a couple of days also [1]. The build emails [2] point to a failure since build 808 [3]. The news added to the Inlong status page before my YuniKorn change has not been published either. Could someone please have a look that understands more of this build. I could not find a data change that could have triggered this failure. Wilfred [1] https://incubator.apache.org/clutch/ [2] https://lists.apache.org/thread/oylx5jp8m1xpvs1m32kq7o1otsrbb9cj [3] https://ci-builds.apache.org/job/Incubator/job/Incubator-SVN-Clutch-Analysis-part-1/808/console - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache YuniKorn (Incubating) 0.12.1 (RC1)
> On 27 Dec 2021, at 10:29, Justin Mclean wrote: > > Hi, > > +1 (binding) > > I checked: > - incubating in name > - DISCLAIMER exists > - LICENSE and NOTICE are fine > - No unexpected binary fines in the releases > - All files have ASF headers > - Can't compile but that’s probably my setup (OSX) > > I did notice a couple of references to cloudera’s JIRA e.g > https://jira.cloudera.com/browse/COMPX-4041and > https://jira.cloudera.com/browse/COMPX-4042 which seems a little unusual? Filed YUNIKORN-987 to remove them. They are totally irrelevant and slipped into an earlier release. Wilfred - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Mentors] podling report text
ng > Comments: > - [ ] (teaclave) Furkan Kamaci > Comments: > - [ ] (teaclave) Jianyong Dai > Comments: > - [ ] (teaclave) Matt Sicker > Comments: > - [ ] (teaclave) Zhijie Shen > Comments: > - [ ] (teaclave) Gordon King > Comments: > > ### IPMC/Shepherd notes: > > > > > ## Training > > The Training project aims to develop resources which can be used for > training purposes in various media formats, languages and for various Apache > and non-Apache target projects. > > Training has been incubating since 2019-02-21. > > ### Three most important unfinished issues to address before graduating: > > 1. > 2. > 3. > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > ### How has the community developed since the last report? > > > ### How has the project developed since the last report? > > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [ ] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > -XX-XX > > ### When were the last committers or PPMC members elected? > > > ### Have your mentors been helpful and responsive? > Are things falling through the cracks? If so, please list any > open issues that need to be addressed. > > ### Is the PPMC managing the podling's brand / trademarks? > Are 3rd parties respecting and correctly using the podlings > name and brand? If not what actions has the PPMC taken to > correct this? Has the VP, Brand approved the project name? > > ### Signed-off-by: > > - [ ] (training) Craig Russell > Comments: > - [ ] (training) Christofer Dutz > Comments: > - [ ] (training) Justin Mclean > Comments: > - [ ] (training) Lars Francke > Comments: > > ### IPMC/Shepherd notes: > > > > > ## YuniKorn > > YuniKorn is a standalone resource scheduler responsible for scheduling batch > jobs and long-running services on large scale distributed systems running in > on-premises environments as well as different public clouds. > > YuniKorn has been incubating since 2020-01-21. > > ### Three most important unfinished issues to address before graduating: > > 1. > 2. > 3. > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > ### How has the community developed since the last report? > > > ### How has the project developed since the last report? > > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [ ] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > -XX-XX > > ### When were the last committers or PPMC members elected? > > > ### Have your mentors been helpful and responsive? > Are things falling through the cracks? If so, please list any > open issues that need to be addressed. > > ### Is the PPMC managing the podling's brand / trademarks? > Are 3rd parties respecting and correctly using the podlings > name and brand? If not what actions has the PPMC taken to > correct this? Has the VP, Brand approved the project name? > > ### Signed-off-by: > > - [ ] (yunikorn) Junping Du > Comments: > - [ ] (yunikorn) Felix Cheung > Comments: > - [ ] (yunikorn) Jason Lowe > Comments: > - [ ] (yunikorn) Holden Karau > Comments: > - [ ] (yunikorn) Wei-Chiu Chuang > Comments: > - [ ] (yunikorn) Luciano Resende > Comments: > > ### IPMC/Shepherd notes: > > > > > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > Wilfred Spiegelenburg Senior Staff Software Engineer <https://www.cloudera.com/>
Re: Incubator disclaimer missing from several podling websites
Text on the website has been fixed. Wilfred > On 17 Sep 2021, at 22:35, sebb wrote: > > As the subject says: the disclaimer is missing from the following websites: > > Age > BlueMarlin (no website at all) > Doris - does not work at all without JavaScript > Inlong - does not work without Javascript > Kyuubi > Liminal > Linkis - no website yet > Nemo > > Yunikorn has some incorrect text: ", sponsored by the name of Apache > TLP sponsor." > > Milagro looks OK in a browser, but uses a redirect that does not work > for automated checkers. > Given that the redirect is unconditional, this would be better done by > the server, e.g. through .htaccess. > > It should be present on all pages. > > - > 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] Download links need to use closer.lua not closer.cgi or mirrors.cgi
YuniKorn site fixed. New version of the site deployed using closer.lua Wilfred > On 17 Sep 2021, at 08:59, Justin Mclean wrote: > > Hi, > > Download links should use https://www.apache.org/dyn/closer.lua not > closer.cgi or mirrors.cgi > > Projects that should check this: > Doris > EventMesh > Heron > HiveMall > Milagro > Pegasus > PonyMail > Shenyu > Spot > StreamPipes > Teaclave > Yunikorn > > Again this is generated by a script so may not be 100% accurate. > > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > Wilfred Spiegelenburg Senior Staff Software Engineer <https://www.cloudera.com/>
Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0
We are not using any of the polyfills except for the one that is mandatory (zone.js) which is part of the angular framework. The angular framework is not part of the source tar. The zone.js file is also not part of the source tar. The polyfills.ts file just defines that it will be imported when you build the app. After cleanup the polyfills.ts file would be a license header and 1 import statement. Is that acceptable? Wilfred > On 30 Jul 2021, at 18:55, Justin Mclean wrote: > > Hi, > >> The base settings are code generated. The software that generates these base >> setting is angular. It shows up as a MIT license [1]. >> The file content after the generation is part of the created project which >> then gets customised. > > > You might want to double check that. A quick glance that this page [1] > mentions polyfills that are either public domain, MIT or Apache licensed. > Obviously all of these licenses are compatible but it would be good to know > which it is. > > Kind Regards, > Justin > > 1. https://angular.io/guide/browser-support > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > Wilfred Spiegelenburg Staff Software Engineer <https://www.cloudera.com/>
Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0
> On 30 Jul 2021, at 18:22, Justin Mclean wrote: > > Hi, > >> [3] is a settings file. The comments should have been cleaned up when the >> settings were customised. > > Presumably the file (and it comments) are copyright to someone and under some > license? Do you know who/what that is? > The base settings are code generated. The software that generates these base setting is angular. It shows up as a MIT license [1]. The file content after the generation is part of the created project which then gets customised. Wilfred [1] https://angular.io/license - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0
[1] was added as part of jira YUNIKORN-505. [2] was added as part of jira YUNIKORN-427. Both are apache files: jiras have been logged to add the headers. [3] is a settings file. The comments should have been cleaned up when the settings were customised. I have filed a jira for the cleanup. The file was already in YuniKorn v0.10 Wilfred > On 30 Jul 2021, at 15:46, Justin Mclean wrote: > > Hi, > > -1 (binding) as there files missing headers and a possible license issue. If > the licenses of these files are clarified my vote can change. > > I checked: > - incubating in name > - signatures and hashes are fine > - DISCLAIMER exists > - LICENSE may be OK, except this file? [3] > - NOTICE is fine > - No unexpected binary files > - A couple of files are missing ASF headers > > A couple of files are missing ASF headers, where did they come from and how > are these licensed? [1][2] > > Is this file actually an ASF file or is it a 3rd party file? [3] If it a 3rd > party file how is it licensed? > > Kind Regards, > Justin > > 1. /core/pkg/scheduler/mock_plugin_test.go > 2. /k8shim/test/e2e/predicates/predicates_test.go > 3. /web/src/polyfills.ts > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > Wilfred Spiegelenburg Staff Software Engineer <https://www.cloudera.com/>
Podling reports for July?
I have not seen any mention of the podling reports for July on the mailing lists. The wiki does not have deadlines set. I created report for YuniKorn. Is there something I missed? Wilfred - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Old releases in release area
YuniKorn had been done, download links updated Wilfred > On 27 Apr 2021, at 14:59, Justin Mclean wrote: > > Hi, > > A few projects need to clean up their release area as they have multiple > releases listed in then, only the last release need to be listed as the older > releases are archived. [16] > > The projects are: > Crail [1] > DataLab [2] > Doris [3] > Flagon [4] > Hivemall [5] > Livy [6] > Milagro [7] > MXNet [8] > Nemo [9] > NLPCraft [10] > NuttX [11] > Pinot [12] > Toree [13] > Tuweni [14] > YuniKorn [15] > > Thanks, > Justin > > 1. https://dist.apache.org/repos/dist/release/incubator/crail/ > 2. https://dist.apache.org/repos/dist/release/incubator/datalab/ > 3. https://dist.apache.org/repos/dist/release/incubator/doris/ > 4. https://dist.apache.org/repos/dist/release/incubator/flagon/ > 5. https://dist.apache.org/repos/dist/release/incubator/hivemall/ > 6. https://dist.apache.org/repos/dist/release/incubator/livy/ > 7. https://dist.apache.org/repos/dist/release/incubator/milagro/ > 8. https://dist.apache.org/repos/dist/release/incubator/mxnet/ > 9 https://dist.apache.org/repos/dist/release/incubator/nemo/ > 10. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/ > 11. https://dist.apache.org/repos/dist/release/incubator/nuttx/ > 12. https://dist.apache.org/repos/dist/release/incubator/pinot/ > 13. https://dist.apache.org/repos/dist/release/incubator/toree/ > 14. https://dist.apache.org/repos/dist/release/incubator/tuweni/ > 15. https://dist.apache.org/repos/dist/release/incubator/yunikorn/ > 16 https://archive.apache.org/dist/incubator/ > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > Wilfred Spiegelenburg Staff Software Engineer <https://www.cloudera.com/>
[RESULT][VOTE] Release Apache YuniKorn (Incubating) 0.9.0
Thanks to everyone that participated. The vote to release Apache YuniKorn (incubating) 0.9.0 is now closed. The vote PASSED with 3 binding +1, 0 non binding +1 and 0 -1 votes: Binding votes: - Felix - Jason - Wangda Vote thread can be found at: https://lists.apache.org/thread.html/r15634fd6393ee3f00192c1c7cded046d91355865497db06e0e0050d3%40%3Cgeneral.incubator.apache.org%3E I will be working on publishing the release artefacts. Thank you, Wilfred Apache YuniKorn (incubating)
[VOTE] Release Apache YuniKorn (Incubating) 0.9.0
Hello IPMC The Apache YuniKorn community has voted and approved the release Apache YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members review and vote in this release. YuniKorn is a standalone, universal resource scheduler that can support both long-running and batch workloads. The current release provides a fully functional resource scheduler for K8s. YuniKorn community vote thread: https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E Vote result thread: https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E Issues included in this release: https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799 The release candidate: https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/ This release has been signed with a PGP available here: https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS Git tag for the release: - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0 - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0 - https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0 - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0 The vote will be open for at least 72 hours or until the necessary number of votes is reached. Please vote accordingly: [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0 [ ] +0 [ ] -1 Do not approve (please specify the reason) Thanks, Wilfred Spiegelenburg Apache YuniKorn (Incubating)
