gaoran10 commented on pull request #169:
URL:
https://github.com/apache/pulsar-client-node/pull/169#issuecomment-901647147
@ryansealy Yes, I'll try to use an environment variable.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
+1 for standardizing the PIP workflow!
The proposal looks good!
- Sijie
On Wed, Aug 18, 2021 at 10:46 PM Matteo Merli wrote:
> This is a proposal that I promised to send out for a long time.
> It should be considered as a draft and I'd love to hear feedback on this.
>
> The motivations to impr
Sorry for the typo:
"isn't violating the ASF policy" -> "is violating the ASF policy"
On Wed, Aug 18, 2021 at 10:46 PM Sijie Guo wrote:
> Moving dev@ to BCC. I believe the following two major issues should be
> discussed and addressed in the original email thread with PMC.
>
> 1) Creating sub-c
Moving dev@ to BCC. I believe the following two major issues should be
discussed and addressed in the original email thread with PMC.
1) Creating sub-committees composed of vendor representatives isn't
violating the ASF policy. This PMC has expressed concerns when the original
proposal was raised.
This is a proposal that I promised to send out for a long time.
It should be considered as a draft and I'd love to hear feedback on this.
The motivations to improve the current PIP process are:
* When PIPs were introduced, the process was intentionally left as very
lightweight and not very str
ryansealy edited a comment on pull request #169:
URL:
https://github.com/apache/pulsar-client-node/pull/169#issuecomment-901582109
Can the PULSAR_CPP_PATH be overridable by environment variable? When
building in CI/CD environment it may not always be easy to work in C:\pulsar
root for thi
ryansealy edited a comment on pull request #169:
URL:
https://github.com/apache/pulsar-client-node/pull/169#issuecomment-901582109
Can the PULSAR_CPP_PATH overridable by environment variable? When building
in CI/CD environment it may not always be easy to work in C:\pulsar root for
this.
ryansealy commented on a change in pull request #169:
URL: https://github.com/apache/pulsar-client-node/pull/169#discussion_r691760233
##
File path: binding.gyp
##
@@ -18,14 +18,24 @@
#
{
+ 'conditions': [
+['OS=="win"', {
+ 'variables': {
+'PULSAR_CPP_PAT
ryansealy commented on pull request #169:
URL:
https://github.com/apache/pulsar-client-node/pull/169#issuecomment-901582109
Could you make the PULSAR_CPP_PATH overridable by environment variable? When
building in CI/CD environment it may not always be easy to work in C:\pulsar
root for th
Hi Matteo,
I'm sorry if my last message suggested that volunteering to take on an
effort gives anyone the right to start acting on behalf of the PMC. That
certainly wasn't my intent. The original message in this thread proposed a
way to help people who want to organize meetups do so more successfu
> I think it's entirely understandable for the PMC to say "we don't want to
> be responsible for this", but it would be highly unfortunate for the PMC to
> say "we don't want to be responsible for this AND no one from the community
> is allowed to do this either", especially when there are people
>
Hi everyone, long time reader, first time poster. :-)
Here are my two cents: I would like to see the PMC encourage anyone and
everyone who is willing to volunteer their time and effort to do things
that will help the community grow (as long as it adheres to Apache policies
of course). There are a
On Wed, Aug 18, 2021 at 3:15 PM Jonathan Ellis wrote:
>
> Hi Matteo,
>
> You will remember that I brought up the subcommittee idea in private
> yesterday, and followed up today [before the email you sent and quoted
> here] with an intention to start this public thread.
There have been several con
I don't think we should create any sub-committees to bypass the PMC.
The sub-committee topic or proposal should be properly discussed and
approved by the PMC.
In regards to meetups, I don't think we should put every Pulsar meetup
under one umbrella group even this group is managed by PMC. Pulsar
m
Hi Matteo,
You will remember that I brought up the subcommittee idea in private
yesterday, and followed up today [before the email you sent and quoted
here] with an intention to start this public thread.
Meanwhile, Aaron has not been hiding the groundwork he is laying for
meetups, including colla
Hello all,
On the Meet-ups, we already have ones that have just started up in
Northern California, Southern California, and the Netherlands (run by 3
different people) and I know of at least one more.
Are there others? The only good thing about this Covid world is that the
events that are schedule
gaoran10 opened a new pull request #169:
URL: https://github.com/apache/pulsar-client-node/pull/169
# Motivation
Currently, building in windows needs some changes to do.
# Modification
Add windows building configurations in `binding.gyp`.
Add windows building-related
Since this proposal comes as a reaction to a discussion that was
already happening on the private@ PMC mailing list, I want to add the
context.
This was my original comment, where I was pointing out the
inappropriateness of the Meetup group namings.
On Wed, Aug 18, 2021 at 1:34 PM Matteo Merli w
Hi all,
Meetups are an important part of community building and knowledge sharing
for open source projects like Apache Pulsar. At the same time, the work of
recruiting speakers and organizing sponsors [1] is both time consuming and
not core to project governance.
I propose that the PMC designate
RobertIndie opened a new pull request #86:
URL: https://github.com/apache/pulsar-dotpulsar/pull/86
This PR adds support for the multi-topics consumer and partitioned consumer.
Co-authored-by: Zike Yang
Co-authored-by: Zixuan Liu
--
This is an automated message from the Apache
20 matches
Mail list logo
