[jira] [Closed] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney closed COMDEV-544.
---
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at
> [https://community.apache.org/gsoc/guide-to-being-a-mentor.html].
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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] [Resolved] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved COMDEV-544.
-
Resolution: Fixed
Thanks [~rbowen] for merging.
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at
> [https://community.apache.org/gsoc/guide-to-being-a-mentor.html].
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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] [Commented] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838694#comment-17838694
]
Lewis John McGibbney commented on COMDEV-544:
-
[~sebb] thank you, I was on a mob ile device and actually missed the top
navigation. Thank you
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at
> [https://community.apache.org/gsoc/guide-to-being-a-mentor.html].
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated COMDEV-544:
Description:
h1. Purpose
Improve comdev website navigation to Google Summer of Code (GSoC) mentor
resources.
h1. Context
Having been ‘away’ for a few years, this year I decided to make an attempt to
re-engage with the GSoC program.
I quickly realized that I was totally out of touch having absolutely no idea
where the mentor community conversations were happening (they happen on
ment...@community.apache.org) and being hopelessly unable to locate GSoC
mentoring documentation via the comdev website.
Thankfully [~sanyam] [pointed me at the
documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
and I was able to get back up to speed. Thank you Sanyam :)
h1. Challenges
Looking at [https://community.apache.org/gsoc/], as of writing, although loads
of content exists for students (which is great) no navigation exists to mentor
resources.
In my case, this meant that I couldn’t find and entirely missed the excellent
content available at
[https://community.apache.org/gsoc/guide-to-being-a-mentor.html].
h1. Proposal
I think that a “{*}Mentors: read this{*}” Section should be added to
[https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
content from above.
was:
h1. Purpose
Improve comdev website navigation to Google Summer of Code (GSoC) mentor
resources.
h1. Context
Having been ‘away’ for a few years, this year I decided to make an attempt to
re-engage with the GSoC program.
I quickly realized that I was totally out of touch having absolutely no idea
where the mentor community conversations were happening (they happen on
ment...@community.apache.org) and being hopelessly unable to locate GSoC
mentoring documentation via the comdev website.
Thankfully [~sanyam] [pointed me at the
documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
and I was able to get back up to speed. Thank you Sanyam :)
h1. Challenges
Looking at [https://community.apache.org/gsoc/], as of writing, although loads
of content exists for students (which is great) no navigation exists to mentor
resources.
In my case, this meant that I couldn’t find and entirely missed the excellent
content available at [https://community.apache.org/mentoring]/.
h1. Proposal
I think that a “{*}Mentors: read this{*}” Section should be added to
[https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
content from above.
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at
> [https://community.apache.org/gsoc/guide-to-being-a-mentor.html].
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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] [Commented] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838692#comment-17838692
]
Lewis John McGibbney commented on COMDEV-544:
-
Thank you both.
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at [https://community.apache.org/mentoring]/.
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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] [Commented] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838688#comment-17838688
]
Sebb commented on COMDEV-544:
-
Note that there is a Mentor link under GSoC menu item on most pages
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at [https://community.apache.org/mentoring]/.
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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] [Commented] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources
[
https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838680#comment-17838680
]
Rich Bowen commented on COMDEV-544:
---
FYI, that page is at
[https://github.com/apache/comdev-site/blob/main/source/gsoc/_index.md] if you
want to add such a section.
> Improve comdev website navigation to GSoC mentor resources
> --
>
> Key: COMDEV-544
> URL: https://issues.apache.org/jira/browse/COMDEV-544
> Project: Community Development
> Issue Type: Task
> Components: Website
>Reporter: Lewis John McGibbney
>Priority: Minor
>
> h1. Purpose
> Improve comdev website navigation to Google Summer of Code (GSoC) mentor
> resources.
> h1. Context
> Having been ‘away’ for a few years, this year I decided to make an attempt to
> re-engage with the GSoC program.
> I quickly realized that I was totally out of touch having absolutely no idea
> where the mentor community conversations were happening (they happen on
> ment...@community.apache.org) and being hopelessly unable to locate GSoC
> mentoring documentation via the comdev website.
> Thankfully [~sanyam] [pointed me at the
> documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
> and I was able to get back up to speed. Thank you Sanyam :)
> h1. Challenges
> Looking at [https://community.apache.org/gsoc/], as of writing, although
> loads of content exists for students (which is great) no navigation exists to
> mentor resources.
> In my case, this meant that I couldn’t find and entirely missed the excellent
> content available at [https://community.apache.org/mentoring]/.
> h1. Proposal
> I think that a “{*}Mentors: read this{*}” Section should be added to
> [https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
> content from above.
--
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-544) Improve comdev website navigation to GSoC mentor resources
Lewis John McGibbney created COMDEV-544:
---
Summary: Improve comdev website navigation to GSoC mentor resources
Key: COMDEV-544
URL: https://issues.apache.org/jira/browse/COMDEV-544
Project: Community Development
Issue Type: Task
Components: Website
Reporter: Lewis John McGibbney
h1. Purpose
Improve comdev website navigation to Google Summer of Code (GSoC) mentor
resources.
h1. Context
Having been ‘away’ for a few years, this year I decided to make an attempt to
re-engage with the GSoC program.
I quickly realized that I was totally out of touch having absolutely no idea
where the mentor community conversations were happening (they happen on
ment...@community.apache.org) and being hopelessly unable to locate GSoC
mentoring documentation via the comdev website.
Thankfully [~sanyam] [pointed me at the
documentation|[https://lists.apache.org/thread/dqmrwzjogl3sdb2v8s36v8mxf5o1yqsj]]
and I was able to get back up to speed. Thank you Sanyam :)
h1. Challenges
Looking at [https://community.apache.org/gsoc/], as of writing, although loads
of content exists for students (which is great) no navigation exists to mentor
resources.
In my case, this meant that I couldn’t find and entirely missed the excellent
content available at [https://community.apache.org/mentoring]/.
h1. Proposal
I think that a “{*}Mentors: read this{*}” Section should be added to
[https://community.apache.org/gsoc/] which simply hyperlinks to the relevant
content from above.
--
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: Where is GSoC communications taking place?
Hi Sure feel free to update Let me know, if you need any help, happy to assist let me also take a look on the comdev-gsoc site, if we have stale data to update with latest gsoc updates Thanks, Sanyam Goel On Thu, Apr 18, 2024 at 5:54 PM Lewis John Mcgibbney < lewis.mcgibb...@gmail.com> wrote: > Hi Sanyam, > Thank you so much. > I’m going to suggest some edits to the comdev website to improve navigation > to the hyperlinks you provided. They are not linked to from the GSoC page > so we can fix that now. > Thanks for all your efforts as Org Admin for GSoC this year. > lewismc > > On Thu, Apr 18, 2024 at 04:44 Sanyam Goel wrote: > > > Hi Lewis > > all the communication is happening on ment...@community.apache.org list > > > > Please subscribe to it, > > this list is specific for GSoC mentors only and all the communication > > there should not be available outside that list > > Also I advice you to go through the following links as below for more > steps > > https://community.apache.org/mentoring/ > > https://community.apache.org/gsoc/guide-to-being-a-mentor.html > > > > > https://community.apache.org/gsoc/guide-to-being-a-mentor.html#staying-in-touch > > > > FYI: we haven't received any scoring on the proposals received for the > > Nutch project, I advise you to start a new communication thread on the > > mentors list, as the deadline is already passed and we can continue from > > there. > > you can find all the details/announcements in the mentor list > > > > > > Thanks, > > Sanyam Goel > > > > On Thu, Apr 18, 2024 at 4:07 AM lewis john mcgibbney > > > wrote: > > > >> Hi dev@, > >> Can someone please point me to the GSoC happenings? I’ve not heard > >> anything > >> since been approved on the Nutch mailing list > >> https://lists.apache.org/thread/tk8x6sf2mt1lt0v10j30djqjk6vwpgb2 > >> Thanks in advance. > >> lewismc > >> > >> > >> -- > >> http://home.apache.org/~lewismc/ > >> http://people.apache.org/keys/committer/lewismc > >> > > >
Re: Where is GSoC communications taking place?
Hi Sanyam, Thank you so much. I’m going to suggest some edits to the comdev website to improve navigation to the hyperlinks you provided. They are not linked to from the GSoC page so we can fix that now. Thanks for all your efforts as Org Admin for GSoC this year. lewismc On Thu, Apr 18, 2024 at 04:44 Sanyam Goel wrote: > Hi Lewis > all the communication is happening on ment...@community.apache.org list > > Please subscribe to it, > this list is specific for GSoC mentors only and all the communication > there should not be available outside that list > Also I advice you to go through the following links as below for more steps > https://community.apache.org/mentoring/ > https://community.apache.org/gsoc/guide-to-being-a-mentor.html > > https://community.apache.org/gsoc/guide-to-being-a-mentor.html#staying-in-touch > > FYI: we haven't received any scoring on the proposals received for the > Nutch project, I advise you to start a new communication thread on the > mentors list, as the deadline is already passed and we can continue from > there. > you can find all the details/announcements in the mentor list > > > Thanks, > Sanyam Goel > > On Thu, Apr 18, 2024 at 4:07 AM lewis john mcgibbney > wrote: > >> Hi dev@, >> Can someone please point me to the GSoC happenings? I’ve not heard >> anything >> since been approved on the Nutch mailing list >> https://lists.apache.org/thread/tk8x6sf2mt1lt0v10j30djqjk6vwpgb2 >> Thanks in advance. >> lewismc >> >> >> -- >> http://home.apache.org/~lewismc/ >> http://people.apache.org/keys/committer/lewismc >> >
Re: Where is GSoC communications taking place?
Hi Lewis all the communication is happening on ment...@community.apache.org list Please subscribe to it, this list is specific for GSoC mentors only and all the communication there should not be available outside that list Also I advice you to go through the following links as below for more steps https://community.apache.org/mentoring/ https://community.apache.org/gsoc/guide-to-being-a-mentor.html https://community.apache.org/gsoc/guide-to-being-a-mentor.html#staying-in-touch FYI: we haven't received any scoring on the proposals received for the Nutch project, I advise you to start a new communication thread on the mentors list, as the deadline is already passed and we can continue from there. you can find all the details/announcements in the mentor list Thanks, Sanyam Goel On Thu, Apr 18, 2024 at 4:07 AM lewis john mcgibbney wrote: > Hi dev@, > Can someone please point me to the GSoC happenings? I’ve not heard anything > since been approved on the Nutch mailing list > https://lists.apache.org/thread/tk8x6sf2mt1lt0v10j30djqjk6vwpgb2 > Thanks in advance. > lewismc > > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc >
Where is GSoC communications taking place?
Hi dev@, Can someone please point me to the GSoC happenings? I’ve not heard anything since been approved on the Nutch mailing list https://lists.apache.org/thread/tk8x6sf2mt1lt0v10j30djqjk6vwpgb2 Thanks in advance. lewismc -- http://home.apache.org/~lewismc/ http://people.apache.org/keys/committer/lewismc
Re: GSOC proposal guidelines or templates
Hi Miko, Welcome to the community! Here are some hints about the application template https://community.apache.org/gsoc/#application-template and other related resources. Best wishes for your proposal. On Sun, 31 Mar 2024 at 20:17, Miko Aro wrote: > > Hello Danny, > > I would like to know if there are any other proposal guidelines or > templates for GSOC 2024 program under the Apache Software Foundation (ASF) > one will have to conform to aside from the accepted template on the page on > here <https://community.apache.org/gsoc/>. > > Recently found out about the GSOC 2024 program and I see it as an > opportunity to contribute to open source software and fully join the ASF as > a contributor. Of particular interest to me is the Apache Beam and the > three project ideas such as adding BigTable and Spanner IO integrations to > ManagedIO, implementing use cases for data processing, data and machine > learning transformations as well as adding more features and transforms to > the Yaml SDK. > > I have conducted an initial research to dig into the ideas list for Apache > Beam and I have found some ways on how to tackle the problems. I will > submit a proposal by tomorrow April 1, 2024. > > My names are Miko Aro and I live in Austin, Texas. > > Thanks, > > Miko > > Miko Aro -- Best Regards, Priya - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
GSOC proposal guidelines or templates
Hello Danny, I would like to know if there are any other proposal guidelines or templates for GSOC 2024 program under the Apache Software Foundation (ASF) one will have to conform to aside from the accepted template on the page on here <https://community.apache.org/gsoc/>. Recently found out about the GSOC 2024 program and I see it as an opportunity to contribute to open source software and fully join the ASF as a contributor. Of particular interest to me is the Apache Beam and the three project ideas such as adding BigTable and Spanner IO integrations to ManagedIO, implementing use cases for data processing, data and machine learning transformations as well as adding more features and transforms to the Yaml SDK. I have conducted an initial research to dig into the ideas list for Apache Beam and I have found some ways on how to tackle the problems. I will submit a proposal by tomorrow April 1, 2024. My names are Miko Aro and I live in Austin, Texas. Thanks, Miko Miko Aro
[GSOC 2024] New Idea: A Minimal Superset of Java | JavaPlus
he latest version anymore) to use freely too.
This would be accomplished using a Gradle plugin as a preprocessor,
converting any of our JavaPlus constructs to their Java 8 counterparts and
then sending the new source off to javac to be compiled, eliminating the
need for brittle ASM invocations to hook into the compiler directly while
still having fairly low added runtime. For the most part, it would be
simple regex find-and-replace, avoiding any bytecode generation on purpose
so the end user can see exactly what their code is ending up as.
If possible, I'd like to also add the ability to apply the annotation-based
parts to preexisting libraries too, using what's essentially a ".d.ts" file
but for Java. This would allow the convenience factor for advanced users
without *requiring* it of newer ones, but it's likely out of scope for this
project.
To be honest, I'm just tired of having to track down my getters and
setters. If I can replace this:
> private String foo = "bar;
public String getFoo() {
>
return this.foo;
>
}
>
public void setFoo(String newVal) {
>
this.foo = newVal;
>
doOtherThing();
>
}
with this:
> String foo = "bar";
>
get() {
> return foo;
> }
>
set(newVal) {
> foo = newVal;
> doOtherThing();
> }
>
without having to leave my precious Java? And all it takes is banging my
head against some regex for 150 hours? That sounds like a fair trade to me.
I have a full plan formulated with a finalized process for every step, but
this is a "brief" overview of it. For the most part, I just *desperately*
need the input of people who are experienced with this area. Even if you
don't accept this for GSoC, I would still love to chat about it in the
future, because I think it will help Java be just a little bit better for
everyone.
So, what do you think? Does this sound like a good proposal idea? Let me
know your thoughts in the replies; I look forward to your feedback, and I
happily await this being torn apart by people more knowledgeable in the
field than I.
Thank you so much for your time,
Caleb Brandt
About Me:
I'm a hobbyist API developer and fixer of things: if I see something that
I'm able to resolve, I might as well help out. The biggest power of
programming is that if you solve a problem for yourself, you also solve it
for *every single person who will ever live*, which is why I admire
open-source consortiums such as you guys so greatly. You're everything I
wanted to be when I grew up, and I'm applying because you still represent
the hallmark of what good coding is to me: helping people do stuff more
easily, just because you *can*.
I'm a Junior at the University of Central Florida, finishing up my
Bachelor's degree in Computer Science. In my off-time, I make
compatibility mods for Minecraft: optimizing interactions between other
mods using Mixin (a framework for ASM), reflectively exposing APIs for
other developers, patching bugs, and anything else I can do to make the
ecosystem a bit better than how I found it. I also attempt to patch any
bugs I encounter in open-source software; I already spent the time tracking
it down, I might as well take one more step and fix it for *everyone* too.
Re: [QUESTION] What should community do in GSoC timeline?
Thank you for the response! I now have a clearer understanding of how to participate in GSoC. On Wed, Mar 13, 2024, at 22:56, Lewis John McGibbney wrote: > Hi Xuanwo, > It’s been a few years since I participated in GSoC as a mentor… but > this year I intend to. Let me see if I can provide answers to some of > your questions. > > On 2024/03/11 03:07:29 Xuanwo wrote: >> >> 2024-02-22: Potential GSoC contributors discuss application ideas with >> mentoring organizations >> >> Q: Should those ideas/proposals been posted to mailing list? Or just discuss >> with mentors? > > Mailing list is great however I don’t think there are any hard rules. > This period is really just for attracting interest in the initiative > (if it was created by the PMC/Committership) or convincing a PMC to > take on your initiative (if it was created by a potential GSoC student). > >> Q: Should student-submitted ideas/proposals be added to Jira? > > Yes absolutely. Make sure the JIRA issue is labeled with “gsoc2024” as > well. That way it will show up in the filter at > https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2024. > >> >> 2024-04-15: Proposals to ASF projects must be reviewed roughly and have a >> potential mentor so that we know how many slots to request. >> >> Q: Who will review/rank/score those proposals? The corresponding community's >> PMC? >> > > > In short yes but really it is down to the mentor(s). It is always good > to have a backup mentor as well in-case the mentor is unable to see the > project through. > > HTH > lewismc > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org -- Xuanwo - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [QUESTION] What should community do in GSoC timeline?
Hi Xuanwo, It’s been a few years since I participated in GSoC as a mentor… but this year I intend to. Let me see if I can provide answers to some of your questions. On 2024/03/11 03:07:29 Xuanwo wrote: > > 2024-02-22: Potential GSoC contributors discuss application ideas with > mentoring organizations > > Q: Should those ideas/proposals been posted to mailing list? Or just discuss > with mentors? Mailing list is great however I don’t think there are any hard rules. This period is really just for attracting interest in the initiative (if it was created by the PMC/Committership) or convincing a PMC to take on your initiative (if it was created by a potential GSoC student). > Q: Should student-submitted ideas/proposals be added to Jira? Yes absolutely. Make sure the JIRA issue is labeled with “gsoc2024” as well. That way it will show up in the filter at https://issues.apache.org/jira/issues/?jql=labels+%3D+gsoc2024. > > 2024-04-15: Proposals to ASF projects must be reviewed roughly and have a > potential mentor so that we know how many slots to request. > > Q: Who will review/rank/score those proposals? The corresponding community's > PMC? > In short yes but really it is down to the mentor(s). It is always good to have a backup mentor as well in-case the mentor is unable to see the project through. HTH lewismc - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Interest in Future Collaboration for GSoC 2024
Hello Akhilesh, mentors@ is the list for mentors only, not for GSoC contributors :) I can recommend you to check this page: [1] Then find the project you would like to participate in here: [2] (you can filter by your favorite language :)) Additionally you can search for the "gsoc2024" label in JIRA [3] :) Also we recently added a page in our community website with projects that have "Good Frist Issues". You can see it here: [4] It might help you to know where to start. Please send any additional questions to the dev@community mailing-list or better to the dev@ list of the particular Apache project you would like to contribute :) [1] https://community.apache.org/gsoc/ [2] https://projects.apache.org/projects.html [3] https://issues.apache.org/jira/browse [4] https://community.apache.org/committers/good-first-issues.html > From: Akhilesh Kumar Yadav > To: ment...@community.apache.org > Cc: > Bcc: > Date: Mon, 26 Feb 2024 04:04:33 +0530 > Subject: Interest in Future Collaboration for GSoC 2024 > > Greetings! > > I hope this message finds you well. I am writing to express my admiration for > the innovative technology that your organization is working on for GSoC 2024. > I have been following your work and find it truly amazing. > > Currently, I am committed to another organisation and may not be able to > contribute to your projects at this time. However, I noticed that your > organisation sometimes faces a shortage of proposals. If such a situation > arises, please consider this email as an expression of my interest. > > I hold a strong interest in your organisation and would be more than willing > to submit a comprehensive proposal should the need arise. I have also been an > active contribution at open source projects and have decent programming > experience. > > Thank you. I look forward to the possibility of future interactions. > > Best regards, > Akhilesh. -- Best regards, Maxim - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[QUESTION] What should community do in GSoC timeline?
Hello, everyone This is the first year that both I and the OpenDAL community are participating in GSoC. I'm somewhat confused about when and how our community fits into the GSoC timeline. I'll ask questions throughout the timeline, collect them into an FAQ, and submit a PR to the GSoC site if others have similar questions. 2024-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations Q: Should those ideas/proposals been posted to mailing list? Or just discuss with mentors? Q: Should student-submitted ideas/proposals be added to Jira? 2024-04-15: Proposals to ASF projects must be reviewed roughly and have a potential mentor so that we know how many slots to request. Q: Who will review/rank/score those proposals? The corresponding community's PMC? Xuanwo - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] docs: Update gsoc timeline (comdev-site)
solomax commented on PR #152: URL: https://github.com/apache/comdev-site/pull/152#issuecomment-1928718540 Thanks a million @Xuanwo ! -- 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: [PR] docs: Update gsoc timeline (comdev-site)
solomax merged PR #152: URL: https://github.com/apache/comdev-site/pull/152 -- 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: [PR] docs: Update gsoc timeline (comdev-site)
Xuanwo commented on PR #152: URL: https://github.com/apache/comdev-site/pull/152#issuecomment-1928709995 > I would have hardcoded year and dates from [developers.google.com/open-source/gsoc/timeline](https://developers.google.com/open-source/gsoc/timeline) shifter by two days for `evaluation deadlines` Updated, PTAL. -- 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: [PR] docs: Update gsoc timeline (comdev-site)
solomax commented on code in PR #152: URL: https://github.com/apache/comdev-site/pull/152#discussion_r1479166641 ## source/gsoc/_index.md: ## @@ -136,35 +136,35 @@ date indicated. ## Student Application and Selection - - 2023-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations Review Comment: well, I would VOTE for having up-to-date dates (to have something for the reference) -- 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: [PR] docs: Update gsoc timeline (comdev-site)
Xuanwo commented on code in PR #152: URL: https://github.com/apache/comdev-site/pull/152#discussion_r1479165690 ## source/gsoc/_index.md: ## @@ -136,35 +136,35 @@ date indicated. ## Student Application and Selection - - 2023-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations Review Comment: How about remove the old dates and leave a TBD here? -- 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: [PR] docs: Update gsoc timeline (comdev-site)
solomax commented on code in PR #152: URL: https://github.com/apache/comdev-site/pull/152#discussion_r1479164467 ## source/gsoc/_index.md: ## @@ -136,35 +136,35 @@ date indicated. ## Student Application and Selection - - 2023-02-22: Potential GSoC contributors discuss application ideas with mentoring organizations Review Comment: the dates are different for each year plus we are shifting original GSoC dates (making them 1-2 days earlier) to have enough time to ping mentors -- 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: [PR] docs: Update gsoc timeline (comdev-site)
Xuanwo commented on PR #152: URL: https://github.com/apache/comdev-site/pull/152#issuecomment-1928691783 cc priyasharma1, would you like to take a review on this? Thanks! -- 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
[PR] docs: Update gsoc timeline (comdev-site)
Xuanwo opened a new pull request, #152: URL: https://github.com/apache/comdev-site/pull/152 I'm not sure about this change. Are we stick to this timeline? Or we just remove them entirely? Current timeline is a bit confusing. -- 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: [Important] GSoC 2024 Project Ideas
Hello All,
This is a gentle reminder to kindly add your ideas at the earliest.
(You can keep refining them later)
So far there are only 8 ideas on the list [1], we generally apply with
a larger number every year.
Also if you consider any of the open ideas from GSoC'23 worthy to-be
included again please update the label ('gsoc2024') on it.
Please feel free to pass-on this message to your fellow communities.
Looking forward to your support.
On Thu, 25 Jan 2024 at 12:53, Priya Sharma wrote:
>
> Hello PMCs,
>
> Google Summer of Code is the ideal opportunity for you to attract new
> contributors to your projects and GSoC 2024 is here.
>
> The ASF will be applying as a participating organization for GSoC 2024.
> As a part of the application we need you all to *mandatorily* start
> recording your ideas now [1] latest by 3rd Feb.
>
> There is slight change in the rules this year, just reiterating here:
> - For the 2024 program, there will be three options for project scope:
> medium at ~175 hours, large at ~350 hours and a new size: small at ~90
> hours.
> Please add "*full-time*" label to the JIRA for 350 hour project ,
> "*part-time*" label for 175 hours project and “*small*” for a 90 hour
> project.
>
> Note: They are looking to bring more open source projects in the AI/ML
> field into GSoC 2024, so we encourage more projects from this domain
> to participate.
>
> If you are a new mentor or your project is participating for the first
> time, please read [2][3].
>
> On behalf of the GSoC 2024 admins,
>
> [1] https://s.apache.org/gsoc2024ideas
> [2] https://community.apache.org/gsoc.html
> [3] https://community.apache.org/guide-to-being-a-mentor.html
--
Best Regards,
Org Admins
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Re: [PR] GSoC 2024 updates (comdev-site)
solomax merged PR #151: URL: https://github.com/apache/comdev-site/pull/151 -- 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: [PR] GSoC 2024 updates (comdev-site)
bdelacretaz commented on PR #151: URL: https://github.com/apache/comdev-site/pull/151#issuecomment-1912218732 Thanks @priyasharma1 ,all good for me! I suspect the short code will change next January 1st, before GsoC 2025 is ready to go, but that's not dramatic... -- 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: [PR] GSoC 2024 updates (comdev-site)
priyasharma1 commented on PR #151: URL: https://github.com/apache/comdev-site/pull/151#issuecomment-1912034800 Thanks for the review @bdelacretaz and @solomax! I have made the requested changes and adittionally also added a shortcode for current year, so we do not need to update these pages every year. Let me know your views on it. -- 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: [PR] GSoC 2024 updates (comdev-site)
solomax commented on code in PR #151: URL: https://github.com/apache/comdev-site/pull/151#discussion_r1467319283 ## source/gsoc/gsoc-admin-tasks.md: ## @@ -23,7 +23,7 @@ contributors to your projects. If you want to participate with your project you now need to - understand what it means to be a mentor [1] - - propose your project ideas. Just label your issues with gsoc2023 in Jira and + - propose your project ideas. Just label your issues with gsoc2024 in Jira and Review Comment: ```suggestion - propose your project ideas. Just label your issues with `gsoc2024` in Jira and ``` -- 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: [PR] GSoC 2024 updates (comdev-site)
bdelacretaz commented on code in PR #151: URL: https://github.com/apache/comdev-site/pull/151#discussion_r1466183349 ## source/gsoc/guide-to-being-a-mentor.md: ## @@ -18,13 +18,13 @@ submit ideas via Jira (if your project does not use Jira you can [use the Comdev * Add an issue to Jira (if your project does not use Jira you can [use the Comdev GSoC Issue Tracker For GSoC Tasks](use-the-comdev-gsoc-issue-tracker-for-gsoc-tasks.html) * Add sub-tasks if necessary -* Label the main issue with "*mentor*" (these will show up at the [ASF-wide list of issues](https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2023)%20AND%20labels%20in%20(mentor,%20Mentor))) -* Label the main issue with "*gsoc2023*" if appropriate (these will show up at [GSoC 2023 Ideas](https://s.apache.org/gsoc2023ideas)) +* Label the main issue with "*mentor*" (these will show up at the [ASF-wide list of issues](https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2024)%20AND%20labels%20in%20(mentor,%20Mentor))) +* Label the main issue with "*gsoc2024*" if appropriate (these will show up at [GSoC 2024 Ideas](https://s.apache.org/gsoc2024ideas)) Size of project -Starting this year there are 2 types of projects available. Please put "full-time" label for ~350 hours project and "part-time" label for ~175 hours project +Starting this year there are 3 types of projects available. Please put "full-time" label for ~350 hours project and "part-time" label for ~175 hours project "small" label for ~90 hours project Review Comment: I'd say "starting in 2024" so we're less likely to have stale info here later if we forget to update it ;-) -- 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: [PR] GSoC 2024 updates (comdev-site)
bdelacretaz commented on code in PR #151: URL: https://github.com/apache/comdev-site/pull/151#discussion_r1466182585 ## source/gsoc/gsoc-admin-tasks.md: ## @@ -23,7 +23,7 @@ contributors to your projects. If you want to participate with your project you now need to - understand what it means to be a mentor [1] - - propose your project ideas. Just label your issues with gsoc2023 in Jira and + - propose your project ideas. Just label your issues with gsoc2024 in Jira and they will show up at [2]. See also [1]. Review Comment: The `[2] https://s.apache.org/gsoc2011tasks` footnote is probably not useful anymore, either this page needs to be reworked to remove such precise references that need to be changed every year, or a warning added at the top of the page that details might not be valid anymore. -- 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
[PR] GSoC 2024 updates (comdev-site)
priyasharma1 opened a new pull request, #151: URL: https://github.com/apache/comdev-site/pull/151 (no comment) -- 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
[Important] GSoC 2024 Project Ideas
Hello PMCs, Google Summer of Code is the ideal opportunity for you to attract new contributors to your projects and GSoC 2024 is here. The ASF will be applying as a participating organization for GSoC 2024. As a part of the application we need you all to *mandatorily* start recording your ideas now [1] latest by 3rd Feb. There is slight change in the rules this year, just reiterating here: - For the 2024 program, there will be three options for project scope: medium at ~175 hours, large at ~350 hours and a new size: small at ~90 hours. Please add "*full-time*" label to the JIRA for 350 hour project , "*part-time*" label for 175 hours project and “*small*” for a 90 hour project. Note: They are looking to bring more open source projects in the AI/ML field into GSoC 2024, so we encourage more projects from this domain to participate. If you are a new mentor or your project is participating for the first time, please read [2][3]. On behalf of the GSoC 2024 admins, [1] https://s.apache.org/gsoc2024ideas [2] https://community.apache.org/gsoc.html [3] https://community.apache.org/guide-to-being-a-mentor.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Regarding GSOC
Hello Vaibhav, mentors@ is the list for mentors only, not for GSoC contributors :) I can recommend you to check this page: [1] Then find the project you would like to participate in here: [2] (you can filter by your favorite language :)) Additionally you can search for the "gsoc2024" label in JIRA [3] :) Also we recently added a page in our community website with projects that have "Good Frist Issues". You can see it here: [4] It might help you to know where to start. Please send any additional questions to the dev@community mailing-list or better to the dev@ list of the particular Apache project you would like to contribute :) [1] https://community.apache.org/gsoc/ [2] https://projects.apache.org/projects.html [3] https://issues.apache.org/jira/browse [4] https://community.apache.org/committers/good-first-issues.html > From: Vaibhav Verma > To: ment...@community.apache.org > Cc: > Bcc: > Date: Fri, 12 Jan 2024 09:34:49 +0530 > Subject: Regarding GSOC > Respected Sir, > I am Vaibhav Verma, a computer science undergrad and I am currently in second > year of my degree. I am new to open source contributions but I am aware of C, > C++, JavaScript. I am also eager to learn about new technologies. I would > love to contribute to your organization (The Apache Software Foundation) but > could you please tell me how to get started? > Hoping to hear from you soon. > > Regards > Vaibhav - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] rbowen merged pull request #104: moves gsoc to a top-level nav item
rbowen merged PR #104: URL: https://github.com/apache/comdev-site/pull/104 -- 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
regarding GSoc first round selection(pre selection round)
hello mentors, i am willing to contribute for apache maven's common skin update and i wanted to know about the pre selection process,when will it commence and on which platform(slack?) also, i am super new to the apache community and would love to know about some good first issues . thankyou
[jira] [Closed] (COMDEV-249) GSoC [RocketMQ]Message Delivery Once Semantic Implementation
[ https://issues.apache.org/jira/browse/COMDEV-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-249. Resolution: Abandoned > GSoC [RocketMQ]Message Delivery Once Semantic Implementation > > > Key: COMDEV-249 > URL: https://issues.apache.org/jira/browse/COMDEV-249 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: Von Gosling >Priority: Major > > The duplicated messages will impose the extra cost if the user needs > non-repeating messages. > In most cases, the user needs to store the consumer records to determine if a > message is duplicated, and the store stage should guarantee consistency. So > we need to support a strict and non-redundant message delivery mechanism. > In this context, we hope to design a delivery once plugin, say, you could > design a global(but need raft guarantee multi-copy data) storage, using the > hooker of RocketMQ ConsumeMessageHook to finish the task. > -- 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 proposal Make RocketMQ support higher versions of Java
Dear Project Mentor, I am Abhijeet from India and I am excited to apply for the RocketMQ project as a part of GSoC. I have professional experience working with Java and Scala and I am well-versed in the modern paradigm of Java and functional programming. I have been contributing to RocketMQ for the past month and I am interested in open-source software development, as I find it rewarding to solve challenging problems that support the community. I am particularly interested in the project that aims to update the RocketMQ codebase to support newer versions of Java in a cross-compile manner. I believe that this is a crucial project that will enable RocketMQ users to take advantage of the latest Java features and performance improvements while maintaining backward compatibility with previous versions of Java. Regarding my approach to the project, I would begin by analyzing the existing codebase and identifying any dependencies that need to be changed to support the new Java versions. I would then proceed to update these dependencies while ensuring backward compatibility with previous versions of Java. I would also test and verify that the new version of RocketMQ works correctly and is stable. Throughout the project, I would work closely with the community to gather feedback and suggestions for improvement. I have relevant experience in Java programming and software development, and I have been actively contributing to RocketMQ for the past month. I have also worked on several open-source projects in the past, which has helped me develop my skills in software development and collaborating with other developers. I am available full-time for the duration of the GSoC program, and I am committed to completing the project within the given timeline. I would also be happy to collaborate with other developers in the community to ensure the success of the project. Thank you for considering my proposal. Please let me know if you have any questions or if there are any additional details I can provide. Sincerely, Abhijeet - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: GSoC proposal Make RocketMQ support higher versions of Java
Hi Abhijeet, This is perhaps the wrong list. You need to send this email to the dev mailing list of the respective project i.e. RocketMQ, which is d...@rocketmq.apache.org All the best!! On Tue, 4 Apr 2023 at 10:33, Abhijeet Mishra wrote: > > Dear Project Mentor, > > I am Abhijeet from India and I am excited to apply for the RocketMQ > project as a part of GSoC. I have professional experience working with > Java and Scala and I am well-versed in the modern paradigm of Java and > functional programming. I have been contributing to RocketMQ for the > past month and I am interested in open-source software development, as > I find it rewarding to solve challenging problems that support the > community. > > I am particularly interested in the project that aims to update the > RocketMQ codebase to support newer versions of Java in a cross-compile > manner. I believe that this is a crucial project that will enable > RocketMQ users to take advantage of the latest Java features and > performance improvements while maintaining backward compatibility with > previous versions of Java. > > Regarding my approach to the project, I would begin by analyzing the > existing codebase and identifying any dependencies that need to be > changed to support the new Java versions. I would then proceed to > update these dependencies while ensuring backward compatibility with > previous versions of Java. I would also test and verify that the new > version of RocketMQ works correctly and is stable. Throughout the > project, I would work closely with the community to gather feedback > and suggestions for improvement. > > I have relevant experience in Java programming and software > development, and I have been actively contributing to RocketMQ for the > past month. I have also worked on several open-source projects in the > past, which has helped me develop my skills in software development > and collaborating with other developers. > > I am available full-time for the duration of the GSoC program, and I > am committed to completing the project within the given timeline. I > would also be happy to collaborate with other developers in the > community to ensure the success of the project. > > Thank you for considering my proposal. Please let me know if you have > any questions or if there are any additional details I can provide. > > Sincerely, > Abhijeet > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > -- Best Regards, Priya - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
My Proposal Draft for Apache ShenYu Gsoc 2023 - Design license scanning function
Hello to all the members of the community, I hope this email finds you all well. I am particularly interested in designing a license scanning function as it aligns with my interests and skills. I believe that my proposal to design a license scanning function will benefit the project by automating the process of checking licenses manually. By going through the community discussions, it was possible for me to find well-written proposals, and I have included a link to my draft proposal based on such a proposal below, which includes details about my idea and how I plan to implement it. I am open to feedback on my proposal and am willing to make changes as needed. https://gist.github.com/salmanthasleem/3f979552aeff0018c23f190580ebe93a I would like to mention that I have cloned the project and run it locally. Currently, I am trying to learn more about licensing and how it works in the Apache Shenyu project. Additionally, I'm working on a task issued in the "apache/shenyu-dashboard" to make myself familiar with the codebase. This will be my first open-source contribution, and I am excited about the opportunity to contribute to this project more and more. I would also like to apologize for any confusion or misunderstanding that may have occurred in my previous emails sent to the Apache Shenyu community. As a beginner, I am still learning how open-source communities work, and I may have come across as rude or wrongly addressed some issues. Please let me know if there is anything that I can do to improve my communication with you. Thank you for your time and consideration. I look forward to hearing back from you. Thank You, Salman Thasleem
GSoC proposal Make RocketMQ support higher versions of Java
Dear Project Mentor, I am Abhijeet from India and I am excited to apply for the RocketMQ project as a part of GSoC. I have professional experience working with Java and Scala and I am well-versed in the modern paradigm of Java and functional programming. I have been contributing to RocketMQ for the past month and I am interested in open-source software development, as I find it rewarding to solve challenging problems that support the community. I am particularly interested in the project that aims to update the RocketMQ codebase to support newer versions of Java in a cross-compile manner. I believe that this is a crucial project that will enable RocketMQ users to take advantage of the latest Java features and performance improvements while maintaining backward compatibility with previous versions of Java. Regarding my approach to the project, I would begin by analyzing the existing codebase and identifying any dependencies that need to be changed to support the new Java versions. I would then proceed to update these dependencies while ensuring backward compatibility with previous versions of Java. I would also test and verify that the new version of RocketMQ works correctly and is stable. Throughout the project, I would work closely with the community to gather feedback and suggestions for improvement. I have relevant experience in Java programming and software development, and I have been actively contributing to RocketMQ for the past month. I have also worked on several open-source projects in the past, which has helped me develop my skills in software development and collaborating with other developers. I am available full-time for the duration of the GSoC program, and I am committed to completing the project within the given timeline. I would also be happy to collaborate with other developers in the community to ensure the success of the project. Thank you for considering my proposal. Please let me know if you have any questions or if there are any additional details I can provide. Sincerely, Abhijeet - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Broken link in GSoC article on news.a.o
Op wo 29 mrt 2023 om 16:57 schreef sebb : > On Wed, 29 Mar 2023 at 15:42, Roy Lenferink wrote: > > > > I just noticed a broken link in the following blog post: > > > https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023 > > > > The link "Students: read this!" refers to > > > > https://community.apache.org/gsoc.html#students-read-this > > > > instead of > > > > https://community.apache.org/gsoc/#students-read-this > > > > This probably has to do with refactoring the GSoC sections. > > I think it is more likely due to the __index.md renames. > > In this case it was the re-ordering of the gsoc content. > > Does anyone know who wrote that blog post and how to correct the broken > > link? > > There should be no need to correct the blog post. > > Indeed unless that link never worked, I don't think that is the > correct way to fix a broken link, as it will only fix that instance of > the link. > There may be many others. > > It should be possible to redirect to the updated page using .htaccess > (I'll try and fix that shortly). > I just learned about the existence of Hugo aliases [1] and that seems to work for me locally. See [2] on how this applies to the refactored GSoC content. Do we have a preference on .htaccess (single file with all redirects) vs Hugo aliases (old urls close to the new files) ? [1] https://gohugo.io/content-management/urls/#aliases [2] https://github.com/apache/comdev-site/pull/98 > > Sebb > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Broken link in GSoC article on news.a.o
On Wed, 2023-03-29 at 15:56 +0100, sebb wrote: > On Wed, 29 Mar 2023 at 15:42, Roy Lenferink > wrote: > > > > I just noticed a broken link in the following blog post: > > https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023 > > > > The link "Students: read this!" refers to > > > > https://community.apache.org/gsoc.html#students-read-this > > > > instead of > > > > https://community.apache.org/gsoc/#students-read-this > > > > This probably has to do with refactoring the GSoC sections. > > I think it is more likely due to the __index.md renames. > > > Does anyone know who wrote that blog post and how to correct the > > broken > > link? > > There should be no need to correct the blog post. > > Indeed unless that link never worked, I don't think that is the > correct way to fix a broken link, as it will only fix that instance > of > the link. > There may be many others. > > It should be possible to redirect to the updated page using .htaccess > (I'll try and fix that shortly). The link did work until last week, when all gsoc content was moved into a gsoc subdir. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Broken link in GSoC article on news.a.o
On Wed, 29 Mar 2023 at 15:42, Roy Lenferink wrote: > > I just noticed a broken link in the following blog post: > https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023 > > The link "Students: read this!" refers to > > https://community.apache.org/gsoc.html#students-read-this > > instead of > > https://community.apache.org/gsoc/#students-read-this > > This probably has to do with refactoring the GSoC sections. I think it is more likely due to the __index.md renames. > Does anyone know who wrote that blog post and how to correct the broken > link? There should be no need to correct the blog post. Indeed unless that link never worked, I don't think that is the correct way to fix a broken link, as it will only fix that instance of the link. There may be many others. It should be possible to redirect to the updated page using .htaccess (I'll try and fix that shortly). Sebb - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Broken link in GSoC article on news.a.o
I just noticed a broken link in the following blog post: https://news.apache.org/foundation/entry/asf-to-mentor-gsoc-contributors-in-2023 The link "Students: read this!" refers to https://community.apache.org/gsoc.html#students-read-this instead of https://community.apache.org/gsoc/#students-read-this This probably has to do with refactoring the GSoC sections. Does anyone know who wrote that blog post and how to correct the broken link?
Re: GSoC 2023 Contribution
Thanks a lot. I will check them out On Wed, Mar 22, 2023 at 11:55 AM Priya Sharma wrote: > Hi Rishita, > Additionally, GSoC 2023 Ideas list is available here > https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2023+Ideas+list > > Choose the idea and project that meets your preferences and start > engaging with the respective project's community. > You can also find good first issues in the project's issue tracker > (GitHub or Jira). > > Hurry up, the application deadline is approaching. All the best! > > On Wed, 22 Mar 2023 at 09:01, Maxim Solodovnik > wrote: > > > > Hello Rishita Jain, > > > > mentors@ is the list for mentors only, not for GSoC contributors :) > > I can recommend you to check this page: > https://community.apache.org/gsoc/ > > > > Then find the project you would like to participate in here: > > https://projects.apache.org/projects.html? > > language#Java > > > > Additionally you can search for the "gsoc2023" label in JIRA [1] :) > > > > Please send any additional questions to the dev@community mailing-list > > or better to the dev@ list of the particular Apache project you would > > like to contribute :) > > > > [1] https://issues.apache.org/jira/browse > > > > > > > From: Rishita Jain > > > To: "ment...@community.apache.org" > > > Cc: > > > Bcc: > > > Date: Wed, 22 Mar 2023 03:01:12 +0530 > > > Subject: GSoC 2023 Contribution > > > > > > Hello Mentors, > > > > > > > > > Hope you are doing well. I am interested in your project and would > like to contribute to it. Can you please suggest some resources so that I > can learn new technologies that you have used in your project. > > > > > > > > > > > > Also can you please assign me some good first issues for the starting > that I can do and catch up soon. > > > > > > > > > Thank you > > > > > > Regards > > > > > > Rishita Jain > > > > > > > > -- > > Best regards, > > Maxim > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > -- > Best Regards, > Priya >
Re: GSoC 2023 Contribution
Hi Rishita, Additionally, GSoC 2023 Ideas list is available here https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2023+Ideas+list Choose the idea and project that meets your preferences and start engaging with the respective project's community. You can also find good first issues in the project's issue tracker (GitHub or Jira). Hurry up, the application deadline is approaching. All the best! On Wed, 22 Mar 2023 at 09:01, Maxim Solodovnik wrote: > > Hello Rishita Jain, > > mentors@ is the list for mentors only, not for GSoC contributors :) > I can recommend you to check this page: https://community.apache.org/gsoc/ > > Then find the project you would like to participate in here: > https://projects.apache.org/projects.html? > language#Java > > Additionally you can search for the "gsoc2023" label in JIRA [1] :) > > Please send any additional questions to the dev@community mailing-list > or better to the dev@ list of the particular Apache project you would > like to contribute :) > > [1] https://issues.apache.org/jira/browse > > > > From: Rishita Jain > > To: "ment...@community.apache.org" > > Cc: > > Bcc: > > Date: Wed, 22 Mar 2023 03:01:12 +0530 > > Subject: GSoC 2023 Contribution > > > > Hello Mentors, > > > > > > Hope you are doing well. I am interested in your project and would like to > > contribute to it. Can you please suggest some resources so that I can learn > > new technologies that you have used in your project. > > > > > > > > Also can you please assign me some good first issues for the starting that > > I can do and catch up soon. > > > > > > Thank you > > > > Regards > > > > Rishita Jain > > > > -- > Best regards, > Maxim > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > -- Best Regards, Priya - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: GSoC 2023 Contribution
Hello Rishita Jain, mentors@ is the list for mentors only, not for GSoC contributors :) I can recommend you to check this page: https://community.apache.org/gsoc/ Then find the project you would like to participate in here: https://projects.apache.org/projects.html? language#Java Additionally you can search for the "gsoc2023" label in JIRA [1] :) Please send any additional questions to the dev@community mailing-list or better to the dev@ list of the particular Apache project you would like to contribute :) [1] https://issues.apache.org/jira/browse > From: Rishita Jain > To: "ment...@community.apache.org" > Cc: > Bcc: > Date: Wed, 22 Mar 2023 03:01:12 +0530 > Subject: GSoC 2023 Contribution > > Hello Mentors, > > > Hope you are doing well. I am interested in your project and would like to > contribute to it. Can you please suggest some resources so that I can learn > new technologies that you have used in your project. > > > > Also can you please assign me some good first issues for the starting that I > can do and catch up soon. > > > Thank you > > Regards > > Rishita Jain -- 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?
On Tue, 21 Mar 2023 at 21:46, wrote: > > On Tue, 2023-03-21 at 14:35 +0100, Roy Lenferink wrote: > > Something I have been wondering for a couple of weeks now: does it > > make > > sense to > > keep the current name 'mentors@community' for the GSoC mentors > > mailing list > > ? > > > > Maybe it is possible to rename the mentors@community mailing list to > > something > > like gsoc-mentors@community to prevent confusion that we have an > > active > > mentors program. > > While I might agree, it seems it would be less disruptive to do this > between GSoC's, rather than while one is currently in-flight. > huge +1 I believe it would be better to create new JIRA project between GSoCs too but this can be done on-the-fly to move ML would be much distinctive :( > > > > > And maybe also introduce a new list, e.g. gsoc@community for all GSoC > > stuff > > (the JIRA notifications can also be send there). I feel like all the > > GSoC > > notifications are a bit > > much for the dev@community list. > > > > Op di 21 mrt 2023 om 14:27 schreef : > > > > > On Tue, 2023-03-21 at 10:28 +0700, Maxim Solodovnik wrote: > > > > Done: > > > > > > > https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0 > > > > Sorry for delay :) > > > > > > > > New JIRA GSOC project was created (Thanks to sebb) > > > > So I'll try to update all docs, move current JIRAs and notify > > > > mentors@ > > > > list as my next steps :)) > > > > > > This is fantastic. Thanks. > > > > > > --Rich > > > > > > > > > > > > > > > > > > On Thu, 16 Mar 2023 at 23:55, wrote: > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > --- > > > -- > > > 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?
On Tue, 2023-03-21 at 14:35 +0100, Roy Lenferink wrote: > Something I have been wondering for a couple of weeks now: does it > make > sense to > keep the current name 'mentors@community' for the GSoC mentors > mailing list > ? > > Maybe it is possible to rename the mentors@community mailing list to > something > like gsoc-mentors@community to prevent confusion that we have an > active > mentors program. While I might agree, it seems it would be less disruptive to do this between GSoC's, rather than while one is currently in-flight. > > And maybe also introduce a new list, e.g. gsoc@community for all GSoC > stuff > (the JIRA notifications can also be send there). I feel like all the > GSoC > notifications are a bit > much for the dev@community list. > > Op di 21 mrt 2023 om 14:27 schreef : > > > On Tue, 2023-03-21 at 10:28 +0700, Maxim Solodovnik wrote: > > > Done: > > > > > https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0 > > > Sorry for delay :) > > > > > > New JIRA GSOC project was created (Thanks to sebb) > > > So I'll try to update all docs, move current JIRAs and notify > > > mentors@ > > > list as my next steps :)) > > > > This is fantastic. Thanks. > > > > --Rich > > > > > > > > > > > > > On Thu, 16 Mar 2023 at 23:55, wrote: > > > > > > > > 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 > > > > > > > > > > > > > > > > --- > > -- > > 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?
Something I have been wondering for a couple of weeks now: does it make sense to keep the current name 'mentors@community' for the GSoC mentors mailing list ? Maybe it is possible to rename the mentors@community mailing list to something like gsoc-mentors@community to prevent confusion that we have an active mentors program. And maybe also introduce a new list, e.g. gsoc@community for all GSoC stuff (the JIRA notifications can also be send there). I feel like all the GSoC notifications are a bit much for the dev@community list. Op di 21 mrt 2023 om 14:27 schreef : > On Tue, 2023-03-21 at 10:28 +0700, Maxim Solodovnik wrote: > > Done: > > > https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0 > > Sorry for delay :) > > > > New JIRA GSOC project was created (Thanks to sebb) > > So I'll try to update all docs, move current JIRAs and notify > > mentors@ > > list as my next steps :)) > > This is fantastic. Thanks. > > --Rich > > > > > > > > On Thu, 16 Mar 2023 at 23:55, wrote: > > > > > > 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 > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: GSoC messaging?
On Tue, 2023-03-21 at 10:28 +0700, Maxim Solodovnik wrote: > Done: > https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0 > Sorry for delay :) > > New JIRA GSOC project was created (Thanks to sebb) > So I'll try to update all docs, move current JIRAs and notify > mentors@ > list as my next steps :)) This is fantastic. Thanks. --Rich > > > On Thu, 16 Mar 2023 at 23:55, wrote: > > > > 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 > > > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: GSoC messaging?
On Tue, 21 Mar 2023 at 10:28, Maxim Solodovnik wrote: > > Done: > https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0 > Sorry for delay :) > > New JIRA GSOC project was created (Thanks to sebb) > So I'll try to update all docs, move current JIRAs and notify mentors@ > list as my next steps :)) > All seems to be done Hopefully there will be less noise :) > > On Thu, 16 Mar 2023 at 23:55, wrote: > > > > 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 > > > > > -- > Best regards, > Maxim -- Best regards, Maxim - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] [comdev-site] solomax merged pull request #95: [Update]: References to Comdev Jira with the GSOC Jira project (gsoc-2023)
solomax merged PR #95: URL: https://github.com/apache/comdev-site/pull/95 -- 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
[jira] [Commented] (COMDEV-524) Apache ShenYu Gsoc 2023 - Design license scanning function
[ https://issues.apache.org/jira/browse/COMDEV-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703021#comment-17703021 ] Zhenxu Ke commented on COMDEV-524: -- Sounds like you want the `license-eye dependency resolve --output` ?https://github.com/apache/skywalking-eyes/tree/main#resolve-dependencies-licenses > Apache ShenYu Gsoc 2023 - Design license scanning function > -- > > Key: COMDEV-524 > URL: https://issues.apache.org/jira/browse/COMDEV-524 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: SiYing Zheng >Priority: Major > Labels: GSOC, ShenYu, gsoc2023, java, part-time > > *Background* > At present, shenyu needs to manually check whether the license is correct one > by one when releasing the version. > *Tasks* > # Discuss with the tutor to complete the requirement design and technical > design of the scanning license. > # Finished scanning the initial version of the license. > # Complete the corresponding test. > *Relevant Skills* > # Familiar with Java. -- 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: GSoC messaging?
Done: https://github.com/apache/comdev-site/commit/4d4fb12609f3b3ef62e398acac4282798ddafcc0 Sorry for delay :) New JIRA GSOC project was created (Thanks to sebb) So I'll try to update all docs, move current JIRAs and notify mentors@ list as my next steps :)) On Thu, 16 Mar 2023 at 23:55, wrote: > > 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 > -- Best regards, Maxim - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-524) Apache ShenYu Gsoc 2023 - Design license scanning function
[ https://issues.apache.org/jira/browse/COMDEV-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated COMDEV-524: Labels: GSOC ShenYu gsoc2023 java part-time (was: GSOC gsoc2023 java part-time) > Apache ShenYu Gsoc 2023 - Design license scanning function > -- > > Key: COMDEV-524 > URL: https://issues.apache.org/jira/browse/COMDEV-524 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: SiYing Zheng >Priority: Major > Labels: GSOC, ShenYu, gsoc2023, java, part-time > > *Background* > At present, shenyu needs to manually check whether the license is correct one > by one when releasing the version. > *Tasks* > # Discuss with the tutor to complete the requirement design and technical > design of the scanning license. > # Finished scanning the initial version of the license. > # Complete the corresponding test. > *Relevant Skills* > # Familiar with Java. -- 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-524) Apache ShenYu Gsoc 2023 - Design license scanning function
SiYing Zheng created COMDEV-524: --- Summary: Apache ShenYu Gsoc 2023 - Design license scanning function Key: COMDEV-524 URL: https://issues.apache.org/jira/browse/COMDEV-524 Project: Community Development Issue Type: Task Components: GSoC/Mentoring ideas Reporter: SiYing Zheng *Background* At present, shenyu needs to manually check whether the license is correct one by one when releasing the version. *Tasks* # Discuss with the tutor to complete the requirement design and technical design of the scanning license. # Finished scanning the initial version of the license. # Complete the corresponding test. *Relevant Skills* # Familiar with Java. -- 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] [Closed] (COMDEV-501) [GSOC] [SkyWalking] Pending Task on K8s
[ https://issues.apache.org/jira/browse/COMDEV-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yihao Chen closed COMDEV-501. - Resolution: Fixed Closing in favor of detailed new task created by other mentors > [GSOC] [SkyWalking] Pending Task on K8s > --- > > Key: COMDEV-501 > URL: https://issues.apache.org/jira/browse/COMDEV-501 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Yihao Chen >Priority: Major > Labels: SkyWalking, full-time, gsoc2023, mentor > > Apache SkyWalking is an application performance monitor tool for distributed > systems, especially designed for microservices, cloud native and > container-based (Kubernetes) architectures. This task is about a pending task > on K8s. -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- External issue URL: https://github.com/apache/skywalking/issues/10562 > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: SkyWalking, gsoc2023, part-time > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Fully unify/merge the query planner and executor for Measure and TopN > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-515: -- External issue URL: https://github.com/apache/skywalking/issues/10561 > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: SkyWalking, full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > [1]: [EXPLAIN in > MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking or other APMs > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-523) GSoC: Observability Improvement for RocketMQ Streams
[ https://issues.apache.org/jira/browse/COMDEV-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ni Ze updated COMDEV-523: - Description: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. was: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. > GSoC: Observability Improvement for RocketMQ Streams > > > Key: COMDEV-523 > URL: https://issues.apache.org/jira/browse/COMDEV-523 > Project: Community Development > Issue Type: Task >Reporter: Ni Ze >Priority: Major > Labels: RocketMQ, full-time, gsoc2023, mentor > > h2. *RocketMQ Streams* > RocketMQ Streams is a lightweight stream processing framework, application > gains the stream processing ability by depending on RocketMQ Streams as an > SDK. > h2. Background > Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] > The architecture document of RocketMQ Streams: [RocketMQ Streams > examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] > [architecture > doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] > h2. *Task* > The observability needs to be enhanced in the following aspects: > * The metric of client/processor/thread/state/rocksdb; > * The topology of streaming process; > * Mutli-output of metrics; > This task need you to study the implementation details of RocketMQ Streams > streams, and find out the key indicators in the stream processing process. > Design and implement a complete set of observability solutions, and finally > use it to complete runtime problem diagnosis; > h2. Mentor > nize, Committer of of Apache RocketMQ, > [k...@apache.org|
[jira] [Updated] (COMDEV-523) GSoC: Observability Improvement for RocketMQ Streams
[ https://issues.apache.org/jira/browse/COMDEV-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ni Ze updated COMDEV-523: - Description: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. was: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [[architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. > GSoC: Observability Improvement for RocketMQ Streams > > > Key: COMDEV-523 > URL: https://issues.apache.org/jira/browse/COMDEV-523 > Project: Community Development > Issue Type: Task >Reporter: Ni Ze >Priority: Major > Labels: RocketMQ, full-time, gsoc2023, mentor > > h2. *RocketMQ Streams* > RocketMQ Streams is a lightweight stream processing framework, application > gains the stream processing ability by depending on RocketMQ Streams as an > SDK. > h2. Background > Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] > The architecture document of RocketMQ Streams: [RocketMQ Streams > examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] > [architecture > doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]] > h2. *Task* > The observability needs to be enhanced in the following aspects: > * The metric of client/processor/thread/state/rocksdb; > * The topology of streaming process; > * Mutli-output of metrics; > This task need you to study the implementation details of RocketMQ Streams > streams, and find out the key indicators in the s
[jira] [Updated] (COMDEV-523) GSoC: Observability Improvement for RocketMQ Streams
[ https://issues.apache.org/jira/browse/COMDEV-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ni Ze updated COMDEV-523: - Description: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [[architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. was: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,[architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. > GSoC: Observability Improvement for RocketMQ Streams > > > Key: COMDEV-523 > URL: https://issues.apache.org/jira/browse/COMDEV-523 > Project: Community Development > Issue Type: Task >Reporter: Ni Ze >Priority: Major > Labels: RocketMQ, full-time, gsoc2023, mentor > > h2. *RocketMQ Streams* > RocketMQ Streams is a lightweight stream processing framework, application > gains the stream processing ability by depending on RocketMQ Streams as an > SDK. > h2. Background > Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] > The architecture document of RocketMQ Streams: [RocketMQ Streams > examples,|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] > [[architecture > doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] > h2. *Task* > The observability needs to be enhanced in the following aspects: > * The metric of client/processor/thread/state
[jira] [Updated] (COMDEV-523) GSoC: Observability Improvement for RocketMQ Streams
[ https://issues.apache.org/jira/browse/COMDEV-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ni Ze updated COMDEV-523: - Description: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples,[architecture doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. was: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples |https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [ Topology Construction and Data Processing Process|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. > GSoC: Observability Improvement for RocketMQ Streams > > > Key: COMDEV-523 > URL: https://issues.apache.org/jira/browse/COMDEV-523 > Project: Community Development > Issue Type: Task >Reporter: Ni Ze >Priority: Major > Labels: RocketMQ, full-time, gsoc2023, mentor > > h2. *RocketMQ Streams* > RocketMQ Streams is a lightweight stream processing framework, application > gains the stream processing ability by depending on RocketMQ Streams as an > SDK. > h2. Background > Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] > The architecture document of RocketMQ Streams: [RocketMQ Streams > examples,[architecture > doc|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd]|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] > h2. *Task* > The observability needs to be enhanced in the following aspects: > * The metric of client/processor/thread/state/rocksdb; > * The topology of streaming process; > * Mutli-output of metrics; > This task need you to study the implementation details of RocketMQ Streams > streams, and find out the key indicators in the stream processing process. > Design and implement a complete set of observability solutions, and finally > use it to complete runtime problem diagnosis; > h2. Mentor > nize, Committer of of Apache RocketMQ
[jira] [Updated] (COMDEV-523) GSoC: Observability Improvement for RocketMQ Streams
[ https://issues.apache.org/jira/browse/COMDEV-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ni Ze updated COMDEV-523: - Description: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples |https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [ Topology Construction and Data Processing Process|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. was: h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples |https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [ Topology Construction and Data Processing Process|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. > GSoC: Observability Improvement for RocketMQ Streams > > > Key: COMDEV-523 > URL: https://issues.apache.org/jira/browse/COMDEV-523 > Project: Community Development > Issue Type: Task >Reporter: Ni Ze >Priority: Major > Labels: RocketMQ, full-time, gsoc2023, mentor > > h2. *RocketMQ Streams* > RocketMQ Streams is a lightweight stream processing framework, application > gains the stream processing ability by depending on RocketMQ Streams as an > SDK. > h2. Background > Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] > The architecture document of RocketMQ Streams: [RocketMQ Streams examples > |https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] > [ Topology Construction and Data Processing > Process|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] > > h2. *Task* > The observability needs to be enhanced in the following aspects: > * The metric of client/processor/thread/state/rocksdb; > * The topology of streaming process; > * Mutli-output of metrics; > This task need you to study the implementation details of RocketMQ Streams > streams, and find out the key indicators in the stream processing process. > Design and implement a complete set of observability solutions, and fin
[jira] [Created] (COMDEV-523) GSoC: Observability Improvement for RocketMQ Streams
Ni Ze created COMDEV-523: Summary: GSoC: Observability Improvement for RocketMQ Streams Key: COMDEV-523 URL: https://issues.apache.org/jira/browse/COMDEV-523 Project: Community Development Issue Type: Task Reporter: Ni Ze h2. *RocketMQ Streams* RocketMQ Streams is a lightweight stream processing framework, application gains the stream processing ability by depending on RocketMQ Streams as an SDK. h2. Background Repo of RocketMQ Streams: [https://github.com/apache/rocketmq-streams] The architecture document of RocketMQ Streams: [RocketMQ Streams examples |https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486386&idx=1&sn=198722f8ba0c65d8a06bcc6c23f42f86&chksm=ce6466bbf913efad859a4a643475d2f2eb2cfe5e351c4e332f40797aab78adebc202af8ff386&scene=21#wechat_redirect] [ Topology Construction and Data Processing Process|https://mp.weixin.qq.com/s?__biz=Mzg2NDcxMzgzMA==&mid=2247486423&idx=1&sn=b9b1ac3a9492f951f7ddf8ed50a53097&chksm=ce6466def913efc8fc39fc5e26d59b53996cebf0c76fb7a162892cb1803a69501e070c30b083&token=1627591522&lang=zh_CN#rd] h2. *Task* The observability needs to be enhanced in the following aspects: * The metric of client/processor/thread/state/rocksdb; * The topology of streaming process; * Mutli-output of metrics; This task need you to study the implementation details of RocketMQ Streams streams, and find out the key indicators in the stream processing process. Design and implement a complete set of observability solutions, and finally use it to complete runtime problem diagnosis; h2. Mentor nize, Committer of of Apache RocketMQ, [k...@apache.org|mailto:k...@apache.org] h4. -- 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: GSoC messaging?
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: GSoC messaging?
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?
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
[jira] [Updated] (COMDEV-521) [GSoC][Beam] Build out Beam Machine Learning Use Cases
[ 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
[ 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 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?
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
[ 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
[jira] [Updated] (COMDEV-520) [GSOC][SkyWalking] Add Terraform provider for Apache SkyWalking
[ 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
[jira] [Updated] (COMDEV-518) Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
[
https://issues.apache.org/jira/browse/COMDEV-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik updated COMDEV-518:
Labels: ShenYu gsoc gsoc2023 (was: Shenyu gsco)
> Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
> -
>
> Key: COMDEV-518
> URL: https://issues.apache.org/jira/browse/COMDEV-518
> Project: Community Development
> Issue Type: New Feature
> Components: Comdev, GSoC/Mentoring ideas
>Reporter: Keguo Li
>Priority: Major
> Labels: ShenYu, gsoc, gsoc2023
>
> h2. Background
> Shenyu is a native API gateway for service proxy, protocol translation and
> API governance. It can manage and maintain the API through Shenyu-admin, and
> support internationalization in Chinese and English. Unfortunately,
> Shenyu-admin is only internationalized on the front end. The message prompt
> returned by the back-end interface is still in English. Therefore, we need to
> implement internationalization support for the back-end interface.This will
> lay a good foundation for shenyu to move towards more language support.
> h2. Relevant skills
> * Related skills spring resources
> * Spring Internationalization
> * Front-end react framework
> h2. API reference
> {code:java}
> java.util.Locale;
> org.springframework.context.MessageSource;
> org.springframework.context.support.ResourceBundleMessageSource; {code}
> h2. Interface effect example
> {code:java}
> ## zh request example
> POST http://localhost:9095/plugin
> Content-Type: application/json
> Location: cn-zh
> X-Access-Token: xxx
> {
> "name": "test-create-plugin",
> "role": "test-create-plugin",
> "enabled": true,
> "sort": 100
> }
> Respone
> {
> "code": 600,
> "message": "未登录"
> }
> ### en request example
> POST http://localhost:9095/plugin
> Content-Type: application/json
> Location: en
> X-Access-Token: xxx
> {
> "name": "test-create-plugin",
> "role": "test-create-plugin",
> "enabled": true,
> "sort": 100
> }
> Respone
> {
> "code": 600,
> "message": "token is error"
> } {code}
> h2. Task List
> * The task discussed with the tutor how to achieve the internationalization
> of shenyu-admin background
> * Some prompt message translation
> * Get through the internationalization of front-end, obtain the client
> region information through http protocol, support the language of the
> corresponding region.
> * Leave the extension of other multi-language internationalization support
> interface, so as to facilitate the localization transformation of subsequent
> users.
--
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-518) Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
[
https://issues.apache.org/jira/browse/COMDEV-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keguo Li updated COMDEV-518:
Description:
h2. Background
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. It can manage and maintain the API through Shenyu-admin, and
support internationalization in Chinese and English. Unfortunately,
Shenyu-admin is only internationalized on the front end. The message prompt
returned by the back-end interface is still in English. Therefore, we need to
implement internationalization support for the back-end interface.This will lay
a good foundation for shenyu to move towards more language support.
h2. Relevant skills
* Related skills spring resources
* Spring Internationalization
* Front-end react framework
h2. API reference
{code:java}
java.util.Locale;
org.springframework.context.MessageSource;
org.springframework.context.support.ResourceBundleMessageSource; {code}
h2. Interface effect example
{code:java}
## zh request example
POST http://localhost:9095/plugin
Content-Type: application/json
Location: cn-zh
X-Access-Token: xxx
{
"name": "test-create-plugin",
"role": "test-create-plugin",
"enabled": true,
"sort": 100
}
Respone
{
"code": 600,
"message": "未登录"
}
### en request example
POST http://localhost:9095/plugin
Content-Type: application/json
Location: en
X-Access-Token: xxx
{
"name": "test-create-plugin",
"role": "test-create-plugin",
"enabled": true,
"sort": 100
}
Respone
{
"code": 600,
"message": "token is error"
} {code}
h2. Task List
* The task discussed with the tutor how to achieve the internationalization of
shenyu-admin background
* Some prompt message translation
* Get through the internationalization of front-end, obtain the client region
information through http protocol, support the language of the corresponding
region.
* Leave the extension of other multi-language internationalization support
interface, so as to facilitate the localization transformation of subsequent
users.
was:
h2. Background
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. It can manage and maintain the API through Shenyu-admin, and
support internationalization in Chinese and English. Unfortunately,
Shenyu-admin is only internationalized on the front end. The message prompt
returned by the back-end interface is still in English. Therefore, we need to
implement internationalization support for the back-end interface.This will lay
a good foundation for shenyu to move towards more language support.
h2. Relevant skills
* Related skills spring resources
* Spring Internationalization
* Front-end react framework
h2. API reference
java.util.Localeorg.springframework.context.MessageSourceorg.springframework.context.support.ResourceBundleMessageSource;
h2. Interface effect example
{code:java}
## zh request example
POST http://localhost:9095/plugin
Content-Type: application/json
Location: cn-zh
X-Access-Token: xxx
{
"name": "test-create-plugin",
"role": "test-create-plugin",
"enabled": true,
"sort": 100
}
Respone
{
"code": 600,
"message": "未登录"
}
### en request example
POST http://localhost:9095/plugin
Content-Type: application/json
Location: en
X-Access-Token: xxx
{
"name": "test-create-plugin",
"role": "test-create-plugin",
"enabled": true,
"sort": 100
}
Respone
{
"code": 600,
"message": "token is error"
} {code}
h2. Task List
* The task discussed with the tutor how to achieve the internationalization of
shenyu-admin background
* Some prompt message translation
* Get through the internationalization of front-end, obtain the client region
information through http protocol, support the language of the corresponding
region.
* Leave the extension of other multi-language internationalization support
interface, so as to facilitate the localization transformation of subsequent
users.
> Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
> -
>
> Key: COMDEV-518
> URL: https://issues.apache.org/jira/browse/COMDEV-518
> Project: Community Development
> Issue Type: New Feature
> Components: Comdev, GSoC/Mentoring ideas
>Reporter: Keguo Li
>Priority: Major
> Labels: Shenyu, gsco
>
> h2. Background
> Shenyu is a native API gateway for service proxy, protocol translation and
> API governance. It can ma
[jira] [Updated] (COMDEV-518) Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
[
https://issues.apache.org/jira/browse/COMDEV-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keguo Li updated COMDEV-518:
Description:
h2. Background
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. It can manage and maintain the API through Shenyu-admin, and
support internationalization in Chinese and English. Unfortunately,
Shenyu-admin is only internationalized on the front end. The message prompt
returned by the back-end interface is still in English. Therefore, we need to
implement internationalization support for the back-end interface.This will lay
a good foundation for shenyu to move towards more language support.
h2. Relevant skills
* Related skills spring resources
* Spring Internationalization
* Front-end react framework
h2. API reference
java.util.Localeorg.springframework.context.MessageSourceorg.springframework.context.support.ResourceBundleMessageSource;
h2. Interface effect example
{code:java}
## zh request example
POST http://localhost:9095/plugin
Content-Type: application/json
Location: cn-zh
X-Access-Token: xxx
{
"name": "test-create-plugin",
"role": "test-create-plugin",
"enabled": true,
"sort": 100
}
Respone
{
"code": 600,
"message": "未登录"
}
### en request example
POST http://localhost:9095/plugin
Content-Type: application/json
Location: en
X-Access-Token: xxx
{
"name": "test-create-plugin",
"role": "test-create-plugin",
"enabled": true,
"sort": 100
}
Respone
{
"code": 600,
"message": "token is error"
} {code}
h2. Task List
* The task discussed with the tutor how to achieve the internationalization of
shenyu-admin background
* Some prompt message translation
* Get through the internationalization of front-end, obtain the client region
information through http protocol, support the language of the corresponding
region.
* Leave the extension of other multi-language internationalization support
interface, so as to facilitate the localization transformation of subsequent
users.
was:
h2. Background
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. It can manage and maintain the API through Shenyu-admin, and
support internationalization in Chinese and English. Unfortunately,
Shenyu-admin is only internationalized on the front end. The message prompt
returned by the back-end interface is still in English. Therefore, we need to
implement internationalization support for the back-end interface.This will lay
a good foundation for shenyu to move towards more language support.
h2. Relevant skills
* Related skills spring resources
* Spring Internationalization
* Front-end react framework
h2. API reference
java.util.Localeorg.springframework.context.MessageSourceorg.springframework.context.support.ResourceBundleMessageSource;
h2. Interface effect example
### zh request examplePOST http://localhost:9095/pluginContent-Type:
application/jsonLocation: cn-zhX-Access-Token: xxx{ "name":
"test-create-plugin","role": "test-create-plugin","enabled": true,"sort":
100}Respone{ "code": 600,"message": "未登录"}### en request examplePOST
http://localhost:9095/pluginContent-Type: application/jsonLocation:
enX-Access-Token: xxx{ "name": "test-create-plugin","role":
"test-create-plugin","enabled": true,"sort": 100}Respone{ "code":
600,"message": "token is error"}
h2. Task List
* The task discussed with the tutor how to achieve the internationalization of
shenyu-admin background
* Some prompt message translation
* Get through the internationalization of front-end, obtain the client region
information through http protocol, support the language of the corresponding
region.
* Leave the extension of other multi-language internationalization support
interface, so as to facilitate the localization transformation of subsequent
users.
> Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
> -
>
> Key: COMDEV-518
> URL: https://issues.apache.org/jira/browse/COMDEV-518
> Project: Community Development
> Issue Type: New Feature
> Components: Comdev, GSoC/Mentoring ideas
>Reporter: Keguo Li
>Priority: Major
> Labels: Shenyu, gsco
>
> h2. Background
> Shenyu is a native API gateway for service proxy, protocol translation and
> API governance. It can manage and maintain the API through Shenyu-admin, and
> support internationali
[jira] [Created] (COMDEV-518) Apache ShenYu Gsoc 2023 - Shenyu-Admin Internationalization
Keguo Li created COMDEV-518:
---
Summary: Apache ShenYu Gsoc 2023 - Shenyu-Admin
Internationalization
Key: COMDEV-518
URL: https://issues.apache.org/jira/browse/COMDEV-518
Project: Community Development
Issue Type: New Feature
Components: Comdev, GSoC/Mentoring ideas
Reporter: Keguo Li
h2. Background
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. It can manage and maintain the API through Shenyu-admin, and
support internationalization in Chinese and English. Unfortunately,
Shenyu-admin is only internationalized on the front end. The message prompt
returned by the back-end interface is still in English. Therefore, we need to
implement internationalization support for the back-end interface.This will lay
a good foundation for shenyu to move towards more language support.
h2. Relevant skills
* Related skills spring resources
* Spring Internationalization
* Front-end react framework
h2. API reference
java.util.Localeorg.springframework.context.MessageSourceorg.springframework.context.support.ResourceBundleMessageSource;
h2. Interface effect example
### zh request examplePOST http://localhost:9095/pluginContent-Type:
application/jsonLocation: cn-zhX-Access-Token: xxx{ "name":
"test-create-plugin","role": "test-create-plugin","enabled": true,"sort":
100}Respone{ "code": 600,"message": "未登录"}### en request examplePOST
http://localhost:9095/pluginContent-Type: application/jsonLocation:
enX-Access-Token: xxx{ "name": "test-create-plugin","role":
"test-create-plugin","enabled": true,"sort": 100}Respone{ "code":
600,"message": "token is error"}
h2. Task List
* The task discussed with the tutor how to achieve the internationalization of
shenyu-admin background
* Some prompt message translation
* Get through the internationalization of front-end, obtain the client region
information through http protocol, support the language of the corresponding
region.
* Leave the extension of other multi-language internationalization support
interface, so as to facilitate the localization transformation of subsequent
users.
--
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-517) Apache ShenYu Gsoc 2023 - ShenYu End-To-End SpringCloud plugin test case
[
https://issues.apache.org/jira/browse/COMDEV-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fengen He updated COMDEV-517:
-
Description:
h3. *Background:*
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. but Shenyu lack of End-To-End Tests.
*Relevant skills：*
1.Understand the architecture of ShenYu
2.Understand SpringCloud micro-service and ShenYu SpringCloud proxy plugin.
3.Understand ShenYu e2e framework and architecture.
*How to coding*
1.please refer to {{org.apache.shenyu.e2e.testcase.plugin.DividePluginCases}}
*How to test*
1.start shenyu admin in docker
2.start shenyu boostrap in docker
3.run test case {{org.apache.shenyu.e2e.testcase.plugin.PluginsTest#testDivide}}
h3. Task List
1.develop e2e tests of the springcloud plug-in.
2.write shenyu e2e springcloud plugin documentation in shenyu-website.
3.refactor the existing plugin test cases.
*Links:*
website： [https://shenyu.apache.org/]
issues: [https://github.com/apache/shenyu/issues/4474]
was:
h3. *Background:*
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. but Shenyu lack of End-To-End Tests.
*Relevant skills：*
1.Understand the architecture of ShenYu
2.Understand SpringCloud micro-service and ShenYu SpringCloud proxy plugin.
3.Understand ShenYu e2e framework and architecture.
*How to coding*
1.please refer to {{org.apache.shenyu.e2e.testcase.plugin.DividePluginCases}}
*How to test*
1.start shenyu admin in docker
2.start shenyu boostrap in docker
3.run test case {{org.apache.shenyu.e2e.testcase.plugin.PluginsTest#testDivide}}
h3. Task List
1.develop e2e tests of the springcloud plug-in.
2.write shenyu e2e springcloud plugin documentation in shenyu-website.
3.refactor the existing plugin test cases.
*Links:*
website： [https://shenyu.apache.org/]{*}{*}
issues: https://github.com/apache/shenyu/issues/4474
> Apache ShenYu Gsoc 2023 - ShenYu End-To-End SpringCloud plugin test case
>
>
> Key: COMDEV-517
> URL: https://issues.apache.org/jira/browse/COMDEV-517
> Project: Community Development
> Issue Type: Improvement
> Components: Comdev, GSoC/Mentoring ideas
>Reporter: Fengen He
>Priority: Major
> Labels: ShenYu, gsoc, gsoc2023, part-time
>
> h3. *Background:*
> Shenyu is a native API gateway for service proxy, protocol translation and
> API governance. but Shenyu lack of End-To-End Tests.
> *Relevant skills：*
> 1.Understand the architecture of ShenYu
> 2.Understand SpringCloud micro-service and ShenYu SpringCloud proxy plugin.
> 3.Understand ShenYu e2e framework and architecture.
> *How to coding*
> 1.please refer to {{org.apache.shenyu.e2e.testcase.plugin.DividePluginCases}}
> *How to test*
> 1.start shenyu admin in docker
> 2.start shenyu boostrap in docker
> 3.run test case
> {{org.apache.shenyu.e2e.testcase.plugin.PluginsTest#testDivide}}
> h3. Task List
> 1.develop e2e tests of the springcloud plug-in.
> 2.write shenyu e2e springcloud plugin documentation in shenyu-website.
> 3.refactor the existing plugin test cases.
>
> *Links:*
> website： [https://shenyu.apache.org/]
> issues: [https://github.com/apache/shenyu/issues/4474]
>
--
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-517) Apache ShenYu Gsoc 2023 - ShenYu End-To-End SpringCloud plugin test case
Fengen He created COMDEV-517:
Summary: Apache ShenYu Gsoc 2023 - ShenYu End-To-End SpringCloud
plugin test case
Key: COMDEV-517
URL: https://issues.apache.org/jira/browse/COMDEV-517
Project: Community Development
Issue Type: Improvement
Components: Comdev, GSoC/Mentoring ideas
Reporter: Fengen He
h3. *Background:*
Shenyu is a native API gateway for service proxy, protocol translation and API
governance. but Shenyu lack of End-To-End Tests.
*Relevant skills：*
1.Understand the architecture of ShenYu
2.Understand SpringCloud micro-service and ShenYu SpringCloud proxy plugin.
3.Understand ShenYu e2e framework and architecture.
*How to coding*
1.please refer to {{org.apache.shenyu.e2e.testcase.plugin.DividePluginCases}}
*How to test*
1.start shenyu admin in docker
2.start shenyu boostrap in docker
3.run test case {{org.apache.shenyu.e2e.testcase.plugin.PluginsTest#testDivide}}
h3. Task List
1.develop e2e tests of the springcloud plug-in.
2.write shenyu e2e springcloud plugin documentation in shenyu-website.
3.refactor the existing plugin test cases.
*Links:*
website： [https://shenyu.apache.org/]{*}{*}
issues: https://github.com/apache/shenyu/issues/4474
--
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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated COMDEV-515: Labels: SkyWalking full-time gsoc2023 (was: full-time gsoc2023) > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: SkyWalking, full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > [1]: [EXPLAIN in > MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking or other APMs > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik updated COMDEV-516: Labels: SkyWalking gsoc2023 part-time (was: gsoc2023 part-time) > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: SkyWalking, gsoc2023, part-time > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Fully unify/merge the query planner and executor for Measure and TopN > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- difficulty-level: Easy (was: Medium) > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: gsoc2023, part-time > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Fully unify/merge the query planner and executor for Measure and TopN > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- Labels: gsoc2023 part-time (was: full-time gsoc2023) > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: gsoc2023, part-time > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Fully unify/merge the query planner and executor for Measure and TopN > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Fully unify/merge the query planner and executor for Measure and TopN h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Fully unify/merge the query planner and executor for Measure and TopN (easy, part-time) h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Fully unify/merge the query planner and executor for Measure and TopN > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Fully unify/merge the query planner and executor for Measure and TopN (easy, part-time) h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives 1. Fully unify the query planner and h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Fully unify/merge the query planner and executor for Measure and TopN > (easy, part-time) > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives 1. Fully unify the query planner and h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was:Placerholder > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: gsoc2023, part-time > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > 1. Fully unify the query planner and > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- difficulty-level: Easy (was: Medium) > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: gsoc2023, part-time > > Placerholder -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- Labels: full-time gsoc2023 (was: gsoc2023 part-time) > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > 1. Fully unify the query planner and > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-516) [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-516: -- difficulty-level: Medium (was: Easy) > [GSOC] [SkyWalking] Unify query planner and executor in BanyanDB > > > Key: COMDEV-516 > URL: https://issues.apache.org/jira/browse/COMDEV-516 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > 1. Fully unify the query planner and > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-515: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI [1]: [EXPLAIN in MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking or other APMs h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI [1]: [EXPLAIN in MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > [1]: [EXPLAIN in > MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking or other APMs > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-515: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI [1]: [EXPLAIN in MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine # Have an experience of Apache SkyWalking h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI [1]: [EXPLAIN in MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > [1]: [EXPLAIN in > MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > # Have an experience of Apache SkyWalking > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-515: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI [1]: [EXPLAIN in MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] h3. *Recommended Skills* # Familiar with Go # Have a basic understanding of database query engine h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [hanahm...@apache.org|mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query, # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI h3. *Recommended Skills* # Use Golang h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > [1]: [EXPLAIN in > MySQL|https://dev.mysql.com/doc/refman/8.0/en/using-explain.html] > h3. *Recommended Skills* > # Familiar with Go > # Have a basic understanding of database query engine > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [hanahm...@apache.org|mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-515: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query, # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI h3. *Recommended Skills* # Use Golang h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [mailto:lujiaj...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query, # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI h3. *Recommended Skills* # Use Golang h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:morning...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query, > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > h3. *Recommended Skills* > # Use Golang > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, [mailto:lujiaj...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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-515) [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB
[ https://issues.apache.org/jira/browse/COMDEV-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajing Lu updated COMDEV-515: -- Description: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query, # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI h3. *Recommended Skills* # Use Golang h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:morning...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, [mailto:hanahm...@apache.org] * Mailing List: d...@skywalking.apache.org was: h3. Background SkyWalking BanyanDB is an observability database, aims to ingest, analyze and store Metrics, Tracing and Logging data. h3. Objectives # Support EXPLAIN[1] for both measure query and stream query, # Add self-observability including trace and metrics for query subsystem # Support EXPLAIN in the client SDK & CLI and add query plan visualization in the UI h3. Requirements # Use Golang h3. Mentor * Mentor: Jiajing Lu, Apache SkyWalking PMC, [lujiaj...@apache.org|mailto:morning...@apache.org] * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere, [k...@apache.org|mailto:k...@apache.org] * Mailing List: d...@skywalking.apache.org > [GSOC] [SkyWalking] Self-Observability of the query subsystem in BanyanDB > - > > Key: COMDEV-515 > URL: https://issues.apache.org/jira/browse/COMDEV-515 > Project: Community Development > Issue Type: Task >Reporter: Jiajing Lu >Priority: Major > Labels: full-time, gsoc2023 > > h3. Background > SkyWalking BanyanDB is an observability database, aims to ingest, analyze and > store Metrics, Tracing and Logging data. > h3. Objectives > # Support EXPLAIN[1] for both measure query and stream query, > # Add self-observability including trace and metrics for query subsystem > # Support EXPLAIN in the client SDK & CLI and add query plan visualization > in the UI > h3. *Recommended Skills* > # Use Golang > h3. Mentor > * Mentor: Jiajing Lu, Apache SkyWalking PMC, > [lujiaj...@apache.org|mailto:morning...@apache.org] > * Mentor: Hongtao Gao, Apache SkyWalking PMC, Apache ShardingSphere PMC, > [mailto:hanahm...@apache.org] > * Mailing List: d...@skywalking.apache.org -- 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
