[MENTORS] June report timeline - reports due June 2024

2024-05-15 Thread jmclean
Dates for next board report: Wed June 05 - Podling reports due by end of day Sun June 09 - Shepherd reviews due by end of day Sun June 09 - Summary due by end of day Tue June 11 - Mentor signoff due by end of day Wed June 12 - Report submitted to Board Wed June 19 - Board meeting Expected to

Re: [QUESTION] KIE - NPM package names

2024-05-15 Thread Dave Fisher
Here’s my 2 cents. Incubation is a journey, and if there are parts that are yet to be compliant that should be fine. In the end all will be squared away. For the IPMC - should we have something like DISCLAIMER-WIP for binary convenience packaging? Best, Dave > On May 15, 2024, at 1:13 PM,

Re: [QUESTION] KIE - NPM package names

2024-05-15 Thread Tiago Bento
Tison, Thanks for the reply! On Wed, May 15, 2024 at 1:43 PM tison wrote: > > We have an official account on NPM [1] and the associated org [2] (cc @Mark > Thomas IIRC who manages this account). > > [1] https://www.npmjs.com/~theasf > [2] https://www.npmjs.com/org/apache > > Both of these

Re: [QUESTION] KIE - NPM package names

2024-05-15 Thread tison
We have an official account on NPM [1] and the associated org [2] (cc @Mark Thomas IIRC who manages this account). [1] https://www.npmjs.com/~theasf [2] https://www.npmjs.com/org/apache Both of these associations can improve the verification and brand for your release, while you may use the

Re: [QUESTION] KIE - NPM package names

2024-05-15 Thread Tiago Bento
Shawn, Does that mean you didn't publish anything to NPM as part of your releases while in the incubator? On Wed, May 15, 2024 at 12:31 PM Shawn Yang wrote: > > Hi Tiago, > > From the current incubator release policy, you need to rename all npm > packages to apache-xxx before releasing. The

Re: [QUESTION] KIE - NPM package names

2024-05-15 Thread Shawn Yang
Hi Tiago, >From the current incubator release policy, you need to rename all npm packages to apache-xxx before releasing. The packages released before should be on to left intact. I came across same issue when we release apache fury. In your case, most packages starts with kie. Fury has similar

Re: [QUESTION] KIE - NPM package names

2024-05-15 Thread PJ Fanning
Podlings are allowed some leeway. Ideally, you should aim to eventually rename your binary artifacts to include Apache KIE branding. I think it should be ok to make an initial release with the existing naming, especially if you comply with the other requirements in the NPM distribution guidelines

[QUESTION] KIE - NPM package names

2024-05-15 Thread Tiago Bento
Hi general@incubator, The distribution guidelines [1] say packages published to NPM should be named `apache-`, however, at KIE, we have a somewhat big set of packages that are published under these scopes: - @kie-tools/* - @kie-tools-core/* - @kie-tools-scripts/* There are also some VS Code