Re: Podling Brpc Report Reminder - December 2021

[Justin Mclean]

Hi,

> BTW： I just checked the pod report template of 
> https://cwiki.apache.org/confluence/display/INCUBATOR/December2021 
> 
Thanks for notifying me of that I’ve fixed the template for you.

Kind Regards,
Justin

ApacheCon @Home 2020 call for papers closes in 2 days!

[Justin Mclean]

Hi,

Only a couple of days to go before to call for papers closes for ApacheCon 
@Home 2020 on Monday. 

The Incubator will be running a track at this online conference, so if you're 
thinking of submitting something, please don't delay. We'll accept talks on the 
Apache incubator itself, and talks about projects in Incubator. If you have 
recently graduated (or may do shortly), you are still welcome to submit a talk.

You can submit your talks here:
https://acna2020.jamhosted.net/cfp.html

And register to attend the conference here:
https://hopin.to/events/apachecon-home

So far (with a couple of months to go) more than 900 people have signed up for 
the conference.

Thanks,
Justin
-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Podling report formatting

[Justin Mclean]

Hi,

Some podlings (BCCed) are not formatting the reports correctly. Please do not 
remove or change  the existing formatting when editing your report in the 
incubator report.

In particular do not change the formatting of the sign-off area, we have tools 
that work off this and they depend on it being in a particular format.

As noted at the top of the page it's also best to:
• Do not change existing formatting.
• Keep all lines under 76 characters long.
• All content under the ### headings should be indented by two spaces. Do not 
use tabs.
• Please don't change the text in the headings or add new ones.
• Include a space after a bullet point or full stop on a numbered list.
• Use [X] (X and no spaces) to sign off reports.
• Do not include long URLs and use apache URL shortener https://s.apache.org.

Thanks,
Justin

P.S Thanks goes to Daffodil for a perfectly formatted report.
-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: [VOTE] Release Apache brpc(incubating) 0.9.7-rc03

[Justin Mclean]

Hi,

> “ Unless otherwise specified, all Category B licensed works should be 
> included in binary-only form in Apache Software Foundation convenience 
> binaries (and not source code). " 
> 
> 
> @Justin, Do we have any exception(Unless otherwise specified? ) to include b 
> licenses in the source code? 

In general there are no exceptions for Category B code, but as an incubating 
project and if you use the work in progress disclaimer, not that this is an 
issue in that disclaimer, and comply with all terms of that  category B 
licenses then you shod lie fine. This issue would need to be be fixed before 
graduation.

Thanks,
Justin 

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: [VOTE] Release Apache brpc(incubating) 0.9.7-rc03

[Justin Mclean]

Hi,

> - About the supporting function written by Dean Edwards in
> ./src/brpc/builtin/sorttable_js.cpp: apache TrafficControl and spark also
> include the same sortable.js and they only list the MIT licenses [1][2]

Please don't follow what TLP projects do, especially when policy says to do 
otherwise, they may have other reason for doing things they do or may not be up 
to date with policy. Spark is not a good example for a podling to follow when 
it come to it's LICENSE and NOTICE files.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: please review pod report for brpc Dec 2019

[Justin Mclean]

Hi,

Please make sure you fill in all sections of the report, as noted above the 
answer to these questions are missing:
- Answer the question about have you mentors being helpful
- Answer the question about managing you brand

Incomplete reports might be rejected and you may be asked to report again next 
month.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: please review pod report for brpc Dec 2019

[Justin Mclean]

Hi,

There also seems to be very little conversion on this mailing list, have you 
considered moving the GitHub email notifications off the dev list? You may want 
to consider adding "moving discussion to the mailing list" as one of the things 
that needs to be done before graduation.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: [VOTE] Release Apache brpc(incubating) 0.9.7-rc01

[Justin Mclean]

Hi,
For the next release candidate you might want to consider using the work in 
progress disclaimer [1] and list the licensing issue in that. Remember your 
first release doesn't need to be perfect and making release helps build a 
community.
Thanks,
Justin
1. https://incubator.apache.org/policy/incubation.html#disclaimers


-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: please review pod report for brpc Dec 2019

[Justin Mclean]

Hi,

Thanks for submitting the report. However it is incomplete and could do with 
some improvements.

Can you please:
- Answer the question about have you mentors being helpful
- Answer the question about managing you brand

if would also be nice to see some more detail in the community and project 
growth sections. 

I assume that under the releases section by "still on first apache release" 
means you are working on the first release?

I'm slightly concerned that the project has been incubating for a year and has 
not added any committers. I note that you have 50+ contributors to your repo. 
Have you possibly set the bar for contributions too high? Has the project 
discussed what is a suitable level of contribution to become a committer? I 
can't see any documentation on your web site on how to become a committer.

Thanks,
Justin


-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: Hi，Is there any official documents for all requirements to release an apache release？

[Justin Mclean]

Hi,

> We are preparing for the first release of apache release for brpc.
>  
> I search from mail list, there are several documents to describe it.
>  
> I just wonder that  if there  any official document available we can refer?

There is many, e.g release [1] and distribution policy [2] but a lot it depends 
on how complex your release is.

If you have any question ask your mentors or ask on on the general incubator 
list.

Thanks,
Justin

1. http://www.apache.org/legal/release-policy.html
2. https://www.apache.org/dev/release-distribution.html

Re: Anything I can help with to get your incubator report in ASAP?

[Justin Mclean]

Hi,

> It looks like that we don’t need to file one.

You did need to file one, but despite the reminders, missed the date to do so. 
You'll be asked to report again next month.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: Incubator Podling Report (Due 6th February)

[Justin Mclean]

Hi,

Is anyone form the PPMC dealing with the report due in a few days? This mailing 
lists seem rather quiet.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Incubator Podling Report (Due 6th February)

[Justin Mclean]

Hi,

The incubator PMC would appreciated if you could complete the podling report on 
time it's due on 6th February in a few days.

It's best if you discuss the contents of the report on the list a week before 
it is due and work collaboratively on it before submitting it.

It takes time to prepare the incubator report, have your mentors sign off the 
report and for the board to review it, so it's best if you can get it in early.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Re: Incubator Podling Report (Due 2nd January)

[Justin Mclean]

Hi,

The report is due today [1], if for some reason you can't submit a report just 
say so. 
if a report is not submitted then you will be asked to report again next month.

Thanks,
Justin

1. https://wiki.apache.org/incubator/January2019

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org

Incubator Podling Report (Due 2nd January)

[Justin Mclean]

Hi,

The incubator PMC would appreciated if you could complete the podling report on 
time it's due on 2nd January in a few days. It takes time to prepare the 
incubator report, have your mentors sign off the report and for the board to 
review it, so it's best if you can get it in early.

Thanks,
Justin

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org