pment: https://pulsar.apache.org/docs/next/develop-load-manager/
Yu
On Thu, Jul 27, 2023 at 11:04 AM Yubiao Feng
wrote:
> Hi Yu
>
> It is amazing; thanks for your great work.
>
> Thanks
> Yubiao
>
> On Thu, Jun 29, 2023 at 2:43 PM Yu wrote:
>
> > Hi team,
>
Hi team,
This is our OSPP project -- Optimizing the findability of Pulsar
documentation with SEO strategies [1], aiming to improve the findability
and searchability of content on the Pulsar documentation website by
applying effective SEO strategies.
If it is good to go, we'll publish a more deta
feature releases are supported [1])
[1]
https://pulsar.apache.org/contribute/release-policy/#release-frequency-and-support-expectation
Yu
On Thu, Jul 27, 2023 at 11:02 AM Yubiao Feng
wrote:
> The current list of pulsar doc-supported versions is as follows:
> - 2.11.x Documentation
>
e.org/docs/next/concepts-broker-load-balancing-benefits/
[4]
https://pulsar.apache.org/docs/next/concepts-broker-load-balancing-types/
In addition, thanks again for your great guidance! @Demogorgon314 and
@heesung-sn @D-2-Ed
Yu
On Thu, Jul 20, 2023 at 10:17 PM Yu wrote:
> Hi team,
>
>
Congrats!
On Sat, Jul 22, 2023 at 9:53 AM ZhangJian He wrote:
> Congratulations
>
> Thanks
> ZhangJian He
>
>
> On Sat, 22 Jul 2023 at 01:19, Lari Hotari wrote:
>
> > Congratulations, Tison!
> >
> > -Lari
> >
> > On Fri, 21 Jul 2023, 20.05 Michael Marshall,
> wrote:
> >
> > > Hi Pulsar Communi
/concepts-broker-load-balancing-concepts/
[2] https://pulsar.apache.org/docs/next/reference-metrics/
On Thu, Jun 29, 2023 at 2:42 PM Yu wrote:
> Hi team,
>
> # New Doc | Broker Load Balancing
>
> I am excited to share that the 1st release of our new documentation on
> "Br
Hi Penghui and Girish,
Thanks for your discussions and technical guidance!
I've optimized the docs in https://github.com/apache/pulsar-site/pull/633,
could you PTAL?
Anyone else who wants to take a look and comment, feel free! Thanks!
Yu
On Tue, Jul 4, 2023 at 8:31 AM PengHui Li
/contribute/document-intro/, and don't hesitate to
reach out to me for any assistance or to have your pull requests reviewed.
Yu
On Fri, Jul 7, 2023 at 8:50 AM Yuvaraj Madeshwaran
wrote:
> Dear Apache Pulsar Foundation,
>
> I am writing to express my interest in contributi
Thank you all.
We've added the doc in https://github.com/apache/pulsar-site/pull/631
On Mon, Jul 3, 2023 at 11:15 AM guo jiwei wrote:
> Close the vote with 4(+1 binding) 2(+1 non-binding) 0(-1)
>
> binding:
> Hang
> Yunze
> Mattison
> Penghui
>
> non-binding
> Yubiao
> Asaf
>
>
> Regards
>
s://docs.google.com/document/d/1hkJpfZgTpRr8k39qNy6_82rGVQrJalVtmUl-OVW78fM/edit
[3] Broker Load Balancing | Information Architecture Map:
https://xmind.works/share/dzbyKsnS
[4] Broker Load Balancing | Doc Outline:
https://docs.google.com/document/d/1zshyn93XJp8Y-uvYLTnFCrcUWaHxeiTjPqdaUrR6zf0/edit
Yu
Thank you all!
Left some comments, PTAL.
On Wed, Jun 21, 2023 at 5:00 AM Kiryl Valkovich
wrote:
> Hi, Pulsar developers’ community!
>
>
>
> At the recent Pulsar Virtual Summit Europe 2023, we introduced the major
> pulsar.apache.org site redesign.
>
> We believe that it makes a good first impres
Hi Kiryl,
Thanks for your great contribution. The new look is more clean and
professional!
I've checked the whole design and commented on the doc layout [1]. Can you
please take a look? Thank you!
[1] https://github.com/apache/pulsar-site/pull/560#issuecomment-1553900225
On Thu, May 18, 2023 at
with SEO Strategies* [2].
Feel free to submit your application if interested or forward this to your
network. Thank you!
[1] https://summer-ospp.ac.cn/
[2] Project details:
https://summer-ospp.ac.cn/org/prodetail/23e980570?list=org&navpage=org
Yu
+1 (binding)
It's time to have a frictionless onboarding experience!
On Mon, May 8, 2023 at 9:21 AM Hang Chen wrote:
> +1 (binding)
>
> Best,
> Hang
>
> tison 于2023年5月7日周日 20:32写道：
> >
> > +1 (non-binding)
> >
> > N.B. IIRC PMC members have binding votes.
> >
> > Best,
> > tison.
> >
> >
> > Yu
of Information Architecture (Taking Apache Pulsar as an
Example)
- Inside Apache Pulsar’s Content Strategy
Slides and videos are available at
https://docs.google.com/document/d/1Ec1W0RbpNf11h1OhaDP0wgjGB_CC6jAb94iLY4Ziqx8/edit#
Yu
On Sat, May 6, 2023 at 4:25 PM Dianjin Wang wrote:
> Hi th
.
- Proficiency in any programming language or major in computer science is
preferred.
## Project Repo
- Pulsar documentation and website repo:
https://github.com/apache/pulsar-site
- Pulsar code repo: https://github.com/apache/pulsar
# Mentor Info
## Mentor Name
Yu Liu
## Mentor Email
li
Thanks Dianjing!
This is an activity worth attending based on my previous experience. As a
mentor for OSPP 2021 and 2022, I collaborated with some students and
@urfreespace to create fresh content experiences for Pulsar, such as
Introducing a Bot to Improve the Efficiency of Developing Docs [1] an
+1 for allowing collaborators to review, comment, approve, or request
further changes more conveniently
On Fri, Mar 31, 2023 at 11:26 AM Nitin Goyal
wrote:
> +1 (non-binding)
>
> On Fri, 31 Mar, 2023, 08:41 Jun Ma, wrote:
>
> > +1.
> >
> > Besides using a single source to lift the review effici
Double-check: do we need a PIP for newly added connectors?
https://github.com/apache/pulsar/pull/19821#issuecomment-1488860517
On 2023/03/27 14:14:23 tison wrote:
> Hi Asaf,
>
> > Shouldn’t poeople that has write access to merge must first validate of
> course if PIP is approved before merge?
>
Hi Asaf,
Thanks for your great initiative!
To make the learning path accurate for all roles (beginners, developers,
operators) and give them what they need in minimal viable docs, I would
suggest making changes to information architecture, like creating 3 guides
(subpages of https://pulsar.apache
?
This happens at intervals because decisions might be adjusted based on
additional info that surfaces later.
==Visuals==
Suggest creating illustrations [2] to give users a holistic and bird-eye
view of the whole workflow. A picture is worth a thousand words.
=
s?
> A list of specific changes, usually in the form of a table of contents and
> for each section listing a small description of what it will contain.
>
> Right now when you read the PIP, you can't answer those questions above.
>
>
>
> On Thu, Mar 16, 20
work - this makes the API documentation better for end users and less
> confusing.
>
> One small note: https://pulsar.apache.org/docs/next/admin-api-tutorial/ -
> I
> didn't find a tutorial there, mainly setup instructions.
>
>
> On Fri, Mar 17, 2023 at 11:13 AM Max Xu w
The "who/what/" is too vague.
>
> 2. What exactly do we plan to change?
>
> I couldn't understand what we plan to change, *practically*.
>
> I would expect something like:
> * The table of content would look like this... and mention the TOC and
> explain briefl
=
[1]
- https://github.com/apache/pulsar-site/pull/462
- https://github.com/apache/pulsar-site/pull/403
- https://github.com/apache/pulsar/pull/19002
- https://github.com/apache/pulsar/pull/18680
Yu
Hi Dave and tison, thanks for your feedback!
I've added the required info and explanations to the PIP issue [1]
concisely.
Feel free to take a look and leave your suggestions. TIA!
[1] https://github.com/apache/pulsar/issues/19755
Yu
On Wed, Mar 15, 2023 at 11:11 AM tison wrote:
&g
t before launch.
- Generate a targeted list of early adopters interested in this brand-new
tool.
- Improve SEO by adding relevant keywords.
[1] https://github.com/apache/pulsar-site/pull/462#discussion_r1130770643
Yu
On Wed, Mar 15, 2023 at 11:56 AM Shen Eric
wrote:
> Hi Zhangjian,
>
> We
+1
Thanks, Asaf and Emidio!
The new copywriting and visuals are fantastic!
On Wed, Mar 15, 2023 at 4:56 AM Dave Fisher wrote:
> +1(binding)
>
> Please fix the following sentence: “ Pulsar, although released to Apache
> in 2017 (and actually built in 2012), ” it is not correct. Pulsar code was
>
7;s accepted by the community.
On Wed, Mar 15, 2023 at 12:08 AM Asaf Mesika wrote:
> Side note: PIP should be in markdown in a GitHub issue for prosperity.
> External links lose permissions over time, come and go.
>
>
>
> On Mon, Mar 13, 2023 at 6:00 PM Yu wrote:
>
> >
Hi tison,
Thanks for bringing this up!
>From the official explanations [1], there is a clear distinction line
between them, so users can choose desired/correct categories easily.
[1]
https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-categories-for-discussion
e and progress
...
Feel free to share your thoughts on this proposal, TIA!
[1]
https://docs.google.com/document/d/1H-wEEfut18M18dle6a4-2EWCnLOqyJ81RVYxkPkTXhk/edit
[2]
https://docs.google.com/document/d/1NWmfDyIyUGzXOqX8V28AHyORF72lTFIvxlM6n86wAfU/edit?pli=1#bookmark=id.xgnk69nwtqi
Yu
e PMC.
> 2. By making it an informal, self-reported flag, you avoid the overhead
of board resolutions, etc. and just manage it at the community level. If
someone wants to change their status, they can just say so or submit a pull
request to change their status on the pulsar website.
~~
Hi @asafm and @emidio-cardeira thanks for your great work!
You've contributed new designs (with colors/elements/... that have not been
used) for Pulsar, which is a big step for the community.
Preiviously we've collected some rules at Pulsar Design Style Guide [1],
which are used to create illustr
Hi @visortelle thank you very much for your awsome job! This is a great
addition to the Pulsar website!
I've checked the design and left my comments at
https://github.com/apache/pulsar-site/pull/426#issuecomment-1436220520.
Also request more reviews from relevant stakeholders.
On Mon, Feb 20, 20
ead to the impassability of such topics.
### Modifications
Support getting stats and updating partitioned topics with the keyword
`-partition-{not-number}` in PR[0].
Best,
Ruguo Yu
[0] https://github.com/apache/pulsar/pull/19235
ubspotusercontent-na1.net/hubfs/6585952/Sponsorship%20Prospectus%20Pulsar%20Virtual%20Summit%20Europe%202023.pdf?utm_campaign=Pulsar%20Virtual%20Summit%20Europe%202023&utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz--0FfE3xVne3TMv5zwhWMZqigqyif8UrRmTW3xR2z-kySrD2AVPxmSJvWHj-5m5wH6eoXnX
>>>>>>>>>>
Yu
Congrats Nico!
On Mon, Jan 23, 2023 at 10:47 PM Zixuan Liu wrote:
> Congrats, Nicolò!
>
> Best,
> Zixuan
>
> Dave Fisher 于2023年1月21日周六 06:01写道：
>
> > Congratulations Nicolo!
> >
> > Best,
> > Dave
> >
> > > On Jan 20, 2023, at 6:57 AM, tison wrote:
> > >
> > > Congrats Nico! And well deserved
hanks,
> Penghui
>
> On Sun, Jan 15, 2023 at 6:31 PM Ruguo Yu wrote:
>
> > Hi Community,
> >
> > Currently, we can use PulsarClient to create `Producer`, `Consumer`,
> > `Reader` and `TableView`, releated method as below:
> >
> > ```
&
has default schema.
### Modifications
1. Add `newTableView(Schema)` method and replace
`newTableViewBuilder(Schema)`(attach `@Deprecated` annotation to it) in
PulsarClient
2. Add `newTableView()` method and Scheme default is `Schema.BYTES` in
PulsarClient
Thanks
Ruguo Yu
Congratulations, Yunze!
On 2022/12/29 12:42:36 Haiting Jiang wrote:
> Hi all,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://github.com/BewareMyPower) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
> He is very active in
arshall 于2023年1月4日周三 13:09写道：
> >
> > > Thanks for all of your work on this!
> > >
> > > One follow up is that we should update the PR template [0] so that
> > > contributors know where to contribute documentation.
> > >
> > > Thanks,
> &g
Hi tison, thanks for your great work!
On Fri, Dec 30, 2022 at 6:41 PM tison wrote:
> Hi,
>
> With the resolution of [1], I moved the source of the Pulsar document to
> the site repo[2][3][4][5].
>
> Now, if you'd like to update Pulsar document, you should submit a PR
> against the site repo (apa
gt; * https://github.com/apache/pulsar-site/pull/348
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> tison 于2022年12月26日周一 21:45写道：
> >>
> >>> FYI tracking issue has been created:
> >>> https://github.com/apache/pu
Congrats! Yunze
On Thu, Dec 29, 2022 at 11:00 PM Zike Yang wrote:
> Congratulations! Yunze
>
> BR.
> Zike Yang
>
> On Thu, Dec 29, 2022 at 10:42 PM Zixuan Liu wrote:
> >
> > Congrats! Yunze
> >
> > Best,
> > Zixuan
> >
> > oliver.shen...@gmail.com 于2022年12月29日周四
> 22:34写道：
> >
> > >
>
+1
On Tue, Dec 20, 2022 at 3:12 PM Yunze Xu
wrote:
> +1 (non-binding)
>
> Thanks,
> Yunze
>
> On Tue, Dec 20, 2022 at 3:06 PM Zike Yang wrote:
> >
> > +1 (non-binding)
> >
> > Thanks,
> > Zike Yang
> >
> > On Tue, Dec 13, 2022 at 4:38 PM Jun Ma wrote:
> > >
> > > Hi all,
> > >
> > > I'm going
Hi tison,
Thanks for raising this up!
Our community had a similar discussion previously and chose to "keep" the
doc repo stay in the Pulsar main repo at that time.
[1] lists the pros and cons of "keep" and "not keep" solutions.
I'm +0 on this proposal because I think the total scores of these t
Hi tison,
Thanks for clearing up various issues and PRs!
One quick question:
For the "Discussion posts" converted from "Issues", can we set it not to
sync to dev@pulsar.apache.org (since they do not have new discussions and
comments)?
Thank you!
On Mon, Dec 12, 2022 at 10:30 AM Zili Chen wrot
.
Happy Thanksgiving and have a great holiday season, wherever you are
located!
Yu
gt;>>>>>
2. Does it make sense to show contributors for all Pulsar-related repos
(e.g. pulsar, pulsar-site, pulsar-client-cpp, pulsar-helm-chart) on the
Pulsar website?
SkyWalking follows this way, see "Contributors" at
https://skywalking.apache.org/team/.
>>>>
Congratulations! tison
Ruguo Yu
On 2022/11/10 00:15:22 Yu wrote:
> The Project Management Committee (PMC) for Apache Pulsar has invited Zili
> Chen (https://github.com/tisonkun)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a co
submission process. This should enable better productivity.
Welcome and congratulations, Zili Chen!
Please join us in congratulating and welcoming Zili Chen onboard!
Best Regards,
Yu on behalf of the Pulsar PMC
Thanks, Michael!
Feel free to ping me if you need a doc review.
On Tue, Oct 25, 2022 at 2:17 AM Michael Marshall
wrote:
> +1 (binding)
>
> Thank you all for voting.
>
> I am closing the vote with 4 binding +1 votes (Dave, Enrico, PengHui,
> Michael) and 2 non-binding +1 votes (Bo, Zike).
>
> I w
ggestions or concerns.
Many thanks for your technical guidance! @urfreespace,
@signormercurio, @tisonkun, @nodece
Yu
Hi tison,
Thanks for taking care of the docs!
Seems that archiving the incubating docs does not affect the existing
workflow of Pulsar doc update/maintenance.
+1 for this proposal.
Yu
On Mon, Oct 17, 2022 at 3:24 PM tison wrote:
> Hi folks,
>
> I noticed that we write a lot of logic
lease Note
website in the *Pulsar Release Note Guide* [2]. Please follow the steps
there.
>>>>>>>>>>>>
# 2
Now, the Pulsar Release Note website is generated automatically.
This great work is done by @signormercurio and @urfreespace! [4]
Huge THANKS to you!
+1, thank you, Michael!
On Wed, Oct 12, 2022 at 1:00 PM Matteo Merli wrote:
> +1 Thanks Michael for fixing these!
>
>
>
> On Tue, Oct 11, 2022 at 9:52 PM Michael Marshall
> wrote:
>
> > Hi All,
> >
> > I had a brief discussion with Matteo about mailing list notifications
> > for our apache/pul
ntation-related guides to the Contribution page
[4] later.
[1] https://github.com/apache/pulsar/discussions/17310
[2] https://github.com/apache/pulsar-site/pull/242#issuecomment-1272700632
[3] https://github.com/apache/pulsar/tree/master/wiki/release
[4] https://pulsar.apache.org/contributing/
Yu
Thanks Lari!
Does this issue cause the tests for PRs like
https://github.com/apache/pulsar/pull/17198 to be hang?
On 2022/09/06 14:41:07 Dave Fisher wrote:
> We are going to need to take actions to fix our problems. See
> https://issues.apache.org/jira/browse/INFRA-23633?focusedCommentId=176007
#diff-f3115b8be648c3dc440594799619e7ce4408a34efab13b9d57a902030b62562c
[2] https://github.com/apache/pulsar/issues/16637
~~
Feel free to comment, thank you!
Yu
On Tue, Sep 6, 2022 at 10:57 AM Yunze Xu
wrote:
> Hi all,
>
> I'm working on 2.8.4 release recently. When I followed the release
> process,
-cpp/include/pulsar
- Python: have no idea
~~
Thank you!
Yu
On Fri, Sep 2, 2022 at 1:17 AM Lari Hotari wrote:
> On 2022/09/01 08:36:11 Yu wrote:
> > # 1
> > For pure doc PRs (only update .md files), do they run the same tests as
> > code PRs?
> > If so, can
Hi Lari,
Thanks for raising this up! May I know your thoughts on these questions?
# 1
For pure doc PRs (only update .md files), do they run the same tests as
code PRs?
If so, can we set them to run only doc-related tests and skip code tests
(since they're easily failed)?
In this way
pache/pulsar/issues/14928
Yu
On Thu, Aug 25, 2022 at 1:16 PM tison wrote:
> Anyway, it's a separate topic to discuss. If you want to discuss issue
> types and whether to label components, please start another thread.
>
> Best,
> tison.
>
>
> tison 于2022年8月25日周四 13:12写道：
nYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit?pli=1
[3] https://lists.apache.org/thread/90rcjf1dv0fbkb5hm31kmgr65fj0nfnn
[4]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu, mangoGoForward, Max
Thanks Max!
Agree with applying the same rules ( [type] [scope] summary) for writing issue
titles.
On 2022/08/25 02:48:51 Max Xu wrote:
> LGTM.
>
> And I think we should also update our issue templates.
>
> Best,
> Max Xu
>
>
> On Tue, Aug 23, 2022 at 6:04 P
Hi Dave, thanks for your great reminder! We'll add those rules.
Yu, signormercurio, urfreespace
On Tue, Aug 23, 2022 at 10:33 PM Dave Fisher wrote:
> If page urls change then we should also add http redirect rules to help
> users who bookmarked these docs.
>
> Sent from my iP
e "PIP
metadata" file.
3. ...
Yu
On Wed, Aug 24, 2022 at 10:01 AM PengHui Li wrote:
> Hi Rajan,
>
> > I didn't understand this part. You want one to create a PR before
> submitting a proposal? That's clearly not a good idea because if the PIP
> approach wi
Hi team,
Now is 3 working days after the initial discussion
We'll start replacing brodocs with docsify for docs since there is no
objection or technical suggestions.
Yu, signormercurio, urfreespace
On Fri, Aug 19, 2022 at 5:09 PM Yu wrote:
> Thanks Dave!
>
> > How is this se
[1] https://lists.apache.org/thread/90rcjf1dv0fbkb5hm31kmgr65fj0nfnn
[2]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu and mangoGoForward
On Tue, Aug 23, 2022 at 5:59 PM Yu wrote:
> Hi Jiuming, Yunze, tison,
Hi Jiuming, Yunze, tison,
Thanks for your vote!
Hi tison,
> "packaging logics"
> For example, build the docker image, build & publish shell scripts.
If you refer to these changes, they belong to [build] scope.
Yu and Zixuan
On Tue, Aug 23, 2022 at 1:25 PM
quot;misc" or "chore"? [1]
Choice A: misc
Choice B: chore
Thank you all!
[1]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.58q1qxhu7pio
Yu
On Mon, Aug 22, 2022 at 12:44 PM Yu wrote:
> Hi
d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.khz275ok35u5
[2]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.nnekhkthmwlh
Yu and Zixuan
On Mon, Aug 22, 2022 at 12:40 PM Yu wrote:
> Thank you tison and Zixuan!
>
> Agre
rmats are fine to go:
- Submit breaking changes
[feat][broker]! Support xx
- Submit PIP changes
[feat][broker] PIP-198: Support xx
Feel free to comment, thank you!
[1] https://pulsar.apache.org/docs/next/admin-api-packages
Yu and Zi
-1uJyd1k9_h56xiiVRVOnrLcCnTmg9n7SrHhNVNEEi4/edit#bookmark=id.q5m2r5pimdi6
[2] https://github.com/apache/pulsar/issues/16637
Yu
nsidered to replace it.
[1] https://github.com/apache/pulsar/issues/15664
Yu and signormercurio
On Thu, Aug 18, 2022 at 9:46 PM Dave Fisher wrote:
>
>
> Sent from my iPhone
>
> > On Aug 18, 2022, at 4:55 AM, Yu wrote:
> >
> > Hi team,
> >
> > To red
oth “storage” and “tiered storage” scopes.
Bookie changes go to “storage”.
Tiered storage changes go to “tiesto” (abbr. "ts" is not used since it
might be confused with TypeScript).
Hi developers, which do you prefer? Or any other suggestions? Thank you!
Yu
On Fri, Aug 19, 2022 at 5:01
om/apache/pulsar/pull/16055
- Add guides:
[feat][workflow] Add instructions for previewing website changes,
https://github.com/apache/pulsar-site/pull/136
~~
Yu
On Thu, Aug 18, 2022 at 11:51 PM Zixuan Liu wrote:
> > Since here uses a singular noun, how about using "dep"
Congrats Jiwei!
On Fri, Aug 19, 2022 at 10:45 AM Zixuan Liu wrote:
> Congrats!
>
> Zixuan
>
> Jun M 于2022年8月19日周五 10:16写道：
>
> > Congrats to Jiwei!
> >
> >
> > Cheers,
> > Jun
> >
>
/tools/pulsar-config/2.11.0-SNAPSHOT/#/
Yu, signormercurio, urfreespace
/pulsar.apache.org/docs/next/client-libraries-rest
[3]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.nnekhkthmwlh
Yu
On Thu, Aug 18, 2022 at 10:50 AM Zixuan Liu wrote:
> Thank yu for your work! Overall looks good to me, but I would
31kmgr65fj0nfnn
[3]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
[4]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=kix.849jztd92uk7
Yu
Hi team
Thanks for your feedback!
Here is the voting result:
Our existing convention (customized based on Angular) is chosen!
~~
Our existing convention votes:
5, +1: Yu, Alex, Yunze, Jun, Qiang,
1, +0: tison
Angular convention votes:
1, +1: tison
~~
I’ll close this discussion
Hi team,
Feel free to choose your desired convention **before EOD 8/16 (UTC +8)**.
We'll close this discussion and move to the next topic after that time.
Thank you!
Yu and mangoGoForward
On Mon, Aug 15, 2022 at 6:27 PM Yu wrote:
> Hi tison,
>
> Thanks for your suggesti
.
I'll initiate an official discussion on these details and the definition of
[type][scope] in another independent email.
[1]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu and mangoGoForward
On Mon, Aug 15, 2022 at 12:
!
[1]
https://docs.google.com/document/d/1sJlUNAHnYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit?pli=1
[2]
https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit-message-header
[3]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
[4] https:/
Hi team, Thanks for all your suggestions! I'll move PIP 198 forward since
we get 3 binding votes (Penghui, Lari, Michael) [1].
[1] https://lists.apache.org/thread/m7hfgpdjthrk8ogz3mnkprs018tkkc0m
Yu
s://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
[3] https://github.com/apache/pulsar/pulls
On Wed, Aug 10, 2022 at 6:11 PM Yu wrote:
>
> Hi team,
>
> Thanks for all your suggestions!
>
> I'll move PIP 19
to issue 2.
[1]
https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit-message-header
[2]
https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit?pli=1#bookmark=id.y8943h392zno
Yu
On Wed, Aug 10, 2022 at 6:05 PM Yu wrote:
> Hi Lari,
>
> Tha
ed based on Angular) [2],
seems that Angular only saves one char.
For example,
- Angular: feat(broker): add xxx → (): occupy 3 chars
- Ours: [feat][broker] add xxx → (): occupy 4 chars
(2) I agree with Michael. Brackets make info clearer.
Yu
[1]
https://github.com/apache/pulsar/pull/16836
Hi tison,
Thanks for your suggestions!
> Currently, I'd suggest: feature -> feat workflow -> ci improve/cleanup ->
> chore...
I agree on some and will send votes step by step to let the community decide.
On 2022/08/09 09:21:54 tison wrote:
> Hi Yu,
>
> To be c
hould later move the standard to our website where the whole
> project can easily contribute to and follow the general contribution
> process - that is, send a pull request, review, and merge. I regard current
> gdoc content as a temporary container for this content.
>
> If this proposa
, @laminar*, @*danpi
[1] https://pulsar.apache.org/tools/pulsar-admin/2.11.0-SNAPSHOT/#functions
[2]
https://docs.google.com/spreadsheets/d/1YHYTkIXR8-Ql103u-IMI18TXLlGStK8uJjDsOOA0T20/edit#gid=1784579914
[3] https://github.com/apache/pulsar/pull/16853
Yu
other thoughts
Feel free to comment, thank you!
[1] https://lists.apache.org/thread/sk9ops3t94jmzc5tndk08y9khf7pj6so
[2] https://github.com/apache/pulsar/pulls
[3]
https://docs.google.com/document/d/1sJlUNAHnYAbvu9UtEgCrn_oVTnVc1M5nHC19x1bFab4/edit?pli=1#
Yu, Max, mangoGoForward
Hi Zixuan and Tison,
Thanks for your comments!
We're considering your suggestion and will turn the proposal into a PIP and
call a vote.
Yu, Max, mangoGoForward
On Mon, Aug 1, 2022 at 4:29 PM Zixuan Liu wrote:
> Hi Yu,
>
> This is a good idea, I noticed this thread for a long tim
+1 since it improves the efficiency of managing docs.
On Thu, Jul 28, 2022 at 8:16 AM M Jun wrote:
> Hi, Pulsar community,
>
> I'd like to start a vote on PIP-190: Simplify Pulsar documentation release
> and maintenance strategy.
>
> You can find the proposal at https://github.com/apache/pulsar/
+1 for this proposal since it improves the efficiency of managing docs.
We'll take it as we reach a lazy consensus and implement this plan if there is
no objection until tomorrow.
On 2022/07/25 09:13:50 M Jun wrote:
> Hi Asaf,
>
> The doc files for all older versions are independent copies, sto
Congrats Michael! Thanks for your contribution to the doc and website!
On Wed, Jul 27, 2022 at 12:46 AM Nicolò Boschi wrote:
> Congrats! Very well deserved!!
>
> Nicolò Boschi
>
> Il Mar 26 Lug 2022, 18:26 Christophe Bornet ha
> scritto:
>
> > Congratulations Michael ! Well deserved !
> >
> > L
to be part of the great event! Save your spot today!
Best,
Yu
[1] https://pulsar-summit.org/event/san-francisco-2022
Hi tison, thanks for creating this vote!
I thought we reached a lay consensus since there was no objection since the
last discussion [1]
+1 for this proposal.
I've explained the reasons and showed the benefits previously [2]
[1] https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn
[2]
Hi team,
Now we have a fresh "Community" page [1], which shows the Pulsar PMC list,
contributors over time, monthly active contributors, etc.
Thanks Wenqing for making this happen!
[1] https://pulsar.apache.org/community#section-community
Yu
On Tue, Jul 5, 2022 at 9:15 PM Yu wr
submission process. This should enable better productivity.
Welcome and congratulations, Zixuan Liu!
Please join us in congratulating and welcoming Zixuan Liu onboard!
Best Regards,
Yu on behalf of the Pulsar PMC
1 - 100 of 222 matches
Mail list logo
