Re: [All] GSoC 2022

I have posted two ideas for GSoC mini projects under: https://issues.apache.org/jira/browse/STATISTICS-54 https://issues.apache.org/jira/browse/NUMBERS-186 Alex

Re: [All] GSoC 2022

Le ven. 25 févr. 2022 à 04:39, Matt Juntunen a écrit : > > I just added a similar placeholder issue for geometry: Thanks! I've added GEOMETRY-144 to the list. Regards, Gilles > [...] - To unsubscribe, e-mail:

Re: [All] GSoC 2022

I just added a similar placeholder issue for geometry: https://issues.apache.org/jira/browse/GEOMETRY-145. I hope those are the kinds of ideas we're going for here. Regards, Matt J On Wed, Feb 23, 2022 at 12:05 PM Gilles Sadowski wrote: > > Ping. > > Nothing for "Geometry", "Statistics", ...

Re: [All] GSoC 2022

Ping. Nothing for "Geometry", "Statistics", ... (?) ;-) Regards, Gilles Le mer. 9 févr. 2022 à 14:57, Gilles Sadowski a écrit : > > Hi. > > >>> [...] > > > > > > > > Shall we open a "GSoC 2022" report in each concerned JIRA project? > > > > > > Yes. I think we just create some tickets and tag

Re: [All] GSoC 2022

Hi. >>> [...] > > > > > > Shall we open a "GSoC 2022" report in each concerned JIRA project? > > > > Yes. I think we just create some tickets and tag them with the > > appropriate tag (GSOC 2022 ?). There should be some left over from > > last time to repurpose or use as templates for new ones. >

Re: [All] GSoC 2022

Hello. Le mer. 2 févr. 2022 à 10:47, Alex Herbert a écrit : > > On Mon, 31 Jan 2022 at 15:06, Gilles Sadowski wrote: > > > > Hello. > > > > Le jeu. 27 janv. 2022 à 18:09, Alex Herbert a > > écrit : > > > > > > I would be willing to go through GSOC again. > > > > Thanks; I know that back in

Re: [All] GSoC 2022

On Mon, 31 Jan 2022 at 15:06, Gilles Sadowski wrote: > > Hello. > > Le jeu. 27 janv. 2022 à 18:09, Alex Herbert a > écrit : > > > > I would be willing to go through GSOC again. > > Thanks; I know that back in 2020, it had been a disproportionate > amount of work... > > > I think that the > >

Re: [All] GSoC 2022

Hello. Le jeu. 27 janv. 2022 à 18:09, Alex Herbert a écrit : > > I would be willing to go through GSOC again. Thanks; I know that back in 2020, it had been a disproportionate amount of work... > I think that the > statistics component could again serve as a project. There are some > packages

Re: [All] GSoC 2022

I would be willing to go through GSOC again. I think that the statistics component could again serve as a project. There are some packages in Math that could be moved to make use of the updated distributions (e.g. math.stat.inference) or perhaps a reworking of the math.stat.descriptive package to

Re: [All] GSoC 2022

I think this would be a great idea. There's even some potential work that can be done related to fuzz testing if we want to expand our OSS-Fuzz coverage. I imagine we have plenty of interesting Jira tickets that could make for GSoC projects, too. On Wed, Jan 26, 2022 at 7:16 AM Gilles Sadowski

[All] GSoC 2022

Hello. Do we want to come up with a common (Commons) call for contributions? [I.e. identify components/areas/features where help would be appreciated, who can provide "mentorship" (even with strictly limited available time), what level of proficiency (with Java and tooling) is required from

Re: [All] GSoC news?

Hi all, Though I'm not having the GSoC recognition this year I would like to contribute ASF at my best and I begin it from my proposed idea. Hope you all will support me to achieve it. Best Regards, Gimhana. On 4 May 2018 at 04:19, Gilles wrote: > > One of the

Re: [All] GSoC news?

One of the benefits of team work and being part of a "community" is that processes are supposedly more robust, even if not everyone does the right thing all the time. Or so I thought. Gilles On Thu, 3 May 2018 18:39:12 +0100, Mark Thomas wrote: On 03/05/18 15:42, Gilles wrote: On Thu, 3 May

Re: [All] GSoC news?

On 03/05/18 15:42, Gilles wrote: > On Thu, 3 May 2018 13:56:06 +0100, Mark Thomas wrote: >> On 03/05/18 13:15, Gilles wrote: >>> On Thu, 3 May 2018 12:59:04 +0100, Mark Thomas wrote: On 03/05/18 12:41, Gilles wrote: > Hi. > > Should we worry that there is no email traffic about

Re: [All] GSoC news?

On Thu, 3 May 2018 13:56:06 +0100, Mark Thomas wrote: On 03/05/18 13:15, Gilles wrote: On Thu, 3 May 2018 12:59:04 +0100, Mark Thomas wrote: On 03/05/18 12:41, Gilles wrote: Hi. Should we worry that there is no email traffic about the GSoC proposals? Did we have any GSoC proposals?

Re: [All] GSoC news?

On 03/05/18 13:15, Gilles wrote: > On Thu, 3 May 2018 12:59:04 +0100, Mark Thomas wrote: >> On 03/05/18 12:41, Gilles wrote: >>> Hi. >>> >>> Should we worry that there is no email traffic about >>> the GSoC proposals? >> >> Did we have any GSoC proposals? > > Yes.[1] No. Those are not proposals.

Re: [All] GSoC news?

On Thu, 3 May 2018 12:59:04 +0100, Mark Thomas wrote: On 03/05/18 12:41, Gilles wrote: Hi. Should we worry that there is no email traffic about the GSoC proposals? Did we have any GSoC proposals? Yes.[1] Were any accepted? By whom? I have no idea about the formal process but

Re: [All] GSoC news?

On 03/05/18 12:41, Gilles wrote: > Hi. > > Should we worry that there is no email traffic about > the GSoC proposals? Did we have any GSoC proposals? Were any accepted? I recall one mentor request from Commons and I don't see that mentor listed as requesting to mentor a proposal in the (internal

[All] GSoC news?

Hi. Should we worry that there is no email traffic about the GSoC proposals? Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [ALL] GSoC 2010 - accepted projects

Hi everyone, Thanks for the welcome. I'm very pleased to have been accepted into Google Summer of Code under the ASF. I've been a long-time user of Apache software projects, and I'm happy to now have the opportunity to contribute something back. If anyone has any questions for me about my

[ALL] GSoC 2010 - accepted projects

This year, we have two accepted projects for GSoC 2010. Congratulations, Jake and Long! We now begin what GSoC refers to as the community bonding period. So, Jake and Long -- if you have any questions about any aspect of the ASF in general or Commons in particular, please feel free to ask. Theres

Re: [ALL] GSoC 2010 - accepted projects

Dear Rahul, Thank you for your passional and openhanded welcome ceremony :-) It is my honor to do something for Apache, it helps me so much, i should give some feed back, now, opportunity comes, I am pleased to work with you guys. Regards Long 2010/4/29 Rahul Akolkar rahul.akol...@gmail.com

Re: [all] GSoC

The results are out: http://code.google.com/soc/2008/asf/about.html Apache Commons got no slot this year despite some really good applications received. The ranking system was a bit biased toward projects with more mentors, hopefully this will be fixed for the next Summer of Code. Emmanuel

Re: [all] GSoC

On Mon, Mar 10, 2008 at 8:47 PM, Henri Yandell [EMAIL PROTECTED] wrote: I'd been struggling - Codec has some phonetic codecs to implement, but there's not a huge amout there. CSV could be hooked to Performance. There are lots of places that could use improved unit tests. Generally though -

Re: [all] GSoC

On 3/10/08, Henri Yandell [EMAIL PROTECTED] wrote: I'd been struggling - Codec has some phonetic codecs to implement, but there's not a huge amout there. CSV could be hooked to Performance. There are lots of places that could use improved unit tests. Generally though - it always feels that

Re: [all] GSoC

There are some TODOs for Commons Configuration that may fit as GSoC topics : CONFIGURATION-312 WindowsConfiguration CONFIGURATION-258 JSON configuration CONFIGURATION-198 OGDL configuration CONFIGURATION-201 YAML configuration These are new configuration formats, it might be interesting

Re: [all] GSoC

Feel free to add it to the wiki. Would you do the mentoring? Just wondering if that isn't a bit too little work for 1-2 month full time. cheers -- Torsten On 10.03.2008, at 12:05, Emmanuel Bourg wrote: There are some TODOs for Commons Configuration that may fit as GSoC topics :

Re: [all] GSoC

Hi! Any idea for GSoC [1]? I think it would be worth participating VFS or IO: File Alteration Monitor with native support (I can sponsor some basic code-base for linux). If it is located in IO or in another package it should be possible to plugin VFS. Means, should not deal with plain

Re: [all] GSoC

Torsten Curdt a écrit : Feel free to add it to the wiki. Would you do the mentoring? Yes I'll be available to do the mentoring. Just wondering if that isn't a bit too little work for 1-2 month full time. Writing only one configuration is probably not long enough for 2 months (btw writing

Re: [all] GSoC

I'd been struggling - Codec has some phonetic codecs to implement, but there's not a huge amout there. CSV could be hooked to Performance. There are lots of places that could use improved unit tests. Generally though - it always feels that we lack something big enough. Which makes sense; we're a