Re: Refer to Answer as Apache Answer in Docs
Thanks for your follow up! Best, tison. Feng Dong 于2024年6月13日周四 10:45写道： > > Hi tison, > > Thank you for the reminder, we have fixed the issue. > > On Fri, Jun 7, 2024 at 10:12 PM tison wrote: > > > Hi, > > > > According to ASF's trademark policy, at least the first and most appoiante > > occurrence of the project name should use the full form "Apache Answer". > > > > I noticed that some of our docs still use Answer instead, like [1]. > > Although the English version of this page uses Apache Answer properly, it > > seems the Chinese version is less touched and updated. > > > > [1] https://answer.apache.org/zh-CN/docs/ > > > > Best, > > tison. > > - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Refer to Answer as Apache Answer in Docs
Hi, According to ASF's trademark policy, at least the first and most appoiante occurrence of the project name should use the full form "Apache Answer". I noticed that some of our docs still use Answer instead, like [1]. Although the English version of this page uses Apache Answer properly, it seems the Chinese version is less touched and updated. [1] https://answer.apache.org/zh-CN/docs/ Best, tison.
Re: [VOTE] Release Apache Answer(Incubating) v1.3.1-RC2 (Round2)
+1 binding * Download link valid * Checksum and signature matches * LICENSE NOTICE DISCLIAMER exist at the source tarball and binary tarball * Compile from source * Run the darwin-arm64 prebuilt binary Best, tison. Shuailing LI 于2024年5月14日周二 11:46写道： > Hello, > > This is a call for vote to release Apache Answer(Incubating) version > v1.3.1-RC2. > > There was an exception in the release file of the last vote, And we > should use the official location for the KEYS file. > https://lists.apache.org/thread/w6gkfcyonrxjmcv0pffbhg2h1q6c1l9c > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.1-incubating-RC2/ > > Release notes: > https://github.com/apache/incubator-answer/releases/tag/v1.3.1-RC2 > > Git tag for the release: > https://github.com/apache/incubator-answer/releases/tag/v1.3.1-RC2 > > Git commit id for the release: > > > https://github.com/apache/incubator-answer/commit/3a375881b845a529e89dab31da48c822b524d261 > > Keys to verify the Release Candidate: > https://downloads.apache.org/incubator/answer/KEYS > > The vote will be open for at least 72 hours or until the necessary > number of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and PGP signatures are valid. > [ ] Source code distributions have correct names matching the current > release. > [ ] LICENSE and NOTICE files are correct for each Answer repo. > [ ] All files have license headers if necessary. > [ ] No unlicensed compiled archives bundled in source archive. > > To compile from the source, please refer to: > > https://github.com/apache/incubator-answer#building-from-source > > Thanks, > shuai >
Re: Podling Answer Report Reminder - May 2024
This still seems missing. Please remember to report. Best, tison. 于2024年4月18日周四 11:38写道： > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 15 May 2024. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, May 01). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2024 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Note: The format of the report has changed to use markdown. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC > > - > To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org > For additional commands, e-mail: dev-h...@answer.apache.org > >
Fwd - Incubation Report for February 2024
Please fulfill the Incubation Report at [1] by the end of next week (2024-03-02). [1] https://cwiki.apache.org/confluence/display/INCUBATOR/February2024 Best, tison. -- Forwarded message - 发件人： tison Date: 2024年2月24日周六 10:44 Subject: [NOTICE] Incubation Report for February 2024 To: Incubator Hi, I'm trying to create an Incubation Report page for February 2024 at [1], including the following podlings according to the report group info that they should report in this month: * answer * fury * horaedb * streampark But it still lacks information that I need some help: 1. What is the desired timeline and shepherd assignments? 2. Missing IPMC level report. Perhaps the only way is going through the mailing list? 3. Missing other projects need a report. I guess we have a script to list out from the podling.xml file, but I don't find it. I may write it when I have some spare time if there is no one. I don't promise :P Best, tison. [1] https://cwiki.apache.org/confluence/display/INCUBATOR/February2024 - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Re: Do we encourage audience to contribute on JIRA?
> Answer, may be chosen because it is near the top of the dropdown, who knows. This is very possible and thanks for your action :D (I remember when I developed a user-facing support system, the most chosen issue category was "Login Issues" because it's listed as the first item, and many of the reports just have nothing to do with login ...) Best, tison. Gavin McDonald 于2024年2月1日周四 21:28写道： > > Hi, > > On Thu, Feb 1, 2024 at 12:51 PM tison wrote: > > > To be clear, IIRC the Answer podling doesn't use JIRA. > > > > Right. All projects by default get listed over at selfserve.apache.org and > when > someone wants a Jira Account they need to choose a project. > > Answer, may be chosen because it is near the top of the dropdown, who knows. > > In any case, Infra needs to know that the project does not use Jira, > otherwise the > selfserve will just assume it does. > > I have with my Infra Hat on disabled 'answer' from the dropdown so that > these requests > will no longer happen. > > HTH > > Gav... > > > > > > Best, > > tison. > > > > tison 于2024年2月1日周四 19:49写道： > > > > > > Hi, > > > > > > I received a few account requests associated with the answer project > > > in the last few months [1]. > > > > > > This is quite abnormal to me because generally contributors won't find > > > the self-serve page and send such a request if they don't get > > > explicitly encouraged. > > > > > > So I wonder if any of you or any content in our site encourages it, or > > > you have some inputs on this topic? > > > > > > Best, > > > tison. > > > > > > [1] > > https://selfserve.apache.org/jira-account-review.html?token=f1db7f05-b286-4e48-9711-cbf4a0e3874d > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org > > For additional commands, e-mail: dev-h...@answer.apache.org > > > > > > -- > > > *Gavin McDonald - * > Systems Administrator, ASF Infrastructure Team > V.P Travel Assistance Committee > > https://tac.apache.org - Applications now open for Community Over Code 2024 > in Bratislava, Slovakia. Don't delay, apply today! - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Re: Do we encourage audience to contribute on JIRA?
To be clear, IIRC the Answer podling doesn't use JIRA. Best, tison. tison 于2024年2月1日周四 19:49写道： > > Hi, > > I received a few account requests associated with the answer project > in the last few months [1]. > > This is quite abnormal to me because generally contributors won't find > the self-serve page and send such a request if they don't get > explicitly encouraged. > > So I wonder if any of you or any content in our site encourages it, or > you have some inputs on this topic? > > Best, > tison. > > [1] > https://selfserve.apache.org/jira-account-review.html?token=f1db7f05-b286-4e48-9711-cbf4a0e3874d - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Do we encourage audience to contribute on JIRA?
Hi, I received a few account requests associated with the answer project in the last few months [1]. This is quite abnormal to me because generally contributors won't find the self-serve page and send such a request if they don't get explicitly encouraged. So I wonder if any of you or any content in our site encourages it, or you have some inputs on this topic? Best, tison. [1] https://selfserve.apache.org/jira-account-review.html?token=f1db7f05-b286-4e48-9711-cbf4a0e3874d - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.5-RC2
+1 binding + Download links are valid + Checksums and PGP signatures are valid + Source code distributions have correct names matching the current release + LICENSE, NOTICE, and DISCLAIMER files exist + Binary releases can run and version matches (darwin-arm64) ? No unexpected binary files. I suspect ui/build/favicon.ico can be generated/copied during the building. This is an improvement point that is not a blocker. Best, tison. LinkinStar 于2024年1月30日周二 19:04写道： > > Hello, > > This is a call for vote to release Apache Answer(Incubating) version > v1.2.5-RC2. > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.5-incubating-RC2/ > > Release notes: > https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC2 > > Git tag for the release: > https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC2 > > Git commit id for the release: > > https://github.com/apache/incubator-answer/commit/5132cb391238cf26d3d206403b5b737451fd189a > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS > > The vote will be open for at least 72 hours or until the necessary > number of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and PGP signatures are valid. > [ ] Source code distributions have correct names matching the current > release. > [ ] LICENSE and NOTICE files are correct for each Answer repo. > [ ] All files have license headers if necessary. > [ ] No unlicensed compiled archives bundled in source archive. > > To compile from the source, please refer to: > > https://github.com/apache/incubator-answer#building-from-source > > Thanks, > LinkinStar - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.5-RC1
+1 (binding) explicitly Best, tison. tison 于2024年1月30日周二 12:31写道： > > + Download links are valid > + Checksums and PGP signatures are valid > + Source code distributions have correct names matching the current > release > + LICENSE, NOTICE, and DISCLAIMER files exist > + No unexpected binary files. > + Binary releases can run and version matches (darwin-arm64) > > Suggestion: You may try to package the files under a directory so that > it doesn't mess up the extracted folder. That is, currently the > extracted files will be extracted to the current directory, and I > suggest you add a folder named apache-answer-1.2.5-incubating-xxx/ to > contain them. This is neither a blocker nor a hard requirement; just > from my experience that can be convenient. > > Best, > tison. > > LinkinStar 于2024年1月30日周二 12:20写道： > > > > Hello, > > > > This is a call for vote to release Apache Answer(Incubating) version > > v1.2.5-RC1. > > > > The release candidates: > > > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.5-incubating-RC1/ > > > > Release notes: > > https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC1 > > > > Git tag for the release: > > https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC1 > > > > Git commit id for the release: > > > > https://github.com/apache/incubator-answer/commit/968f23db7ff920b29793589c8a3ba7e8eb402695 > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS > > > > The vote will be open for at least 72 hours or until the necessary > > number of votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] Source code distributions have correct names matching the current > > release. > > [ ] LICENSE and NOTICE files are correct for each Answer repo. > > [ ] All files have license headers if necessary. > > [ ] No unlicensed compiled archives bundled in source archive. > > > > To compile from the source, please refer to: > > > > https://github.com/apache/incubator-answer#building-from-source > > > > Thanks, > > LinkinStar - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Re: [VOTE] Release Apache Answer(Incubating) v1.2.5-RC1
+ Download links are valid + Checksums and PGP signatures are valid + Source code distributions have correct names matching the current release + LICENSE, NOTICE, and DISCLAIMER files exist + No unexpected binary files. + Binary releases can run and version matches (darwin-arm64) Suggestion: You may try to package the files under a directory so that it doesn't mess up the extracted folder. That is, currently the extracted files will be extracted to the current directory, and I suggest you add a folder named apache-answer-1.2.5-incubating-xxx/ to contain them. This is neither a blocker nor a hard requirement; just from my experience that can be convenient. Best, tison. LinkinStar 于2024年1月30日周二 12:20写道： > > Hello, > > This is a call for vote to release Apache Answer(Incubating) version > v1.2.5-RC1. > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.5-incubating-RC1/ > > Release notes: > https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC1 > > Git tag for the release: > https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC1 > > Git commit id for the release: > > https://github.com/apache/incubator-answer/commit/968f23db7ff920b29793589c8a3ba7e8eb402695 > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS > > The vote will be open for at least 72 hours or until the necessary > number of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and PGP signatures are valid. > [ ] Source code distributions have correct names matching the current > release. > [ ] LICENSE and NOTICE files are correct for each Answer repo. > [ ] All files have license headers if necessary. > [ ] No unlicensed compiled archives bundled in source archive. > > To compile from the source, please refer to: > > https://github.com/apache/incubator-answer#building-from-source > > Thanks, > LinkinStar - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org
Re: ASF Event link broken?
Thank you! Best, tison. sebb 于2023年10月31日周二 17:57写道： > Try adding .html at the end. I think that used to be done > automatically, but no longer seems to be happening. > > Note that a new method is now recommended, see: > > https://www.apache.org/events/README.txt > (as linked from the Whimsy page) > > On Tue, 31 Oct 2023 at 08:53, tison wrote: > > > > Whimsy guides podlings to add a link to > > https://www.apache.org/events/current-event. > > > > But this page is now 404. Is it moved or what we should update it with? > > > > Best, > > tison. > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
ASF Event link broken?
Whimsy guides podlings to add a link to https://www.apache.org/events/current-event. But this page is now 404. Is it moved or what we should update it with? Best, tison.
