Re: KIE - Question about "staging" binaries/artifacts
Thank you all for the inputs, but we still seeking clarity on NPM. We - Apache KIE podling - are trying to get a single release procedure for all binaries, but with lack of NPM infra for staging makes it really complex. I notice that OpenDAL publishes to NPM, is there anyone involved in OpenDAL here that could help us sort this out? For container images, we have similar issue with staging… less of issue is the build. On Mon, May 13, 2024 at 5:50 PM PJ Fanning wrote: > I may be misinterpreting 'live website' but it is quite common for Apache > projects to have a 'staged' version of their website (i.e. a pre-release > version of the web site). > https://kie.apache.org/ could also have a https://kie.staged.apache.org/ > > https://pekko.staged.apache.org/ is a staged version of > https://pekko.apache.org/ (for instance) > > See the .asf.yaml docs: > > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain > > For quay.io, you could raise a JIRA for INFRA team to discuss supporting > an > account for deployments. Or maybe, the KIE PPMC could set up an account and > share the credentials among the KIE release managers. > > > > > > On Mon, 13 May 2024 at 22:30, Tiago Bento wrote: > > > Thank you for the prompt responses. > > > > We're aware that for Maven artifacts we could "promote" them after > > publishing them to a staging repo. > > > > But for container images, for example, I'm not sure I understand how such > > process would look like. Prior to being in Apache, we used to push images > > to Quay.io under a "[version]-prerelease" tag for "staging". Then we > would > > have a completely new build when we would be ready for a actual release. > > > > I guess for other kinds of artifacts, like the NPM packages, live > > websites, and Chrome and VS Code Extensions, I also still don't > understand > > very well how this could be achieved... Any advice? It's hard to tell > what > > "promoting" those would look like, as for example, one of our live > websites > > is hosted in GitHub Pages. > > > > Thanks again! > > > > Regards, > > > > Tiago Bento > > > > > > > > On 2024/05/13 20:35:35 PJ Fanning wrote: > > > For Java jars, the ASF has repository.apache.org - a Nexus instance > that > > > can be used to stage and later release jars. > > > The login credentials are the same credentials you use to access other > > ASF > > > resources. > > > > > > > > > On Mon, 13 May 2024 at 21:28, Enrico Olivelli > > wrote: > > > > > > > Tiago, > > > > > > > > > > > > Il Lun 13 Mag 2024, 22:11 Tiago Bento ha > > scritto: > > > > > > > > > Hello general@incubator, > > > > > > > > > > My name is Tiago Bento (@tiagobento on GitHub), and I’m one of the > > > > > committers of the KIE project of the incubator. > > > > > > > > > > We’re gearing towards our first release under Apache, and we’re > very > > > > > excited to be approaching this important milestone. > > > > > > > > > > Some resources [1] [2] that we found already guided us in the right > > > > > direction, but still, some questions remain about the release > process > > > > > itself. > > > > > > > > > > We understand that in Apache, releases are done from the source > code > > > > > perspective, not the binaries/artifacts’. However, we still don’t > > > > > understand very clearly how Apache verifies signatures and > checksums > > > > > of the binaries that are eventually published. > > > > > > > > > > > > > It is better that in case you provide binaries to your users those > > binaries > > > > are released together with the sources during the same VOTE. > > > > > > > > Having reproducible builds would help a lot, but that's not always > > easy to > > > > do. > > > > > > > > In your VOTE you should stage all the sources and binaries, signed > > with the > > > > same signature (by the release manager) and the same artifacts will > be > > > > promoted in case of a successful VOTE. > > > > > > > > The PMC can at least verify the signatures and any digests that are > > staged > > > > as part of the VOTE. > > > > > > > > Please note that if you don't have a reproducible build the PMC will > > never > > > > be able to verify that the binaries match the sources. > > > > > > > > > > > > > The KIE project has three main types of consumable artifacts: Maven > > > > > modules, Container images, and NPM packages; and we also maintain > > some > > > > > live web pages like https://sandbox.kie.org, and extensions for > > Chrome > > > > > [3] and VS Code [4]. > > > > > > > > > > For the release to be voted, we understand we have to provide a > .zip > > > > > file containing the source code along with instructions on how to > > > > > build it. Once/if approved, our understanding is that the exact > same > > > > > approved source code could be used to build and publish > > > > > binaries/artifacts of any sort to public registries/repositories. > > > > > > > > > > I’m laying out all the information I could gather so
Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name
+1 (non-binding) Alex On Tue, May 7, 2024 at 8:35 PM Francis Chuang wrote: > +1 (binding) > > I think this is a pragmatic and well-thought out approach. > > Francis > > On 8/05/2024 10:31 am, 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: [VOTE] Accept GraphAr into the ASF Incubator
+1 (non-binding) On Fri, Mar 15, 2024 at 5:08 AM Charles Zhang wrote: > +1 (binding) > > Best wishes, > Charles Zhang > from Apache InLong > > > Xiaoqiao He 于2024年3月15日周五 16:44写道： > > > +1 (binding) > > Good Luck! > > > > Best Regards, > > - He Xiaoqiao > > > > On Fri, Mar 15, 2024 at 4:33 PM PJ Fanning wrote: > > > > > +1 binding > > > > > > On Fri, 15 Mar 2024 at 09:18, Kent Yao wrote: > > > > > > > > +1 binding & Good luck! > > > > > > > > Kent Yao > > > > > > > > Calvin Kirs 于2024年3月15日周五 14:02写道： > > > > > > > > > > +1 binding > > > > > > > > > > On Fri, Mar 15, 2024 at 1:58 PM Yu Li wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > With positive feedback from the proposal discussion [1], I am > > > starting > > > > > > this official vote to accept GraphAr into the Incubator. Here is > > the > > > > > > proposal: > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/GraphArProposal > > > > > > > > > > > > Please cast your vote: > > > > > > [ ] +1, accept GraphAr into the Incubator > > > > > > [ ] +0, I don't care either way > > > > > > [ ] -1, do not accept GraphAr into the Incubator, because... > > > > > > > > > > > > The vote will open for one week from today, 15 March, 2024. > Thanks. > > > > > > > > > > > > Best Regards, > > > > > > Yu > > > > > > > > > > > > [1] > > https://lists.apache.org/thread/bldz3rnp8nvhlmrd2gqkl30fgk9z3zhx > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best wishes！ > > > > > CalvinKirs > > > > > > > > - > > > > 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: [VOTE] Podling web sites: make (incubator.) optional in podling urls
+1 (non-binding) On Tue, Mar 12, 2024 at 6:14 PM Justin Mclean wrote: > > +1 binding > > - > 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: Request for Temporary Exception for LGPL Dependency in Apache KIE Podling
tison, First and foremost, as a past Hibernate contributor with personal relationship with Hibernate team members I’m very aware of this plan to change license… and they are finally reaching a point that this has been communicated in public :) - so I have a high level of confidence that the team behind this is actively working on this… But, relicensing is not simple… and we definitely should plan for the situation that Hibernate just can’t do it. In this case, we have a few options (non-exclusive): - adjust API level to just JPA and hack around some tests using OpenJPA - in case of core operations, that might be risky to use unsupported library (ie. OpenJPA for Quarkus in a production code)… we can always go back to JDBC. So, we are not neglecting and are prepared to react in different ways. On Tue, Mar 5, 2024 at 12:39 PM tison wrote: > Thanks for reaching out Alex :D > > I agree with PJ and emphasize that we should highlight the license > issue on release. > > Also, for others in this thread, the thorough solution described above is: > > > The Hibernate team is in the process of relicensing from LGPL to Apache > License 2.0. > > To Alex: > > How much confidence do you have in this direction? Are you involved in > this effort? > > What if the relicensing doesn't happen? Do you have an alternative plan? > > Best, > tison. > > Alex Porcelli 于2024年3月6日周三 01:25写道： > > > > Thank you PJ! This is very helpful! > > > > On Tue, Mar 5, 2024 at 12:23 PM PJ Fanning wrote: > > > > > > https://incubator.apache.org/policy/incubation.html#disclaimers > > > > > > Have a look at the Disclaimers doc. If you use the WIP Disclaimer then > you > > > can do releases that are not fully ASF compliant. It would be good to > > > document clearly about this dependency license issue. > > > > > > > > > > > > On Tue 5 Mar 2024, 17:53 Alex Porcelli, wrote: > > > > > > > Dear Members of the Apache Incubator, > > > > > > > > I hope this email finds you well. My name is Alex Porcelli, and I am > > > > part of the Apache KIE podling community [1]. I am reaching out to > > > > discuss a matter regarding a dependency we have under LGPL, which > > > > falls under Category X according to Apache guidelines. > > > > > > > > The dependency is Hibernate ORM [2], the only supported JPA provider > > > > for Quarkus [3] - the primary runtime provider for Apache KIE > podling. > > > > > > > > However, I'd like to emphasize the urgency of our situation. Our > > > > community has dedicated substantial effort over the past six months > to > > > > prepare for our initial Apache release. Unfortunately, this delay in > > > > releasing Apache KIE is unprecedented for this community, and it is > > > > critical for us to deliver new releases promptly. Not only does our > > > > large user base eagerly anticipate a new release, but older versions > > > > may also pose security vulnerabilities (CVEs). Additionally, with our > > > > previous release process through Red Hat decommissioned, Apache now > > > > stands as our sole means of distribution. > > > > > > > > Given these circumstances, I kindly ask the Apache Incubator to > > > > consider granting us a temporary exception to maintain the LGPL > > > > dependency for our initial releases. We understand the importance of > > > > adhering to Apache licensing requirements and are willing to make > > > > necessary adjustments while ensuring compliance. However, we believe > > > > that allowing us to proceed with proper disclaimers in place would > > > > enable us to maintain momentum and meet the expectations of our user > > > > community. > > > > > > > > Furthermore, I would like to inform you that the Hibernate team is in > > > > the process of relicensing from LGPL to ASLv3, as indicated in their > > > > recent blog post [4]. This transition aligns with our long-term goals > > > > and demonstrates our commitment to compliance with Apache guidelines. > > > > > > > > We are open to any guidance or suggestions from the Incubator PMC on > > > > how best to proceed. > > > > > > > > Thank you for considering our request. > > > > > > > > Best regards, > > > > Alex Porcelli > > > > Apache KIE Podling Community Member > > > > > > > > [1] - Apache KIE: https://kie.apache.org/ > > > > [2]
Re: Request for Temporary Exception for LGPL Dependency in Apache KIE Podling
Thank you PJ! This is very helpful! On Tue, Mar 5, 2024 at 12:23 PM PJ Fanning wrote: > > https://incubator.apache.org/policy/incubation.html#disclaimers > > Have a look at the Disclaimers doc. If you use the WIP Disclaimer then you > can do releases that are not fully ASF compliant. It would be good to > document clearly about this dependency license issue. > > > > On Tue 5 Mar 2024, 17:53 Alex Porcelli, wrote: > > > Dear Members of the Apache Incubator, > > > > I hope this email finds you well. My name is Alex Porcelli, and I am > > part of the Apache KIE podling community [1]. I am reaching out to > > discuss a matter regarding a dependency we have under LGPL, which > > falls under Category X according to Apache guidelines. > > > > The dependency is Hibernate ORM [2], the only supported JPA provider > > for Quarkus [3] - the primary runtime provider for Apache KIE podling. > > > > However, I'd like to emphasize the urgency of our situation. Our > > community has dedicated substantial effort over the past six months to > > prepare for our initial Apache release. Unfortunately, this delay in > > releasing Apache KIE is unprecedented for this community, and it is > > critical for us to deliver new releases promptly. Not only does our > > large user base eagerly anticipate a new release, but older versions > > may also pose security vulnerabilities (CVEs). Additionally, with our > > previous release process through Red Hat decommissioned, Apache now > > stands as our sole means of distribution. > > > > Given these circumstances, I kindly ask the Apache Incubator to > > consider granting us a temporary exception to maintain the LGPL > > dependency for our initial releases. We understand the importance of > > adhering to Apache licensing requirements and are willing to make > > necessary adjustments while ensuring compliance. However, we believe > > that allowing us to proceed with proper disclaimers in place would > > enable us to maintain momentum and meet the expectations of our user > > community. > > > > Furthermore, I would like to inform you that the Hibernate team is in > > the process of relicensing from LGPL to ASLv3, as indicated in their > > recent blog post [4]. This transition aligns with our long-term goals > > and demonstrates our commitment to compliance with Apache guidelines. > > > > We are open to any guidance or suggestions from the Incubator PMC on > > how best to proceed. > > > > Thank you for considering our request. > > > > Best regards, > > Alex Porcelli > > Apache KIE Podling Community Member > > > > [1] - Apache KIE: https://kie.apache.org/ > > [2] - Hibernate ORM: https://hibernate.org/orm/ > > [3] - Quarkus: https://quarkus.io/ > > [4] - Blog post on relicensing: https://in.relation.to/2023/11/18/license/ > > > > - > > 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
Request for Temporary Exception for LGPL Dependency in Apache KIE Podling
Dear Members of the Apache Incubator, I hope this email finds you well. My name is Alex Porcelli, and I am part of the Apache KIE podling community [1]. I am reaching out to discuss a matter regarding a dependency we have under LGPL, which falls under Category X according to Apache guidelines. The dependency is Hibernate ORM [2], the only supported JPA provider for Quarkus [3] - the primary runtime provider for Apache KIE podling. However, I'd like to emphasize the urgency of our situation. Our community has dedicated substantial effort over the past six months to prepare for our initial Apache release. Unfortunately, this delay in releasing Apache KIE is unprecedented for this community, and it is critical for us to deliver new releases promptly. Not only does our large user base eagerly anticipate a new release, but older versions may also pose security vulnerabilities (CVEs). Additionally, with our previous release process through Red Hat decommissioned, Apache now stands as our sole means of distribution. Given these circumstances, I kindly ask the Apache Incubator to consider granting us a temporary exception to maintain the LGPL dependency for our initial releases. We understand the importance of adhering to Apache licensing requirements and are willing to make necessary adjustments while ensuring compliance. However, we believe that allowing us to proceed with proper disclaimers in place would enable us to maintain momentum and meet the expectations of our user community. Furthermore, I would like to inform you that the Hibernate team is in the process of relicensing from LGPL to ASLv3, as indicated in their recent blog post [4]. This transition aligns with our long-term goals and demonstrates our commitment to compliance with Apache guidelines. We are open to any guidance or suggestions from the Incubator PMC on how best to proceed. Thank you for considering our request. Best regards, Alex Porcelli Apache KIE Podling Community Member [1] - Apache KIE: https://kie.apache.org/ [2] - Hibernate ORM: https://hibernate.org/orm/ [3] - Quarkus: https://quarkus.io/ [4] - Blog post on relicensing: https://in.relation.to/2023/11/18/license/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Have Amoro join the Incubator
+1 (non-binding) On Sat, Mar 2, 2024 at 8:44 PM Justin Mclean wrote: > Hi, > > Following on from the discussion of the Amoro proposal [1][2], let's vote > on having it join the Incubator. > > Please cast your vote: > > [ ] +1, have it join the Incubator as an incubating project > [ ] +0, I have no strong opinion either way > [ ] -1, do not have it join the Incubator because... > > Kind Regards, > Justin > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal > 2. https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00
Re: Podling web sites: .incubator. required?
+1 (non-binding) On Wed, Feb 28, 2024 at 10:01 AM Suyan wrote: > > +1 non-binding > > This looks a little more concise. > > Sincerely, > Suyan > > Craig Russell 于2024年2月28日周三 08:18写道： > > > > It was policy at one point for podlings to have .incubator. in their home > > page url. But many podlings now have transitioned away from this and simply > > use their podling.apache.org name. The policy document is a bit iffy on the > > subject: > > https://incubator.apache.org/guides/branding.html > > > > > After a podling has been approved, the lists are created, and the initial > > > code drop has commenced, you MUST refer to the podling as Apache > > > Podling-Name AND mention that the project is under Incubation. Suitable > > > mentions include: > > > > > > • Inclusion of the http://podling-name.incubator.apache.org/ URL > > > > > > • Apache Podling-Name is currently undergoing Incubation at the > > > Apache Software Foundation. > > > > > > The Incubator PMC (IPMC) must approve other references before you publish > > > them. You only need to make these statements upon the first reference to > > > the podling in a document. > > > > I feel this is very much like the former requirement for mail lists to > > include incubator.apache.org as part of their name. This turned out to be a > > huge waste of time for the podling as well as for infra when upon > > graduation all of the documentation and tooling for mail lists had to > > change. > > > > I would propose that as part of our official policy we recommend the > > podling's url as https://podling.apache.org and get rid of the .incubator. > > in the url. > > > > WDYT? > > > > Craig L Russell > > c...@apache.org > > > > > > - > > 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Update Website Template (WAS: Help to get the Wayang project website in shape)
+1 (non-binding) Awesome initiative! On Wed, Feb 14, 2024 at 7:48 AM Twice wrote: > +1. > > Docusaurus is super suitable for building open-source project > websites, and currently being used by lots of ASF projects. > > Replacing the original website template makes sense to me. > > Best, > Twice > > On Wed, Feb 14, 2024 at 3:54 PM Suyan wrote: > > > > +1, that's great! > > > > Sincerely, > > Suyan > > > > tison 于2024年2月4日周日 23:17写道： > > > > > > Hi, > > > > > > I finally find some time to prepare a demo for the new website > template [1]. > > > > > > It may still open to be improved including a download page template > > > and a community page template, as well as some guides as its docs. But > > > I'd like to first collecting feedback and finding which PMC is > > > responsible for this repository [2]. > > > > > > The background is that our current template is quite old and not > > > updated for the past six years. Few people understand those techniques > > > and have a hard time to build their own site. Also, new policy > > > compliance and new techniques benefits can be included in the template > > > to help new projects (podlings) build a wonderful site. > > > > > > I'm glad to maintain this repo but I find myself has no permission > > > over this repo. So again, which PMC is responsible for this > > > repository? > > > > > > Best, > > > tison. > > > > > > [1] > https://github.com/tisonkun/apache-website-template/tree/docusaurus > > > [2] https://github.com/apache/apache-website-template/ > > > > > > Alex Porcelli 于2024年1月30日周二 04:53写道： > > > > > > > > Another shout-out for tison and the Apache Fury to provide such a > nice > > > > starting point for new websites. > > > > > > > > I managed to put, for now, a simple placeholder website for Apache > KIE > > > > (incubation). > > > > > > > > Thank you tison and the Apache Fury community! > > > > > > > > On Fri, Jan 26, 2024 at 4:10 AM Xuanwo wrote: > > > > > > > > > > > I managed to move our old website to Docusaurus in one day - > using the template > > > > > > structure from Fury, if you don’t mind. > > > > > > > > > > Congrats! > > > > > > > > > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote: > > > > > > Hey tison, > > > > > > > > > > > > Thank you for the head-up. I managed to move our old website to > > > > > > Docusaurus in one day - using the template structure from Fury, > if you > > > > > > don’t mind. Awesome stuff, would love when we’d had a template > for the > > > > > > podlings to setup a good looking, SEO friendly project page. > That’s > > > > > > needed to grow the community! > > > > > > > > > > > > Cheers, thanks again, > > > > > > —Alex > > > > > > > > > > > >> On Jan 25, 2024, at 12:01, tison wrote: > > > > > >> > > > > > >> Hi Alexander, > > > > > >> > > > > > >> I use Docusaurus for Kvrocks and Fury. Their configuration > should be > > > > > >> straightforward to follow already. The most simple one now is > > > > > >> https://github.com/apache/incubator-fury-site. > > > > > >> > > > > > >> Also, Docu is well-documented https://docusaurus.io/docs. > > > > > >> > > > > > >> I'm thinking of updating the website template [1] with Docu but > have > > > > > >> not yet had time and understand which PMC manages this project. > > > > > >> > > > > > >> Best, > > > > > >> tison. > > > > > >> > > > > > >> [1] https://github.com/apache/apache-website-template > > > > > >> > > > > > >> Alexander Alten-Lorenz > 于2024年1月25日周四 18:20写道： > > > > > >>> > > > > > >>> Hi Xuanwo, > > > > > >>> > > > > > >>> Thank you, highly appreciated! Do you have any how-to for > setting Docusaurus up? > > > > > >>> > > > > >
Re: Help to get the Wayang project website in shape
Another shout-out for tison and the Apache Fury to provide such a nice starting point for new websites. I managed to put, for now, a simple placeholder website for Apache KIE (incubation). Thank you tison and the Apache Fury community! On Fri, Jan 26, 2024 at 4:10 AM Xuanwo wrote: > > > I managed to move our old website to Docusaurus in one day - using the > > template > > structure from Fury, if you don’t mind. > > Congrats! > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote: > > Hey tison, > > > > Thank you for the head-up. I managed to move our old website to > > Docusaurus in one day - using the template structure from Fury, if you > > don’t mind. Awesome stuff, would love when we’d had a template for the > > podlings to setup a good looking, SEO friendly project page. That’s > > needed to grow the community! > > > > Cheers, thanks again, > > —Alex > > > >> On Jan 25, 2024, at 12:01, tison wrote: > >> > >> Hi Alexander, > >> > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be > >> straightforward to follow already. The most simple one now is > >> https://github.com/apache/incubator-fury-site. > >> > >> Also, Docu is well-documented https://docusaurus.io/docs. > >> > >> I'm thinking of updating the website template [1] with Docu but have > >> not yet had time and understand which PMC manages this project. > >> > >> Best, > >> tison. > >> > >> [1] https://github.com/apache/apache-website-template > >> > >> Alexander Alten-Lorenz 于2024年1月25日周四 18:20写道： > >>> > >>> Hi Xuanwo, > >>> > >>> Thank you, highly appreciated! Do you have any how-to for setting > >>> Docusaurus up? > >>> > >>> —Alex > >>> > On Jan 25, 2024, at 11:01, Xuanwo wrote: > > Hi, alexander > > > We aren't web designers and we would love to find helping hands to get > > the page in order, including re-organizing and rewriting. > > I'm with the OpenDAL Community, and we also lack web designers. Our > community > opted for Docusaurus[1], which we found easy to start with and set up. It > offers a decent theme suitable for open-source projects. For reference, > you > can check out OpenDAL's homepage[2]. We hope our experience proves > useful. > > [1] https://docusaurus.io/ > [2] https://opendal.apache.org/ > > On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote: > > Hi incubator community, > > > > Would anyone be willing to help the Wayang project with our website? > > We aren't web designers and we would love to find helping hands to get > > the page in order, including re-organizing and rewriting. > > > > thank you, cheers, > > --alexander > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > -- > Xuanwo > > - > 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 > >>> > >> > >> - > >> 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 > > -- > Xuanwo > > - > 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: [QUESTION] Reproducible build for container images
Daniel, That’s exactly the reason. There’s also this link referencing the requirement [1]. https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=287607354#content/view/287607354 Regards, _ Alex Porcelli http://porcelli.me On Tue, Jan 23, 2024 at 9:58 AM Daniel Gruno wrote: > On 1/23/24 15:49, PJ Fanning wrote: > > Hi Alex, > > > > While reproducible builds are a great idea, the Incubator PMC does not > > require them. Plugging away at improving things so that reproducible > > builds can be produced in future is a useful thing to do. > > This may be related to https://issues.apache.org/jira/browse/INFRA-25140 > which *does* require reproducible builds for KIE. > > > > > Regards, > > PJ > > > > On Tue, 23 Jan 2024 at 14:58, Alex Porcelli wrote: > >> > >> In the KIE podling, we regularly publish container images as part of > >> our releases. We've achieved semantically identical images, verified > >> using the 'diffoci' tool. However, due to current Docker/OCI engine > >> limitations, we can't eliminate variations in file metadata caused by > >> automatically appended timestamps. > >> > >> The latest version of Buildkit offers a solution but still needs to be > >> integrated into the build engines. I want to ask the Incubator PMC: Is > >> achieving semantically verifiable images sufficient for now, as we > >> await the integration of Buildkit changes into Docker/OCI build > >> engines? > >> > >> Regards, > >> - > >> Alex > >> Apache KIE PPMC > >> > >> - > >> 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 > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[QUESTION] Reproducible build for container images
In the KIE podling, we regularly publish container images as part of our releases. We've achieved semantically identical images, verified using the 'diffoci' tool. However, due to current Docker/OCI engine limitations, we can't eliminate variations in file metadata caused by automatically appended timestamps. The latest version of Buildkit offers a solution but still needs to be integrated into the build engines. I want to ask the Incubator PMC: Is achieving semantically verifiable images sufficient for now, as we await the integration of Buildkit changes into Docker/OCI build engines? Regards, - Alex Apache KIE PPMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [QUESTION] Oracle JDBC Driver as a test dependency
Thank you all for the valuable inputs... to play safe I opened a ticket [1] with legal for better clarity. [1] https://issues.apache.org/jira/browse/LEGAL-663 On Wed, Jan 10, 2024 at 8:30 PM Justin Mclean wrote: > > Hi, > > > In your source release anything in Category A is fair game. Things in > > Category B are not. Things in Category X never are. > > While correct, that’s not the full story; you also can’t have anything as a > dependency whose license is a category X one. > > Kind Regards, > Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[QUESTION] Oracle JDBC Driver as a test dependency
In KIE podling we have reference for the Oracle JDBC driver being used only for tests [1], however based on this ticket [2], it's not clear if we can continue to use it or this dependency has to be removed. Guidance on this topic would be highly appreciated! Regards, Alex [1] https://github.com/apache/incubator-kie-kogito-runtimes/blob/3aa26113d7e88f0fd7d0331ec20fe392f343afb6/kogito-test-utils/pom.xml#L89-L99 [2] https://issues.apache.org/jira/browse/LEGAL-526 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [KIE] Code import question
Brian hope you don’t mind if I share additional details for the members of the mailing list. Some of the repositories have several stars, followers, historical list of Pull Request and several other relevant metadata associated with them. If a transfer between existing kiegroup and Apache organizations is allowed, all that metadata are preserved. Hopefully this would be possible. Regarding code cleanup, what Brian meant is the files headers changes from existing copyright to the proper Apache headers. Regards, Alex Porcelli PPMC KIE On Fri, Aug 25, 2023 at 4:34 PM Brian Proffitt wrote: > Hey all, > > I was reading the Initial Code Import document[1] and while it says > Infra needs the code attached to a JIRA ticket (after the SGA or CCLA > has been completed), it also seems to say that you can pull all of it > in via a GitHub export-> import operation[2]. > > So, my questions: > > 1) Is a direct import allowed? > 2) If this is yes, I should then create the JIRA ticket to build the > "receiving" Apache repos, and attach the SGA to that, correct? > 3) Cleanup can happen after the code is imported, correct? > > Thanks for your help! > BKP > > [1] https://incubator.apache.org/guides/transitioning_asf.html > [2] > https://incubator.apache.org/guides/transitioning_asf.html#importing_history > > > Brian Proffitt > VP, Marketing & Publicity > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Regards, _ Alex Porcelli http://porcelli.me
Apache infrastructure for CI?
Is there an infrastructure in Apache for CI (Jenkins, etc) for its projects? If yes, where can we find more information on how to onboard? If not, how do projects deal with CI infrastructure? Regards, Alex Porcelli KIE Podling - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
