[GitHub] [pulsar-site] MMirelli commented on pull request #126: Update out-of-sync url to get openssl.cnf in TLS transport documentation

[GitBox]

MMirelli commented on PR #126:
URL: https://github.com/apache/pulsar-site/pull/126#issuecomment-1173156732

   Opened https://github.com/apache/pulsar/pull/16362


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] MMirelli closed pull request #126: Update out-of-sync url to get openssl.cnf in TLS transport documentation

[GitBox]

MMirelli closed pull request #126: Update out-of-sync url to get openssl.cnf in 
TLS transport documentation
URL: https://github.com/apache/pulsar-site/pull/126


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] SignorMercurio commented on pull request #132: Fix inaccurate community info

[GitBox]

SignorMercurio commented on PR #132:
URL: https://github.com/apache/pulsar-site/pull/132#issuecomment-1173255575

   > I'll ask the community whether to show company info or not.
   
   I think the phonebook page does not contain the information about 
committers' companies, so newly added committers do not have the `org` field.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

How to Show Info about Community?

[Yu]

Hi team,

We're updating [1] the "Meet the Community" info [2] since the current info
is obsolete.

Several questions on how to show the info:

==

Q1: only show PMC members and add a tip?

Context:

a. Nowadays, we have more and more PMC members (30 in total) and committers
(62 in total) while many of them are inactive.

b. If we show them all, the list on the website would be very long as they
are growing all the time.

c. How about showing only PMC members and adding a tip?
The tip can be: For the complete and up-to-date list of PMC members and
committers, see [Apache Pulsar Committee](
https://projects.apache.org/committee.html?pulsar).

d. Similar cases are Cassandra [3] and Flink [4].

==

Q2: show organizations or not?

Context:

a. `org` is in the team.js file [5]. Shall we show organizations on the
Pulsar website?

b.1 Showing

- Pros: It demonstrates that Pulsar is a diverse community because people are
from various organizations.

- Cons: Organization info needs to be collected and added manually

- Example: Spark [6]

b.2 Not showing

- Pros: people work as individuals to make contributions to Pulsar (weaken
vendors)

==

Feel free to comment, thank you!

[1] https://github.com/apache/pulsar-site/pull/132
[1] https://pulsar.apache.org/community#section-community
[3] https://cassandra.apache.org/_/community.html#meet-the-community
[4] https://flink.apache.org/community.html#people
[5]
https://github.com/apache/pulsar-site/blob/7441570e2a79c56f073bdc8c3dabe41fbad7411a/site2/website-next/data/team.js#L29
[6] https://spark.apache.org/committers.html

Yu and Wenqing

[GitHub] [pulsar-site] michaeljmarshall opened a new pull request, #133: Only generate Javadocs for released versions of Pulsar

[GitBox]

michaeljmarshall opened a new pull request, #133:
URL: https://github.com/apache/pulsar-site/pull/133

   Main issues: https://github.com/apache/pulsar/issues/14838 
https://github.com/apache/pulsar/issues/13916 
https://github.com/apache/pulsar/issues/16094
   
   ## Motivation
   
   The current Javadocs are generated based on unreleased versions of Pulsar. 
As a result, the website links have `-SNAPSHOT` in them. This is confusing, and 
can also lead to problems where the docs do not align with specific versions. 
This PR is a step towards cleaning up the `-SNAPSHOT` references (there are 
several more locations, but I am just fixing the Javadoc case in this PR).
   
   ## Changes
   
   * Update Javadoc generation script so that it downloads the released source 
code for pulsar and then builds the Javadocs from that source. (This change is 
in the first commit.)
   * Run the script against versions 2.7.0 through 2.10.1. (These were all 
added in the second commit.)
   
   ## Note
   This change does not make these docs referenced on the website. There is 
additional work that I plan to complete to make the `replace.js` script 
reference these docs. I will contribute once I fix all of the generated docs 
with `-SNAPSHOT`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] michaeljmarshall commented on pull request #133: Only generate Javadocs for released versions of Pulsar

[GitBox]

michaeljmarshall commented on PR #133:
URL: https://github.com/apache/pulsar-site/pull/133#issuecomment-1173351514

   @urfreespace - I did not realize just how big these Javadoc files were until 
opening this PR. This PR literally adds 8 million lines of generated Javadocs. 
Should we add the script to the main branch and only commit the generated docs 
to the `asf-site-next` branch?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] michaeljmarshall commented on pull request #133: Only generate Javadocs for released versions of Pulsar

[GitBox]

michaeljmarshall commented on PR #133:
URL: https://github.com/apache/pulsar-site/pull/133#issuecomment-1173353058

   Looks like the generated docs from the broker for all versions are about 304 
MB.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

New Release Notes Workflow

[Yu]

Hi team (especially release managers),

Since we have a new Pulsar Release Notes page [1], the workflow of
submitting release notes is changed.

I've documented steps and added examples on the wiki [2], please follow the
new rules.

Feel free to comment, thank you!

[1] https://pulsar.apache.org/release-notes/
[2]
https://github.com/apache/pulsar/wiki/Release-process#16-write-release-notes

Yu & urfree

[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #134: Customize tabs and highlight tab sections

[GitBox]

SignorMercurio opened a new pull request, #134:
URL: https://github.com/apache/pulsar-site/pull/134

   Close apache/pulsar#16180.
   
   Screenshot:
   
   
![image](https://user-images.githubusercontent.com/32540679/177086232-e553b8c1-6b54-4b0d-9c3c-1137018b66b3.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] michaeljmarshall commented on pull request #133: Only generate Javadocs for released versions of Pulsar

[GitBox]

michaeljmarshall commented on PR #133:
URL: https://github.com/apache/pulsar-site/pull/133#issuecomment-1173363143

   Interestingly, the following returns now results:
   
   ```shell
   grep -R "/api/pulsar-broker" content/docs/
   ```
   
   That indicates to me that the website doesn't actually point to the broker's 
Javadocs. Why do we generate and host them if they are not referenced? I wonder 
if we can remove them and save some space.
   
   Either way, we still need to decide the right workflow for adding generated 
docs. I think it would make sense to keep them in the `main` branch, but I am 
open to opinions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] [PIP-179] Support the admin API to check unknown request parameters

[Hang Chen]

+1 (binding)

Thanks,
Hang

Lan Liang  于2022年7月1日周五 18:03写道：
>
> +1,NB
>
>
> - lan.liang
>  Replied Message 
> | From | Enrico Olivelli |
> | Date | 6/30/2022 18:35 |
> | To | Dev |
> | Subject | Re: [VOTE] [PIP-179] Support the admin API to check unknown 
> request parameters |
> +1 (binding)
>
> Enrico
>
> Il giorno gio 30 giu 2022 alle ore 08:57 Zike Yang  ha 
> scritto:
>
> +1
>
> Zike Yang
>
> On Thu, Jun 30, 2022 at 12:38 PM mattison chao 
> wrote:
>
> +1(non-binding)
>
> Best,
> Mattison
>
> On Thu, 30 Jun 2022 at 12:35, Michael Marshall 
> wrote:
>
> +1
>
> - Michael
>
> On Wed, Jun 29, 2022 at 9:29 PM Qiang Huang 
> wrote:
>
> +1
>
> Yubiao Feng  于2022年6月30日周四
> 00:40写道：
>
> Hi Pulsar Community
>
> I would like to start a VOTE on "Support the admin API to check
> unknown
> request parameters" (PIP-179).
>
> The proposal can be read at
> https://github.com/apache/pulsar/issues/16135
>
> and the discussion thread is available at
> https://lists.apache.org/thread/m8vkxl46njm7sh0r1mqsn25jggq9v8kb
>
> Voting will stay open for at least 48h.
>
> Thanks
> Yubiao Feng
>
>
>
> --
> BR,
> Qiang Huang
>
>

Re: How to Show Info about Community?

[tison]

Hi Yu,

Thanks for starting this discussion. Here are my two coins.

1. For showing membership, I suggest you take a look at SkyWalking's Team
page[1]. As the Pulsar ecosystem grows larger and larger, the framework
SkyWalking's Team page used is a good fit IMO.
2. For organization affinity, I suggest we don't include them since it's
hard to maintain and in Apache we always play as individuals.

Best,
tison.

[1] https://skywalking.apache.org/team/


Yu  于2022年7月4日周一 12:35写道：

> Hi team,
>
> We're updating [1] the "Meet the Community" info [2] since the current info
> is obsolete.
>
> Several questions on how to show the info:
>
> ==
>
> Q1: only show PMC members and add a tip?
>
> Context:
>
> a. Nowadays, we have more and more PMC members (30 in total) and committers
> (62 in total) while many of them are inactive.
>
> b. If we show them all, the list on the website would be very long as they
> are growing all the time.
>
> c. How about showing only PMC members and adding a tip?
> The tip can be: For the complete and up-to-date list of PMC members and
> committers, see [Apache Pulsar Committee](
> https://projects.apache.org/committee.html?pulsar).
>
> d. Similar cases are Cassandra [3] and Flink [4].
>
> ==
>
> Q2: show organizations or not?
>
> Context:
>
> a. `org` is in the team.js file [5]. Shall we show organizations on the
> Pulsar website?
>
> b.1 Showing
>
> - Pros: It demonstrates that Pulsar is a diverse community because people
> are
> from various organizations.
>
> - Cons: Organization info needs to be collected and added manually
>
> - Example: Spark [6]
>
> b.2 Not showing
>
> - Pros: people work as individuals to make contributions to Pulsar (weaken
> vendors)
>
> ==
>
> Feel free to comment, thank you!
>
> [1] https://github.com/apache/pulsar-site/pull/132
> [1] https://pulsar.apache.org/community#section-community
> [3] https://cassandra.apache.org/_/community.html#meet-the-community
> [4] https://flink.apache.org/community.html#people
> [5]
>
> https://github.com/apache/pulsar-site/blob/7441570e2a79c56f073bdc8c3dabe41fbad7411a/site2/website-next/data/team.js#L29
> [6] https://spark.apache.org/committers.html
>
> Yu and Wenqing
>

Re: [VOTE] PIP-165: Auto release client useless connections

[Yubiao Feng]

The PIP passes with 3 bindings +1: Hang Chen, Penghui Li, and Jia Zhai. I
will start working, Please help to move to the wiki. Thanks
Yubiao Feng

On Mon, Jun 20, 2022 at 9:37 AM Jia Zhai  wrote:

> +1
>
> On Fri, Jun 17, 2022 at 11:35 AM Yubiao Feng
>  wrote:
>
> > Hi  Matteo, Enrico, LinLin
> >
> > I would appreciate it if you could give me some comments.
> >
> > Thanks
> > Yubiao.Feng
> >
> > On Wed, Jun 15, 2022 at 2:47 PM Hang Chen  wrote:
> >
> > > +1
> > >
> > > Thanks,
> > > Hang
> > >
> > > Zike Yang  于2022年6月15日周三 10:31写道：
> > > >
> > > > +1
> > > >
> > > >
> > > > Zike Yang
> > > >
> > > > On Wed, Jun 15, 2022 at 10:28 AM Haiting Jiang <
> > jianghait...@apache.org>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Haiting
> > > > >
> > > > > On 2022/06/14 10:28:22 Xiangying Meng wrote:
> > > > > > +1
> > > > > >
> > > > > > On Tue, Jun 14, 2022 at 3:52 PM Gavin Gao <
> zhangmin...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > > On 2022/06/01 07:11:51 Yubiao Feng wrote:
> > > > > > > > Hi Pulsar Community:
> > > > > > > >
> > > > > > > > There were some mistakes in the last email, so I have
> corrected
> > > them.
> > > > > > > >
> > > > > > > > I would like to start a VOTE on "Auto release client useless
> > > > > connections"
> > > > > > > > (PIP-165).
> > > > > > > >
> > > > > > > > Proposal Link: [PIP-165] Auto release client useless
> > connections
> > > ·
> > > > > Issue
> > > > > > > > #15516 · apache/pulsar (github.com)
> > > > > > > > 
> > > > > > > >
> > > > > > > > Discuss Link: [DISCUSS] [PIP-165] Auto release client useless
> > > > > > > > connections-Apache Mail Archives
> > > > > > > > <
> > > https://lists.apache.org/thread/t6h98qs2coc56z06tw38hdlljl67ft4n>
> > > > > > > >
> > > > > > > > Voting will stay open for at least 48h.
> > > > > > > > Thanks, Yubiao Feng
> > > > > > > >
> > > > > > > > On Wed, Jun 1, 2022 at 2:40 PM Yubiao Feng <
> > > > > yubiao.f...@streamnative.io>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > [VOTE] PIP-165: Auto release client useless connectionsHi
> > > Pulsar
> > > > > > > > > Community, I would like to start a VOTE on "Auto release
> > client
> > > > > useless
> > > > > > > > > connections" (PIP-165). The proposal can be read at
> > > > > > > > > https://github.com/apache/pulsar/issues/15516
> > > > > > > > >  and the
> > > discussion
> > > > > > > thead
> > > > > > > > > is available at
> > > > > > > > >
> > > https://lists.apache.org/thread/t6h98qs2coc56z06tw38hdlljl67ft4n
> > > > > > > > >   Voting will stay open for at least 48h. Thanks, Yubiao
> Feng
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> >
>