Hi Yu, To be clear, the candidates of types and components are a bit long which may waste space for meaningful information.
For example, Angular names feature as feat to save letters. GitHub only shows the first 50 characters for PR title. I'd like to confirm that the name of types and components are not voted in this thread and postponed when we review the patch. Currently, I'd suggest: feature -> feat workflow -> ci improve/cleanup -> chore dependency -> dep function -> fn security -> sec website -> site ... Best, tison. Qiang Huang <qiang.huang1...@gmail.com> 于2022年8月9日周二 15:07写道： > +1 (non-binding) I like the idea of check PR title as a job. > Good job, Yu. > > tison <wander4...@gmail.com> 于2022年8月8日周一 22:07写道： > > > +1 (non-binding) to the proposal itself. > > > > Although, we should 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 proposal gets accepted, @Yu you can create an issue for the dev > doc > > part and ping me. I can offer my help to write so. > > > > Best, > > tison. > > > > > > Zike Yang <z...@apache.org> 于2022年8月8日周一 13:35写道： > > > > > +1 (non-binding) > > > > > > Thanks > > > Zike Yang > > > > > > On Mon, Aug 8, 2022 at 1:06 PM Xiangying Meng <xiangy...@apache.org> > > > wrote: > > > > > > > > +1(non-binding) > > > > > > > > yours sincerely, > > > > xiangying Meng > > > > > > > > On Thu, Aug 4, 2022 at 4:13 PM Yu <li...@apache.org> wrote: > > > > > > > > > Hi team, > > > > > > > > > > It has been 4 months since we discussed the [Guideline] Pulsar PR > > > Naming > > > > > Convention [1]. > > > > > > > > > > Nowadays, when reading the PR list [2], you’ll find more and more > > > people > > > > > follow and get used to this rule. > > > > > > > > > > It improves collaboration efficiency, that is great! > > > > > > > > > > This makes us think about moving the rule forward, that is, > > > standardizing > > > > > PR title naming using GitHub Actions, which is a more efficient > way. > > > > > > > > > > So we'd like to start a vote on PIP 198: Standardize PR Naming > > > Convention > > > > > using GitHub Actions [3]. > > > > > > > > > > > > > > > This proposal contains: > > > > > > > > > > - Why do this? > > > > > > > > > > - How do this? > > > > > > > > > > - Pre-discussions and 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 > > > > > > > > > > > > > -- > BR, > Qiang Huang >
