Hi,
> ▶ shasum -c apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512
> shasum: apache-liminal-0.0.1rc4-INCUBATING-source.tar.gz.sha512: No such file
> or directory
>
> ⍉
> ▶ shasum -a 512 -c
Hi,
Here is my checking list,
[x] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[x] LICENSE and NOTICE files are correct (From[1]).
[x] All files have license headers if necessary.
[x] Install successfully.
PGP signatures are well. However, I got the following
Exactly. Here’s a link -
https://www.apache.org/foundation/marks/naming.html#namesearch
It’s available from here -
https://incubator.apache.org/guides/names.html#podling_suitable_name_search
Regards,
Dave
Sent from my iPhone
> On Jan 27, 2021, at 7:42 PM, Justin Mclean wrote:
>
> Hi,
>
>
Hi Justin:
Thank you for your prompt reply, I understand. And there is one more
question for help:
- NOTICE is missing information from other Apache licensed NOTICE files.
Information from these NOTICE files [5][6][7][10] will need to be added.
We did it in the way of [6] [10]. What is the
Hi,
> 1. If the referenced file source has the original version statement, we
> should keep it as it is and cannot replace it with the Apache v2 statement?
Correct.
> 2. If the referenced file source does not have a version statement, but the
> project of the file has a version statement, do
Hi,
> 1. Is it necessary to remove the description of part B in the above
> screenshot?
I can’t see teh screen shot so not sure what you are asking here sorry.
> 2. If the file source itself does not have a LICENSE authorization statement,
> but the top level of the project is Apache V2 or
Hi,
To help trademarks it would bee best if you provided them with some search
results as described here. [1] Have a look at a couple of the other recent
polling name search JIRAs to get a good idea of what is needed.
Thanks,
Justin
1. http://incubator.apache.org/guides/names.html
Hi,
+1 (binding) but only because of WIP DISCLAIMER. LICENSE is not correct and
source release contains Category B licensed bits.
I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER (WIP) exist but information has not been updated in it
- LICENSE looks OK but I’ve not
Hi Justin,
Regarding the point 3, I have questions:
1. If the referenced file source has the original version statement, we
should keep it as it is and cannot replace it with the Apache v2 statement?
2. If the referenced file source does not have a version statement, but the
project of the file
[image: image.png]
Hi Justin:
Regarding the third point, I don’t quite understand. Regarding [3] [4] [9]:
1. Is it necessary to remove the description of part B in the above
screenshot?
2. If the file source itself does not have a LICENSE authorization
statement, but the top level of the
Thank you for your correction, a PODLINGNAMESEARCH issue has been created
and followed up.
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-188
On Thu, Jan 28, 2021 at 9:21 AM Dave Fisher wrote:
>
>
> > On Jan 27, 2021, at 4:58 PM, vongosling wrote:
> >
> > Agree to raise this issue,
Hi,
> - These files seem to have incorrect headers [1][2][3][4][8][9]. ASF headers
> should include a copyright line and 3rd part headers need to be kept
> unchanged.
Sorry that should be "ASF headers should NOT include a copyright line”
Thanks,
Justin
Hi, Justin
Thanks for your check, we will go through your comments and create jira
correspondingly.
On Thu, Jan 28, 2021 at 10:43 AM Goson zhang wrote:
> Thanks Justin, very complete and detailed guidance, thank you!!
>
> The BDB download problem, if the third-party warehouse cannot let
Thanks Justin, very complete and detailed guidance, thank you!!
The BDB download problem, if the third-party warehouse cannot let everyone
compile, we will make adjustments.
Thanks
Justin Mclean 于2021年1月28日周四 上午10:01写道：
> Hi,
>
> -1 (binding) due to license and notice issues and possible
Hi,
-1 (binding) due to license and notice issues and possible inclusion of
Category X software
It unclear to me if the berkeleydb-je licensing issue has been resolved. I
can’t find any discussion of it on your mailing list. Can someone tell me what
the outcome of this was?
I checked:
-
> On Jan 27, 2021, at 4:58 PM, vongosling wrote:
>
> Agree to raise this issue, even before podling starts. Initial teams need
> to follow up on this potential problem[1]. Let's see how things go :-)
>
> [1] https://issues.apache.org/jira/browse/INFRA-21353
No! Naming is not an INFRA
Hi,
+1 of the source release, but -1 on the whl file.
For the source release I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER (WIP) exists but still has "List of known issues goes here”. You
need to mention what issue this release has.
- LICENSE is good
- NOTICE is
Agree to raise this issue, even before podling starts. Initial teams need
to follow up on this potential problem[1]. Let's see how things go :-)
[1] https://issues.apache.org/jira/browse/INFRA-21353
Matt Sicker 于2021年1月28日周四 上午12:35写道：
> It's typically a good idea to figure out your project
If you want to do the name search before being accepted then please submit a
JIRA here:
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/
You then provide the results of your search in the issue. The trademark
committee / VP, Brand will review. This might take a few weeks.
It is up
It's typically a good idea to figure out your project name early on.
If you have to change the name before graduation in order to get a
trademark, then that wastes the momentum gathered under the old name.
That can always happen after the podling boots up, though.
On Wed, 27 Jan 2021 at 07:44,
This is just a reminder, not an instruction.
The naming search and approval will officially happen when you are powerful
enough to graduate.
Personally, I would like to see this as a potential risk, not just
regarding Solace.
Of course, this is your option. you should know, if you can't get
Hi,
I am honored that JB and François are willing to help the eventmesh
project. I will soon initiate a discussion on evaluating Karaf 5 in the
community.
regards,
Eason Chen
On Wed, Jan 27, 2021 at 8:54 PM wrote:
> +1 for me to be mentor on the project :)
>
> regards,
>
> François
>
I would like to make a comments about this serious problem too,
In order not to cause unnecessary trouble in the future, we also request the
infra member from apache to help check whether this name is appropriate[1].
For us, we have used the name EventMesh for a long time, and we want to keep
@Sheng Wu
thank you for your kindly reminder. I would like to clarify this concerns.
As @Duane Pauls clarified this before:
“*I work for Solace and have consulted internally to confirm that we do not
have any copyright or trademark on the term “Event Mesh”. It’s true it is
something our
+1 for me to be mentor on the project :)
regards,
François
fpa...@apache.org
Le 27/01/2021 à 13:50, Jean-Baptiste Onofre a écrit :
> If you are open to evaluate/PoC EventMesh with Karaf (especially, Karaf 5
> would be a prefect candidate), you can count on me !
>
> I would be more than happy
If you are open to evaluate/PoC EventMesh with Karaf (especially, Karaf 5 would
be a prefect candidate), you can count on me !
I would be more than happy to be mentor on EventMesh if you think it would be
helpful.
Thanks !
Regards
JB
> Le 27 janv. 2021 à 13:47, Eason Chen a écrit :
>
>
Thanks to the attention of @JB and @François,
I have to admit that Karaf's lightweight operating environment, hot
deployment, dynamic configuration, and safe and rich management functions
are indeed very helpful to help developers and users deploy applications
more flexibly. We will further
Hi
I want to send a reminder for your project name chosen.
Event Mesh is widely used as a concept and term, you could find it through
Google search, https://www.google.com/search?q=event+mesh=event+mesh
Sheng Wu 吴晟
Twitter, wusheng1108
于2021年1月27日周三 下午5:12写道：
> Hi,
>
> Yes, it looks very
Hi,
Yes, it looks very promising.
I will be very happy to help in the incubation process and integrate the
project into Karaf with JB ;)
regards,
François
fpa...@apache.org
Le 27/01/2021 à 10:07, vongosling a écrit :
> Hi,
>
> This is a very young but promising project. The team attached
Hi,
This is a very young but promising project. The team attached great
importance to this project according to the feedback given by communities.
Through the efforts of the last five months, I am glad to see positive
changes in the project and community.
@Jean-Baptiste Onofré EventMesh really
Hi Eason,
That’s an interesting proposal, indeed.
I would rewrite some part of the proposal, but overall good.
I will check if the EventMesh architecture is "pluggable", meaning that we
"could" replace RocketMQ with another messaging/async provider.
Anyway, if you need some help on the
Good time of the time to all!
I'd like to bring this new interesting project for the discussion, comments
and feedback with the aim of starting a formal [VOTE] of its acceptance
into Incubator.
People behind this project aren't new to Apache: some of them were behind
the Apache RocketMQ, which I
32 matches
Mail list logo
