Re: [ALC] Request to establish ALC in Guangdong-Hong Kong-Macao Greater Bay Area(GBA) (or Shenzhen, as a starter, if GBA is not applicable)

[tison]

Hi,

Thank Eason for starting this thread! Looking forward to meet in ALC GBA.

best,
tison.

On 2021/09/16 10:33:09, Eason Chen  wrote:
> Hi, ComDev PMC
>
> In order to provide software for the public good through the Apache Way in
> the Greater Bay Area(GBA), spread awareness on Apache in local
communities,
> host various events for local open source enthusiasts that include
> students, developers, and the business community, share information about
> ASF, The Apache Way, and various Apache  projects, bring together project
> users and developers. I am very happy to apply to establish an ALC
> Chapter(ACL GBA).
>
>
> ACL GBA Mentors：
>
> - Willem Jiang （Apache ID: ningjiang, ASF member，IPMC member，Apache Local
> Community Chapter Beijing Leader, PMC of Apache Apisix, Apache Camel,
> Apache CXF, ,Apache RocketMQ, Apache ServiceMix, Apache ServiceComb,
Apache
> SkyWalking，Apache Shardingsphere，Apache Iotdb )
>
> - Ted Liu (Apache id: tedliu, ASF member, Incubator PMC member,
Fundraising
> Committee member, Sponsor Ambassador)
>
> - VonGosing (Apache id:vongosling, ASF member, IPMC member)
>
>
> ACL GBA Members:
>
> - Eason Chen (Apache id: chenguangsheng, Apache EventMesh(incubating)
PPMC)
>
> - Ming Wen（Apache ID：wenming，ASF member, Apache Incubator PMC，Apache
APISIX
> PMC Chair）
>
> - Heng Du（Apache ID：duhengforever Apache RocketMQ PMC）
>
> - Liang Chen (Apache id: chenliang613, ASF member, Apache Incubator PMC,
> Apache CarbonData PMC Chair)
>
> - Zhenxu Ke (Apache ID: kezhenxu94, Apache Incubator PMC, Apache
SkyWalking
> PMC)
>
> - Guocheng Zhang (Apache ID：gosonzhang，Apache InLong (incubating) PPMC)
>
> - XiaoYu (Apache ID: xiaoyu Apache ShenYu (incubator) PPMC)
>
> - Mike Xue (Apache id: mikexue, Apache EventMesh (incubaiting) PPMC)
>
> - Charles Zhang (Apache ID：dockerzhang，Apache InLong (incubating) PPMC)
>
> - Lin Lin（Apache ID: linlin, Apache Pulsar PMC）
>
> - Jerry Shao（Apache ID: jshao，ASF member，IPMC member，Apache Spark PMC）
>
> - Sammi Chen (Apache ID: sammichen, Apache Hadoop PMC, Apache Ozone PMC
> Chair)
>
> - Zili Chen(Apache ID: tison, Apache Flink Committer, Apache Curator PMC,
> Apache Incubator Committer, Apache InLong (incubating) PPMC)
>
> - Shuai Di(Apache ID: shuaidi, Apache Linkis(incubating) PPMC)
>
>
> Warm Regards,
>
> Eason Chen
>

Re: Welcome Ted Liu as a New PMC Member

[tison]

Congrats and well deserved!

BTW I'd like to know where are wiki pages or other information source of ComDev
with which I may follow up things?

Best,
tison.


Michael McCandless  于2021年10月19日周二 下午7:41写道：

> Welcome Ted!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Mon, Oct 18, 2021 at 7:48 AM Swapnil M Mane 
> wrote:
>
> > Hi everyone,
> >
> > The ComDev PMC has invited Ted Liu to become a member of the committee
> > and we are glad to announce that he has accepted the nomination.
> >
> > Ted has been a great open-source supporter, is active on our lists and
> > has helped organise and run events in China. He is actively involved
> > in the ALC initiative in China, Incubator, Fundraising and has been an
> > integral part of ApacheCon Asia.
> >
> > Please join me in welcoming Ted and congratulating him on his new role.
> >
> > Thanks,
> > Swapnil M Mane,
> > On behalf of the ComDev PMC
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: Thoughts on alternative communication channels for our communities

[tison]

Hi Roman,

I noticed your summary and focus on user-facing channels. Comments inline.

Roman Shaposhnik 于2022年2月22日 周二23:32写道：

> Thanks for all the feedback so far. If I were to summarize what's been
> expressed
> on this thread so far, it seems that we're all agreeing that:
>1. Even if mailing lists appear to be clunky in 2022 they are still
> appreciated
> as THE channel for any kind of "official" ASF business to be conducted
> (e.g. major decision points, voting, etc.). In that sense -- whatever
> other
> channels may have been used to build consensus -- the final (or
> official
> if you will) closure is expected to happen on a mailing list.


Yes. Actually communication happens in various way, public or private,
despite of the rules we set up or encourage. But we still need a single
source of truth for catching up decisions and mailing list works well in
this direction.

2. There are TONS of alternative communication channels for developers
> and users to explore and it is unlikely that we will have any semblance
> of convergence there -- these are too fragmented by geographical,
> cultural,
> language and other preferences.
>
> Now, if I were to make an observation, I'd split our constituency in 3 of
> the
> usual concentric circles: PMC, Developers/Committers, Users.
>
> It sounds like making sure that all official PMC business to be conducted
> on the
> mailing list is not only desirable from the ASF's perspective but also
> [mostly]
> appreciated by the PMCs themselves. That leaves Developers/Committers and
> Users.
>
> My biggest problem is actually with users -- it seems that having all these
> extra
> communication channels makes it more difficult for newcomers to find good
> entry points re: engaging with the projects -- or maybe not. That's still
> not clear
> to me and I would love to hear more feedback.
>
> What do ppl think?
>
> Thanks,
> Roman.


I think the challenge here for the wider community of developers and users
are somehow the same - community members who are less involved tends to use
the channel they're familiar with and responsive.

Why GitHub issues and discussions mentioned many times? It's because that
the actual development activities happens there for those projects and
questions or discussion thrown there get responses. The point that you
don't have to create a new account is important as mentioned above in this
thread.

Now let's think of a typical journey of a user. The most frequently asked
question is "How do I do X". It should be almost covered by documents, and
when documents cannot solve the question, communication requirements occur.

No matter what channel it provides, a user@ mailing list, an Q&A GitHub
discussion, or a user forum, what users want eagerly is to get response and
answered. Always a project's README should tell where you can ask a
question and make sure it's THE channel you put an eye on.

Users preference matters here since the cost here may be too high to just
ask a question but subscribing a mailing list and receiving all
notification. Especially younger users may be even lack of knowledge to
subscribe a mailing list (it's common in China).

This can be something like "friction". Users used to ask on StackOverflow
won't be willing to switch to another channel for one question.

On communication tools topic, I always sort out channels into 2×2 kinds.

1. topic grouped channel
2. instant messaging channel

multiples

1. user channel
2. developer channel (can be further diveded into ecosystem developer,
kernel Developer and maintainers)

I think a community should grow all of them in the real world. But keep one
topic grouped channel as SSOT of decisions.

You should build instant messaging channel just like IRC in the early days,
because if operated properly, it strengthens connections and closed short
topic effectively.

However, topic grouped channel is required also because tough discussions
require more time and focused (by topic). Instant messaging can hardly
achieve it even if threads are supposed, because the mindset is to
"chatting".

Users wants their questions to be answered, in the way they are familiar
with. Apache Flink resolves most possible input channel.

1. user@ mailing list. And for Chinese users, user-zh@. Note that the
latter reflects "in the way they're familiar with".
2. Vendors' solution engineers answer questions on StackOverflow.
3. Contributors from China answer questions in DingTalk, WeChat, or Feishu.
4.  ...

Of course, it requires more community members who can answer user questions.

To sum up, you CAN have multiple channels for answering user questions and
collect best practices. Whether or not it's fragmented is up to (1) whether
or not you conclude FAQ into (central) docs and (2) whether or not you can
covered all of those channels so that users get them all responsive.

> --
Best,
tison.

Re: Welcome Willem Jiang as a New PMC Member

[tison]

Congrats and well deserved!

Best,
tison.


Willem Jiang  于2022年2月24日周四 15:38写道：

> Thanks everyone，
> it is an honor for me to be a part of ComDev PMC.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Feb 24, 2022 at 2:50 PM Swapnil M Mane 
> wrote:
> >
> > Hi everyone,
> >
> > The ComDev PMC has invited Willem Jiang to become a member of the
> committee
> > and we are glad to announce that he has accepted the nomination.
> >
> > Willem has been a great open-source supporter, deeply understand Apache
> Way and
> > has helped organise and run various events in China. He is actively
> involved
> > in the ALC initiative in China. He is the chapter lead of ALC Beijing
> > and a mentor of ALC Shenzhen.
> > Also, he has been an integral part of ApacheCon Asia and played a
> > vital role in organising and executing ApacheCon Asia.
> > Along with his active participation in community development, he is
> > also part of numerous other Apache projects as well.
> >
> > Please join me in welcoming Willem and congratulating him on his new
> role.
> >
> > Thanks,
> > Swapnil M Mane,
> > On behalf of the ComDev PMC
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

How to turn on GitHub Discussion?

[tison]

Hi,

I notice that Apache SkyWalking enables GitHub Discussion[1] feature for
better communication
between developers and users. But I don't find an entry in .asf.yaml
configs[2].

Hence, I'd ask for help that how to turn on GitHub Discussion for a
repository under apache org
on GitHub? I'm going to make a proposal to do so for Apache InLong
(incubator) FYI.

Best,
tison.

[1] https://github.com/apache/skywalking/discussions
[2] https://github.com/apache/skywalking/blob/master/.asf.yaml

Re: How to turn on GitHub Discussion?

[tison]

Sorry I just find docs about it:
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions

XD

Best,
tison.


tison  于2022年2月25日周五 13:47写道：

> Hi,
>
> I notice that Apache SkyWalking enables GitHub Discussion[1] feature for
> better communication
> between developers and users. But I don't find an entry in .asf.yaml
> configs[2].
>
> Hence, I'd ask for help that how to turn on GitHub Discussion for a
> repository under apache org
> on GitHub? I'm going to make a proposal to do so for Apache InLong
> (incubator) FYI.
>
> Best,
> tison.
>
> [1] https://github.com/apache/skywalking/discussions
> [2] https://github.com/apache/skywalking/blob/master/.asf.yaml
>

SPDX identifiers in Apache projects

[tison]

Hi,

Recently I notice the SPDX identifiers format defined by the Linux
Foundation for machine
processing of license information based on the SPDX License Identifiers
that are here available:
http://spdx.org/licenses/.

I can see that all of Apache project use it's own License header
template[1] and curious what's
the suggestions on using SPDX identifiers in Apache projects. Can an Apache
project adopts both
conventions? Is it encouraged or acceptable a general project using Apache
License using the
SPDX identifiers as license header?

Best,
tison.

[1]
https://github.com/apache/skywalking-eyes/blob/eb0e0b091ea41213f712f622797e37526ca1e5d6/assets/header-templates/Apache-2.0-ASF.txt

Re: How to become member in Apache foundtion

[tison]

Hi Michael,

>From your description, it's vague that why you want to know how to become a
member in ASF. Basically, running projects under Apache License doesn't
require you to be a member of ASF.

If you're looking forward to running your projects under ASF, I'd suggest
you to read the Apache Incubator Cookbook:
https://incubator.apache.org/cookbook .

For the question itself, you may read these related pages:
* https://www.apache.org/foundation/governance/members.html
* https://www.apache.org/foundation/governance/meetings
* https://www.apache.org/foundation/governance/meetings#membervoting

Best,
tison.


Liu Ted  于2022年5月30日周一 17:11写道：

> Hi Michael,
> There are quite a few ASF members at Alibaba Cloud already. If needed, I
> can help you engage with them so that you can learn from each other.
>
> Best regards,
> Ted Liu (刘天栋)Wechat: tedliu002
>
>
>   2022 年 5 月 30 日周一 17:03，于巍(漠雪) 写道：
>
> Hi Dev,
>
> I am working at Alibaba cloud database group, and we open source two
> database project by Apache license last year. Could you please tell me how
> to become member in Apache foundtion, I have check in google but not found
> right anwser for now.
>
> Regards
> Michael Yu.
>
>
>
>

Looking for a landscape or roadmap(picture) of Apache projects

[tison]

Hi community,

I'm going to post a landscape in my PPT to introduce ASF and Apache
projects to students but failed to find such one. A landscape may look like
https://landscape.cncf.io/.

Apart from the landscape form, I remember that in "Trillions and Trillions
Served" it shows that we ever produced a T-shirt that print a roadmap of
Apache projects.

I'm asking for help if anyone on this mailing list can share a landscape or
roadmap(picture) of Apache projects.

Looking forward to hearing from you :)

Best,
tison.

Re: Looking for a landscape or roadmap(picture) of Apache projects

[tison]

Hi Ted,

Thank you! This looks great.

Best,
tison.

Re: Looking for a landscape or roadmap(picture) of Apache projects

[tison]

Hi Christiano,

You can refer to this tweet
https://twitter.com/tison1096/status/1535928890018844673. I include the
roadmap picture (of an Apache topic T-shirt) there.

Thank Ted and I'd like to know where I can buy such a T-shirt :P

Best,
tison.


Christiano Anderson  于2022年6月11日周六 14:35写道：

> Hi,
>
> I guess the landscape or roadmap was not sent to the mailing list. I'm
> interested on this topic as well, could you please send it to me?
>
> Thank you
>
>
> --- Original Message ---
> On Saturday, June 11th, 2022 at 07:30, tison  wrote:
>
>
> >
> >
> > Hi Ted,
> >
> > Thank you! This looks great.
> >
> > Best,
> > tison.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Re: Authorization required for translating “Trillions and Trillions Served”

[tison]

Thank Ted, for starting this thread!

I'm gonna translate this documentary's manuscript into Chinese and perhaps
make some comments. This, from my perspective, can be a kind of remix and
need some approvals from the authors. If we said the documentary is under
CC-BY 4.0 or so, it could be trivial to follow. But I don't find such
COPYING info in the original video :)

Best,
tison.


Liu Ted  于2022年12月19日周一 22:58写道：

> Dear Myrle, Thanks.
>
> Hi Mr. Joe Brockmeier, Any advice?
>
> Best regards,
>
> Ted Liu
>
>
> 2022 年 12 月 19 日周一 19:48，Myrle Krantz
>  写道：
> I'm not sure whether the ASF owns the copyright (ie work for hire) or
> whether that remained with the creator of the film.  M&PR (ie Joe
> Brockmeier) should have access to the original contract so they should be
> able to answer that.  I'd expect though that, if we do own the copyright,
> we'd want to use it to enable things like translations.
>
> Best Regards,
> Myrle
>
> On Mon, Dec 19, 2022 at 12:31 PM Liu Ted 
> wrote:
>
> > Hi, Does anyone know what authorization is required by the ASF if one
> > wanted to translate and/or use the content of this "Trillions and
> Trillions
> > Served"?
> > https://www.youtube.com/watch?v=JUt2nb0mgwg
> >
> > Best regards,
> > Ted Liu
>
>

Re: you asked for feedback

[tison]

Hi Jennifer,

ASF mailing list does not allow inline images. You can upload to any hosted
service and share the link.

Best,
tison.


Jennifer Smith  于2023年3月28日周二 19:14写道：

> Hello,
> Newbie here. You asked for feedback. See screenshot.
>
> [image: image.png]
>

Re: Standardise on 'main' as the default branch?

[tison]

> Name the branch, on which development happens "develop" and the one that
contains the released versions "releases". With "main" you never really
know what it's used for.

To me, "main" is always "develop".

Best,
tison.


sebb  于2023年4月2日周日 19:34写道：

> On Sun, 2 Apr 2023 at 09:39, Christofer Dutz 
> wrote:
> >
> > I would like to make a slightly different proposal.
> > Name the branch, on which development happens "develop" and the one that
> contains the released versions "releases". With "main" you never really
> know what it's used for.
>
> I agree that main is no less ambiguous than master, but the website
> does not really have a development/release cycle, so I'm not sure
> 'release' is appropriate here.
>
> Maybe the default branch should be something like 'production' or
> 'live' for websites.
> However that would mean changing the other repos to keep in step.
>
> > But I think I brought this up multiple times before, so if be +1 on a
> change.
>
> Thanks!
>
> > Chris
> >
> > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
> > 
> > From: Willem Jiang 
> > Sent: Sunday, April 2, 2023 10:19:44 AM
> > To: dev@community.apache.org 
> > Subject: Re: Standardise on 'main' as the default branch?
> >
> > +1 for it.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Apr 1, 2023 at 8:11 PM sebb  wrote:
> > >
> > > All bar one of the 4 comdev Git repos use 'main' as the default branch.
> > >
> > > I think we should standardise on that going forward, and change the
> > > default branch for comdev-site.
> > >
> > > Agreed?
> > >
> > > Sebb
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Donating a project to ASF

[tison]

Hi David,

ASF welcomes open-source projects with a health community and can serve as
an umbrella of such projects.

After reading the issue mentioned above, I'd like to ask for a community
overview
of this project; especially after Shopify shifts away from this project, is
the community
still vibrant to maintain the software?

For donating a project to ASF, there are generally two ways:

1. Going through the incubator process[1];
2. An existing project accepts large portion of code contributions, with
clear IP clearance[2].

For approach 1, you can read the proposal guide and try to answer the
questions in
proposal template[3].

For approach 2, maybe you can try to get in touch with Kafka PMC. But I'm
afraid there are
already several open-source Go clients, and they may not accept this one
specially.

Best,
tison.

[1] https://incubator.apache.org/guides/proposal.html
[2] https://incubator.apache.org/guides/ip_clearance.html
[3] Proposal



David Mariassy  于2023年4月11日周二 21:36写道：

> Hi,
>
> My company would like to learn more about the process of donating one of
> our OSS projects (shopify/sarama <https://github.com/Shopify/sarama>) to
> Apache. There is a vibrant community supporting the project, while
> Shopify's own development priorities shifted such that we no longer
> consider ourselves to be the best stewards of the project (more details
> here
> <https://github.com/Shopify/sarama/issues/2461>). If you have any
> guidelines on how to go about potentially converting Shopify/sarama into
> apache/sarama, please let me know!
>
> Thanks in advance!
>
> --
> David Mariassy
> Staff Data Developer
> [image: Shopify]
> <https://www.shopify.com/?utm_medium=salessignatures&utm_source=hs_email>
>

Where I can get the full video of Trillions and Trillions Served documentary?

[tison]

Hi,

Today, I noticed that this documentary gets hidden from the youtube source.
Is there anywhere I can watch it or download it?

Best,
tison.

Re: Getting involved as newcomer to ASF

[tison]

Hi Prathamesh,

Did you read through the community page of Cassandra[1]?

The primary channel of ASF project is via mailing list. I checked that
Cassandra's
mailing list is active so you can subscribe its user@ or dev@ mailing list
to ask
questions or ask its maintainers to add you to specific Slack channel.

Best,
tison.

[1] https://cassandra.apache.org/_/community.html#discussions


Prathamesh Palaskar  于2023年6月5日周一 05:52写道：

> Hello,
>
> I am exploring Cassandra as a means to get involved with ASF. I tried to
> get in touch for Cassandra through Cassandra channel but it requires An
> apache id or apache email address. I have not managed to find any link to
> create an account for  anywhere on the website. Please advise , where can I
> find this information?
>
> Regards,
> Prathamesh
>

Re: Signing releases using automated release infra

[tison]

Hi Daniel,

> Automating this process *requires* a
> reproducible build process that has been approved by the ASF security
> team

It sseems the security team has limited bandwidth to process such a review
request. I make the request to secur...@apache.org for OpenDAL (incubating)
and the team member tells me they are working on other items now.

This is of course understandable, while I'm wondering if we have a JIRA
project to track this request instead of I keep an eye on the security
mailing list which is quite busy for other threads. Also, I don't think
such a request needs to be private and secur...@apache.org is private.

Briefly, I'm not sure if we have a public tracking place for requests
on automating
releases.

Best,
tison.


Daniel Gruno  于2023年7月19日周三 17:28写道：

> On 2023-07-19 11:21, Francis Chuang wrote:
> > Is infra happy to explore the case where release artifacts are
> automatically uploaded via CI?
>
> The exploration is already ongoing.
>
> >
> > This would go a long way towards automating our release process as
> asking RMs to download the release artifacts from GitHub and uploading them
> manually is a bit clunky.
>
> I do want to point out one thing that is a general requirement and not
> specific to this email or project: Automating this process *requires* a
> reproducible build process that has been approved by the ASF security
> team. That is the first place projects should look when they decide to
> explore this route, and is a requirement before infra will even
> entertain the notion of automated artifacts for a project.
>
> >
> > On 2023/07/18 19:55:00 Volkan Yazıcı wrote:
> >> Abstract: Signing release artifacts using an automated release
> >> infrastructure has been officially approved by LEGAL. This enables
> >> projects to sign artifacts using, say, GitHub Actions.
> >>
> >> I have been trying to overhaul the Log4j release process and make it
> >> as frictionless as possible since last year. As a part of that effort,
> >> I wanted to sign artifacts in CI during deployment and in a
> >> `members@a.o` thread[0] I explained how one can do that securely with
> >> the help of Infra. That was in December 2022. It has been a long,
> >> rough journey, but we succeeded. In this PR[1], Legal has updated the
> >> release policy to reflect that this process is officially allowed.
> >> Further, Infra put together guides[2][3] to assist projects. Logging
> >> Services PMC has already successfully performed 4 Log4j Tools releases
> >> using this approach, see its release process[4] for a demonstration.
> >>
> >> [0] (members only!)
> >> https://lists.apache.org/thread/1o12mkjrhyl45f9pof94pskg55vhs61n
> >> [1] https://github.com/apache/www-site/pull/235
> >> [2] https://infra.apache.org/release-publishing.html#signing
> >> [3]
> https://infra.apache.org/release-signing.html#automated-release-signing
> >> [4]
> https://github.com/apache/logging-log4j-tools/blob/master/RELEASING.adoc
> >>
> >> # F.A.Q.
> >>
> >> ## Why shall a project be interested in this?
> >>
> >> It greatly simplifies the release process. See Log4j Tools release
> >> process[4], probably the simplest among all Java-based ASF projects.
> >>
> >> ## How can a project get started?
> >>
> >> 1. Make sure your project builds are reproducible (otherwise there is
> >> no way PMC can verify the integrity of CI-produced and -signed
> >> artifacts)
> >> 2. Clone and adapt INFRA-23996 (GPG keys in GitHub secrets)
> >> 3. Clone and adapt INFRA-23974 (Nexus creds. in GitHub secrets for
> >> snapshot deployments)
> >> 4. Clone and adapt INFRA-24051 (Nexus creds. in GitHub secrets for
> >> staging deployments)
> >>
> >> You might also want to check this[5] GitHub Action workflow for
> inspiration.
> >>
> >> [5]
> https://github.com/apache/logging-log4j-tools/blob/master/.github/workflows/build.yml
> >>
> >> ## Does the "automated release infrastructure" (CI) perform the full
> release?
> >>
> >> No. CI *only* uploads signed artifacts to Nexus. The release manager
> >> (RM) still needs to copy the CI-generated files to SVN, PMC needs to
> >> vote, and, upon consensus, RM needs to "close" the release in Nexus
> >> and so on.
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

[QUESTION] Download statistics missing

[tison]

Hi,

Previously, I used https://logging1-he-de.apache.org/stats to fetch
download statistics of certain projects like Pulsar. But I notice that the
data are missing for the past day and past week (perhaps more).

Is the provision broken, or is it shut down on purpose?

Best,
tison.

Re: [QUESTION] Download statistics missing

[tison]

Thank you Daniel! This works.

Best,
tison.


Daniel Gruno  于2023年8月9日周三 13:28写道：

> On 2023-08-09 07:23, tison wrote:
> > Hi,
> >
> > Previously, I used https://logging1-he-de.apache.org/stats to fetch
> > download statistics of certain projects like Pulsar. But I notice that
> the
> > data are missing for the past day and past week (perhaps more).
> >
> > Is the provision broken, or is it shut down on purpose?
> >
> > Best,
> > tison.
> >
>
> Use the more generic https://logs.apache.org/stats/ address instead of a
> specific node name. The database cluster is currently migrating to a new
> setup, and there will be a period where the dataset is not complete. It
> will eventually fill up :)
>
>

Please add Pulsar Summit to the Events calendar

[tison]

Hi,

Please add Pulsar Summit to the Apache Events calendar[1]. It has
trademarks approval[2].

Pulsar Summit – October 25-27, 2023
https://pulsar-summit.org/event/north-america-2023
San Francisco

Best,
tison.

[1] https://events.apache.org/event/calendar.html
[2] https://lists.apache.org/thread/hwyy82xbrv6qm6dnssc5dmy1f8n4o7dt

Re: Please add Pulsar Summit to the Events calendar

[tison]

Thank you!

I saw an entry for Pulsar Summit APAC at 2023-11-17 to 2023-11-18. But it
isn't planned on the pulsar-summit site and I don't hear of it. Do you know
when and who add this entry?

Best,
tison.


 于2023年8月30日周三 21:55写道：

> On Wed, 2023-08-30 at 09:25 +0800, tison wrote:
> > Hi,
> >
> > Please add Pulsar Summit to the Apache Events calendar[1]. It has
> > trademarks approval[2].
> >
> > Pulsar Summit – October 25-27, 2023
> > https://pulsar-summit.org/event/north-america-2023
> > San Francisco
> >
> > Best,
> > tison.
> >
> > [1] https://events.apache.org/event/calendar.html
> > [2] https://lists.apache.org/thread/hwyy82xbrv6qm6dnssc5dmy1f8n4o7dt
>
> Done.
>

Re: Please add Pulsar Summit to the Events calendar

[tison]

Thank you!

I saw the thread[1]. So far, the preparation of APAC hasn't been started
and IIUC the date hasn't been determined (the date of NA changed also). We
(the Pulsar PMC) will send a new request when the date is confirmed.

Best,
tison.

[1] https://lists.apache.org/thread/hwyy82xbrv6qm6dnssc5dmy1f8n4o7dt

Mark Thomas  于2023年8月30日周三 23:46写道：

> It was requested by mme...@apache.org on the trademarks@ list
>
> Mark
>
>
> On 30/08/2023 16:44, rbo...@rcbowen.com wrote:
> > On Wed, 2023-08-30 at 22:30 +0800, tison wrote:
> >> Thank you!
> >>
> >> I saw an entry for Pulsar Summit APAC at 2023-11-17 to 2023-11-18.
> >> But it
> >> isn't planned on the pulsar-summit site and I don't hear of it. Do
> >> you know
> >> when and who add this entry?
> >
> > I don't, although it was either me or Mark Thomas. I've removed it.
> > Please let me know if we need to add anything back.
> >
> > --Rich
> >
> >>  于2023年8月30日周三 21:55写道：
> >>
> >>> On Wed, 2023-08-30 at 09:25 +0800, tison wrote:
> >>>> Hi,
> >>>>
> >>>> Please add Pulsar Summit to the Apache Events calendar[1]. It has
> >>>> trademarks approval[2].
> >>>>
> >>>> Pulsar Summit – October 25-27, 2023
> >>>> https://pulsar-summit.org/event/north-america-2023
> >>>> San Francisco
> >>>>
> >>>> Best,
> >>>> tison.
> >>>>
> >>>> [1] https://events.apache.org/event/calendar.html
> >>>> [2]
> >>>> https://lists.apache.org/thread/hwyy82xbrv6qm6dnssc5dmy1f8n4o7dt
> >>>
> >>> Done.
> >>>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>

[DISCUSS] Possibility to use BuildJet for ARM CI support?

[tison]

BuildJet[1] provides a good GitHub integration to run CI workflows on ARM
machines. I use it for my personal project and it works well[2].

Recently, in Apache Kvrocks we found that the ARM build on AMD machine with
QEMU supports [3] often exceeds the max timeout limitation (6 hours). So
we're seeking for possibility to support ARM CI env.

Is it possible to use BuildJet for so? I can imagine either we have a grant
or try to negotiate a target sponsorship.

Best,
tison.

[1] https://buildjet.com/for-github-actions
[2]
https://github.com/korandoru/hawkeye/blob/d58b3fc1f869790fa44ae95c20a8a9e69f34c834/.github/workflows/release.yml#L39-L40
[3]
https://github.com/apache/kvrocks/blob/10465a4255369165d8674dd2b57974099e5bd7af/.github/workflows/nightly.yaml#L40-L45

Enable tasklist for apache GitHub org

[tison]

Background -
https://docs.github.com/en/issues/managing-your-tasks-with-tasklists/creating-a-tasklist

This feature can help project/issue management and doesn't requirement
extra payment. May our admin join the wishlist so that we can enable it
later. (Or perhaps we're already in the wishlist?)

Best,
tison.

Re: Helping to welcome non-english communities by questioning our rules?

[tison]

FWIW, I ever wrote a (Chinese) blog about communication tools for an OSS
community[1], that has a section to talk about mailing list.

I enter the OSS world with the Perl 6 (a.k.a. Raku) community so it's
native to me for working with mailing list and even IRC. But it's quite
unfamiliar for especially new contributors even from a worldwide
perspective.

> What if we had a global storage for everything that happens in a project?

Convey/Forwarding to the mailing list is the current solution. I'm
prototyping a community tool to archive activities and will be glad to
collaborate. As Orbit or CommonRoom does, saving all the activities from
different channels so that we can be both (1) archive (2) searchable, and
(3) even _analyzable_.



Best,
tison.

[1] https://zhuanlan.zhihu.com/p/395057453


 于2023年10月26日周四 22:20写道：

> On Thu, 2023-10-26 at 07:42 +, Christofer Dutz wrote:
> > We have this rule: If it didn’t happen on the list, it didn’t happen
> > (Don’t even know if it’s really written down somewhere or if it’s
> > just a common mantra).
>
> It's written here:
>
> https://community.apache.org/newbiefaq#NewbieFAQ-IsthereaCodeofConductforApacheprojects
> ?
>
> And here: https://incubator.apache.org/guides/committer.html
>
> Whether those constitute "policy" or just best practice is left as an
> exercise for the reader.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Helping to welcome non-english communities by questioning our rules?

[tison]

For holding translated content, the FSF hosts translations for its licenses
as "Unofficial translations"[1].

The reason can be that it's somehow legal terms so it's at risk if
different versions imply different meanings. But for the "policy" where we
generally have the understanding "Whether those constitute "policy" or just
best practice is left as an exercise for the reader.", if there are ASF
members maintain the content, I agree that we can mark the translated
content as official.

Best,
tison.

[1] https://www.gnu.org/licenses/translations.en.html


tison  于2023年10月27日周五 11:46写道：

> FWIW, I ever wrote a (Chinese) blog about communication tools for an OSS
> community[1], that has a section to talk about mailing list.
>
> I enter the OSS world with the Perl 6 (a.k.a. Raku) community so it's
> native to me for working with mailing list and even IRC. But it's quite
> unfamiliar for especially new contributors even from a worldwide
> perspective.
>
> > What if we had a global storage for everything that happens in a
> project?
>
> Convey/Forwarding to the mailing list is the current solution. I'm
> prototyping a community tool to archive activities and will be glad to
> collaborate. As Orbit or CommonRoom does, saving all the activities from
> different channels so that we can be both (1) archive (2) searchable, and
> (3) even _analyzable_.
>
>
>
> Best,
> tison.
>
> [1] https://zhuanlan.zhihu.com/p/395057453
>
>
>  于2023年10月26日周四 22:20写道：
>
>> On Thu, 2023-10-26 at 07:42 +, Christofer Dutz wrote:
>> > We have this rule: If it didn’t happen on the list, it didn’t happen
>> > (Don’t even know if it’s really written down somewhere or if it’s
>> > just a common mantra).
>>
>> It's written here:
>>
>> https://community.apache.org/newbiefaq#NewbieFAQ-IsthereaCodeofConductforApacheprojects
>> ?
>>
>> And here: https://incubator.apache.org/guides/committer.html
>>
>> Whether those constitute "policy" or just best practice is left as an
>> exercise for the reader.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

ASF Event link broken?

[tison]

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.

Re: ASF Event link broken?

[tison]

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
>
>

Re: Community building advice

[tison]

Hi Rich,

Thanks a lot for starting this thread and driving this effort. I'm glad to
offer help and join the force if it can have an umbrella issue/ticket that
we can go into the concrete subtasks.

So far, I share some common feelings as you described above:

* Super-high committer bars even trade committer titles with certain effort
(25 PR = committer; this can encourage speculation instead of
collaboration, and generally, the PMC will later find that the newly
elected committers vanished since "the trade is finished").
* Committer/PMC elections influenced by company affiliation/role rather
than by public discussion - Yes, of course. It may indicate another problem
with the ability to say no and how we build such an environment.

Besides, emphasizing the importance of a project's vision may also help
since an OSS community exists to solve a specific range of problems.
Without a clear definition of the vision, a project is at high risk to
continue. Also, this can be a rectification for thinking too tightly of
so-called "no code contributions".

All the sentences I use above can be associated with one or more concrete
real stories. I don't know if we use this story directly (vs. anonymously)
in the advice page.

Best,
tison.


 于2023年10月31日周二 22:47写道：

> Hi, folks,
>
> As discussed various times on Slack, I am planning to create some
> concrete, practical advice to our project communities about how to grow
> their developer communities. I've put a bullet list here -
> https://community.apache.org/communitybuilding/ - and will be
> developing that over the coming year (I hope).
>
> I have become more than a little concerned about trends that I'm seeing
> across the Foundation: Super-high committer bars with no real
> justification; Ignoring contributors, who then eventually go away in
> frustration; Off-list discussions that are then never discussed in the
> view of the community; Committer/PMC elections influenced by company
> affiliation/role rather than by public discussion. I am hoping that we
> can address some of these by education, and by having "official" pages
> that we can point to when projects are learning how to be ASF
> projects.
>
> Yes, some of this happens in the Incubator. My concern is post-
> incubator, when the decision-makers on the project arrives post-
> incubator, and so don't benefit from that experience. A second-
> generation problem, you might say.
>
> Anyways, as always, I welcome and appreciate your participation in
> writing this stuff, and in organizing it.
>
> Thanks.
>
> --Rich
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [DISCUSS] How about hosting discourse as an alternative way for mailing list?

[tison]

+cc comdev

Maybe you will be intested in this new type communication.

Best,
tison.

Xuanwo  于2023年12月19日周二 19:15写道：
>
> > Discourse will provide us an incoming email address. All email sent to
> > this address will become a post in discourse. We need to add this
> > address into the dev@o.a.o's subcriber list.
>
> This is talking about Discourse SaaS which cost about $100 ($50 if we have 
> non-profit discount).
>
> If we can request a vm from ASF Infra, we will need:
>
> - VM with 4C8G
> - Postgresql
> - A SMTP account to send mails
> - A domain like discuss.opendal.apache.org
>
> On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
> >> Does it need any configuration from the mailing list part, i.e.,
> >> involve INFRA setup?
> >
> > Discourse will provide us an incoming email address. All email sent to
> > this address will become a post in discourse. We need to add this
> > address into the dev@o.a.o's subcriber list.
> >
> > No another setup needed, AFAIK.
> >
> > We need some test and demo to make sure everything works as expected.
> > At the time of writing, I don't know how to do that.
> >
> > On Tue, Dec 19, 2023, at 18:19, tison wrote:
> >>> called mailing list mode
> >>
> >> Does it need any configuration from the mailing list part, i.e.,
> >> involve INFRA setup?
> >>
> >> I don't know how this happen but as long as we have a readable copy on
> >> the dev@ mailing list, other integration as view can be OK.
> >>
> >> Best,
> >> tison.
> >>
> >> Jun Ouyang  于2023年12月19日周二 18:16写道：
> >>>
> >>> Hi xuanwo:
> >>> That’s great! I strongly agree with this change. But I have a concern 
> >>> about
> >>> markdown support sync to Maillist, It seems will cause more bad 
> >>> experiences
> >>> for Maillist users.
> >>>
> >>> *GPG public key: 4A6D297E6F74638E4D5F8E99152AC7B5F7608B26*
> >>> *Thanks,*
> >>> *Jun Ouyang*
> >>>
> >>>
> >>> On Tue, Dec 19, 2023 at 17:36 Xuanwo  wrote:
> >>>
> >>> > Hi, all opendal community members
> >>> >
> >>> > I'm thinking about hosting discourse as an alternative way for mailing
> >>> > list.
> >>> >
> >>> > Discourse has a feature called mailing list mode. After enabling this
> >>> > feature, we will sync every post between our mailling list and 
> >>> > discourse.
> >>> >
> >>> > - Users can create/reply to posts created in discourse via email.
> >>> > - Users can create/reply to posts send by email in discourse.
> >>> > - Users can search all posts in discourse.
> >>> >
> >>> > By adding this new alternative, I can see the following benefits:
> >>> >
> >>> > - All discussion still happen and archived on mailing list (here).
> >>> > - Users like mailing list can still uses mailing list without any 
> >>> > change.
> >>> > - Users like forums can use discourse instead.
> >>> > - Users don't need to subscribe the email list first before asking
> >>> > questions.
> >>> > - Markdown support, Full-text search support, better UI/UX...
> >>> >
> >>> > What do you think? Do you want this alternative?
> >>> >
> >>> > Xuanwo
> >>> >
> >
> > --
> > Xuanwo
>
> --
> Xuanwo

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

Re: [DISCUSS] How about hosting discourse as an alternative way for mailing list?

[tison]

After a closer look, I don't think Discourse brings too much value but
a new platform to track.

Although as long as it's a third-party integration that doesn't affect
the view from a pure mailing list user, I don't object it. But it
doesn't seem valuable to me.

INFRA provides https://lists.apache.org/list.html?d...@opendal.apache.org
to track the threads and it's also searchable.

Best,
tison.

tison  于2023年12月19日周二 19:23写道：
>
> +cc comdev
>
> Maybe you will be intested in this new type communication.
>
> Best,
> tison.
>
> Xuanwo  于2023年12月19日周二 19:15写道：
> >
> > > Discourse will provide us an incoming email address. All email sent to
> > > this address will become a post in discourse. We need to add this
> > > address into the dev@o.a.o's subcriber list.
> >
> > This is talking about Discourse SaaS which cost about $100 ($50 if we have 
> > non-profit discount).
> >
> > If we can request a vm from ASF Infra, we will need:
> >
> > - VM with 4C8G
> > - Postgresql
> > - A SMTP account to send mails
> > - A domain like discuss.opendal.apache.org
> >
> > On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
> > >> Does it need any configuration from the mailing list part, i.e.,
> > >> involve INFRA setup?
> > >
> > > Discourse will provide us an incoming email address. All email sent to
> > > this address will become a post in discourse. We need to add this
> > > address into the dev@o.a.o's subcriber list.
> > >
> > > No another setup needed, AFAIK.
> > >
> > > We need some test and demo to make sure everything works as expected.
> > > At the time of writing, I don't know how to do that.
> > >
> > > On Tue, Dec 19, 2023, at 18:19, tison wrote:
> > >>> called mailing list mode
> > >>
> > >> Does it need any configuration from the mailing list part, i.e.,
> > >> involve INFRA setup?
> > >>
> > >> I don't know how this happen but as long as we have a readable copy on
> > >> the dev@ mailing list, other integration as view can be OK.
> > >>
> > >> Best,
> > >> tison.
> > >>
> > >> Jun Ouyang  于2023年12月19日周二 18:16写道：
> > >>>
> > >>> Hi xuanwo:
> > >>> That’s great! I strongly agree with this change. But I have a concern 
> > >>> about
> > >>> markdown support sync to Maillist, It seems will cause more bad 
> > >>> experiences
> > >>> for Maillist users.
> > >>>
> > >>> *GPG public key: 4A6D297E6F74638E4D5F8E99152AC7B5F7608B26*
> > >>> *Thanks,*
> > >>> *Jun Ouyang*
> > >>>
> > >>>
> > >>> On Tue, Dec 19, 2023 at 17:36 Xuanwo  wrote:
> > >>>
> > >>> > Hi, all opendal community members
> > >>> >
> > >>> > I'm thinking about hosting discourse as an alternative way for mailing
> > >>> > list.
> > >>> >
> > >>> > Discourse has a feature called mailing list mode. After enabling this
> > >>> > feature, we will sync every post between our mailling list and 
> > >>> > discourse.
> > >>> >
> > >>> > - Users can create/reply to posts created in discourse via email.
> > >>> > - Users can create/reply to posts send by email in discourse.
> > >>> > - Users can search all posts in discourse.
> > >>> >
> > >>> > By adding this new alternative, I can see the following benefits:
> > >>> >
> > >>> > - All discussion still happen and archived on mailing list (here).
> > >>> > - Users like mailing list can still uses mailing list without any 
> > >>> > change.
> > >>> > - Users like forums can use discourse instead.
> > >>> > - Users don't need to subscribe the email list first before asking
> > >>> > questions.
> > >>> > - Markdown support, Full-text search support, better UI/UX...
> > >>> >
> > >>> > What do you think? Do you want this alternative?
> > >>> >
> > >>> > Xuanwo
> > >>> >
> > >
> > > --
> > > Xuanwo
> >
> > --
> > Xuanwo

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

Re: [DISCUSS] How about hosting discourse as an alternative way for mailing list?

[tison]

Hi Bowen,

Thanks for your advice! I want to involve INFRA in the first place,
but IIRC user@infra.a.o is private.

Shall we invite INFRA members to this thread, or we start a new thread
on user@infra.a.o?

Best,
tison.

 于2023年12月19日周二 21:28写道：
>
> On Tue, 2023-12-19 at 19:23 +0800, tison wrote:
> > +cc comdev
> >
> > Maybe you will be intested in this new type communication.
>
> I would encourage you to take this up with Infra. I am certain that
> this has come up before, and that Infra has already done some research
> into Discourse, not only in terms of hosting it for projects, but for
> the Foundation as a whole, and have thoughts about the sustainability
> of doing this in individual VMs vs some kind of service provider. I
> don't know what their advice will be, but they are definitely the right
> folks to ask for that advice.
>
>
>
> > Xuanwo  于2023年12月19日周二 19:15写道：
> > >
> > > > Discourse will provide us an incoming email address. All email
> > > > sent to
> > > > this address will become a post in discourse. We need to add this
> > > > address into the dev@o.a.o's subcriber list.
> > >
> > > This is talking about Discourse SaaS which cost about $100 ($50 if
> > > we have non-profit discount).
> > >
> > > If we can request a vm from ASF Infra, we will need:
> > >
> > > - VM with 4C8G
> > > - Postgresql
> > > - A SMTP account to send mails
> > > - A domain like discuss.opendal.apache.org
> > >
> > > On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
> > > > > Does it need any configuration from the mailing list part,
> > > > > i.e.,
> > > > > involve INFRA setup?
> > > >
> > > > Discourse will provide us an incoming email address. All email
> > > > sent to
> > > > this address will become a post in discourse. We need to add this
> > > > address into the dev@o.a.o's subcriber list.
> > > >
> > > > No another setup needed, AFAIK.
> > > >
> > > > We need some test and demo to make sure everything works as
> > > > expected.
> > > > At the time of writing, I don't know how to do that.
> > > >
> > > > On Tue, Dec 19, 2023, at 18:19, tison wrote:
> > > > > > called mailing list mode
> > > > >
> > > > > Does it need any configuration from the mailing list part,
> > > > > i.e.,
> > > > > involve INFRA setup?
> > > > >
> > > > > I don't know how this happen but as long as we have a readable
> > > > > copy on
> > > > > the dev@ mailing list, other integration as view can be OK.
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > > Jun Ouyang  于2023年12月19日周二 18:16写道：
> > > > > >
> > > > > > Hi xuanwo:
> > > > > > That’s great! I strongly agree with this change. But I have a
> > > > > > concern about
> > > > > > markdown support sync to Maillist, It seems will cause more
> > > > > > bad experiences
> > > > > > for Maillist users.
> > > > > >
> > > > > > *GPG public key: 4A6D297E6F74638E4D5F8E99152AC7B5F7608B26*
> > > > > > *Thanks,*
> > > > > > *Jun Ouyang*
> > > > > >
> > > > > >
> > > > > > On Tue, Dec 19, 2023 at 17:36 Xuanwo 
> > > > > > wrote:
> > > > > >
> > > > > > > Hi, all opendal community members
> > > > > > >
> > > > > > > I'm thinking about hosting discourse as an alternative way
> > > > > > > for mailing
> > > > > > > list.
> > > > > > >
> > > > > > > Discourse has a feature called mailing list mode. After
> > > > > > > enabling this
> > > > > > > feature, we will sync every post between our mailling list
> > > > > > > and discourse.
> > > > > > >
> > > > > > > - Users can create/reply to posts created in discourse via
> > > > > > > email.
> > > > > > > - Users can create/reply to posts send by email in
> > > > > > > discourse.
> > > > > > > - Users can search all posts in discourse.
> > > > > > >
> > > > > > > By adding this new alternative, I can see the following
> > > > > > > benefits:
> > > > > > >
> > > > > > > - All discussion still happen and archived on mailing list
> > > > > > > (here).
> > > > > > > - Users like mailing list can still uses mailing list
> > > > > > > without any change.
> > > > > > > - Users like forums can use discourse instead.
> > > > > > > - Users don't need to subscribe the email list first before
> > > > > > > asking
> > > > > > > questions.
> > > > > > > - Markdown support, Full-text search support, better
> > > > > > > UI/UX...
> > > > > > >
> > > > > > > What do you think? Do you want this alternative?
> > > > > > >
> > > > > > > Xuanwo
> > > > > > >
> > > >
> > > > --
> > > > Xuanwo
> > >
> > > --
> > > Xuanwo
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>

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

Update Website Template (WAS: Help to get the Wayang project website in shape)

[tison]

Hi,

I finally find some time to prepare a demo for the new website template [1].

It may still open to be improved including a download page template
and a community page template, as well as some guides as its docs. But
I'd like to first collecting feedback and finding which PMC is
responsible for this repository [2].

The background is that our current template is quite old and not
updated for the past six years. Few people understand those techniques
and have a hard time to build their own site. Also, new policy
compliance and new techniques benefits can be included in the template
to help new projects (podlings) build a wonderful site.

I'm glad to maintain this repo but I find myself has no permission
over this repo. So again, which PMC is responsible for this
repository?

Best,
tison.

[1] https://github.com/tisonkun/apache-website-template/tree/docusaurus
[2] https://github.com/apache/apache-website-template/

Alex Porcelli  于2024年1月30日周二 04:53写道：
>
> Another shout-out for tison and the Apache Fury to provide such a nice
> starting point for new websites.
>
> I managed to put, for now, a simple placeholder website for Apache KIE
> (incubation).
>
> Thank you tison and the Apache Fury community!
>
> On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
> >
> > > I managed to move our old website to Docusaurus in one day - using the 
> > > template
> > > structure from Fury, if you don’t mind.
> >
> > Congrats!
> >
> > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
> > > Hey tison,
> > >
> > > Thank you for the head-up. I managed to move our old website to
> > > Docusaurus in one day - using the template structure from Fury, if you
> > > don’t mind. Awesome stuff, would love when we’d had a template for the
> > > podlings to setup a good looking, SEO friendly project page. That’s
> > > needed to grow the community!
> > >
> > > Cheers, thanks again,
> > >  —Alex
> > >
> > >> On Jan 25, 2024, at 12:01, tison  wrote:
> > >>
> > >> Hi Alexander,
> > >>
> > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be
> > >> straightforward to follow already. The most simple one now is
> > >> https://github.com/apache/incubator-fury-site.
> > >>
> > >> Also, Docu is well-documented https://docusaurus.io/docs.
> > >>
> > >> I'm thinking of updating the website template [1] with Docu but have
> > >> not yet had time and understand which PMC manages this project.
> > >>
> > >> Best,
> > >> tison.
> > >>
> > >> [1] https://github.com/apache/apache-website-template
> > >>
> > >> Alexander Alten-Lorenz  于2024年1月25日周四 18:20写道：
> > >>>
> > >>> Hi Xuanwo,
> > >>>
> > >>> Thank you, highly appreciated! Do you have any how-to for setting 
> > >>> Docusaurus up?
> > >>>
> > >>> —Alex
> > >>>
> > >>>> On Jan 25, 2024, at 11:01, Xuanwo  wrote:
> > >>>>
> > >>>> Hi, alexander
> > >>>>
> > >>>>> We aren't web designers and we would love to find helping hands to get
> > >>>>> the page in order, including re-organizing and rewriting.
> > >>>>
> > >>>> I'm with the OpenDAL Community, and we also lack web designers. Our 
> > >>>> community
> > >>>> opted for Docusaurus[1], which we found easy to start with and set up. 
> > >>>> It
> > >>>> offers a decent theme suitable for open-source projects. For 
> > >>>> reference, you
> > >>>> can check out OpenDAL's homepage[2]. We hope our experience proves 
> > >>>> useful.
> > >>>>
> > >>>> [1] https://docusaurus.io/
> > >>>> [2] https://opendal.apache.org/
> > >>>>
> > >>>> On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote:
> > >>>>> Hi incubator community,
> > >>>>>
> > >>>>> Would anyone be willing to help the Wayang project with our website?
> > >>>>> We aren't web designers and we would love to find helping hands to get
> > >>>>> the page in order, including re-organizing and rewriting.
> > >>>>>
> > >>>>> thank you, cheers,
> > >>>>> --alexander
> > >>>>
> > >>>> --
> > >>>> Xuanwo
> > --
> > Xuanwo

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

Re: [WG: Website] Proposal - Website working group

[tison]

+1 Please count me in this WG. Below is my thoughts:

> I would hope that a WG would have regular checkins (could be email, Slack, 
> Google Meet

For an async group, we can use ASF Slack with a new channel.
#zookeeper-release is in this flavor and it works well. For any
actionable items we can discuss on GitHub Issues, JIRA tickets, or
GitHub PRs correspondingly.

For a sync meeting, I may prefer an on-demand meeting to a "regular
meeting" due to my proactive nature...And I'm in the +08:00 timezone
so in my previous experience, the regular schedule is often unfriendly
to me.

For certain site updates and maintenance, I share the feeling that we
have scattered knowledge as I state in this blog draft [1]. Besides,
I'm tracking two concrete improvements related to foundation level
website topics:

* Update Website Template [2]
* Update project maturity model to include trademark and branding [3]

I wonder if these tasks are under the WG objects - we can start the WG
effectively now to see if it's valuable to establish a formal
structure.

Best,
tison.

[1] 
https://github.com/tisonspieces/www-site/pull/8/files#diff-e57a0db6bf085338381727205cda6daef8f930a4b5059b58093cadd2889d6ae5R316-R324
[2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx
[3] https://lists.apache.org/thread/oc9jft1tyo7cbphcyrtwobf4w5rcbhfw

Trista Pan  于2024年2月8日周四 17:06写道：
>
> > Ensure that we don’t duplicate, contradict, or confuse.
>
>
> Agreed, I’d like to be part of it if. Please let me know if there are 
> anything I can give a hand. Thanks.
>
>
>
> --
> Trista Pan
> Twitter & Github: tristaZero
>
>
>
>
> On 02/8/2024 00:11，Rich Bowen wrote：
> Proposed: Form a formal Website working group.
>
> (I am aware that I haven’t defined “working group” yet, and I do, in fact, 
> intend to propose a Working Groups Working Group which could possibly 
> formalize what a working group looks like. I have some ideas, but no desire 
> to go define it on my own.)
>
> The Website WG would, obviously, be responsible for the maintenance of the 
> website. I am aware that some folks think I’m just off doing that on my own, 
> and that’s part of what I’m trying to avoid (see 
> https://lists.apache.org/thread/nwvr28gq51c8v0wkqjv8xvvc2xqrtf03 for further 
> commentary). I would like to gather a group of people who 1) care about it 
> and 2) are willing to do some of (NOT ALL) the work.
>
> Specific things that I believe we should tackle include
>
> * Long-term maintenance of the site. This involves regular audits, 
> implementing metrics, and perhaps other things
> * Reorg - this is a short-term task that I’ve been just doing on my own, 
> which ensures it will never get done, and if it did, there may be some 
> disagreement about how I did it.
> * Deduplication - work closely with MarkPub to figure out the *right* place 
> for certain information; work through the policy/best-practice dichotomy and 
> ensure that we are *not* duplicating policy docs; Work on content on www.a.o 
> <http://www.a.o/> that is closely related to content on community.a.o - which 
> one is authoritative? Ensure that we don’t duplicate, contradict, or confuse.
>
> There’s probably more.
>
> I would hope that a WG would have regular checkins (could be email, Slack, 
> Google Meet, I really don’t care, as long as everyone is engaging with the 
> conversation.)
>
> If you are interested in helping form this group, please speak up in this 
> thread, and help us help one another.
>
> —
> Rich Bowen
> rbo...@rcbowen.com
>
>
>
>

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

Re: [WG: WG] Proposal: Working groups working group

[tison]

>> I just want to make these things more discoverable
> please feel free to jump in and make an infra ticket to move/mirror that to 
> GitHub

If discoverable is an object, I suggest we use GitHub, at least as a
mirror and accept issues and discussions. It's also easier to share
over social media.

I created the ticket that you can check [1].

Best,
tison.

[1] https://issues.apache.org/jira/browse/INFRA-25482

Rich Bowen  于2024年2月8日周四 22:32写道：
>
>
> > On Feb 7, 2024, at 11:22 AM, Rich Bowen  wrote:
> >
> > * Where to we want to track WG status? I would propose that we create 
> > GitHub.com/apache/community <http://github.com/apache/community> for stuff 
> > like this, to mirror GitHub.com/kubernetes/community 
> > <http://github.com/kubernetes/community>, at least in spirit, but would 
> > like to discuss this with more people
>
> I’ve started putting stuff in 
> https://svn.apache.org/repos/asf/comdev/community
>
> I like svn. If you don’t, please feel free to jump in and make an infra 
> ticket to move/mirror that to GitHub.
>
> —Rich
>

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

Re: [WG: WG] Proposal: Working groups working group

[tison]

> Responsibilities

I like the idea of reporting somehow regularly. I found Rust team
works well in this area (meetings [1], updates [2]).

A more complicated example is Rust's Async WG [3]. Mainly, the goal of
a WG, status quo and what it wants to resolve/improve, then keep the
progress updated. I hope that WGs live finitely and for some
continuous improving domains, we create WGs for concrete milestones.

> Membership

We welcome all the participants. But to cooperate with the ASF/comdev,
I try to propose requiring a sponsor from the comdev PMC, and one or
more comdev committers involved.

More concretely, said a WG proposal with an initial members group,
with one or more committers as mentors, and approved by the comdev
PMC. This should be similar to the Incubator process.

Best,
tison.

[1] 
https://github.com/rust-lang/leadership-council/tree/main/minutes/sync-meeting
[2] 
https://github.com/rust-lang/compiler-team/blob/master/content/working-groups/nll/NOTES.md
[3] https://rust-lang.github.io/wg-async/

tison  于2024年2月8日周四 22:49写道：
>
> >> I just want to make these things more discoverable
> > please feel free to jump in and make an infra ticket to move/mirror that to 
> > GitHub
>
> If discoverable is an object, I suggest we use GitHub, at least as a
> mirror and accept issues and discussions. It's also easier to share
> over social media.
>
> I created the ticket that you can check [1].
>
> Best,
> tison.
>
> [1] https://issues.apache.org/jira/browse/INFRA-25482
>
> Rich Bowen  于2024年2月8日周四 22:32写道：
> >
> >
> > > On Feb 7, 2024, at 11:22 AM, Rich Bowen  wrote:
> > >
> > > * Where to we want to track WG status? I would propose that we create 
> > > GitHub.com/apache/community <http://github.com/apache/community> for 
> > > stuff like this, to mirror GitHub.com/kubernetes/community 
> > > <http://github.com/kubernetes/community>, at least in spirit, but would 
> > > like to discuss this with more people
> >
> > I’ve started putting stuff in 
> > https://svn.apache.org/repos/asf/comdev/community
> >
> > I like svn. If you don’t, please feel free to jump in and make an infra 
> > ticket to move/mirror that to GitHub.
> >
> > —Rich
> >

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

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[tison]

It seems that the repo is foundation-wise that I have the permission to
move forward this effort.

I'll push the branch and update the README. And then ask for INFRA to make
it the default branch, as well as setting the repo as a repo template.

I believe comdev and the Incubator are related to these actions so I post
here for visibility, and welcome any feedback if you second this or have
suggestions.

Best,
tison.


tison 于2024年2月4日 周日23:16写道：

> Hi,
>
> I finally find some time to prepare a demo for the new website template
> [1].
>
> It may still open to be improved including a download page template
> and a community page template, as well as some guides as its docs. But
> I'd like to first collecting feedback and finding which PMC is
> responsible for this repository [2].
>
> The background is that our current template is quite old and not
> updated for the past six years. Few people understand those techniques
> and have a hard time to build their own site. Also, new policy
> compliance and new techniques benefits can be included in the template
> to help new projects (podlings) build a wonderful site.
>
> I'm glad to maintain this repo but I find myself has no permission
> over this repo. So again, which PMC is responsible for this
> repository?
>
> Best,
> tison.
>
> [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus
> [2] https://github.com/apache/apache-website-template/
>
> Alex Porcelli  于2024年1月30日周二 04:53写道：
> >
> > Another shout-out for tison and the Apache Fury to provide such a nice
> > starting point for new websites.
> >
> > I managed to put, for now, a simple placeholder website for Apache KIE
> > (incubation).
> >
> > Thank you tison and the Apache Fury community!
> >
> > On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
> > >
> > > > I managed to move our old website to Docusaurus in one day - using
> the template
> > > > structure from Fury, if you don’t mind.
> > >
> > > Congrats!
> > >
> > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
> > > > Hey tison,
> > > >
> > > > Thank you for the head-up. I managed to move our old website to
> > > > Docusaurus in one day - using the template structure from Fury, if
> you
> > > > don’t mind. Awesome stuff, would love when we’d had a template for
> the
> > > > podlings to setup a good looking, SEO friendly project page. That’s
> > > > needed to grow the community!
> > > >
> > > > Cheers, thanks again,
> > > >  —Alex
> > > >
> > > >> On Jan 25, 2024, at 12:01, tison  wrote:
> > > >>
> > > >> Hi Alexander,
> > > >>
> > > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be
> > > >> straightforward to follow already. The most simple one now is
> > > >> https://github.com/apache/incubator-fury-site.
> > > >>
> > > >> Also, Docu is well-documented https://docusaurus.io/docs.
> > > >>
> > > >> I'm thinking of updating the website template [1] with Docu but have
> > > >> not yet had time and understand which PMC manages this project.
> > > >>
> > > >> Best,
> > > >> tison.
> > > >>
> > > >> [1] https://github.com/apache/apache-website-template
> > > >>
> > > >> Alexander Alten-Lorenz  于2024年1月25日周四
> 18:20写道：
> > > >>>
> > > >>> Hi Xuanwo,
> > > >>>
> > > >>> Thank you, highly appreciated! Do you have any how-to for setting
> Docusaurus up?
> > > >>>
> > > >>> —Alex
> > > >>>
> > > >>>> On Jan 25, 2024, at 11:01, Xuanwo  wrote:
> > > >>>>
> > > >>>> Hi, alexander
> > > >>>>
> > > >>>>> We aren't web designers and we would love to find helping hands
> to get
> > > >>>>> the page in order, including re-organizing and rewriting.
> > > >>>>
> > > >>>> I'm with the OpenDAL Community, and we also lack web designers.
> Our community
> > > >>>> opted for Docusaurus[1], which we found easy to start with and
> set up. It
> > > >>>> offers a decent theme suitable for open-source projects. For
> reference, you
> > > >>>> can check out OpenDAL's homepage[2]. We hope our experience
> proves useful.
> > > >>>>
> > > >>>> [1] https://docusaurus.io/
> > > >>>> [2] https://opendal.apache.org/
> > > >>>>
> > > >>>> On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote:
> > > >>>>> Hi incubator community,
> > > >>>>>
> > > >>>>> Would anyone be willing to help the Wayang project with our
> website?
> > > >>>>> We aren't web designers and we would love to find helping hands
> to get
> > > >>>>> the page in order, including re-organizing and rewriting.
> > > >>>>>
> > > >>>>> thank you, cheers,
> > > >>>>> --alexander
> > > >>>>
> > > >>>> --
> > > >>>> Xuanwo
> > > --
> > > Xuanwo
>

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[tison]

I've pushed the code to 'docusarus' branch on this repo, and file a
ticket on INFRA [1] to ask for some privileges actions.

Best,
tison.

[1] https://issues.apache.org/jira/browse/INFRA-25486

tison  于2024年2月10日周六 18:32写道：
>
> It seems that the repo is foundation-wise that I have the permission to move 
> forward this effort.
>
> I'll push the branch and update the README. And then ask for INFRA to make it 
> the default branch, as well as setting the repo as a repo template.
>
> I believe comdev and the Incubator are related to these actions so I post 
> here for visibility, and welcome any feedback if you second this or have 
> suggestions.
>
> Best,
> tison.
>
>
> tison 于2024年2月4日 周日23:16写道：
>>
>> Hi,
>>
>> I finally find some time to prepare a demo for the new website template [1].
>>
>> It may still open to be improved including a download page template
>> and a community page template, as well as some guides as its docs. But
>> I'd like to first collecting feedback and finding which PMC is
>> responsible for this repository [2].
>>
>> The background is that our current template is quite old and not
>> updated for the past six years. Few people understand those techniques
>> and have a hard time to build their own site. Also, new policy
>> compliance and new techniques benefits can be included in the template
>> to help new projects (podlings) build a wonderful site.
>>
>> I'm glad to maintain this repo but I find myself has no permission
>> over this repo. So again, which PMC is responsible for this
>> repository?
>>
>> Best,
>> tison.
>>
>> [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus
>> [2] https://github.com/apache/apache-website-template/
>>
>> Alex Porcelli  于2024年1月30日周二 04:53写道：
>> >
>> > Another shout-out for tison and the Apache Fury to provide such a nice
>> > starting point for new websites.
>> >
>> > I managed to put, for now, a simple placeholder website for Apache KIE
>> > (incubation).
>> >
>> > Thank you tison and the Apache Fury community!
>> >
>> > On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
>> > >
>> > > > I managed to move our old website to Docusaurus in one day - using the 
>> > > > template
>> > > > structure from Fury, if you don’t mind.
>> > >
>> > > Congrats!
>> > >
>> > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
>> > > > Hey tison,
>> > > >
>> > > > Thank you for the head-up. I managed to move our old website to
>> > > > Docusaurus in one day - using the template structure from Fury, if you
>> > > > don’t mind. Awesome stuff, would love when we’d had a template for the
>> > > > podlings to setup a good looking, SEO friendly project page. That’s
>> > > > needed to grow the community!
>> > > >
>> > > > Cheers, thanks again,
>> > > >  —Alex
>> > > >
>> > > >> On Jan 25, 2024, at 12:01, tison  wrote:
>> > > >>
>> > > >> Hi Alexander,
>> > > >>
>> > > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be
>> > > >> straightforward to follow already. The most simple one now is
>> > > >> https://github.com/apache/incubator-fury-site.
>> > > >>
>> > > >> Also, Docu is well-documented https://docusaurus.io/docs.
>> > > >>
>> > > >> I'm thinking of updating the website template [1] with Docu but have
>> > > >> not yet had time and understand which PMC manages this project.
>> > > >>
>> > > >> Best,
>> > > >> tison.
>> > > >>
>> > > >> [1] https://github.com/apache/apache-website-template
>> > > >>
>> > > >> Alexander Alten-Lorenz  于2024年1月25日周四 
>> > > >> 18:20写道：
>> > > >>>
>> > > >>> Hi Xuanwo,
>> > > >>>
>> > > >>> Thank you, highly appreciated! Do you have any how-to for setting 
>> > > >>> Docusaurus up?
>> > > >>>
>> > > >>> —Alex
>> > > >>>
>> > > >>>> On Jan 25, 2024, at 11:01, Xuanwo  wrote:
>> > > >>>>
>> > > >>>> Hi, alexa

[REQUEST] Create apache/community GitHub Repo (WAS: Working groups working group)

[tison]

According to the INFRA ticket [1], we'd better create the
apache/community GitHub repo first.

I'm glad to execute the self-serve command but I'm yet to be a COMDEV
PMC member. I remember that in another thread, it's said that an
Apache Member can self-request to be a PMC member, so:

* If any COMDEV PMC member can create the GitHub repo on self-serve
platform [2];
* If it's possible, I'd like to self-request to be a PMC member and do
the set up by myself.

What do you think?

[1] https://issues.apache.org/jira/browse/INFRA-25482
[2] https://gitbox.apache.org/boxer/?action=newrepo

Best,
tison.

tison  于2024年2月8日周四 22:49写道：
>
> >> I just want to make these things more discoverable
> > please feel free to jump in and make an infra ticket to move/mirror that to 
> > GitHub
>
> If discoverable is an object, I suggest we use GitHub, at least as a
> mirror and accept issues and discussions. It's also easier to share
> over social media.
>
> I created the ticket that you can check [1].
>
> Best,
> tison.
>
> [1] https://issues.apache.org/jira/browse/INFRA-25482
>
> Rich Bowen  于2024年2月8日周四 22:32写道：
> >
> >
> > > On Feb 7, 2024, at 11:22 AM, Rich Bowen  wrote:
> > >
> > > * Where to we want to track WG status? I would propose that we create 
> > > GitHub.com/apache/community <http://github.com/apache/community> for 
> > > stuff like this, to mirror GitHub.com/kubernetes/community 
> > > <http://github.com/kubernetes/community>, at least in spirit, but would 
> > > like to discuss this with more people
> >
> > I’ve started putting stuff in 
> > https://svn.apache.org/repos/asf/comdev/community
> >
> > I like svn. If you don’t, please feel free to jump in and make an infra 
> > ticket to move/mirror that to GitHub.
> >
> > —Rich
> >

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

Re: [REQUEST] Create apache/community GitHub Repo (WAS: Working groups working group)

[tison]

> Why not migrate the SVN repo to Git?
> Is there any need to keep the info in SVN?

I'm +1 in this direction. But it doesn't bother me if we keep a gate
to allow commiting via SVN and sync to GitHub. If Rich likes this way
and now he is the most active volunteer on this initiative.

Best,
tison.

sebb  于2024年2月12日周一 23:25写道：
>
> Why not migrate the SVN repo to Git?
> Is there any need to keep the info in SVN?
>
> On Mon, 12 Feb 2024 at 15:14, tison  wrote:
> >
> > According to the INFRA ticket [1], we'd better create the
> > apache/community GitHub repo first.
> >
> > I'm glad to execute the self-serve command but I'm yet to be a COMDEV
> > PMC member. I remember that in another thread, it's said that an
> > Apache Member can self-request to be a PMC member, so:
> >
> > * If any COMDEV PMC member can create the GitHub repo on self-serve
> > platform [2];
> > * If it's possible, I'd like to self-request to be a PMC member and do
> > the set up by myself.
> >
> > What do you think?
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-25482
> > [2] https://gitbox.apache.org/boxer/?action=newrepo
> >
> > Best,
> > tison.
> >
> > tison  于2024年2月8日周四 22:49写道：
> > >
> > > >> I just want to make these things more discoverable
> > > > please feel free to jump in and make an infra ticket to move/mirror 
> > > > that to GitHub
> > >
> > > If discoverable is an object, I suggest we use GitHub, at least as a
> > > mirror and accept issues and discussions. It's also easier to share
> > > over social media.
> > >
> > > I created the ticket that you can check [1].
> > >
> > > Best,
> > > tison.
> > >
> > > [1] https://issues.apache.org/jira/browse/INFRA-25482
> > >
> > > Rich Bowen  于2024年2月8日周四 22:32写道：
> > > >
> > > >
> > > > > On Feb 7, 2024, at 11:22 AM, Rich Bowen  wrote:
> > > > >
> > > > > * Where to we want to track WG status? I would propose that we create 
> > > > > GitHub.com/apache/community <http://github.com/apache/community> for 
> > > > > stuff like this, to mirror GitHub.com/kubernetes/community 
> > > > > <http://github.com/kubernetes/community>, at least in spirit, but 
> > > > > would like to discuss this with more people
> > > >
> > > > I’ve started putting stuff in 
> > > > https://svn.apache.org/repos/asf/comdev/community
> > > >
> > > > I like svn. If you don’t, please feel free to jump in and make an infra 
> > > > ticket to move/mirror that to GitHub.
> > > >
> > > > —Rich
> > > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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

Re: [WG: Sharpeners] Proposed - Sharpeners

[tison]

Thank you for starting this discussion, Rich.

I'm trying to get the points of this WG:

1. This WG is NOT a new office to "shepherd" TLPs, but to write down
how any community member can help in sharpening an ASF project.
2. For applying any suggestions, the request is delegated to the
Board, Trademarks, or other offices in the case; a member of this WG
can be an accountable assistant.

So, the main work items of this WG are shaping how any community
member can "supervise" an ASF project and how to collaborate with
offices to get TLPs to work well. Also, "ensure" that such guidances
are put into work.

If so, I'd recall my previous comment as an Incubator mentor that:

>> As a podling mentor, I know that many podlings join the ASF by influences 
>> from other TLPs. So if the TLP violates our policies, it increases the 
>> friction when we help the podlings to comply with our policies.

I already worked with trademarks@ to spot and fix issues on a few
TLPs' content. I'm glad to join this WG to share my experience
contributing to well-formed guidance.

Best,
tison.

Rich Bowen  于2024年2月12日周一 23:20写道：
>
>
> —

> Rich Bowen
> rbo...@rcbowen.com
>
>
>
>
> > On Feb 11, 2024, at 6:04 PM, Phil Steitz  wrote:
> >
> > I am working on a PR to take a stab at tweaking the wording.  I am also
> > playing with some ideas around use cases - kinds of things sharpeners will
> > work on.  I think it's really a good idea to get some rough consensus on
> > what is in/out of scope before we start this.
>
> Indeed. Both what’s in and out of scope, and specific examples would be 
> really helpful. I am sure that I have a lot of preconceived notions of how 
> *I* would do this kind of work, but one of the major goals of working groups 
> is to document this so that people without those assumptions can get involved 
> without too much ramp-up time.
>
> Looking forward to your thoughts on this.
>

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

Self-request as a PMC member for COMDEV

[tison]

Hi,

Repost this thread and cc Swapnil for more visibility.

I'm reviewing and patching related repos now and noticed that this
request is pending. Since active committers are reviewing patches,
this is not in a rush. But I'm afraid that this email gets
overwhelmed.

Rich Bowen  wrote:
> Meanwhile, as per ComDev policy, your request to be a ComDev PMC member is 
> approved. Swapnil, can you pull the lever, please.

My profile for reference https://whimsy.apache.org/roster/committer/tison.

Best,
tison.

Rich Bowen  于2024年2月12日周一 23:23写道：
>
> On Feb 12, 2024, at 10:13 AM, tison  wrote:
> >
> > According to the INFRA ticket [1], we'd better create the
> > apache/community GitHub repo first.
> >
> > I'm glad to execute the self-serve command but I'm yet to be a COMDEV
> > PMC member. I remember that in another thread, it's said that an
> > Apache Member can self-request to be a PMC member, so:
> >
> > * If any COMDEV PMC member can create the GitHub repo on self-serve
> > platform [2];
> > * If it's possible, I'd like to self-request to be a PMC member and do
> > the set up by myself.
>
>
> Done.
>
> Meanwhile, as per ComDev policy, your request to be a ComDev PMC member is 
> approved. Swapnil, can you pull the lever, please.
>
> Thanks.

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

Re: Self-request as a PMC member for COMDEV

[tison]

Thank you, Swapnil. Confirmed all set up.

Best,
tison.

Swapnil M Mane  于2024年2月15日周四 16:07写道：
>
> Thank you Tison, I will take care of this.
>
> Best Regards,
> Swapnil M Mane
>
>
>
>
>
> On Thu, Feb 15, 2024 at 7:15 AM tison  wrote:
> >
> > Hi,
> >
> > Repost this thread and cc Swapnil for more visibility.
> >
> > I'm reviewing and patching related repos now and noticed that this
> > request is pending. Since active committers are reviewing patches,
> > this is not in a rush. But I'm afraid that this email gets
> > overwhelmed.
> >
> > Rich Bowen  wrote:
> > > Meanwhile, as per ComDev policy, your request to be a ComDev PMC member 
> > > is approved. Swapnil, can you pull the lever, please.
> >
> > My profile for reference https://whimsy.apache.org/roster/committer/tison.
> >
> > Best,
> > tison.
> >
> > Rich Bowen  于2024年2月12日周一 23:23写道：
> > >
> > > On Feb 12, 2024, at 10:13 AM, tison  wrote:
> > > >
> > > > According to the INFRA ticket [1], we'd better create the
> > > > apache/community GitHub repo first.
> > > >
> > > > I'm glad to execute the self-serve command but I'm yet to be a COMDEV
> > > > PMC member. I remember that in another thread, it's said that an
> > > > Apache Member can self-request to be a PMC member, so:
> > > >
> > > > * If any COMDEV PMC member can create the GitHub repo on self-serve
> > > > platform [2];
> > > > * If it's possible, I'd like to self-request to be a PMC member and do
> > > > the set up by myself.
> > >
> > >
> > > Done.
> > >
> > > Meanwhile, as per ComDev policy, your request to be a ComDev PMC member 
> > > is approved. Swapnil, can you pull the lever, please.
> > >
> > > Thanks.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >

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

[DISCUSS] Create a new repo for website template

[tison]

## Background ##

More background can be found in [1][2]. The current website template [3]
has not been updated for six years and uses outdated tech that can hardly
be used for new podlings.

I developed a new template[4], and it's been used for a few podlings
already. All of them are glad to see this improvement.

## Proposal ##

Create a new repo under COMDEV PMC to host the new website template. Such a
template is mainly for new podlings setup but is also suitable for any TLPs.

The name is to be determined. Following the self-serve rules, we can only
create repo with comdev- prefix, so perhaps comdev-website-template.

Or from why I create an INFRA ticket, apache/website-template-docusaurus,
with INFRA's help.

## Reject Alternative ##

1. Create a new branch under apache/apache-website-template.
It's discussed in [5][6] and doesn't seem a good direction.

2. Create a new repo under Incubator PMC.
I'm hesitant about this, actually. But Andrew Wetmore wrote:

> This is not the purview of the Incubator, and it's not the purview of
Infra.

It's kind of reasonable, so I reached out here first.

Best,
tison.

[1] https://issues.apache.org/jira/browse/INFRA-25494
[2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx
[3] https://github.com/apache/apache-website-template/
[4] github.com/tisonkun/apache-website-template/tree/docusaurus
[5] https://issues.apache.org/jira/browse/INFRA-25486
[6] https://github.com/apache/apache-website-template/pull/17

Re: [DISCUSS] Create a new repo for website template

[tison]

Hi Daniel,

This is my original proposal. See "Reject Alternative" for more details.

Sebb stated "Could perhaps be compared to changing from Java to Kotlin."

Or at least we let COMDEV PMC "own" apache/apache-website-template?

My major object is to publish the docu template under ASF namespace, and
not as a secondary source behind an unmaintained one, which is unreasonable.

Best,
tison.


Daniel Gruno  于2024年2月20日周二 17:45写道：

> On 2/20/24 10:34, tison wrote:
> > ## Background ##
> >
> > More background can be found in [1][2]. The current website template [3]
> > has not been updated for six years and uses outdated tech that can hardly
> > be used for new podlings.
> >
> > I developed a new template[4], and it's been used for a few podlings
> > already. All of them are glad to see this improvement.
> >
> > ## Proposal ##
> >
> > Create a new repo under COMDEV PMC to host the new website template.
> Such a
> > template is mainly for new podlings setup but is also suitable for any
> TLPs.
> >
> > The name is to be determined. Following the self-serve rules, we can only
> > create repo with comdev- prefix, so perhaps comdev-website-template.
> >
> > Or from why I create an INFRA ticket, apache/website-template-docusaurus,
> > with INFRA's help.
> >
> > ## Reject Alternative ##
> >
> > 1. Create a new branch under apache/apache-website-template.
> > It's discussed in [5][6] and doesn't seem a good direction.
> >
> > 2. Create a new repo under Incubator PMC.
> > I'm hesitant about this, actually. But Andrew Wetmore wrote:
> >
> >> This is not the purview of the Incubator, and it's not the purview of
> > Infra.
> >
> > It's kind of reasonable, so I reached out here first.
> >
> > Best,
> > tison.
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-25494
> > [2] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx
> > [3] https://github.com/apache/apache-website-template/
> > [4] github.com/tisonkun/apache-website-template/tree/docusaurus
> > [5] https://issues.apache.org/jira/browse/INFRA-25486
> > [6] https://github.com/apache/apache-website-template/pull/17
> >
>
> This feels like we are over-engineering the solution to a simple
> problem. Just use the existing website-template repository, have the
> default branch be an empty branch with a README that tells you what the
> different examples are, each in their own branch or directory.
>
> The repository is meant to show examples, it's not being used in
> production or dynamically pulled in on other website builds, so breaking
> existing structures is perfectly reasonable.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [DISCUSS] Create a new repo for website template

[tison]

> And/or just point to the source code of existing ASF websites which
> can serve as living examples.

You can check the original mailing list thread [1]. I recommend Fury as an
example there because it's just started. Living examples can be supplements
but customized a lot to prevent new podlings from catching up.

This is my initial motivation to create a template and even self-contained
docs to share how to switch features while being compliant with ASF
policies :D

Best,
tison.

[1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx


Bertrand Delacretaz  于2024年2月20日周二 19:32写道：

> On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno 
> wrote:
> > ...Just use the existing website-template repository, have the
> > default branch be an empty branch with a README that tells you what the
> > different examples are, each in their own branch or directory...
>
> And/or just point to the source code of existing ASF websites which
> can serve as living examples.
>
> And encourage people to add GitHub topics to their website
> repositories, so that queries like
>
> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
>
> can give you a list of real live examples that use your favorite
> website generation tool, "hugo" in this example.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [DISCUSS] Create a new repo for website template

[tison]

> I don't want us to make people believe that there
> is a preferred option for building websites.

My two cents:

1. I'm very glad to list any wonderful sites as examples.
2. Take the existing template as an example; it mainly helps those
projects/podlings who get lost in bootstrapping their website. If a
project knows how to build a website, they don't go here. We can
anyway add a note that the template is not _preferred_ but for getting
started if you don't know how to start :D

> The existing https://infra.apache.org/project-site.html page lists a
> number of options, pointing to it could be useful, or we might suggest
> simplifying that page to expose only what ASF infra manages, and move
> the "website building options" to the comdev website.

Hey! Thank you. Then I'm leaning to the solution reuse the
apache-website-template repo, change the default branch a README only
content to listing this. And it just happens to have some branches
(jekyell, docusaurus) that have some content to get start with.

Best,
tison.

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

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[tison]

Hi Dave,

Thanks for picking up this commit. You may join the discussion at [1].

I have all the permission to follow what I want. But since
apache-website-template is technically a foundation-wise repo and I'm
a newcomer here, I'd like to listen to people's opinions before moving
forward; especially there can be some arguments.

Best,
tison.

[1] https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8

Dave Fisher  于2024年2月21日周三 02:35写道：
>
> From the commit email it looks like this repository belongs to the Incubator.
>
> > On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > tison pushed a change to branch jekyll
> > in repository 
> > https://gitbox.apache.org/repos/asf/apache-website-template.git
> >
> >
> >  at f2f8a9e  Update download page template
> >
> > No new revisions were added by this update.
> >
> >
> > -
> > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: cvs-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[tison]

Hi Dave,

> One approach is to find good examples of each build technique. If you look 
> back at older projects you will see various historical waves of technique.

I agree, and that's why I'd prefer a multi branches solution with a
default branch containing README for redirects.

>From another perspective, it's still valuable to provide a template
for new podlings to get started _now_, and if someone (in this case,
it's me) volunteers to provide one for help, there is no reason we
reject it by the tech will fade _years later_.

Best,
tison.

Dave Fisher  于2024年2月21日周三 08:17写道：
>
> Hi Tison,
>
> I’m following along. Infrastructure has a Pelican template site that is out 
> of date: https://github.com/apache/template-site/
>
> One approach is to find good examples of each build technique. If you look 
> back at older projects you will see various historical waves of technique.
>
> Best,
> Dave
>
> > On Feb 20, 2024, at 3:48 PM, tison  wrote:
> >
> > Hi Dave,
> >
> > Thanks for picking up this commit. You may join the discussion at [1].
> >
> > I have all the permission to follow what I want. But since
> > apache-website-template is technically a foundation-wise repo and I'm
> > a newcomer here, I'd like to listen to people's opinions before moving
> > forward; especially there can be some arguments.
> >
> > Best,
> > tison.
> >
> > [1] https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8
> >
> > Dave Fisher  于2024年2月21日周三 02:35写道：
> >>
> >> From the commit email it looks like this repository belongs to the 
> >> Incubator.
> >>
> >>> On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
> >>>
> >>> This is an automated email from the ASF dual-hosted git repository.
> >>>
> >>> tison pushed a change to branch jekyll
> >>> in repository 
> >>> https://gitbox.apache.org/repos/asf/apache-website-template.git
> >>>
> >>>
> >>> at f2f8a9e  Update download page template
> >>>
> >>> No new revisions were added by this update.
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: cvs-h...@incubator.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[tison]

Hi sebb,

Your comments sound like back to the switching default branch solution (a
new branch with history only adding the README becomes the default).

Or you prefer other ways to the same repo direction.

Also is it possible we go back to the COMDEV dedicated thread so that
people can easily follow the context? If we agree, the context here can be
brought there.

Best,
tison.


sebb 于2024年2月21日 周三16:27写道：

> On Wed, 21 Feb 2024 at 00:28, tison  wrote:
> >
> > Hi Dave,
> >
> > > One approach is to find good examples of each build technique. If you
> look back at older projects you will see various historical waves of
> technique.
> >
> > I agree, and that's why I'd prefer a multi branches solution with a
> > default branch containing README for redirects.
>
> However, if a repo is shared in this way, such disjoint branches
> should be initially created as empty orphans.
> Replacing all the files with different ones makes for a confusing history.
>
> > From another perspective, it's still valuable to provide a template
> > for new podlings to get started _now_, and if someone (in this case,
> > it's me) volunteers to provide one for help, there is no reason we
> > reject it by the tech will fade _years later_.
> >
> > Best,
> > tison.
> >
> > Dave Fisher  于2024年2月21日周三 08:17写道：
> > >
> > > Hi Tison,
> > >
> > > I’m following along. Infrastructure has a Pelican template site that
> is out of date: https://github.com/apache/template-site/
> > >
> > > One approach is to find good examples of each build technique. If you
> look back at older projects you will see various historical waves of
> technique.
> > >
> > > Best,
> > > Dave
> > >
> > > > On Feb 20, 2024, at 3:48 PM, tison  wrote:
> > > >
> > > > Hi Dave,
> > > >
> > > > Thanks for picking up this commit. You may join the discussion at
> [1].
> > > >
> > > > I have all the permission to follow what I want. But since
> > > > apache-website-template is technically a foundation-wise repo and I'm
> > > > a newcomer here, I'd like to listen to people's opinions before
> moving
> > > > forward; especially there can be some arguments.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > [1] https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8
> > > >
> > > > Dave Fisher  于2024年2月21日周三 02:35写道：
> > > >>
> > > >> From the commit email it looks like this repository belongs to the
> Incubator.
> > > >>
> > > >>> On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
> > > >>>
> > > >>> This is an automated email from the ASF dual-hosted git repository.
> > > >>>
> > > >>> tison pushed a change to branch jekyll
> > > >>> in repository
> https://gitbox.apache.org/repos/asf/apache-website-template.git
> > > >>>
> > > >>>
> > > >>> at f2f8a9e  Update download page template
> > > >>>
> > > >>> No new revisions were added by this update.
> > > >>>
> > > >>>
> > > >>>
> -
> > > >>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> > > >>> For additional commands, e-mail: cvs-h...@incubator.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> -
> > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > > >>
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Create a new repo for website template

[tison]

Hi Chris,

Thanks you. Now we found a volunteer to improve the jekyll template and
it's good :D

Daniel wrote:
> This feels like we are over-engineering the solution to a simple
> problem. Just use the existing website-template repository, have the
> default branch be an empty branch with a README that tells you what the
> different examples are, each in their own branch or directory.

I'm OK with this. And it seems a solution that no direct reasonable
objection.

Although Sebb comments in the other thread [1] that such a Rip Down commit
can be suboptimal due to the irrelevant history, with INFRA's help we can
use a brand new README branch and make it the default.

I'm going to move forward with the development in docusaurus branch and
recommend Chris to send the patch against the jekyll branch (I'll review it
if you need).

For the master branch tech solution, I'm fine to wait a minutes to rip it
down, switch with a brand new history, or any other suggestions.

Best,
tison.

[1]
https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq


Christian Grobmeier 于2024年2月21日 周三16:07写道：

> Hello,
>
> I love we are picking up this template idea again.
>
> Previously I proposed to add some Docker files to help with quick setup.
> I could add this straightaway to the Jekyll branch.
>
> Does this sound like a good idea?
>
> It could look like what I did for Privacy:
> https://github.com/apache/privacy-website
>
> Please let me know, then I will add it (or forget about it)
>
> Kind regards,
> Christian
>
> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote:
> > From my recent experience, it could save the developer lots of time if
> > they can work on the website's content by adding some markdown files
> > directly.
> > Following the website policy and turning the features of the website
> > engine are one-time work. The ROI would be good if we could share
> > these through the website template.
> >
> > Thanks,
> >
> > Willem Jiang
> >
> > On Tue, Feb 20, 2024 at 8:20 PM tison  wrote:
> >>
> >> > And/or just point to the source code of existing ASF websites which
> >> > can serve as living examples.
> >>
> >> You can check the original mailing list thread [1]. I recommend Fury as
> an
> >> example there because it's just started. Living examples can be
> supplements
> >> but customized a lot to prevent new podlings from catching up.
> >>
> >> This is my initial motivation to create a template and even
> self-contained
> >> docs to share how to switch features while being compliant with ASF
> >> policies :D
> >>
> >> Best,
> >> tison.
> >>
> >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx
> >>
> >>
> >> Bertrand Delacretaz  于2024年2月20日周二 19:32写道：
> >>
> >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno 
> >> > wrote:
> >> > > ...Just use the existing website-template repository, have the
> >> > > default branch be an empty branch with a README that tells you what
> the
> >> > > different examples are, each in their own branch or directory...
> >> >
> >> > And/or just point to the source code of existing ASF websites which
> >> > can serve as living examples.
> >> >
> >> > And encourage people to add GitHub topics to their website
> >> > repositories, so that queries like
> >> >
> >> >
> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
> >> >
> >> > can give you a list of real live examples that use your favorite
> >> > website generation tool, "hugo" in this example.
> >> >
> >> > -Bertrand
> >> >
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > For additional commands, e-mail: dev-h...@community.apache.org
> >> >
> >> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[tison]

It's currently a brand new branch. You can check it in the repo.

Best,
tison.


sebb 于2024年2月22日 周四01:11写道：

> On Wed, 21 Feb 2024 at 09:25, tison  wrote:
> >
> > Hi sebb,
> >
> > Your comments sound like back to the switching default branch solution (a
> > new branch with history only adding the README becomes the default).
>
> I am saying that if the 3 branch solution is adopted the docusaurus
> branch should be created as a new branch.
>
> > Or you prefer other ways to the same repo direction.
> >
> > Also is it possible we go back to the COMDEV dedicated thread so that
> > people can easily follow the context? If we agree, the context here can
> be
> > brought there.
> >
> > Best,
> > tison.
> >
> >
> > sebb 于2024年2月21日 周三16:27写道：
> >
> > > On Wed, 21 Feb 2024 at 00:28, tison  wrote:
> > > >
> > > > Hi Dave,
> > > >
> > > > > One approach is to find good examples of each build technique. If
> you
> > > look back at older projects you will see various historical waves of
> > > technique.
> > > >
> > > > I agree, and that's why I'd prefer a multi branches solution with a
> > > > default branch containing README for redirects.
> > >
> > > However, if a repo is shared in this way, such disjoint branches
> > > should be initially created as empty orphans.
> > > Replacing all the files with different ones makes for a confusing
> history.
> > >
> > > > From another perspective, it's still valuable to provide a template
> > > > for new podlings to get started _now_, and if someone (in this case,
> > > > it's me) volunteers to provide one for help, there is no reason we
> > > > reject it by the tech will fade _years later_.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > Dave Fisher  于2024年2月21日周三 08:17写道：
> > > > >
> > > > > Hi Tison,
> > > > >
> > > > > I’m following along. Infrastructure has a Pelican template site
> that
> > > is out of date: https://github.com/apache/template-site/
> > > > >
> > > > > One approach is to find good examples of each build technique. If
> you
> > > look back at older projects you will see various historical waves of
> > > technique.
> > > > >
> > > > > Best,
> > > > > Dave
> > > > >
> > > > > > On Feb 20, 2024, at 3:48 PM, tison  wrote:
> > > > > >
> > > > > > Hi Dave,
> > > > > >
> > > > > > Thanks for picking up this commit. You may join the discussion at
> > > [1].
> > > > > >
> > > > > > I have all the permission to follow what I want. But since
> > > > > > apache-website-template is technically a foundation-wise repo
> and I'm
> > > > > > a newcomer here, I'd like to listen to people's opinions before
> > > moving
> > > > > > forward; especially there can be some arguments.
> > > > > >
> > > > > > Best,
> > > > > > tison.
> > > > > >
> > > > > > [1]
> https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8
> > > > > >
> > > > > > Dave Fisher  于2024年2月21日周三 02:35写道：
> > > > > >>
> > > > > >> From the commit email it looks like this repository belongs to
> the
> > > Incubator.
> > > > > >>
> > > > > >>> On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
> > > > > >>>
> > > > > >>> This is an automated email from the ASF dual-hosted git
> repository.
> > > > > >>>
> > > > > >>> tison pushed a change to branch jekyll
> > > > > >>> in repository
> > > https://gitbox.apache.org/repos/asf/apache-website-template.git
> > > > > >>>
> > > > > >>>
> > > > > >>> at f2f8a9e  Update download page template
> > > > > >>>
> > > > > >>> No new revisions were added by this update.
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > -
> > >

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[tison]

Hi Shane,

It's under the list. See [1] and the referred thread. I'll try to
submit a patch this week to add this information, including the
pelican info. We'd later move the pelican template to this repo also
in a dedicated branch and make it "just work".

Best,
tison.

[1] https://github.com/apache/apache-website-template/issues/18

Shane Curcuru  于2024年2月26日周一 19:34写道：
>
> tison wrote on 2/4/24 10:16 AM:
> > Hi,
> >
> > I finally find some time to prepare a demo for the new website template [1].
>
> This is awesome; I love providing more default "just use this" templates
> in various themes like this.
>
> One question: why doesn't this also link (At least in the docs for each
> readme maybe?) to the Infra-supported pelican template?  We should at
> least point to that, since infra supports it and it provides a
> python-managed template, in case people like that better than Jekyll/ruby.
>
>https://infra.apache.org/asf-pelican-gettingstarted.html
>
> --
> - Shane
>Member
>The Apache Software Foundation
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[tison]

Yeah ..

The pelican template is a repo template and has its own repo with a
asf-site branch while it may be able to preview ..

I'd like to ask for a repo for the docu template but it ends up with
hosting in another branch in the apache-website-template repo :O

Best,
tison.

Dave Fisher  于2024年2月27日周二 22:42写道：
>
> Hi Shane,
>
> The Pelican ASF Template at https://github.com/apache/template-site is 
> somewhat out of date as many contributors have contributed to ASF Pelican in 
> the last two or three years. It would be good to revisit. I’m not sure I have 
> the time or not, but that would great to update. One area in particular is as 
> simple as adding updates to required privacy policies.
>
> Best,
> Dave
>
> > On Feb 26, 2024, at 7:15 AM, tison  wrote:
> >
> > Hi Shane,
> >
> > It's under the list. See [1] and the referred thread. I'll try to
> > submit a patch this week to add this information, including the
> > pelican info. We'd later move the pelican template to this repo also
> > in a dedicated branch and make it "just work".
> >
> > Best,
> > tison.
> >
> > [1] https://github.com/apache/apache-website-template/issues/18
> >
> > Shane Curcuru  于2024年2月26日周一 19:34写道：
> >>
> >> tison wrote on 2/4/24 10:16 AM:
> >>> Hi,
> >>>
> >>> I finally find some time to prepare a demo for the new website template 
> >>> [1].
> >>
> >> This is awesome; I love providing more default "just use this" templates
> >> in various themes like this.
> >>
> >> One question: why doesn't this also link (At least in the docs for each
> >> readme maybe?) to the Infra-supported pelican template?  We should at
> >> least point to that, since infra supports it and it provides a
> >> python-managed template, in case people like that better than Jekyll/ruby.
> >>
> >>   https://infra.apache.org/asf-pelican-gettingstarted.html
> >>
> >> --
> >> - Shane
> >>   Member
> >>   The Apache Software Foundation
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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

Re: [DISCUSS] Create a new repo for website template

[tison]

PR is ready - https://github.com/apache/apache-website-template/pull/19

I'll invest time to develop the Docu template in the next weeks.

Best,
tison.

Zili Chen  于2024年2月26日周一 11:48写道：
>
> Go into the implementation stage. I plan to submit a patch for updating the 
> master branch this week. Welcome to leave your comment at - 
> https://github.com/apache/apache-website-template/issues/18.
>
> The Docu branch is under development; I'm going to create more wip issues for 
> you to follow.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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

Re: Error while running notifications feature from .asf.yaml in apache-website-template!

[tison]

Seems an INFRA issue ...

How can we move this repo as a COMDEV repo?

Also I notice that a shortcoming of this multiple branches solution is
that GitHub displays contributors only for the default branch. But
it's not quite a big issue anyway ...

Best,
tison.

Apache Infrastructure  于2024年3月8日周五 02:38写道：
>
>
> An error occurred while running notifications feature in .asf.yaml!:
> Invalid notification target 'comm...@community.apache.org'. Must be a valid 
> @apache.apache.org list!
>

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

Re: Error while running notifications feature from .asf.yaml in apache-website-template!

[tison]

Although this mail is from users@infra.a.o, I found it doesn't contain
privacy (or we simply should not copy any content from
users@infra.a.o?).

Also, this email is edit to drop users@infra.a.o as a recipenitent.

Best,
tison.

tison  于2024年3月8日周五 02:42写道：
>
> Seems an INFRA issue ...
>
> How can we move this repo as a COMDEV repo?
>
> Also I notice that a shortcoming of this multiple branches solution is
> that GitHub displays contributors only for the default branch. But
> it's not quite a big issue anyway ...
>
> Best,
> tison.
>
> Apache Infrastructure  于2024年3月8日周五 02:38写道：
> >
> >
> > An error occurred while running notifications feature in .asf.yaml!:
> > Invalid notification target 'comm...@community.apache.org'. Must be a valid 
> > @apache.apache.org list!
> >

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

How to build the community page?

[tison]

Hi,

The README file writes: run `hugo` to get the static content.

I got:

$ hugo
Start building sites …
hugo v0.123.8-5fed9c591b694f314e5939548e11cc3dcb79a79c+extended
darwin/arm64 BuildDate=2024-03-07T13:14:42Z VendorInfo=brew

ERROR render of "section" failed:
"/Users/tison/Brittani/comdev-site/layouts/_default/baseof.html:87:13":
execute of template failed: template: _default/list.html:87:13: executing
"_default/list.html" at : error calling
partial:
"/Users/tison/Brittani/comdev-site/layouts/partials/website-source.html:5:86":
execute of template failed: template: partials/website-source.html:5:86:
executing "partials/website-source.html" at <.Page.File.Path>: error
calling Path: runtime error: invalid memory address or nil pointer
dereference
Total in 77 ms
Error: error building site: render: failed to render pages: render of
"section" failed:
"/Users/tison/Brittani/comdev-site/layouts/_default/baseof.html:87:13":
execute of template failed: template: _default/list.html:87:13: executing
"_default/list.html" – File is nil; wrap it in if or with: {{ with partial
"website-source.html" .>: error calling partial:
"/Users/tison/Brittani/comdev-site/layouts/partials/website-source.html:5:86":
execute of template failed: template: partials/website-source.html:5:86:
executing "partials/website-source.html" at <.Page.File }}{{ .Path }}{{ end
}}

Is the version the issue or I miss some steps?

Best,
tison.

Re: How to build the community page?

[tison]

Locate and fix - https://github.com/apache/comdev-site/pull/161

Best,
tison.


tison  于2024年3月10日周日 00:05写道：

> Hi,
>
> The README file writes: run `hugo` to get the static content.
>
> I got:
>
> $ hugo
> Start building sites …
> hugo v0.123.8-5fed9c591b694f314e5939548e11cc3dcb79a79c+extended
> darwin/arm64 BuildDate=2024-03-07T13:14:42Z VendorInfo=brew
>
> ERROR render of "section" failed:
> "/Users/tison/Brittani/comdev-site/layouts/_default/baseof.html:87:13":
> execute of template failed: template: _default/list.html:87:13: executing
> "_default/list.html" at : error calling
> partial:
> "/Users/tison/Brittani/comdev-site/layouts/partials/website-source.html:5:86":
> execute of template failed: template: partials/website-source.html:5:86:
> executing "partials/website-source.html" at <.Page.File.Path>: error
> calling Path: runtime error: invalid memory address or nil pointer
> dereference
> Total in 77 ms
> Error: error building site: render: failed to render pages: render of
> "section" failed:
> "/Users/tison/Brittani/comdev-site/layouts/_default/baseof.html:87:13":
> execute of template failed: template: _default/list.html:87:13: executing
> "_default/list.html" – File is nil; wrap it in if or with: {{ with partial
> "website-source.html" .>: error calling partial:
> "/Users/tison/Brittani/comdev-site/layouts/partials/website-source.html:5:86":
> execute of template failed: template: partials/website-source.html:5:86:
> executing "partials/website-source.html" at <.Page.File }}{{ .Path }}{{ end
> }}
>
> Is the version the issue or I miss some steps?
>
> Best,
> tison.
>

Re: FYI, ASF volunteers page is live, mentors & speakers are welcome to sign up

[tison]

Cool. Thank you!

Best,
tison.


Bertrand Delacretaz  于2024年3月19日周二 19:45写道：

> Hi,
>
> The new "ASF volunteer mentors & speakers" page [0] is live, meant to
> replace the unmaintained community.zones.apache.org utilities, which
> will soon be redirected to it.
>
> ASF committers are welcome to add their names to that page if you are
> willing to be a mentor and/or speaker on ASF topics.
>
> To do so, add your ASF ID to [1] and if desired you can add some
> additional information (region, languages spoken, website) to [2].
>
> -Bertrand
>
> [0] https://community.apache.org/contributors/asf-volunteers.html
> [1]
> https://github.com/apache/comdev-site/blob/main/source/contributors/asf-volunteers.md
> [2]
> https://github.com/apache/comdev-site/blob/main/static/data/people.json
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Reporter tool for board reports needs some love

[tison]

May I ask where we host the reporter tool source code?

Best,
tison.


Rich Bowen  于2024年3月19日周二 23:52写道：

>
>
>
> > On Mar 18, 2024, at 5:18 PM, Craig Russell  wrote:
> >
> > Hi,
> >
> > Is there anyone who can take a look at the Reporter tool that many
> projects rely on to help create board reports?
> >
> > A number of projects have commented that the statistics seem to be in
> conflict with reality.
>
> Every month several projects make this complaint. I almost always
> encourage them to bring their complaint here. They almost never do, leaving
> us with only the vaguest idea of what they think is broken. Do you feel you
> understand what they think is being reported inaccurately? I think some
> folks have complained about Github stats being off, but that’s pretty easy
> to go retrieve on their own.
>
>

"Maintainer" as an alias of PMC Member?

[tison]

Hi,

Random thought.

You may find people not a native English speaker keep calling a PMC Member
of Apache Foo "Foo PMC".

We correct it so many times and spread the knowledge on list. But the trend
I observed doesn't change and IMO it's hopeless to change.

Since people tend to use a short ref and "committer" gives a one-word
identifier first image, I'm trying to propose officially alias "PMC Member"
as "Maintainer" so that our wording is aligned.

What do you think?

Best,
tison.

Re: "Maintainer" as an alias of PMC Member?

[tison]

> There is nothing to solve here.

I like this idea. Thanks for sharing this option.

Best,
tison.


Rich Bowen 于2024年3月24日 周日20:26写道：

> As much as folks love to debate names ... this isn't a real problem. Some l
> People call PMC members simply "PMC" and while this might grate on some
> people, it's not a real problem. It does not actually cause any bad
> outcomes other than the annoyance of a few people.
>
> There is nothing to solve here.
>
> Creating a new name will simply add yet more confusion and something else
> to get wrong.
>

Re: "Maintainer" as an alias of PMC Member?

[tison]

> Could you do this thread belongs apache Tomcat

While if a project would alias themselves, there should not be a blocker
also?

Best,
tison.


tison 于2024年3月24日 周日20:36写道：

> > There is nothing to solve here.
>
> I like this idea. Thanks for sharing this option.
>
> Best,
> tison.
>
>
> Rich Bowen 于2024年3月24日 周日20:26写道：
>
>> As much as folks love to debate names ... this isn't a real problem. Some
>> l
>> People call PMC members simply "PMC" and while this might grate on some
>> people, it's not a real problem. It does not actually cause any bad
>> outcomes other than the annoyance of a few people.
>>
>> There is nothing to solve here.
>>
>> Creating a new name will simply add yet more confusion and something else
>> to get wrong.
>>
>

Re: Getting a project back on track

[tison]

I can share two examples:

* Livy podling. Users take over the community.
* Ambari. Vendors/Individual Devs revived the community.

But both of them don't seem to be quite active (again).

Best,
tison.


Michael Sokolov  于2024年3月29日周五 22:21写道：

> I guess it depends on what the problem with the project is. It seems
> implicit in your ideas that the project has lost momentum; nobody is
> contributing to it or maintaining it actively? But I just want to
> point out there can be other problems that might need correction with
> different solutions (too much chaos, fighting, legal issues, poor
> quality releases, etc)
>
> On Fri, Mar 29, 2024 at 9:36 AM Rich Bowen  wrote:
> >
> > This week, I’ve been approached by someone concerned about one of our
> projects, and looking for a “how to get back on track” document, with
> concrete, actionable steps that a project can take when it is struggling to
> find contributors. This seems like a great doc that we should write. What
> comes to mind is:
> >
> > * Clearly tell the dev@ and user@ list that the project is at risk if
> they don’t step up
> > * Publish a list of open issues to the Dev list
> > * Contact companies that you know rely on your outputs, and tell them
> that the project is at risk
> > * Clearly document the path/requirements for getting committer. Consider
> lowering your wall a little
> > * What else?
> >
> > Another question that I have is where to put this doc. I’m thinking it
> goes in https://github.com/apache/comdev-site/tree/main/source/pmc
> somewhere, but I’m not sure that to name it.
> >
> >
> >
> > —
> > Rich Bowen
> > rbo...@rcbowen.com
> >
> >
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Getting a project back on track

[tison]

This is why we emphasize community over code. And Kvrocks can be a valuable
example that although quite a few of its "original authors" faded away due
to many reasons, we keep invite new members and due to its product value (a
well-known software's alternative, named Redis), so it can be maintained as
long as a few of code reviewers are there.

The latter is also why sometimes I bring back "code"'s value cause we build
specific SOFTWARE/PROJECT communities. The product value holds to keep
attracting new comers.

> how to get back on track

Back to the question. Another important distinction I'd like to make is

* whether this question is asked by the current PMC; or,
* by someone who may want to take over/contribute to the project and
reactivate it.

Best,
tison.


Rich Bowen  于2024年3月29日周五 22:24写道：

> On Mar 29, 2024, at 10:20 AM, Michael Sokolov  wrote:
> >
> > I guess it depends on what the problem with the project is. It seems
> > implicit in your ideas that the project has lost momentum; nobody is
> > contributing to it or maintaining it actively? But I just want to
> > point out there can be other problems that might need correction with
> > different solutions (too much chaos, fighting, legal issues, poor
> > quality releases, etc)
> >
>
>
> Yes, those things seem useful to address also.
>
> The most common problem we see in ASF projects is that they just wind down
> and lose steam, and end up being one or two people trying to keep the
> lights on, with no time to go out and find helpers.
>
>
>
> > On Fri, Mar 29, 2024 at 9:36 AM Rich Bowen  wrote:
> >>
> >> This week, I’ve been approached by someone concerned about one of our
> projects, and looking for a “how to get back on track” document, with
> concrete, actionable steps that a project can take when it is struggling to
> find contributors. This seems like a great doc that we should write. What
> comes to mind is:
> >>
> >> * Clearly tell the dev@ and user@ list that the project is at risk if
> they don’t step up
> >> * Publish a list of open issues to the Dev list
> >> * Contact companies that you know rely on your outputs, and tell them
> that the project is at risk
> >> * Clearly document the path/requirements for getting committer.
> Consider lowering your wall a little
> >> * What else?
> >>
> >> Another question that I have is where to put this doc. I’m thinking it
> goes in https://github.com/apache/comdev-site/tree/main/source/pmc
> somewhere, but I’m not sure that to name it.
> >>
> >>
> >>
> >> —
> >> Rich Bowen
> >> rbo...@rcbowen.com
> >>
> >>
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Getting a project back on track

[tison]

> * Roadmap -
> a sense of new things that they could help build
> a sense the project is still going someplace

+1 This is what I advise the StreamPark podling every time I meet its
"original author". He shares the challenges that he "cannot find many peers
to collaborate with."

I told him, "Where this project would go is in your mind, and you seldom
speak it out. How can you expect others to spend much time on a project
"not theirs" and figure out what they can do?"

So here is a roadmap this year [1] while I may doubt it's still too
abstract to catch up by other community members not dedicated as his level.

Sorry, I may not be a theorist; just share stories that may help.

Best,
tison.

[1] https://lists.apache.org/thread/k9tk3jlq55ft4ovcgxjv2g6p8bo6qqgl


Shane Curcuru  于2024年3月29日周五 22:39写道：

> Rich Bowen wrote on 3/29/24 9:35 AM:
> > This week, I’ve been approached by someone concerned about one of our
> projects, and looking for a “how to get back on track” document, with
> concrete, actionable steps that a project can take when it is struggling to
> find contributors. This seems like a great doc that we should write. What
> comes to mind is:
> >
> > * Clearly tell the dev@ and user@ list that the project is at risk if
> they don’t step up
> > * Publish a list of open issues to the Dev list
> > * Contact companies that you know rely on your outputs, and tell them
> that the project is at risk
> > * Clearly document the path/requirements for getting committer. Consider
> lowering your wall a little
> > * What else?
>
> * Roadmap - consider publishing a roadmap of what
> features/ideas/improvements to build/docs/etc the project wants to
> implement.  Give contributors a sense of new things that they could help
> build, and a sense the project is still going someplace.
>
> * Double-check your "how to contribute / build / test / submit PR"
> documentation is super clear and easy to follow.  Long-time committers
> on a project often forget all the institutional knowledge they just
> "know", so ensuring the "getting started" document actually works for
> newcomers is always worth looking at.
>
> > Another question that I have is where to put this doc. I’m thinking it
> goes in https://github.com/apache/comdev-site/tree/main/source/pmc
> somewhere, but I’m not sure that to name it.
>
> Yes - primarily advice to PMCs (or active committers).  There are two
> potential primary audiences:
>
> - PMCs that can't find new committers, and ask for help.
>
> - PMCs who might want to regularly self-review how they're working, to
> see if they can improve things for new contributors.
>
> It's kinda "How to encourage new contributors to turn into committers"?
>
> --
> - Shane
>Member
>The Apache Software Foundation
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Getting a project back on track

[tison]

A common mistake for leveraging the power of community is to make
it complicated ”what is suitable for newcomers". Working in many OSS
projects, I practice and encourage other maintainers to practice: Do not
think "community" as an external resource and you need to feed them. We're
part of the community and the evolution of the project is made by the
community.

So, your roadmap, your to-dos, no matter how hard or easy, but only if it's
clear to do or investigate the next step, keep it open. Take over what
you're motivated to do now, and leave the others you want to achieve (and
thus valuable). With a few propagation actions, hackers/enthusiasts would
help, as long as the project provides value and is implemented in a way
they like.

Best,
tison.


tison  于2024年3月29日周五 22:54写道：

> > * Roadmap -
> > a sense of new things that they could help build
> > a sense the project is still going someplace
>
> +1 This is what I advise the StreamPark podling every time I meet its
> "original author". He shares the challenges that he "cannot find many peers
> to collaborate with."
>
> I told him, "Where this project would go is in your mind, and you seldom
> speak it out. How can you expect others to spend much time on a project
> "not theirs" and figure out what they can do?"
>
> So here is a roadmap this year [1] while I may doubt it's still too
> abstract to catch up by other community members not dedicated as his level.
>
> Sorry, I may not be a theorist; just share stories that may help.
>
> Best,
> tison.
>
> [1] https://lists.apache.org/thread/k9tk3jlq55ft4ovcgxjv2g6p8bo6qqgl
>
>
> Shane Curcuru  于2024年3月29日周五 22:39写道：
>
>> Rich Bowen wrote on 3/29/24 9:35 AM:
>> > This week, I’ve been approached by someone concerned about one of our
>> projects, and looking for a “how to get back on track” document, with
>> concrete, actionable steps that a project can take when it is struggling to
>> find contributors. This seems like a great doc that we should write. What
>> comes to mind is:
>> >
>> > * Clearly tell the dev@ and user@ list that the project is at risk if
>> they don’t step up
>> > * Publish a list of open issues to the Dev list
>> > * Contact companies that you know rely on your outputs, and tell them
>> that the project is at risk
>> > * Clearly document the path/requirements for getting committer.
>> Consider lowering your wall a little
>> > * What else?
>>
>> * Roadmap - consider publishing a roadmap of what
>> features/ideas/improvements to build/docs/etc the project wants to
>> implement.  Give contributors a sense of new things that they could help
>> build, and a sense the project is still going someplace.
>>
>> * Double-check your "how to contribute / build / test / submit PR"
>> documentation is super clear and easy to follow.  Long-time committers
>> on a project often forget all the institutional knowledge they just
>> "know", so ensuring the "getting started" document actually works for
>> newcomers is always worth looking at.
>>
>> > Another question that I have is where to put this doc. I’m thinking it
>> goes in https://github.com/apache/comdev-site/tree/main/source/pmc
>> somewhere, but I’m not sure that to name it.
>>
>> Yes - primarily advice to PMCs (or active committers).  There are two
>> potential primary audiences:
>>
>> - PMCs that can't find new committers, and ask for help.
>>
>> - PMCs who might want to regularly self-review how they're working, to
>> see if they can improve things for new contributors.
>>
>> It's kinda "How to encourage new contributors to turn into committers"?
>>
>> --
>> - Shane
>>Member
>>The Apache Software Foundation
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

License for text content

[tison]

Hi,

IIUC, the Apache License 2.0 is mainly to license code and related stuff
that constructs the final software.

However, projects may also create text content like documents. Is it
appropriate to use Apache License 2.0 for them (since quite a few terms may
not be applicable)? Or what licenses shall we use?

For example, a website repo can contain both code and docs. In my personal
site, I wrote:

> Code is licensed under Apache-2.0, words and images are licensed under CC
BY 4.0.

But I don't know if we can write the same to a site repo of an ASF project.

Best,
tison.

Re: [ALC] Request to establish ALC in Shanghai

[tison]

Hi,

+1.

Thanks to Shaofeng for starting ALC Shanghai.
I'm willing to be the mentor of the ALC Shanghai.

I remember that recently we're preparing a DataFusion Meetup perhaps in
Shanghai and I'd like to ask for an ALC collaboration [1][2].

[1]
https://github.com/apache/datafusion/discussions/10341#discussioncomment-9379901
[2]
https://docs.google.com/document/d/1NLGmmfpI4rIdV3pN2ZxM_Rfo5sevTwnT7hhco4NYVUA/edit#heading=h.2bd338xi8gdj

Best,
tison.


Liu Xun  于2024年5月11日周六 09:10写道：

> Please add me to ALC Chapter team list:
> 37. Xun Liu 刘勋; liuxun at apache dot org; Apache Member, PMC member of
> Incubator, Committer of Hadoop and Zeppelin;
>
> Thanks.
>
> On 2024/05/10 09:00:33 ShaoFeng Shi wrote:
> > Hello Community Dev,
> >
> > I'm Shaofen Shi, Apache member and PMC of several projects (incubator,
> > Kylin, Gluten, Horaedb). I live in Shanghai which is the biggest city in
> > China. In Shanghai there are a lot of Apache users, contributors,
> comitters
> > as well as PMC members. Recently we discussed to form the ALC Shanghai so
> > that many events can be organized under it. This proposal has got many
> > responses quickly, and William Jiang has guided us to contact
> dev@community
> > to go through the process.
> >
> > Here is the proposed ALC Chapter team, which has 6 ASF members, and more
> > than 20 PMC member from different projects：
> >
> >
> > 1. Shaofeng Shi 史少锋; shaofengshi at apache dot org; Apache member, PMC of
> > Kylin, Incubator, Gluten, Horaedb;
> > 2. Ted Liu 刘天栋; tedliu at apache dot org; Apache member, PMC member of
> > ComDev, Incubator & Fundraising;
> > 3. He Qi 齐赫; roryqi at apache dot org; PPMC of Uniffle
> > 4. Jeff Zhang 章剑锋; zjffdu at apache dot org; Apache member, PMC member of
> > Tez，Livy, Zeppelin，Incubator
> > 5. Kaijie Chen 陈凯杰; ckj at apache dot org; PMC member of Ozone, Committer
> > of Uniffle
> > 6. Yuming Wang 王玉明; email: yumwang at apache dot org; PMC of Spark
> > 7. Bright Li 李明康; email：slibre at kaoyuanshe dot org; Board Director of
> > KAIYUANSHE
> > 8. Cheng Pan 潘成; chengpan at apache dot org; PMC of Kyuubi Celeborn Toree
> > 9. Junfan Zhang 张俊帆; zuston at apache dot org; PPMC of uniffle
> > 10. Nicholas Jiang 蒋晓峰; nicholasjiang at apache dot org; PMC of Paimon,
> > Committer of Celeborn, Kyuubi, RocketMQ, ShardingSphere
> > 11. Fu Chen 陈福; fchen at apache dot org; PMC of Kyuubi, Celeborn
> > 12. Yun Tang 唐云; tangyun at apache dot org ，committer of Flink
> > 13. Li Cheng 程力; licheng at apache dot org, Committer of Hadoop, Ozone,
> PMC
> > of Ozone
> > 14. Calvin Fu 伏长海; changhaifu at apache dot org，committer of
> > DolphinScheduler
> > 15. Chufeng Gao 高楚枫; chufenggao at apache dot org，PMC member of
> > DolphinScheduler
> > 16. Shaoyun Chen 陈少云; csy at apache dot org, PMC member of Kyuubi,
> > Committer of Celeborn
> > 17. Jerry shao 邵赛赛; jshao at apache dot org, PMC mmeber of Apache Spark,
> > Apache member
> > 18. Meng duan 段蒙; macduan at apache dot org, PPMC of Uniffle
> > 19. Vinoyang 杨华; vinoyang at apache dot org PMC member of Apache Hudi and
> > Kyuubi
> > 20. Dong Li 李栋; lidong at apache dot org; PMC of Apache Kylin
> > 21. Yi Chen 陈怡; sammichen at apache dot org; PMC of Hadoop & Ozone,
> Apache
> > Member
> > 22. Yuxiang Wang 王昱翔; wangyuxiang at apache dot org; committer of
> >  dolphinscheduler
> > 23. Zhankun Tang 汤占坤; ztang at apache dot org; PMC of Hadoop; Apache
> Member.
> > 24. Yanghong Zhong 钟阳红; nju_yaho at apache dot org; PMC of Kylin;
> Committer
> > of Datafusion
> > 25. Chunen Ni 倪春恩; nic at apache dot org; PMC of Kylin
> > 26. Junping Du 堵俊平; junping_du at apache dot org，ASF Member, PMC of
> >  Hadoop, OZone, YuniKorn, Linkis, EventMesh
> > 27. Yao Zhou 周尧;  zhouyao2023 at apache dot org; Committer of SeaTunnel
> > 28. Jie Yao 姚杰; jacksonyao at apache dot org; committer of Ozone,
> > 29. Zhen Wang 王震; wangzhen at apache dot org; PMC of Kyuubi & Linkis
> > 30. Shaohong Xu 徐少鸿; xsh at apache dot org; committer of Ozone
> > 31. Xudong Guo 郭旭东; guoxudong.dev at gmail.com; maintainer of kubevela
> > 32. Rui Li 李锐; lirui at apache dot org; Flink committer, PMC of Hive
> > 33. Jiabao Sun 孙家宝; jiabaosun at apache dot org; Flink committer
> > 34. Zhifang Li 李志方;  zhifgli at gmail dot com;  PMC of Uniffle
> > 35. junjie chen 陈俊杰; junjie at apache dot org; PMC of Inlong
> > 36. Kevin Clair 宋明杰; kevinclair at apache dot org; PMC of Shenyu
> >
> > Please help to review and create related resources once get approved.
> Thank
> > you!
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC member,
> > Apache Incubator PMC member,
> > Email: shaofeng...@apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [WG-Website] Calling attention to projects that Do Stuff Right

[tison]

Hi Rich,

Thanks for sharing this. They look great :D

I agree that we can have a template for these on our comdev site. I saw
podlings to Googling and hit some TLPs page that may not document the stuff
super properly.

I'd share some more similar pages here and see if we can find the common
good parts and if some of them can be improved, so that we have a general
consensus on what to be included in the templates.

* https://opendal.apache.org/community/committers/onboarding and the
related pages on the sidebar.
*
https://streampark.apache.org/community/contribution_guide/become_committer and
the related pages on the sidebar.
* https://curator.apache.org/community/new-committers
* https://inlong.apache.org/community/how-to-become-a-committer and the
related pages on the sidebar.

I can volunteer to add the page on the comdev site within the next month
(June), but I'm glad to follow any other's work. And I'd like to see
opinions if people find certain items on these pages helpful/encouraging or
redundant/misleading.

Best,
tison.


Rich Bowen  于2024年5月16日周四 21:51写道：

> I wanted to draw attention to two projects that are doing amazing things,
> and make a note that we should encourage other projects to do the same.
>
> Specifically:
>
> Yesterday I came across DataFusion’s “how to become a committer” page -
> https://datafusion.apache.org/contributor-guide/governance.html - and I
> would like for us to encourage other projects to use this page as a
> template for documenting their own committer conventions.
>
> Secondly, I came across Arrow’s developer onboarding guide -
> https://arrow.apache.org/docs/developers/overview.html - and would like
> for us to encourage projects to write up something similar for their sites.
>
> These could perhaps go somewhere in https://community.apache.org/pmc/
>
> —
> Rich Bowen
> rbo...@rcbowen.com
>
>
>
>
>

Re: How to transfer / donate an already running opensource project

[tison]

Hi Josh,

This is actually the normal case. You can read
https://incubator.apache.org/cookbook/ and email to
gene...@incubator.apache.org for help.

Best,
tison.

Josh  于2024年6月15日周六 13:23写道：
>
> Dear team,
>
> I'm looking for information on the procedure or process to transfer an
> already running open source project to ASF.
>
> I really would appreciate it if anyone can help me with this information.
>
> Thanks and best regards
> Frank

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

Re: Should HelpWanted be shut down?

[tison]

One may think of iterating all the issues with GitHub REST/GraphQL API
and filter them when label. It MAY be possible for GraphQL but NEVER
for REST API since it have to iterate almost all the (open) issues and
we'd quickly exceed any rate limit (as we have over 2000 repos and
many many issues ...). It's also slow because REST API returns a full
object for the issue every time.

Best,
tison.

tison  于2024年10月25日周五 02:03写道：
>
> To list help wanted issues on our repository, try:
>
> https://github.com/search?q=org:apache+label:%22help+wanted%22&type=issues
> https://github.com/search?q=org:apache+label:%22help+wanted%22&type=pullrequests
> https://github.com/search?q=org:apache+label:%22help+wanted%22&type=discussions
>
> There are some GitHub APIs for this search interface:
>
> https://docs.github.com/en/rest/search/search?apiVersion=2022-11-28
> https://docs.github.com/en/graphql/reference/queries#search
>
> But I don't check it closely and the three URLs above should be easier
> to start with.
>
> Best,
> tison.
>
> sebb  于2024年10月25日周五 00:02写道：
> >
> > On Thu, 24 Oct 2024 at 16:36, Xuanwo  wrote:
> > >
> > > +1 to shut it down.
> > >
> > > We can rebuild it using GitHub APIs as needed, eliminating the need for 
> > > heavy infrastructure like Elasticsearch.
> >
> > Are you offering to help build it?
> >
> > > On Thu, Oct 24, 2024, at 23:23, Christopher wrote:
> > > > An alternative would be to automatically link to open issues in
> > > > GitHub.com/Apache with specific tags, like "help wanted" or "good first
> > > > issue". This is similar to what hacktoberfest does to help participants
> > > > discover new issues. Merely having a listing of issues on GitHub would 
> > > > be
> > > > much easier to support than maintaining a site that manages its own
> > > > authentication, issue submission, and database.
> > > >
> > > > On Thu, Oct 24, 2024, 11:17 Rich Bowen  wrote:
> > > >
> > > >>
> > > >>
> > > >> > On Oct 24, 2024, at 10:04 AM, sebb  wrote:
> > > >> >
> > > >> > The helpwanted.a.o service uses ElasticSearch (ES).
> > > >> > However, the current version is rather old.
> > > >> > This was causing issues with Puppet server deployment.
> > > >> >
> > > >> <…>
> > > >> > ** So is there any point in keeping the system running, or should it
> > > >> > be shut down? **
> > > >>
> > > >> I was actually under the impression that we *had* shut it down. So, 
> > > >> yes, I
> > > >> would be +1 to decomm it entirely. It was a great idea that projects 
> > > >> never
> > > >> really utilized, and as such was never very useful in practice. :(
> > > >>
> > > >> —
> > > >> Rich Bowen
> > > >> rbo...@rcbowen.com
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> > > --
> > > Xuanwo
> > >
> > > https://xuanwo.io/
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >

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

Re: Should HelpWanted be shut down?

[tison]

To list help wanted issues on our repository, try:

https://github.com/search?q=org:apache+label:%22help+wanted%22&type=issues
https://github.com/search?q=org:apache+label:%22help+wanted%22&type=pullrequests
https://github.com/search?q=org:apache+label:%22help+wanted%22&type=discussions

There are some GitHub APIs for this search interface:

https://docs.github.com/en/rest/search/search?apiVersion=2022-11-28
https://docs.github.com/en/graphql/reference/queries#search

But I don't check it closely and the three URLs above should be easier
to start with.

Best,
tison.

sebb  于2024年10月25日周五 00:02写道：
>
> On Thu, 24 Oct 2024 at 16:36, Xuanwo  wrote:
> >
> > +1 to shut it down.
> >
> > We can rebuild it using GitHub APIs as needed, eliminating the need for 
> > heavy infrastructure like Elasticsearch.
>
> Are you offering to help build it?
>
> > On Thu, Oct 24, 2024, at 23:23, Christopher wrote:
> > > An alternative would be to automatically link to open issues in
> > > GitHub.com/Apache with specific tags, like "help wanted" or "good first
> > > issue". This is similar to what hacktoberfest does to help participants
> > > discover new issues. Merely having a listing of issues on GitHub would be
> > > much easier to support than maintaining a site that manages its own
> > > authentication, issue submission, and database.
> > >
> > > On Thu, Oct 24, 2024, 11:17 Rich Bowen  wrote:
> > >
> > >>
> > >>
> > >> > On Oct 24, 2024, at 10:04 AM, sebb  wrote:
> > >> >
> > >> > The helpwanted.a.o service uses ElasticSearch (ES).
> > >> > However, the current version is rather old.
> > >> > This was causing issues with Puppet server deployment.
> > >> >
> > >> <…>
> > >> > ** So is there any point in keeping the system running, or should it
> > >> > be shut down? **
> > >>
> > >> I was actually under the impression that we *had* shut it down. So, yes, 
> > >> I
> > >> would be +1 to decomm it entirely. It was a great idea that projects 
> > >> never
> > >> really utilized, and as such was never very useful in practice. :(
> > >>
> > >> —
> > >> Rich Bowen
> > >> rbo...@rcbowen.com
> > >>
> > >>
> > >>
> > >>
> > >>
> >
> > --
> > Xuanwo
> >
> > https://xuanwo.io/
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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

[DISCUSS] Update project maturity model to include trademark and branding?

[tison]

Hi,

Here is a continued effort of the thread "Update project maturity
model to include trademark and branding?"[1] early this year.

[1] https://lists.apache.org/thread/oc9jft1tyo7cbphcyrtwobf4w5rcbhfw

Brief background: During the graduation of podlings in incubation, we
actively evaluate their treatment for trademark and branding. However,
this is not reflected in our maturity model and can result in the
friction of tribal knowledge.

So, here is my proposed content updated for the project maturity model:

Content BEGIN

Notable items from the Trademark Policy [1], FAQ [2], and Guide [3].
The project should comply with ASF's branding and trademark policy in
all places it controls.

[1] https://www.apache.org/foundation/marks/
[2] https://www.apache.org/foundation/marks/faq/
[3] https://www.apache.org/foundation/marks/guide

TB10 The project correctly uses "Apache Foo" as the project name where required.
TB20 The project resolves any potential trademark issue pointed out to
it promptly.
TB30 The project proactively monitors 3rd party use of its trademarks,
addressing any instances of misuse.
(Note TB30: for example, regularly/irregularly check how downstream
refer to the project, check how 3rd party sites refer to the project)
TB40 Any existing previous domain name relating to the project name is
under the PMC's control.
TB50 Any existing trademarks relating to the project name have been or
are in the process of being transferred to the ASF.

Content END

Feedback, thoughts, etc, are welcome.

I'd first gather feedback on the terms, and once we agree on them, I'd
submit a PR to [2] to update the related pages.

[2] 
https://github.com/apache/comdev-site/blob/main/source/apache-way/apache-project-maturity-model.md?plain=1

Best,
tison.

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

Re: grammatical error on https://community.apache.org/contributors/

[tison]

Hello Will!

Thanks a lot for pointing that out. This is surely a typo that need to
be corrected.

> I did not dare attempt to push the Commit button on my local clone repository.

You are welcome to contribute. Just push a commit, create a pull
request; or even edit the file on GitHub Web UI like [1]. I'm happy to
help merge this fix.

[1] 
https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files.

Best,
tison.

Will Raymond  于2024年12月28日周六 04:41写道：
>
> Hello Apache Devs,
>
> There is a grammatical error at bottom of page:
>
> https://github.com/apache/comdev-site/blob/main/source/contributors/_index.md
> Questions and Feedback
>  
> <https://github.com/apache/comdev-site/blob/main/source/contributors/_index.md#questions-and-feedback>
> If you have other questions, the ComDev team he here to help.
>
> Should be:
>
> If you have other questions, the ComDev team is here to help.
>
> I apologize if this is incorrect protocol for reporting website issues but 
> repository does not have Issues page. I did not dare attempt to push the 
> Commit button on my local clone repository. I am a Git newbie still on Basic 
> Mode.
>
> Best Regards,
> Will
>
> https://github.com/WillTheFarmer/ApacheLogs2MySQL
>

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

Re: [DISCUSS] Update project maturity model to include trademark and branding?

[tison]

I'm going to merge the current version at
https://github.com/apache/comdev-site/pull/199 later this week.

Editions can be made as follow-ups.

To modify the foundation-level trademark guidance pages, I'll start a
new thread for tracking and processing.

Best,
tison.

tison  于2024年12月22日周日 23:46写道：
>
> Sent at https://github.com/apache/comdev-site/pull/199.
>
> Welcome to leave your review.
>
> Best,
> tison.
>
> tison  于2024年12月13日周五 20:03写道：
> >
> > Thanks for all of your feedback!
> >
> > I'll submit a PR to comdev-site next week on which we can finalize the
> > wording. Thank Shane and I'll integrate your suggestions there.
> >
> > Modifying https://www.apache.org/foundation/marks/responsibility
> > sounds generally reasonable. I'll review the page this month and start
> > another thread on trademarks@.
> >
> > Best,
> > tison.
> >
> > Jean-Baptiste Onofré  于2024年12月12日周四 23:21写道：
> > >
> > > Hi,
> > >
> > > It looks good to me. Thanks for proposing this !
> > >
> > > Regards
> > > JB
> > >
> > > On Wed, Nov 27, 2024 at 3:07 AM tison  wrote:
> > > >
> > > > Hi,
> > > >
> > > > Here is a continued effort of the thread "Update project maturity
> > > > model to include trademark and branding?"[1] early this year.
> > > >
> > > > [1] https://lists.apache.org/thread/oc9jft1tyo7cbphcyrtwobf4w5rcbhfw
> > > >
> > > > Brief background: During the graduation of podlings in incubation, we
> > > > actively evaluate their treatment for trademark and branding. However,
> > > > this is not reflected in our maturity model and can result in the
> > > > friction of tribal knowledge.
> > > >
> > > > So, here is my proposed content updated for the project maturity model:
> > > >
> > > > Content BEGIN
> > > >
> > > > Notable items from the Trademark Policy [1], FAQ [2], and Guide [3].
> > > > The project should comply with ASF's branding and trademark policy in
> > > > all places it controls.
> > > >
> > > > [1] https://www.apache.org/foundation/marks/
> > > > [2] https://www.apache.org/foundation/marks/faq/
> > > > [3] https://www.apache.org/foundation/marks/guide
> > > >
> > > > TB10 The project correctly uses "Apache Foo" as the project name where 
> > > > required.
> > > > TB20 The project resolves any potential trademark issue pointed out to
> > > > it promptly.
> > > > TB30 The project proactively monitors 3rd party use of its trademarks,
> > > > addressing any instances of misuse.
> > > > (Note TB30: for example, regularly/irregularly check how downstream
> > > > refer to the project, check how 3rd party sites refer to the project)
> > > > TB40 Any existing previous domain name relating to the project name is
> > > > under the PMC's control.
> > > > TB50 Any existing trademarks relating to the project name have been or
> > > > are in the process of being transferred to the ASF.
> > > >
> > > > Content END
> > > >
> > > > Feedback, thoughts, etc, are welcome.
> > > >
> > > > I'd first gather feedback on the terms, and once we agree on them, I'd
> > > > submit a PR to [2] to update the related pages.
> > > >
> > > > [2] 
> > > > https://github.com/apache/comdev-site/blob/main/source/apache-way/apache-project-maturity-model.md?plain=1
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >

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

Re: [DISCUSS] Update project maturity model to include trademark and branding?

[tison]

Thanks for all of your feedback!

I'll submit a PR to comdev-site next week on which we can finalize the
wording. Thank Shane and I'll integrate your suggestions there.

Modifying https://www.apache.org/foundation/marks/responsibility
sounds generally reasonable. I'll review the page this month and start
another thread on trademarks@.

Best,
tison.

Jean-Baptiste Onofré  于2024年12月12日周四 23:21写道：
>
> Hi,
>
> It looks good to me. Thanks for proposing this !
>
> Regards
> JB
>
> On Wed, Nov 27, 2024 at 3:07 AM tison  wrote:
> >
> > Hi,
> >
> > Here is a continued effort of the thread "Update project maturity
> > model to include trademark and branding?"[1] early this year.
> >
> > [1] https://lists.apache.org/thread/oc9jft1tyo7cbphcyrtwobf4w5rcbhfw
> >
> > Brief background: During the graduation of podlings in incubation, we
> > actively evaluate their treatment for trademark and branding. However,
> > this is not reflected in our maturity model and can result in the
> > friction of tribal knowledge.
> >
> > So, here is my proposed content updated for the project maturity model:
> >
> > Content BEGIN
> >
> > Notable items from the Trademark Policy [1], FAQ [2], and Guide [3].
> > The project should comply with ASF's branding and trademark policy in
> > all places it controls.
> >
> > [1] https://www.apache.org/foundation/marks/
> > [2] https://www.apache.org/foundation/marks/faq/
> > [3] https://www.apache.org/foundation/marks/guide
> >
> > TB10 The project correctly uses "Apache Foo" as the project name where 
> > required.
> > TB20 The project resolves any potential trademark issue pointed out to
> > it promptly.
> > TB30 The project proactively monitors 3rd party use of its trademarks,
> > addressing any instances of misuse.
> > (Note TB30: for example, regularly/irregularly check how downstream
> > refer to the project, check how 3rd party sites refer to the project)
> > TB40 Any existing previous domain name relating to the project name is
> > under the PMC's control.
> > TB50 Any existing trademarks relating to the project name have been or
> > are in the process of being transferred to the ASF.
> >
> > Content END
> >
> > Feedback, thoughts, etc, are welcome.
> >
> > I'd first gather feedback on the terms, and once we agree on them, I'd
> > submit a PR to [2] to update the related pages.
> >
> > [2] 
> > https://github.com/apache/comdev-site/blob/main/source/apache-way/apache-project-maturity-model.md?plain=1
> >
> > Best,
> > tison.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Update project maturity model to include trademark and branding?

[tison]

Sent at https://github.com/apache/comdev-site/pull/199.

Welcome to leave your review.

Best,
tison.

tison  于2024年12月13日周五 20:03写道：
>
> Thanks for all of your feedback!
>
> I'll submit a PR to comdev-site next week on which we can finalize the
> wording. Thank Shane and I'll integrate your suggestions there.
>
> Modifying https://www.apache.org/foundation/marks/responsibility
> sounds generally reasonable. I'll review the page this month and start
> another thread on trademarks@.
>
> Best,
> tison.
>
> Jean-Baptiste Onofré  于2024年12月12日周四 23:21写道：
> >
> > Hi,
> >
> > It looks good to me. Thanks for proposing this !
> >
> > Regards
> > JB
> >
> > On Wed, Nov 27, 2024 at 3:07 AM tison  wrote:
> > >
> > > Hi,
> > >
> > > Here is a continued effort of the thread "Update project maturity
> > > model to include trademark and branding?"[1] early this year.
> > >
> > > [1] https://lists.apache.org/thread/oc9jft1tyo7cbphcyrtwobf4w5rcbhfw
> > >
> > > Brief background: During the graduation of podlings in incubation, we
> > > actively evaluate their treatment for trademark and branding. However,
> > > this is not reflected in our maturity model and can result in the
> > > friction of tribal knowledge.
> > >
> > > So, here is my proposed content updated for the project maturity model:
> > >
> > > Content BEGIN
> > >
> > > Notable items from the Trademark Policy [1], FAQ [2], and Guide [3].
> > > The project should comply with ASF's branding and trademark policy in
> > > all places it controls.
> > >
> > > [1] https://www.apache.org/foundation/marks/
> > > [2] https://www.apache.org/foundation/marks/faq/
> > > [3] https://www.apache.org/foundation/marks/guide
> > >
> > > TB10 The project correctly uses "Apache Foo" as the project name where 
> > > required.
> > > TB20 The project resolves any potential trademark issue pointed out to
> > > it promptly.
> > > TB30 The project proactively monitors 3rd party use of its trademarks,
> > > addressing any instances of misuse.
> > > (Note TB30: for example, regularly/irregularly check how downstream
> > > refer to the project, check how 3rd party sites refer to the project)
> > > TB40 Any existing previous domain name relating to the project name is
> > > under the PMC's control.
> > > TB50 Any existing trademarks relating to the project name have been or
> > > are in the process of being transferred to the ASF.
> > >
> > > Content END
> > >
> > > Feedback, thoughts, etc, are welcome.
> > >
> > > I'd first gather feedback on the terms, and once we agree on them, I'd
> > > submit a PR to [2] to update the related pages.
> > >
> > > [2] 
> > > https://github.com/apache/comdev-site/blob/main/source/apache-way/apache-project-maturity-model.md?plain=1
> > >
> > > Best,
> > > tison.
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >

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

Re: [DISCUSS] Consensus to make release candidates publicly accessible during the voting period

[tison]

FYI start a discussion for OpenDAL [1]. We released multiple languages
binding in OpenDAL so let's see if this approach helps :D

[1] https://github.com/apache/opendal/discussions/5535

Best,
tison.

tison  于2025年1月11日周六 10:52写道：
>
> Hi Justin,
>
> This is great. Thanks for sharing this.
>
> Best,
> tison.
>
> Justin Mclean  于2025年1月10日周五 06:12写道：
> >
> > Hi,
> >
> > Some of this was discussed several years ago, and we had the board approve 
> > some guidelines that can be found here:
> > https://incubator.apache.org/guides/distribution.html
> >
> > Note that covers RC for PyPi and other platforms. Projects are not 
> > prohibited from publishing RCs, they just need to take care that they are 
> > not installed by default and are clearly marked as RCs.
> >
> > Kind Regards,
> > Justin
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >

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

Re: [DISCUSS] Consensus to make release candidates publicly accessible during the voting period

[tison]

Hi Justin,

This is great. Thanks for sharing this.

Best,
tison.

Justin Mclean  于2025年1月10日周五 06:12写道：
>
> Hi,
>
> Some of this was discussed several years ago, and we had the board approve 
> some guidelines that can be found here:
> https://incubator.apache.org/guides/distribution.html
>
> Note that covers RC for PyPi and other platforms. Projects are not prohibited 
> from publishing RCs, they just need to take care that they are not installed 
> by default and are clearly marked as RCs.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

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

Re: [DISCUSS] Consensus to make release candidates publicly accessible during the voting period

[tison]

@Jarek:

> but how PMCS turn that into practice - should be up to them.

Of course. As stated in the the first mail, I'd "establish a consensus
to explicitly allow making release candidates publicly accessible
during the voting period."

It's to "allow" or hint PMCs that they can do so, because, as per
other discussions recently, the 72 hours "requirements" would give a
wrong assumption that it's a MUST and even release candidates can only
stay in dist.apache.org/repos/dist/dev for devs who are able to verify
everything from the source code.

And different languages has their own idiom, like Go can leverage a
Git tag 1.0.3-rc.1, and Rust's cargo can set apache-foo = { git =
"", tag = "1.0.3-rc.1" }. We don't limit the implementation,
just that PMCs _can_ "publish" their RC to central repositories.

@Gary:

> Is this an opt-in or opt-out policy?

It's an opt-in, IMO, suggestion. I'm sorry that the title may read
like a policy, but I actually wrote it to seek a consensus to allow
doing this, not a requirement.

> We wouldn't want to do that for CVE fixed right?

Yes.

@Piotr:

Thanks for your feedback and sharing on how to do with Java/Maven
project. That looks good.

Best,
tison.

Gary Gregory  于2025年1月9日周四 20:43写道：
>
> Is this an opt-in or opt-out policy? We wouldn't want to do that for CVE
> fixed right?
>
> Gaty
>
> On Thu, Jan 9, 2025, 07:07 Jarek Potiuk  wrote:
>
> > Sorry " should be *not *to encourage the projects to make it easy for
> > anyone to install and test the release" ->  "should be to encourage the
> > projects to make it easy for anyone to install and test the release"
> >
> > On Thu, Jan 9, 2025 at 1:06 PM Jarek Potiuk  wrote:
> >
> > > Just a small thing to add - while we are releasing RCs, I think the right
> > > approach should be not to encourage the projects to make it easy for
> > anyone
> > > to install and test the release - which does not automatically mean to
> > > publish RC in the same way the final candidate is published.
> > > The key here is to let the users know that there is a candidate and
> > > encourage them to test it. I think it has more nuances than publishing to
> > > Maven/ PyPI etc. - and PMCs should choose their own ways and encourage
> > > their "dev community" (not end users mind you - those users might be
> > > misled into thinking this is the final release!) to test it.
> > >
> > > There are many ways how this can be done:
> > >
> > > * Airflow is indeed publishing RC candidates in PyPI (PyPI has a great
> > > distinction between pre-release and final candidates and users cannot
> > > mistake them for final versions, they need to explicitly install RC
> > > candidates) and we invite contributors to test the releases via GitHub
> > > issue (automated) where we mark the involved contributors: example here -
> > > https://github.com/apache/airflow/issues/45148  - we usually have at
> > > least 60% "success" rate - i.e. more than half of the users involved are
> > > willing to take the RCs for a spin, install it and test it (and confirm
> > it
> > > works or report issues). This sustainably works for 3-4 years now.
> > >
> > > * However, quite recently in the Python ecosystem at least where the
> > > Python Community standardised packaging and build backend/front-end
> > > approach - it is a very common practice to use GitHub branches to install
> > > the software. There is a way to do it it in a standard way and more often
> > > than not when we find and report (or comment) an  issue in a dependent
> > > library, they create a PR and ask everyone to test it from the branch -
> > an
> > > example of it recently where we found a problem in Pygments and they
> > > created a PR fixing it - issue here
> > > https://github.com/pygments/pygments/issues/2834, PR in Airflow testing
> > > the change in PR here:
> > https://github.com/apache/airflow/pull/45416/files
> > > (basically replacing "pygments>=2.0.1,!=2.19.0" with "pygments @ git+
> > >
> > https://github.com/pygments/pygments.git@a9858663ed85219ed7475f5877b22b9cb49f660f
> > ".
> > > This is a very efficient way of testing - because you can test the fix
> > not
> > > when all the burden of release preparation and rc candidate preparation
> > is
> > > done, but way before, even way before the PR with fix is merged. This is
> > > something we are actually going to encourag

[DISCUSS] Consensus to make release candidates publicly accessible during the voting period

[tison]

Hi,

I'd like to establish a consensus to explicitly allow making release
candidates publicly accessible during the voting period.

This should be an existing exercise that the source code of release
candidates is available on dist.apache.org, e.g., [1].

[1] https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.1.1-rc1/

The situation I'd like to highlight here is that, nowadays verifiers
would find it more convenient to pull the release candidate from a
central repository, like Maven Central, PyPI, crates.io, etc.

I don't know if other projects release versions like 1.0.3-rc.1 to
those repositories during the voting period, but I know a few projects
won't do that before a formal release is cut. This actually harms the
verification the release candidate could receive.

Making a release candidate version on those repositories should be the
same as publishing the source code to dist.apache.org/repos/dist/dev
with an RC tag. So, I'd establish a consensus to allow doing so
explicitly.

For example, when Apache Foo (assumed Rust project) is releasing
1.0.3, the RM could release a 1.0.3-rc.1 version to crates.io, so that
users can simply bump the version to 1.0.3-rc.1 to test it out and
give feedback. These versions would be well-known as under-verifying
status instead of releases endorsed by a TLP PMC.

So does PyPI and Maven Central (rather than making stagingRepositories
only, which is hard to test for developers unfamiliar with it).

Some background:

We require a 72 hours period before calling a formal release. I heard
and experienced that a lot of new developers won't test the release
(candidate) before they are available on those common central
repositories, which, in some way, gives the impression that the ASF
releases slowly. This is, of course, not true.

By allowing developers to test RC on the central repositories and
establish proper assumptions between a formal release and a release
candidate corresponding to the version tag, we can reduce the friction
of the development workflow that new developers are familiar with.

Looking forward to your feedback, and I'd like to know how other TLPs do.

Best,
tison.

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

A page telling the project history would be better than "I'm an original creator of Apache Foo"

[tison]

Hi,

We have seen many threads discussing whether someone self-promotes as
"an original creator of Apache Foo" is suitable.

Today, when I'm reviewing Curator's website, I found an interesting
page [1] that tells the project's history.

[1] https://curator.apache.org/community/history

It clearly states that Jordan Zimmerman is the original author of the
project, which he created while working at Netflix. Later, the project
entered the incubator, graduated, and became a top-level project in
the ASF. All the history after donating is part of Apache Curator.

I would encourage projects to write such a page when they are
interested in identifying the original creators. A project's rationale
explains its motivation, who creates what, and for what reasons (why).
This would be much more valuable content to host. (This is a required
section in the incubation proposal.)

History can continue if anything significant happens after entering
the ASF, but the narrative subject becomes Apache Foo, and we should
be fine with those words.

Best,
tison.

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

Re: [ALC] Request to establish ALC in Florianópolis

[tison]

I remember you guys have already created an #alc-brazil channel on the ASF
Slack workspace?

Overall, this is a good proposal. +1

Best,
tison.


Daniel Salvador  于2025年4月9日周三 10:09写道：

> Hello people,
>
> Other members and I (contributors from Cassandra, CloudStack, Tapestry,
> and others) have been discussing and we would like to start the process
> of establishing ALCs in Brazil. We feel we can gather (old and new)
> contributors together with this process, and build a nice community in
> Brazil.
>
> Most of the currently interested reside in Florianópolis, SC; thus, the
> initial efforts would be to establish an ALC in Florianópolis, SC.
>
> Please let us know your opinion on this.
>
> Best regards,
> Daniel Salvador (gutoveronezi)
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Add to List

[tison]

Hi Simmons,

Welcome!

If you'd like to subscribe to dev@community.apache.org, you can send an
email to dev-subscr...@community.apache.org with any content, and reply to
the confirming email.

I'm glad to hear about any specific actions you'd like to take here. Do you
have something in mind? Or barely subscribing to what people discuss on the
mailing list.

Best,
tison.


Simmons, Delbert  于2025年4月25日周五 04:47写道：

> Hi,
>
> Requesting to be added to this list
>
>
>
> Respectfully,
>
>
> Del Simmons
>
> Consultant
>
> [
> https://imageproxy.zdassets.com/f278a90c30fb481db71e629e726d493f9f3498ab?url=http%3A%2F%2Fzigabytepublic.s3.us-east-2.amazonaws.com%2FZigabyteEmail130x26.png
> ]<
> https://urldefense.com/v3/__http://www.zigabyte.com/__;!!MsNKLpFGsw!d8VVFIzsLhgC9SM4EQq1jA77hUnZWVBLU9gTApv8Rd_choaYLWxwXaxCKinfYePD$>
> | Character | Competence | Community
>
> email: delbert.simm...@zigabyte.com
>
> cell: 803.269.9182
>
>

Re: [ALC] Request to establish ALC in Taipei

[tison]

+1 looks like a good proposal

Best,
tison.


Wei-Chiu Chuang  于2025年4月3日周四 23:48写道：

> +1
> I'm an Apache Member and a member of several PMCs. So if it helps I can
> also join the Chapter's member team.
>
> On Thu, Apr 3, 2025 at 8:23 AM Chia-Ping Tsai  wrote:
>
> > hi All,
> >
> > I'm an Apache Member (Apache ID: chia7712), and I've led the local
> > open-source community, 源來適你/opensource4you [1], for two years. We've
> > successfully fostered contributions to various Apache projects, including
> > Apache Kafka, Apache YuniKorn, Apache Airflow, and Apache Gravitino,
> > resulting in over 10 community members becoming Apache committers.
> >
> > Leveraging the Apache Local Community (ALC) name would be a valuable
> asset
> > in our efforts to attract more contributors to open-source software
> > projects.
> >
> > Thanks,
> > Chia-Ping
> >
> > [1] https://www.facebook.com/opensource4you
> >
>

Re: Software Licensing Machine Learning

[tison]

We have a similar license with extra clauses case recently where you may
read also [1]

[1] https://lists.apache.org/thread/7ns8qh3bzd9yct2hzqzbwhvcd6xbwpgh

Best,
tison.


tison  于2025年4月2日周三 19:43写道：

> This seems like a legal discussion where we have a mailing list,
> legal-disc...@apache.org [1], for this kind of topic.
>
> [1] https://www.apache.org/legal/#communications
>
> You can bring the topic there and people may reply to your idea.
>
> Best,
> tison.
>
>
> Rock de Vocht  于2025年4月2日周三 18:24写道：
>
>> Dear ASF,
>>
>> (Apologies if I sent this message twice, there was a misunderstanding on
>> my part about how the email subscription system worked.)
>>
>> As a developer I am quite concerned about machine learning being applied
>> to our code.  I was wondering if you could perhaps create a new license,
>> like the Apache v2 you have, that included clauses like:
>>
>>
>>1. Definitions:
>>
>>
>>   "Machine learning" shall mean access to this source code by algorithms,
>>   computer systems, and automatic scraping, for the express purpose of
>>   automated coding, and improving learning rates of neural networs.
>>
>>   "Machine Learning Work" shall mean any work or service, whether in
>>   source, object, or hosted software form.
>>
>>
>> 4. Redistribution
>>
>>   (e) If this Software is used for Machine Learning Work, then any and
>>   all parts (including source code, and training data with clear
>>   instructions on how to replicate your Machine Learning Work)
>>   of that Machine Learning Work need to be made publicly available
>>   without any restrictions.
>>
>>
>>
>> I've added such a modified LICENSE (based on your Apache v2) to my own
>> website that includes just these two clauses.
>>
>> https://peter.nz/LICENSE
>>
>> However - as I am not trained in law and licensing, I thought the ASF
>> would be interested in this and perhaps could suggest taking this forward
>> (in whatever form or shape you deem fit).
>>
>> thanks!
>>
>> Rock
>>
>>
>>
>> ---
>>
>> [image: SimSage - Intelligent Information Management]
>>
>> *Rock de Vocht*
>> Chief Science Officer
>> r...@simsage.co.uk
>> +44 (0)7931 467981
>>
>> Intelligent Information Management
>> www.simsage.ai
>>
>> NOTE: The information contained in this email and its attachments is
>> confidential and may be the subject of legal privilege. It is intended only
>> for the named addressees and may not be disclosed to anyone else without
>> the prior consent of SimSage (UK) Ltd. If you are not the named addressee
>> you must not use, disclose, distribute, copy, print or rely on the contents
>> of this email and should destroy it immediately.
>>
>>

Re: Software Licensing Machine Learning

[tison]

This seems like a legal discussion where we have a mailing list,
legal-disc...@apache.org [1], for this kind of topic.

[1] https://www.apache.org/legal/#communications

You can bring the topic there and people may reply to your idea.

Best,
tison.


Rock de Vocht  于2025年4月2日周三 18:24写道：

> Dear ASF,
>
> (Apologies if I sent this message twice, there was a misunderstanding on
> my part about how the email subscription system worked.)
>
> As a developer I am quite concerned about machine learning being applied
> to our code.  I was wondering if you could perhaps create a new license,
> like the Apache v2 you have, that included clauses like:
>
>
>1. Definitions:
>
>
>   "Machine learning" shall mean access to this source code by algorithms,
>   computer systems, and automatic scraping, for the express purpose of
>   automated coding, and improving learning rates of neural networs.
>
>   "Machine Learning Work" shall mean any work or service, whether in
>   source, object, or hosted software form.
>
>
> 4. Redistribution
>
>   (e) If this Software is used for Machine Learning Work, then any and
>   all parts (including source code, and training data with clear
>   instructions on how to replicate your Machine Learning Work)
>   of that Machine Learning Work need to be made publicly available
>   without any restrictions.
>
>
>
> I've added such a modified LICENSE (based on your Apache v2) to my own
> website that includes just these two clauses.
>
> https://peter.nz/LICENSE
>
> However - as I am not trained in law and licensing, I thought the ASF
> would be interested in this and perhaps could suggest taking this forward
> (in whatever form or shape you deem fit).
>
> thanks!
>
> Rock
>
>
>
> ---
>
> [image: SimSage - Intelligent Information Management]
>
> *Rock de Vocht*
> Chief Science Officer
> r...@simsage.co.uk
> +44 (0)7931 467981
>
> Intelligent Information Management
> www.simsage.ai
>
> NOTE: The information contained in this email and its attachments is
> confidential and may be the subject of legal privilege. It is intended only
> for the named addressees and may not be disclosed to anyone else without
> the prior consent of SimSage (UK) Ltd. If you are not the named addressee
> you must not use, disclose, distribute, copy, print or rely on the contents
> of this email and should destroy it immediately.
>
>

[ANNOUNCE] - Establishing ALC Taipei Chapter

[tison]

Hello all,

ComDev PMC is pleased to announce our next Apache Local Community [1]
ALC Chapter - ALC Taipei [2] and Chia-Ping Tsai as ALC Taipei Chapter
lead.

We have the following members in ALC Taipei:

Chia-Ping Tsai (chia7712) Apache Member
Wei-Chiu Chuang (weichiu) Apache Member
PoAn Yang (payang) Apache YuniKorn Committer
Zili Chen (tison) Apache Member
Kai-Hsun Chen (kaihsun) Apache Submarine PMC Member
Luke Chen (showuon) Apache Kafka PMC Member
Kuan Po Tseng (brandboat) Apache YuniKorn Committer
Brandon Lin (fatallin) Apache Submarine Committer
TingYao Huang (tingyao) Apache YuniKorn PMC Member
Chung-En Lee (chungen) Apache Ozone Committer
Wei Lee (weilee) Apache Airflow Committer
Kevin Su (pingsutw) Apache Submarine PMC Member
Wen-Chien Juan (wcjtw) Apache Submarine Committer
Evans Ye (evansye) Apache Member
Ted Liu (tedliu) Apache Member

Congratulations to the ALC Taipei Chapter and wishing them the best
luck for their future events.

[1] https://s.apache.org/alc
[2] https://cwiki.apache.org/confluence/display/COMDEV/ALC+Taipei


Best regards,
The Apache ComDev team,
community.apache.org