Re: Invitation to exhibit at Druid Summit: April 2020/SFO

2020-03-17 Thread Sally Khudairi
Hello everyone --a quick heads-up that Druid Summit has postponed their 
in-person event to November, and will be holding select presentations as a 
virtual event in April.

Further details are available at https://druidsummit.org/

Many thanks,
Sally

- - - 
Vice President Marketing & Publicity
Vice President Sponsor Relations
The Apache Software Foundation

Tel +1 617 921 8656 | s...@apache.org

On Mon, Feb 24, 2020, at 15:41, Sally Khudairi wrote:
> Hello ComDev-ers.
> 
> The Apache Druid community will be at Druit Summit 
> https://druidsummit.org/ 13-15 April in San Francisco (Airport 
> Marriott/Burlingame), and have offered a booth for the ASF to exhibit 
> at during the event.
> 
> Whilst I wait for answers to expo days/hours, how many people can staff 
> the booth, if you can attend sessions, etc., I'd love to know if any 
> local community members are interested/able to participate. 
> 
> Many thanks in advance,
> Sally
> 
> - - - 
> Vice President Marketing & Publicity
> Vice President Sponsor Relations
> The Apache Software Foundation
> 
> Tel +1 617 921 8656 | s...@apache.org
>

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



Re: [jira] [Commented] (COMDEV-346) CloudEvents support for RocketMQ

2020-03-17 Thread Matt Sicker
Send an email to dev-unsubscr...@community.apache.org to unsubscribe
yourself from the list.

On Tue, 17 Mar 2020 at 13:09, Dee Grant  wrote:
>
> Please stop sending me this stuff
>
> On Tue, Mar 17, 2020, 11:37 AM Piyush Mishra (Jira)  wrote:
>
> >
> > [
> > https://issues.apache.org/jira/browse/COMDEV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061046#comment-17061046
> > ]
> >
> > Piyush Mishra commented on COMDEV-346:
> > --
> >
> > Hi [~duheng],
> >
> > Thanks you for your reply. I am going through the general guidelines for
> > GSOC.
> >
> > I noted the dev email that you provided in your reply. Is there any other
> > way as well to connect with the community (irc/slack)? I shall subscribe to
> > the mailing [list d...@rocketmq.dev.org|mailto:
> > list%c2%a0...@rocketmq.dev.org] as well.
> >
> > I want to get started with my proposal, but wanted to know if there is any
> > prerequisite or some conventions to be followed before submitting the
> > proposal on the GSOC application portal. As I believe it would be of great
> > help if I get to interact with the community and get feedback while penning
> > down the proposal at this phase and maybe also be able to start
> > contributing from my end to the community.
> >
> >
> >
> > Thanks
> >
> > Piyush
> >
> > > CloudEvents support for RocketMQ
> > > 
> > >
> > > Key: COMDEV-346
> > > URL: https://issues.apache.org/jira/browse/COMDEV-346
> > > Project: Community Development
> > >  Issue Type: Wish
> > >  Components: GSoC/Mentoring ideas
> > >Reporter: duheng
> > >Priority: Major
> > >  Labels: RocketMQ, gsoc2020
> > >
> > > h3. Context
> > > Events are everywhere. However, event producers tend to describe events
> > differently.
> > > The lack of a common way of describing events means developers must
> > constantly re-learn how to consume events. This also limits the potential
> > for libraries, tooling and infrastructure to aide the delivery of event
> > data across environments, like SDKs, event routers or tracing systems. The
> > portability and productivity we can achieve from event data is hindered
> > overall.
> > > [CloudEvents|https://github.com/cloudevents] is a specification for
> > describing event data in common formats to provide interoperability across
> > services, platforms and systems.
> > > RocketMQ as an event streaming platform, also hopes to improve the
> > interoperability of different event platforms by being compatible with the
> > CloudEvents standard and supporting CloudEvents SDK. In this topic, you
> > need to improve the binding spec. and implement the RocketMQ CloudEvents
> > SDK(Java、Golang or others).
> > > h3. You should learn before applying for this topic
> > > Apache RocketMQ/Apache RocketMQ SDK/CloudEvents
> > > h3. Mentor
> > > [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [
> > vongosl...@apache.org|mailto:vongosl...@apache.org]
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >



-- 
Matt Sicker 

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



Re: [jira] [Commented] (COMDEV-346) CloudEvents support for RocketMQ

2020-03-17 Thread Dee Grant
Please stop sending me this stuff

On Tue, Mar 17, 2020, 11:37 AM Piyush Mishra (Jira)  wrote:

>
> [
> https://issues.apache.org/jira/browse/COMDEV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061046#comment-17061046
> ]
>
> Piyush Mishra commented on COMDEV-346:
> --
>
> Hi [~duheng],
>
> Thanks you for your reply. I am going through the general guidelines for
> GSOC.
>
> I noted the dev email that you provided in your reply. Is there any other
> way as well to connect with the community (irc/slack)? I shall subscribe to
> the mailing [list d...@rocketmq.dev.org|mailto:
> list%c2%a0...@rocketmq.dev.org] as well.
>
> I want to get started with my proposal, but wanted to know if there is any
> prerequisite or some conventions to be followed before submitting the
> proposal on the GSOC application portal. As I believe it would be of great
> help if I get to interact with the community and get feedback while penning
> down the proposal at this phase and maybe also be able to start
> contributing from my end to the community.
>
>
>
> Thanks
>
> Piyush
>
> > CloudEvents support for RocketMQ
> > 
> >
> > Key: COMDEV-346
> > URL: https://issues.apache.org/jira/browse/COMDEV-346
> > Project: Community Development
> >  Issue Type: Wish
> >  Components: GSoC/Mentoring ideas
> >Reporter: duheng
> >Priority: Major
> >  Labels: RocketMQ, gsoc2020
> >
> > h3. Context
> > Events are everywhere. However, event producers tend to describe events
> differently.
> > The lack of a common way of describing events means developers must
> constantly re-learn how to consume events. This also limits the potential
> for libraries, tooling and infrastructure to aide the delivery of event
> data across environments, like SDKs, event routers or tracing systems. The
> portability and productivity we can achieve from event data is hindered
> overall.
> > [CloudEvents|https://github.com/cloudevents] is a specification for
> describing event data in common formats to provide interoperability across
> services, platforms and systems.
> > RocketMQ as an event streaming platform, also hopes to improve the
> interoperability of different event platforms by being compatible with the
> CloudEvents standard and supporting CloudEvents SDK. In this topic, you
> need to improve the binding spec. and implement the RocketMQ CloudEvents
> SDK(Java、Golang or others).
> > h3. You should learn before applying for this topic
> > Apache RocketMQ/Apache RocketMQ SDK/CloudEvents
> > h3. Mentor
> > [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [
> vongosl...@apache.org|mailto:vongosl...@apache.org]
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>


[jira] [Commented] (COMDEV-346) CloudEvents support for RocketMQ

2020-03-17 Thread Piyush Mishra (Jira)


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

Piyush Mishra commented on COMDEV-346:
--

Hi [~duheng],

Thanks you for your reply. I am going through the general guidelines for GSOC.

I noted the dev email that you provided in your reply. Is there any other way 
as well to connect with the community (irc/slack)? I shall subscribe to the 
mailing [list d...@rocketmq.dev.org|mailto:list%c2%a0...@rocketmq.dev.org] as 
well.

I want to get started with my proposal, but wanted to know if there is any 
prerequisite or some conventions to be followed before submitting the proposal 
on the GSOC application portal. As I believe it would be of great help if I get 
to interact with the community and get feedback while penning down the proposal 
at this phase and maybe also be able to start contributing from my end to the 
community.

 

Thanks

Piyush

> CloudEvents support for RocketMQ
> 
>
> Key: COMDEV-346
> URL: https://issues.apache.org/jira/browse/COMDEV-346
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Context
> Events are everywhere. However, event producers tend to describe events 
> differently.
> The lack of a common way of describing events means developers must 
> constantly re-learn how to consume events. This also limits the potential for 
> libraries, tooling and infrastructure to aide the delivery of event data 
> across environments, like SDKs, event routers or tracing systems. The 
> portability and productivity we can achieve from event data is hindered 
> overall.
> [CloudEvents|https://github.com/cloudevents] is a specification for 
> describing event data in common formats to provide interoperability across 
> services, platforms and systems.
> RocketMQ as an event streaming platform, also hopes to improve the 
> interoperability of different event platforms by being compatible with the 
> CloudEvents standard and supporting CloudEvents SDK. In this topic, you need 
> to improve the binding spec. and implement the RocketMQ CloudEvents 
> SDK(Java、Golang or others).
> h3. You should learn before applying for this topic
> Apache RocketMQ/Apache RocketMQ SDK/CloudEvents
> h3. Mentor
> [duhengfore...@apache.org|mailto:duhengfore...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Commented] (COMDEV-346) CloudEvents support for RocketMQ

2020-03-17 Thread duheng (Jira)


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

duheng commented on COMDEV-346:
---

[~piymis] Welcome to participate in this project. Any questions can be asked at 
d...@rocketmq.dev.org. You need to register on the GSoC website first, and then 
write a proposal about this project. The specific process of GSoC can refer to 
[https://summerofcode.withgoogle.com/how-it-works/ 
|https://summerofcode.withgoogle.com/how-it-works/]And it would be better if 
you can submit a proposal on the GSoC website.

> CloudEvents support for RocketMQ
> 
>
> Key: COMDEV-346
> URL: https://issues.apache.org/jira/browse/COMDEV-346
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Context
> Events are everywhere. However, event producers tend to describe events 
> differently.
> The lack of a common way of describing events means developers must 
> constantly re-learn how to consume events. This also limits the potential for 
> libraries, tooling and infrastructure to aide the delivery of event data 
> across environments, like SDKs, event routers or tracing systems. The 
> portability and productivity we can achieve from event data is hindered 
> overall.
> [CloudEvents|https://github.com/cloudevents] is a specification for 
> describing event data in common formats to provide interoperability across 
> services, platforms and systems.
> RocketMQ as an event streaming platform, also hopes to improve the 
> interoperability of different event platforms by being compatible with the 
> CloudEvents standard and supporting CloudEvents SDK. In this topic, you need 
> to improve the binding spec. and implement the RocketMQ CloudEvents 
> SDK(Java、Golang or others).
> h3. You should learn before applying for this topic
> Apache RocketMQ/Apache RocketMQ SDK/CloudEvents
> h3. Mentor
> [duhengfore...@apache.org|mailto:duhengfore...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Commented] (COMDEV-346) CloudEvents support for RocketMQ

2020-03-17 Thread Piyush Mishra (Jira)


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

Piyush Mishra commented on COMDEV-346:
--

Hi,

I would like to work on this project as part of GSOC.

Thanks & Regards

Piyush

> CloudEvents support for RocketMQ
> 
>
> Key: COMDEV-346
> URL: https://issues.apache.org/jira/browse/COMDEV-346
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Context
> Events are everywhere. However, event producers tend to describe events 
> differently.
> The lack of a common way of describing events means developers must 
> constantly re-learn how to consume events. This also limits the potential for 
> libraries, tooling and infrastructure to aide the delivery of event data 
> across environments, like SDKs, event routers or tracing systems. The 
> portability and productivity we can achieve from event data is hindered 
> overall.
> [CloudEvents|https://github.com/cloudevents] is a specification for 
> describing event data in common formats to provide interoperability across 
> services, platforms and systems.
> RocketMQ as an event streaming platform, also hopes to improve the 
> interoperability of different event platforms by being compatible with the 
> CloudEvents standard and supporting CloudEvents SDK. In this topic, you need 
> to improve the binding spec. and implement the RocketMQ CloudEvents 
> SDK(Java、Golang or others).
> h3. You should learn before applying for this topic
> Apache RocketMQ/Apache RocketMQ SDK/CloudEvents
> h3. Mentor
> [duhengfore...@apache.org|mailto:duhengfore...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Commented] (COMDEV-349) RocketMQ Connect Elasticsearch

2020-03-17 Thread Kirill Yankov (Jira)


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

Kirill Yankov commented on COMDEV-349:
--

I have applied for it in my proposal

> RocketMQ Connect Elasticsearch
> --
>
> Key: COMDEV-349
> URL: https://issues.apache.org/jira/browse/COMDEV-349
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Content
> The Elasticsearch sink connector allows moving data from Apache RocketMQ to 
> Elasticsearch 6.x, and 7.x. It writes data from a topic in Apache RocketMQ to 
> an index in Elasticsearch and all data for a topic have the same type.
> [Elasticsearch|https://www.elastic.co/] is often used for text queries, 
> analytics and as an key-value store (use cases). The connector covers both 
> the analytics and key-value store use cases.
> For the analytics use case, each message is in RocketMQ is treated as an 
> event and the connector uses topic+message queue+offset as a unique 
> identifier for events, which then converted to unique documents in 
> Elasticsearch. For the key-value store use case, it supports using keys from 
> RocketMQ messages as document ids in Elasticsearch and provides 
> configurations ensuring that updates to a key are written to Elasticsearch in 
> order.
> So, in this project, you need to implement a sink connector based on 
> OpenMessaging connect API, and will executed on RocketMQ connect runtime.
> h3. You should learn before applying for this topic
> [Elasticsearch|https://www.elastic.co/]/[Apache 
> RocketMQ|https://rocketmq.apache.org/]/[Apache RocketMQ 
> Connect|https://github.com/apache/rocketmq-externals/tree/master/rocketmq-connect]/
>  [OpenMessaging Connect 
> API|https://github.com/openmessaging/openmessaging-connect]
> h3. Mentor
> [duhengfore...@apache.org|mailto:duhengfore...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



[jira] [Commented] (COMDEV-349) RocketMQ Connect Elasticsearch

2020-03-17 Thread Piyush Mishra (Jira)


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

Piyush Mishra commented on COMDEV-349:
--

Hi,
Is the idea still unassigned, then I would like to work on this part of GSOC 20.

> RocketMQ Connect Elasticsearch
> --
>
> Key: COMDEV-349
> URL: https://issues.apache.org/jira/browse/COMDEV-349
> Project: Community Development
>  Issue Type: Wish
>  Components: GSoC/Mentoring ideas
>Reporter: duheng
>Priority: Major
>  Labels: RocketMQ, gsoc2020
>
> h3. Content
> The Elasticsearch sink connector allows moving data from Apache RocketMQ to 
> Elasticsearch 6.x, and 7.x. It writes data from a topic in Apache RocketMQ to 
> an index in Elasticsearch and all data for a topic have the same type.
> [Elasticsearch|https://www.elastic.co/] is often used for text queries, 
> analytics and as an key-value store (use cases). The connector covers both 
> the analytics and key-value store use cases.
> For the analytics use case, each message is in RocketMQ is treated as an 
> event and the connector uses topic+message queue+offset as a unique 
> identifier for events, which then converted to unique documents in 
> Elasticsearch. For the key-value store use case, it supports using keys from 
> RocketMQ messages as document ids in Elasticsearch and provides 
> configurations ensuring that updates to a key are written to Elasticsearch in 
> order.
> So, in this project, you need to implement a sink connector based on 
> OpenMessaging connect API, and will executed on RocketMQ connect runtime.
> h3. You should learn before applying for this topic
> [Elasticsearch|https://www.elastic.co/]/[Apache 
> RocketMQ|https://rocketmq.apache.org/]/[Apache RocketMQ 
> Connect|https://github.com/apache/rocketmq-externals/tree/master/rocketmq-connect]/
>  [OpenMessaging Connect 
> API|https://github.com/openmessaging/openmessaging-connect]
> h3. Mentor
> [duhengfore...@apache.org|mailto:duhengfore...@apache.org], 
> [vongosl...@apache.org|mailto:vongosl...@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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



Re: Invitation to exhibit at Airflow Summit: June 2020/Silicon Valley

2020-03-17 Thread Jarek Potiuk
Just one correction. The corerct CFP link is here:
https://pretalx.com/apache-airflow-summit-bay-area-2020/cfp - I sent a
wrong one initially :(.

J.

On Tue, Mar 17, 2020 at 3:24 AM Sally Khudairi  wrote:

> Hi folks --the event has just been postponed until the Summer and will be
> an online event.
>
> Those interested in participating can submit a presenation at
> https://pretalx.com/orga/event/apache-airflow-summit-bay-area-2020/cfp/text
> through 4 April.
>
> Kind regards,
> Sally
>
> - - -
> Vice President Marketing & Publicity
> Vice President Sponsor Relations
> The Apache Software Foundation
>
> Tel +1 617 921 8656 | s...@apache.org
>
> On Wed, Mar 4, 2020, at 10:17, Sally Khudairi wrote:
> > Hello ComDev-ers.
> >
> > The Apache Airflow community will be holding their first-ever Airflow
> > Summit https://airflowsummit.org 4-5 June in Mountain View, CA, and
> > have offered a booth for the ASF to exhibit at during the event.
> >
> > We are looking for 2 individuals who can staff the booth (11AM-5PM; you
> > will also be able to attend sessions), etc.,
> >
> > Please let me know if any local community members are interested/able
> > to participate.
> >
> > Many thanks in advance,
> > Sally
> >
> > - - -
> > Vice President Marketing & Publicity
> > Vice President Sponsor Relations
> > The Apache Software Foundation
> >
> > Tel +1 617 921 8656 | s...@apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

-- 
+48 660 796 129


Re: Welcome

2020-03-17 Thread Manish Sharma
Hii linzarni

On Tue, 17 Mar 2020 at 13:30, linzarni shwe 
wrote:

> Hello


Welcome

2020-03-17 Thread linzarni shwe
Hello 

Re: [ANNOUNCE] - Establishing ALC Warsaw Chapter

2020-03-17 Thread Priya Sharma
Congratulations ALC Warsaw. Wish you a great journey ahead!!

Best wishes,
Priya

On Mon, 16 Mar 2020 at 18:30, Tomasz Urbaszek  wrote:

> Thanks Swapnil for help and this great news!
>
> T.
>
> On Mon, Mar 16, 2020 at 1:40 PM Jarek Potiuk  wrote:
>
> > Great to be part of it ! Thanks Swapnil!
> >
> > J.
> >
> >
> > On Mon, Mar 16, 2020 at 1:34 PM Swapnil M Mane 
> > wrote:
> >
> > > Hello all,
> > >
> > > ComDev PMC is pleased to announce our next Apache Local Community [1]
> > > ALC Chapter - ALC Warsaw [2] and Tomek Urbaszek as ALC Warsaw Chapter
> > > lead.
> > >
> > > We have the following members in ALC Warsaw:
> > >
> > > 1. Andrzej Bialecki
> > > -- ASF Member
> > > -- PMC (Lucene, Incubator, Gora)
> > >
> > > 2. Jarek Potiuk
> > > -- PMC (Airflow)
> > >
> > > 3. Tomek Urbaszek
> > > -- Committer (Airflow)
> > >
> > > 4. Kamil Breguła
> > > -- Committer (Airflow)
> > >
> > > Congratulations to the ALC Warsaw Chapter and wishing them the best
> > > luck for their future events.
> > >
> > > [1] https://s.apache.org/alc
> > > [2] https://s.apache.org/alc-warsaw
> > >
> > > Best regards,
> > > The Apache ComDev team,
> > > community.apache.org
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> >
> > --
> > +48 660 796 129
> >
>


Re: GSOC: mentor/student matching - enforce specific student/friend?

2020-03-17 Thread Thomas Andraschko
Ping :D

Thomas Andraschko  schrieb am Di., 10. März
2020, 08:57:

> 1) Where is it? :D But can i or the student enforce that we work together?
>
> 2) no really :) Probably 1-1,5 months, it was just a example.
> I'm currently talking with some other community member for other ideas
>
> Am Di., 10. März 2020 um 01:06 Uhr schrieb Maxim Solodovnik <
> solomax...@gmail.com>:
>
>> (soft move to correct ML)
>>
>> Hello Thomas,
>>
>> On Tue, 10 Mar 2020 at 01:37, Thomas Andraschko 
>> wrote:
>> >
>> > Hi @all,
>> >
>> > i'm PMC in several JavaEE related projects at Apache and never
>> participated
>> > in GSOC or similar.
>> > As you all may know, the JavaEE world is currently migrating to
>> JakartaEE.
>> > Therefore there are many maintenance tasks in all those projects like
>> > renaming javax.*->jakarta.*, Java11 migration, JUnit5, ...
>> >
>> > I now have a friend that is currently studying and wants to take part in
>> > the GSOC.
>> > We live in the same city and we have been working together.
>> > I would really like to be matched with this particular student when he
>> > makes his project proposal.
>> >
>> > I have 2 questions about this matter:
>> >
>> > 1) How can i take part in this matching decision?
>>
>> there is "Want mentor" button :)))
>>
>> >
>> > 2) Would one story like "Apache BVal maintenance" with some substories
>> > (like "javax->jakarta", java 11 migration, etc) be enough?
>>
>> The task sounds trivial
>> Do you believe it can be estimated in 3 months of full time work?
>>
>> >
>> >
>> > Thanks.
>> >
>> > Best regards,
>> > Thomas
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>