Re: [ALC] Request to establish ALC in Xi'an

[Eason Chen]

My big +1, Good Luck!

On Fri, Mar 17, 2023 at 10:14 AM wudi <676366...@qq.com.invalid> wrote:
>
> Thanks! CalvinKirs.
>
> I am very happy with the establishment of ALC in Xi’an!
>
> > 2023年3月17日 上午9:47，Jiafeng.Zhang  写道：
> >
> > This is very good news
> > As a member of Apache Doris PMC, if ALC Xi'an can be established, we will 
> > be able to promote local open source development in the name of ALC
> >
> >
> >
> > -
> > Best wishes！
> > Jiafeng.Zhang / 张家锋
> >
> > Yikun Jiang mailto:yi...@apache.org>> 于2023年3月16日周四 
> > 22:57写道：
> > Thanks! CalvinKirs.
> >
> > +1 from me.
> >
> > I am also exciting about ALC Xi'an setup.
> >
> > On Thursday, March 16, 2023, Willem Jiang  > > wrote:
> > my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
> > Please check out this link[1] for more information.
> > [1]https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
> >  
> > 
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs  > > wrote:
> > >
> > > Hi,
> > >
> > > I'm an ASF member and I know many Apache project developers from
> > > Xi'an. If ALC Xi'an can be established, then I think we can gather
> > > everyone together in the name of ALC to promote the local development
> > > of ASF.
> > >
> > > --
> > > Best wishes！
> > > CalvinKirs
> > >
> > > -
> > > 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: Back to basics: What we do @comdev

[Craig Russell]

> On Mar 16, 2023, at 10:07, sebb  wrote:
> 
> I think there need to be 3 mailing lists instead of just dev@
> 
> general community help
> GSOC
> tool development
> 
> I agree having a separate JIRA for GSOC would be a good idea.
> That would leave COMDEV for the website and various tools.

This is an excellent idea. GSOC is a great sub-project and has lots of interest 
and deserves its own space.

Craig
> 
> Sebb
> 
> On Thu, 16 Mar 2023 at 16:31, Maxim Solodovnik  wrote:
>> 
>> On Thu, 16 Mar 2023 at 23:29, Daniel Gruno  wrote:
>>> 
>>> On 3/16/23 11:26, Maxim Solodovnik wrote:
 
 almost all communications are already at mentors@community :)
 
>>> 
>>> And yet we have 185 messages on this list in just the past month. I do
>>> believe splitting GSOC out from the COMDEV Jira space will make most of
>>> that go away.
>> 
>> Separate GSoC project in JIRA is a great idea!
>> Thanks for it :)))
>> 
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>> 
>> 
>> 
>> --
>> Best regards,
>> Maxim
>> 
>> -
>> 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
> 

Craig L Russell
c...@apache.org


-
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 Xi'an

[wudi]

Thanks! CalvinKirs.

I am very happy with the establishment of ALC in Xi’an!

> 2023年3月17日 上午9:47，Jiafeng.Zhang  写道：
> 
> This is very good news
> As a member of Apache Doris PMC, if ALC Xi'an can be established, we will be 
> able to promote local open source development in the name of ALC
> 
> 
> 
> -
> Best wishes！
> Jiafeng.Zhang / 张家锋
> 
> Yikun Jiang mailto:yi...@apache.org>> 于2023年3月16日周四 
> 22:57写道：
> Thanks! CalvinKirs.
> 
> +1 from me.
> 
> I am also exciting about ALC Xi'an setup.
> 
> On Thursday, March 16, 2023, Willem Jiang  > wrote:
> my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
> Please check out this link[1] for more information.
> [1]https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
>  
> 
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs  > wrote:
> >
> > Hi,
> >
> > I'm an ASF member and I know many Apache project developers from
> > Xi'an. If ALC Xi'an can be established, then I think we can gather
> > everyone together in the name of ALC to promote the local development
> > of ASF.
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
> > -
> > 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 Xi'an

[Jiafeng.Zhang]

This is very good news
As a member of Apache Doris PMC, if ALC Xi'an can be established, we will
be able to promote local open source development in the name of ALC



-
Best wishes！
Jiafeng.Zhang / 张家锋

Yikun Jiang  于2023年3月16日周四 22:57写道：

> Thanks! CalvinKirs.
>
> +1 from me.
>
> I am also exciting about ALC Xi'an setup.
>
> On Thursday, March 16, 2023, Willem Jiang  wrote:
>
>> my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
>> Please check out this link[1] for more information.
>> [1]
>> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
>>
>> Willem Jiang
>>
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>> On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs  wrote:
>> >
>> > Hi,
>> >
>> > I'm an ASF member and I know many Apache project developers from
>> > Xi'an. If ALC Xi'an can be established, then I think we can gather
>> > everyone together in the name of ALC to promote the local development
>> > of ASF.
>> >
>> > --
>> > Best wishes！
>> > CalvinKirs
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> > For additional commands, e-mail: dev-h...@community.apache.org
>> >
>>
>

-- 
张家峰

Website TODO list

[rbowen]

Yes, I know I've been talking a lot today.

Here's what I see as a first cut at a ToDo list for the website:

https://cwiki.apache.org/confluence/display/COMDEV/Website

I appreciate the folks who have, so far, stepped up to say they'll be
part of this effort. I would ask that if you contribute to the above
Wiki page, you are saying that you'll do stuff, not that "someone
should."

Our current website is a reflection of our "someone should (but not
me)" mindset of the past few years, and I'd like to focus on what we
*will* do, not what we think someone might or could some day.

To be clear, that's largely on me. I wrote the
https://community.apache.org/about/ page as a "stuff we could do, if
people showed up to do it", back in 2017. That was a mistake. I'd like
to take it back, and have the website be only things that we *actually
do*, whereas this mailing list is where we talk about what we could,
possibly, do.

--Rich

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

Re: Back to basics: What we do @comdev

[sebb]

I think there need to be 3 mailing lists instead of just dev@

general community help
GSOC
tool development

I agree having a separate JIRA for GSOC would be a good idea.
That would leave COMDEV for the website and various tools.

Sebb

On Thu, 16 Mar 2023 at 16:31, Maxim Solodovnik  wrote:
>
> On Thu, 16 Mar 2023 at 23:29, Daniel Gruno  wrote:
> >
> > On 3/16/23 11:26, Maxim Solodovnik wrote:
> > >
> > > almost all communications are already at mentors@community :)
> > >
> >
> > And yet we have 185 messages on this list in just the past month. I do
> > believe splitting GSOC out from the COMDEV Jira space will make most of
> > that go away.
>
> Separate GSoC project in JIRA is a great idea!
> Thanks for it :)))
>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
>
> --
> Best regards,
> Maxim
>
> -
> 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: GSoC messaging?

[rbowen]

On Thu, 2023-03-16 at 23:24 +0700, Maxim Solodovnik wrote:
> Hello Rich,
> 
> we are using mentors@community.a.o ML for communications
> 
> I'll try to keep https://community.apache.org/gsoc.html page in
> up-to-date state :)
> 
> I'll move all GSoC related pages (there should be 3-5 of them) to
> subfolder (will try to do it before Monday)
> 
> And will update this thread :)

Thank you. That's awesome.

There's a lot of ambiguity, on the website, between GSoC and Mentoring,
and getting the GSoC stuff into a subdir would greatly help with that.

--Rich

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

Re: Back to basics: What we do @comdev

[Maxim Solodovnik]

On Thu, 16 Mar 2023 at 23:29, Daniel Gruno  wrote:
>
> On 3/16/23 11:26, Maxim Solodovnik wrote:
> >
> > almost all communications are already at mentors@community :)
> >
>
> And yet we have 185 messages on this list in just the past month. I do
> believe splitting GSOC out from the COMDEV Jira space will make most of
> that go away.

Separate GSoC project in JIRA is a great idea!
Thanks for it :)))

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


-- 
Best regards,
Maxim

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

Re: Back to basics: What we do @comdev

[Andrew Musselman]

>
> > projects.a.o
> > reporter.a.o
> > helpwanted (I think this is EOL, realistically)
>

I am interested in helping with reporter.a.o and possibly more.

On Thu, Mar 16, 2023 at 9:29 AM Daniel Gruno  wrote:

> On 3/16/23 11:26, Maxim Solodovnik wrote:
> >
> > almost all communications are already at mentors@community :)
> >
>
> And yet we have 185 messages on this list in just the past month. I do
> believe splitting GSOC out from the COMDEV Jira space will make most of
> that go away.
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Back to basics: What we do @comdev

[Daniel Gruno]

On 3/16/23 11:26, Maxim Solodovnik wrote:


almost all communications are already at mentors@community :)



And yet we have 185 messages on this list in just the past month. I do 
believe splitting GSOC out from the COMDEV Jira space will make most of 
that go away.




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

Re: Back to basics: What we do @comdev

[Maxim Solodovnik]

On Thu, 16 Mar 2023 at 22:50, Daniel Gruno  wrote:
>
> On 3/16/23 10:40, rbo...@rcbowen.com wrote:
> > Hi, folks,
> >
> > I have tried to write this email several times, and keep getting
> > overwhelmed. Trying again.
> >
> > Comdev has no focus. Our website is a mess. We have no clear idea of
> > what we do. I would like to get back to basics, and figure out what it
> > actually is that we do here, and get rid of the stuff that we don't.
>
> I completely agree here, this is a perennial request. Comdev is woefully
> oversubscribed to unmaintained projects and initiatives and needs to be
> reigned in to a manageable size.
>
> I would (again, I've mentioned it over the years) really love for us to
> establish some sort of BoM here: Which projects do we currently have,
> which do we have people actively or willing to actively maintain, and
> which projects should we scrap. I believe getting this clarified would
> be a great help.
>
> As a sort of aside, I'd also like for GSOC to be moved to a separate
> list from dev@community (gsoc@community? maybe some generic term for
> these events?)

almost all communications are already at mentors@community :)

> as well as moved out of the COMDEV Jira space. It is
> quite frankly littering the mailing list with messages that do not
> pertain to 90% of the subscribers.
>
> As with Rich, I am also very much willing to help with this.
>
> >
> > For example: Looking at the website, we claim we have a mentoring
> > program. This is not true, and I'd like to cull that entire part of the
> > site. But I don't want to step on people who might actually want to do
> > that work.
> >
> > And that's just one example.
> >
> > A while back (2017) I rather over-optimistically wrote
> > https://community.apache.org/about/ which was a list of things that I
> > hoped that we might do some day. That was a mistake, because it makes
> > promises that nobody is following up on.
> >
> > I want to get back to our mandate:
> >
> > Provide a wide array of information, FAQs, and help to newcomers and
> > existing committers, and maintains a number of helpful tools.
> >
> > We should be a repository for useful information and best practice for
> > people at all levels of our community: newcomers; contributors;
> > committers; pmcs.
> >
> > The tools that we presumably maintain include:
> > projects.a.o
> > reporter.a.o
> > helpwanted (I think this is EOL, realistically)
> >
> > We facilitate Apache Local Communities (which does not appear to be
> > references on the website?)
> >
> > And we also facilitate GSoC
> >
> > I would like to refocus our website, and our efforts, around those
> > things, and drop everything else from our website, until and unless
> > someone actually steps up to do them.
> >
> > And, yes, I'm volunteering to do this work, but want to be sure I'm not
> > taking too much authority in doing so.
> >
> >
> >
> > -
> > 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
>


-- 
Best regards,
Maxim

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

Re: GSoC messaging?

[Maxim Solodovnik]

Hello Rich,

we are using mentors@community.a.o ML for communications

I'll try to keep https://community.apache.org/gsoc.html page in
up-to-date state :)

I'll move all GSoC related pages (there should be 3-5 of them) to
subfolder (will try to do it before Monday)

And will update this thread :)

On Thu, 16 Mar 2023 at 23:11,  wrote:
>
> Ok, I see that https://community.apache.org/gsoc has been updated with
> some info.
>
> Is there a chance we could move gsoc content into a subdirectory,
> rather than having a half-dozen docs in the top level directory?
>
> --Rich
>
> On Thu, 2023-03-16 at 12:04 -0400, rbo...@rcbowen.com wrote:
> >  Do we have any kind of messaging around GSoC this year?
> >
> > I see this in the February Comdev report:
> >
> > ### GSoC
> > We have applied for the GSoC 2023 program and are awaiting
> > the final update from the GSoC team on February 21, 2023.
> > Meanwhile, we will be working on collecting project ideas from
> > various
> > PMCs.
> >
> > And obviously I see the flood if Jira traffic on this list, but do we
> > have any public reporting anywhere about what projects are
> > participating, and what's being worked on?
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>


-- 
Best regards,
Maxim

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

Re: GSoC messaging?

[rbowen]

Ok, I see that https://community.apache.org/gsoc has been updated with
some info.

Is there a chance we could move gsoc content into a subdirectory,
rather than having a half-dozen docs in the top level directory?

--Rich

On Thu, 2023-03-16 at 12:04 -0400, rbo...@rcbowen.com wrote:
>  Do we have any kind of messaging around GSoC this year?
> 
> I see this in the February Comdev report:
> 
> ### GSoC
> We have applied for the GSoC 2023 program and are awaiting
> the final update from the GSoC team on February 21, 2023.
> Meanwhile, we will be working on collecting project ideas from
> various
> PMCs.
> 
> And obviously I see the flood if Jira traffic on this list, but do we
> have any public reporting anywhere about what projects are
> participating, and what's being worked on?
> 
> 


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

Re: Back to basics: What we do @comdev

[Drew Foulks]

On 2023/03/16 15:40:12 rbo...@rcbowen.com wrote:
> Hi, folks,
> 
> I have tried to write this email several times, and keep getting
> overwhelmed. Trying again.
> 
> Comdev has no focus. Our website is a mess. We have no clear idea of
> what we do. I would like to get back to basics, and figure out what it
> actually is that we do here, and get rid of the stuff that we don't.
> 
> For example: Looking at the website, we claim we have a mentoring
> program. This is not true, and I'd like to cull that entire part of the
> site. But I don't want to step on people who might actually want to do
> that work.
> 
> And that's just one example.
> 
> A while back (2017) I rather over-optimistically wrote
> https://community.apache.org/about/ which was a list of things that I
> hoped that we might do some day. That was a mistake, because it makes
> promises that nobody is following up on.
> 
> I want to get back to our mandate:
> 
> Provide a wide array of information, FAQs, and help to newcomers and
> existing committers, and maintains a number of helpful tools.

I absolutely agree, paring back, simplifying, and re-organizing the overwhelming
amount of information available, would make it much easier to get started, and 
stay
involved.
> 
> We should be a repository for useful information and best practice for
> people at all levels of our community: newcomers; contributors;
> committers; pmcs.
> 
> The tools that we presumably maintain include:
> projects.a.o
> reporter.a.o
> helpwanted (I think this is EOL, realistically)
> 
> We facilitate Apache Local Communities (which does not appear to be
> references on the website?)
> 
> And we also facilitate GSoC
> 
> I would like to refocus our website, and our efforts, around those
> things, and drop everything else from our website, until and unless
> someone actually steps up to do them.
> 
> And, yes, I'm volunteering to do this work, but want to be sure I'm not
> taking too much authority in doing so.
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 
I'd be happy to help with this also.

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

[jira] [Updated] (COMDEV-521) [GSoC][Beam] Build out Beam Machine Learning Use Cases

[Pablo Estrada (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pablo Estrada updated COMDEV-521:
-
Description: 
Today, you can do all sorts of Machine Learning using Apache Beam 
([https://beam.apache.org/documentation/ml/overview/]).
 
Many of our users, however, have a hard time getting started with ML and 
understanding how Beam can be applied to their day to day work. The goal of 
this project is to build out a series of Beam pipelines as Jupyter Notebooks 
demonstrating real world ML use cases, from NLP to image recognition to using 
large language models. As you go, there may be bugs or friction points as well 
which will provide opportunities to contribute back to Beam's core ML libraries.

 

Mentor for this will be Danny McCormick

  was:
Today, you can do all sorts of Machine Learning using Apache Beam 
([https://beam.apache.org/documentation/ml/overview/]).
 
Many of our users, however, have a hard time getting started with ML and 
understanding how Beam can be applied to their day to day work. The goal of 
this project is to build out a series of Beam pipelines as Jupyter Notebooks 
demonstrating real world ML use cases, from NLP to image recognition to using 
large language models. As you go, there may be bugs or friction points as well 
which will provide opportunities to contribute back to Beam's core ML libraries
 
 


> [GSoC][Beam] Build out Beam Machine Learning Use Cases
> --
>
> Key: COMDEV-521
> URL: https://issues.apache.org/jira/browse/COMDEV-521
> Project: Community Development
>  Issue Type: Task
>  Components: GSoC/Mentoring ideas
>Reporter: Pablo Estrada
>Priority: Major
>  Labels: Beam, full-time, gsoc, gsoc2023
>
> Today, you can do all sorts of Machine Learning using Apache Beam 
> ([https://beam.apache.org/documentation/ml/overview/]).
>  
> Many of our users, however, have a hard time getting started with ML and 
> understanding how Beam can be applied to their day to day work. The goal of 
> this project is to build out a series of Beam pipelines as Jupyter Notebooks 
> demonstrating real world ML use cases, from NLP to image recognition to using 
> large language models. As you go, there may be bugs or friction points as 
> well which will provide opportunities to contribute back to Beam's core ML 
> libraries.
>  
> Mentor for this will be Danny McCormick



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (COMDEV-521) [GSoC][Beam] Build out Beam Machine Learning Use Cases

[Pablo Estrada (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pablo Estrada updated COMDEV-521:
-
difficulty-level: Medium  (was: Easy)

> [GSoC][Beam] Build out Beam Machine Learning Use Cases
> --
>
> Key: COMDEV-521
> URL: https://issues.apache.org/jira/browse/COMDEV-521
> Project: Community Development
>  Issue Type: Task
>  Components: GSoC/Mentoring ideas
>Reporter: Pablo Estrada
>Priority: Major
>  Labels: Beam, full-time, gsoc, gsoc2023
>
> Today, you can do all sorts of Machine Learning using Apache Beam 
> ([https://beam.apache.org/documentation/ml/overview/]).
>  
> Many of our users, however, have a hard time getting started with ML and 
> understanding how Beam can be applied to their day to day work. The goal of 
> this project is to build out a series of Beam pipelines as Jupyter Notebooks 
> demonstrating real world ML use cases, from NLP to image recognition to using 
> large language models. As you go, there may be bugs or friction points as 
> well which will provide opportunities to contribute back to Beam's core ML 
> libraries.
>  
> Mentor for this will be Danny McCormick



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (COMDEV-521) [GSoC][Beam] Build out Beam Machine Learning Use Cases

[Pablo Estrada (Jira)]

Pablo Estrada created COMDEV-521:


 Summary: [GSoC][Beam] Build out Beam Machine Learning Use Cases
 Key: COMDEV-521
 URL: https://issues.apache.org/jira/browse/COMDEV-521
 Project: Community Development
  Issue Type: Task
  Components: GSoC/Mentoring ideas
Reporter: Pablo Estrada


Beam library developers and Beam users would appreciate this : )

 

This project involves prototyping a few different solutions, so it will be 
large.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

GSoC messaging?

[rbowen]

 Do we have any kind of messaging around GSoC this year?

I see this in the February Comdev report:

### GSoC
We have applied for the GSoC 2023 program and are awaiting
the final update from the GSoC team on February 21, 2023.
Meanwhile, we will be working on collecting project ideas from various
PMCs.

And obviously I see the flood if Jira traffic on this list, but do we
have any public reporting anywhere about what projects are
participating, and what's being worked on?



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

[jira] [Updated] (COMDEV-521) [GSoC][Beam] Build out Beam Machine Learning Use Cases

[Pablo Estrada (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pablo Estrada updated COMDEV-521:
-
Description: 
Today, you can do all sorts of Machine Learning using Apache Beam 
([https://beam.apache.org/documentation/ml/overview/]).
 
Many of our users, however, have a hard time getting started with ML and 
understanding how Beam can be applied to their day to day work. The goal of 
this project is to build out a series of Beam pipelines as Jupyter Notebooks 
demonstrating real world ML use cases, from NLP to image recognition to using 
large language models. As you go, there may be bugs or friction points as well 
which will provide opportunities to contribute back to Beam's core ML libraries
 
 

  was:
Beam library developers and Beam users would appreciate this : )

 

This project involves prototyping a few different solutions, so it will be 
large.


> [GSoC][Beam] Build out Beam Machine Learning Use Cases
> --
>
> Key: COMDEV-521
> URL: https://issues.apache.org/jira/browse/COMDEV-521
> Project: Community Development
>  Issue Type: Task
>  Components: GSoC/Mentoring ideas
>Reporter: Pablo Estrada
>Priority: Major
>  Labels: Beam, full-time, gsoc, gsoc2023
>
> Today, you can do all sorts of Machine Learning using Apache Beam 
> ([https://beam.apache.org/documentation/ml/overview/]).
>  
> Many of our users, however, have a hard time getting started with ML and 
> understanding how Beam can be applied to their day to day work. The goal of 
> this project is to build out a series of Beam pipelines as Jupyter Notebooks 
> demonstrating real world ML use cases, from NLP to image recognition to using 
> large language models. As you go, there may be bugs or friction points as 
> well which will provide opportunities to contribute back to Beam's core ML 
> libraries
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Back to basics: What we do @comdev

[Daniel Gruno]

On 3/16/23 10:40, rbo...@rcbowen.com wrote:

Hi, folks,

I have tried to write this email several times, and keep getting
overwhelmed. Trying again.

Comdev has no focus. Our website is a mess. We have no clear idea of
what we do. I would like to get back to basics, and figure out what it
actually is that we do here, and get rid of the stuff that we don't.


I completely agree here, this is a perennial request. Comdev is woefully 
oversubscribed to unmaintained projects and initiatives and needs to be 
reigned in to a manageable size.


I would (again, I've mentioned it over the years) really love for us to 
establish some sort of BoM here: Which projects do we currently have, 
which do we have people actively or willing to actively maintain, and 
which projects should we scrap. I believe getting this clarified would 
be a great help.


As a sort of aside, I'd also like for GSOC to be moved to a separate 
list from dev@community (gsoc@community? maybe some generic term for 
these events?) as well as moved out of the COMDEV Jira space. It is 
quite frankly littering the mailing list with messages that do not 
pertain to 90% of the subscribers.


As with Rich, I am also very much willing to help with this.



For example: Looking at the website, we claim we have a mentoring
program. This is not true, and I'd like to cull that entire part of the
site. But I don't want to step on people who might actually want to do
that work.

And that's just one example.

A while back (2017) I rather over-optimistically wrote
https://community.apache.org/about/ which was a list of things that I
hoped that we might do some day. That was a mistake, because it makes
promises that nobody is following up on.

I want to get back to our mandate:

Provide a wide array of information, FAQs, and help to newcomers and
existing committers, and maintains a number of helpful tools.

We should be a repository for useful information and best practice for
people at all levels of our community: newcomers; contributors;
committers; pmcs.

The tools that we presumably maintain include:
projects.a.o
reporter.a.o
helpwanted (I think this is EOL, realistically)

We facilitate Apache Local Communities (which does not appear to be
references on the website?)

And we also facilitate GSoC

I would like to refocus our website, and our efforts, around those
things, and drop everything else from our website, until and unless
someone actually steps up to do them.

And, yes, I'm volunteering to do this work, but want to be sure I'm not
taking too much authority in doing so.



-
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

Back to basics: What we do @comdev

[rbowen]

Hi, folks,

I have tried to write this email several times, and keep getting
overwhelmed. Trying again.

Comdev has no focus. Our website is a mess. We have no clear idea of
what we do. I would like to get back to basics, and figure out what it
actually is that we do here, and get rid of the stuff that we don't.

For example: Looking at the website, we claim we have a mentoring
program. This is not true, and I'd like to cull that entire part of the
site. But I don't want to step on people who might actually want to do
that work.

And that's just one example.

A while back (2017) I rather over-optimistically wrote
https://community.apache.org/about/ which was a list of things that I
hoped that we might do some day. That was a mistake, because it makes
promises that nobody is following up on.

I want to get back to our mandate:

Provide a wide array of information, FAQs, and help to newcomers and
existing committers, and maintains a number of helpful tools.

We should be a repository for useful information and best practice for
people at all levels of our community: newcomers; contributors;
committers; pmcs.

The tools that we presumably maintain include:
projects.a.o
reporter.a.o
helpwanted (I think this is EOL, realistically)

We facilitate Apache Local Communities (which does not appear to be
references on the website?)

And we also facilitate GSoC

I would like to refocus our website, and our efforts, around those
things, and drop everything else from our website, until and unless
someone actually steps up to do them.

And, yes, I'm volunteering to do this work, but want to be sure I'm not
taking too much authority in doing so.



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

[jira] [Commented] (COMDEV-481) Projects tool "Projects by number of committers" lacks many projects

[Daniel Gruno (Jira)]

[ 
https://issues.apache.org/jira/browse/COMDEV-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701221#comment-17701221
 ] 

Daniel Gruno commented on COMDEV-481:
-

I've applied the patch now.

> Projects tool "Projects by number of committers" lacks many projects
> 
>
> Key: COMDEV-481
> URL: https://issues.apache.org/jira/browse/COMDEV-481
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Tool
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: comdev-projects_js.patch
>
>
> This page ([https://projects.apache.org/projects.html?number)] only lists 179 
> projects, and turns out those are only the ones that happen to have the same 
> unixgroup as project-ID. E.g. 'lucene-core' with 97 committers is not listed 
> since its unixgroup is 'lucene'.
> The fix is in the attached patch, applying the same projectId-to-unixgroup 
> function as is used elsewhere in the same script. This brings the number of 
> projects listed up to 377.
> I agree with some of the comments in related issue COMDEV-170, that some 
> projects may have committership != unixgroup, but that should be solved 
> separately.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

PR: Remove helpwanted references

[rbowen]

I've opened a PR - https://github.com/apache/comdev-site/pull/87 - to
drop references to the helpwanted tool, since it hasn't really been the
success that we imagined. There's no content in it, and so it's just
frustrating.

Please let me know if there are any objections to merging that. Thanks.

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

[GitHub] [comdev-site] rbowen opened a new pull request, #87: Remove references to helpwanted

[via GitHub]

rbowen opened a new pull request, #87:
URL: https://github.com/apache/comdev-site/pull/87

   The helpwanted site hasn't had useful content on it in years. It was a great 
idea at the time, but it only works if people use it. Removing from our site 
until such time as there's actually content there, if ever.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
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 Xi'an

[Yikun Jiang]

Thanks! CalvinKirs.

+1 from me.

I am also exciting about ALC Xi'an setup.

On Thursday, March 16, 2023, Willem Jiang  wrote:

> my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
> Please check out this link[1] for more information.
> [1]https://cwiki.apache.org/confluence/display/COMDEV/
> Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-
> HowtoapplytosetupALCChapter
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs  wrote:
> >
> > Hi,
> >
> > I'm an ASF member and I know many Apache project developers from
> > Xi'an. If ALC Xi'an can be established, then I think we can gather
> > everyone together in the name of ALC to promote the local development
> > of ASF.
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
> > -
> > 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 Xi'an

[Willem Jiang]

my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
Please check out this link[1] for more information.
[1]https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs  wrote:
>
> Hi,
>
> I'm an ASF member and I know many Apache project developers from
> Xi'an. If ALC Xi'an can be established, then I think we can gather
> everyone together in the name of ALC to promote the local development
> of ASF.
>
> --
> Best wishes！
> CalvinKirs
>
> -
> 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

[ALC] Request to establish ALC in Xi'an

[Calvin Kirs]

Hi,

I'm an ASF member and I know many Apache project developers from
Xi'an. If ALC Xi'an can be established, then I think we can gather
everyone together in the name of ALC to promote the local development
of ASF.

-- 
Best wishes！
CalvinKirs

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

[jira] [Updated] (COMDEV-520) [GSOC][SkyWalking] Add Terraform provider for Apache SkyWalking

[Zhenxu Ke (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhenxu Ke updated COMDEV-520:
-
Summary: [GSOC][SkyWalking] Add Terraform provider for Apache SkyWalking  
(was: [SkyWalking] Add Terraform provider for Apache SkyWalking)

> [GSOC][SkyWalking] Add Terraform provider for Apache SkyWalking
> ---
>
> Key: COMDEV-520
> URL: https://issues.apache.org/jira/browse/COMDEV-520
> Project: Community Development
>  Issue Type: Task
>  Components: GSoC/Mentoring ideas
>Reporter: Zhenxu Ke
>Priority: Major
>  Labels: SkyWalking, full-time, gsoc2023, mentor
>
> Now the deployment methods for SkyWalking are limited, we only have Helm 
> Chart for users to deploy in Kubernetes, other users that are not using 
> Kubernetes have to do all the house keeping stuffs to set up SkyWalking on, 
> for example, VM.
>  
> This issue aims to add a Terraform provider, so that users can conveniently  
> spin up a cluster for demonstration or testing, we should evolve the provider 
> and allow users to customize as their need and finally users can use this in 
> their production environment.
>  
> In this task, we will mainly focus on the support for AWS. In the Terraform 
> provider, users need to provide their access key / secret key, and the 
> provider does the rest stuffs: create VMs, create database/OpenSearch or RDS, 
> download SkyWalking tars, configure the SkyWalking, and start the SkyWalking 
> components (OAP/UI), create public IPs/domain name, etc.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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