chapel-lang/chapel-summer-of-code

Public channel for questions and discussion around summer of code programs (GSoC, RGSoC)

Kritansh Mehrotra

@cyberdynamo

okayy

How many proposals accepted in Chapel btw @lydia-duncan

Lydia Duncan

@lydia-duncan

You’ll find out in 2 hours ;)

Kritansh Mehrotra

@cyberdynamo

lol okay

Omar

@omar-3

Anyways thanks for all the mentors for tolerating our nagging and spamming and our not-so-smart ideas ... Not every organization has such cool mentors ＼(^o^)／

Kritansh Mehrotra

@cyberdynamo

None of my proposal selected :-(

Sai Rajendra Immadi

@immadisairaj

Congrats @ankingcodes @Aniket21mathur @rahulghangas @Rapiz1 for getting selected into GSoC

All the best in your summer of code journey

Kritansh Mehrotra

@cyberdynamo

Only four peoples selected in Chapel this year?

Sai Rajendra Immadi

@immadisairaj

@cyberdynamo yes, that is what is in the GSoC page

Lydia Duncan

@lydia-duncan

Yup. We had a lot of strong candidates, there were some tough decisions made. Thanks to everyone that applied and we hope to continue to work with you all!

Sai Rajendra Immadi

@immadisairaj

@lydia-duncan if there is no problem then can you share where I have gone wrong so it would be really helpful

Omar

@omar-3

me too :"))

Kritansh Mehrotra

@cyberdynamo

I applied for Builtin Exceptions in Chapel but not selected

Lydia Duncan

@lydia-duncan

We try not to give individual feedback in a public forum. We are not able to give everyone individual feedback, but we have tried to give some feedback in the past, typically over email. It may be a little while before we can do that, though

Sai Rajendra Immadi

@immadisairaj

@lydia-duncan yeah sure I agree. I hope to get feedback even if it takes time. Thanks

Kritansh Mehrotra

@cyberdynamo

Agree with @immadisairaj

Ben Albrecht

@ben-albrecht

Thank you to everyone who applied. As @lydia-duncan mentioned, we had many great candidates this year, which made it really difficult to choose only 4 students.

Ankush Bhardwaj

@ankingcodes

Thank you @immadisairaj for your wishes, my mentors and members of Chapel community for having faith in me and selecting me. Congratulations to @rahulghangas @Rapiz1 and @Aniket21mathur. Special thanks to @ben-albrecht who had been so patient and guided me with my project. Looking forward to working hard this summer. :)

Omar

@omar-3

okay sure thanks for guiding us really :D ... About the iterator module, If I'm going to keep working on the module, should I keep working on it as mason package or make a pull request to the itertools module in the master branch? @ben-albrecht

I just don't want to waste the time I have put in the proposal phase :")

Aniket Mathur

@Aniket21mathur

Thank you @immadisairaj <3. Congratulations @rahulghangas @Rapiz1 and @ankingcodes . Thank you to all the mentors for their support throughout <3

Ben Albrecht

@ben-albrecht

@omar-3 - I encourage you to continue working on the itertools mason package, as it is still a useful contribution to the community. The itertools code checked into test/library/packages/itertools pre-dates the existence of the unit test framework, which is why we put it there instead of a mason package to begin with. If there were a stable itertools mason package, I think we could propagate that code into the mason package.

Raktim Malakar

@raktim2015

Congratulations @Aniket21mathur @ankingcodes @rahulghangas @Rapiz1

Rapiz

@Rapiz1

Thanks to all of you! I'm so excited to get selected and looking forward to contributing to Chapel this summer!

Rahul Ghangas

@rahulghangas

Thanks @immadisairaj @raktim2015 . And congratulations @Aniket21mathur @ankingcodes @Rapiz1

parthsarthiprasad

@parthsarthiprasad

I've been facing a trouble with one of the test, can someone run this command and please verify that the test passes or is it just my system's problem.

cd $CHPL_HOME
./util/start_test  ../test/types/string/kbrady/search.chpl

Rapiz

@Rapiz1

@parthsarthiprasad If you are at $CHPL_HOME, then ../test should be ./test, right?

parthsarthiprasad

@parthsarthiprasad

Yeah run that

Rapiz

@Rapiz1

Passed

parthsarthiprasad

@parthsarthiprasad

hmm then it's my branch then. thanks.

Rapiz

@Rapiz1

And I guess there is a nightly CI running on master

Lydia Duncan

@lydia-duncan

A bit late to the party but there are, you can see our nightly testing results here: https://sourceforge.net/p/chapel/mailman/

I recommend only paying attention to the regressions mails, as those are usually the most interesting

And unfortunately you can’t follow the links just yet to see the exact failure modes

RishabhBhatnagar

@RishabhBhatnagar

Hello all, I was looking for projects related to compiler, parser and concurrency to work after the current gsoc period. Can anyone link pointers to the germane projects/issues?

Ankush Bhardwaj

@ankingcodes

Hi @RishabhBhatnagar , to get started with Chapel go to https://chapel-lang.org/contributing.html . I'd also recommend you to check the project ideas list for the ongoing GSoC at https://chapel-lang.org/gsoc/ideas.html and selected projects at https://summerofcode.withgoogle.com/organizations/4605282207924224/#projects to get an idea of which projects might show up next year.

Rapiz

@Rapiz1

@RishabhBhatnagar There are lots of issues about the error message. I think it could be a good start to contribute. You can use the label to filter issues.

arjundashrath

@arjundashrath

Hey there, is this channel valid for GSoC 2021?

Engin Kayraklioglu

@e-kayrakli

I can’t say how many people who are involved in GSoC are still in this room, but I am :)

Hi @arjundashrath!

arjundashrath

@arjundashrath

I'm Arjun, a second year student pursuing computer engineering from Army Institute of Technology, Pune, India. I have a keen interest in working with Chapel for GSoC 2021. I hope to learn and bond with everyone :) . I have a plethora of skills and a vast knowledge of domains like blockchain and software development. I worked as an intern with a software development company in my first year and I am very excited to learn new things

Hello @e-kayrakli nice to meet you!

Lydia Duncan

@lydia-duncan

Welcome! We might end up using a Slack channel instead (and there’s no word on if we’re an accepted org yet) but you’ll hear here if either of those things change!

Engin Kayraklioglu

@e-kayrakli

In the meantime, you can get to know the Chapel community in the main Chapel channel and ask any general questions about Chapel there (https://gitter.im/chapel-lang/chapel)

arjundashrath

@arjundashrath

Thank you @lydia-duncan and @e-kayrakli , i would still love to learn and contribute irrespective of GSoC, I have proper experience in development but I am fairly new to open source, would there be any advice you would like to give about how I go on from here? Thank you so much!

@e-kayrakli yes thank you, I joined the main channel too :)

Engin Kayraklioglu

@e-kayrakli

This is a high-level outline answering that question: https://chapel-lang.org/contributing.html

A doc with more details of the mechanics of contributing to Chapel is here: https://github.com/chapel-lang/chapel/blob/master/doc/rst/developer/bestPractices/ContributorInfo.rst

arjundashrath

@arjundashrath

Thank you, I'll check them out right away!

Where communities thrive

People

Repo info

Activity