discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

OpenSCAD / Google Summer of Code Update

TP
Torsten Paul
Mon, Mar 28, 2016 4:27 PM

The student application period is now over and I first want
to thank everybody involved in supporting the students with
preparing the applications and of cause the students who
applied.

We will now review and discuss the final project proposals
which will take some time. The list of accepted projects
will be published by Google on April 22nd.
(https://developers.google.com/open-source/gsoc/timeline)

For the students that applied, please continue to be
involved in that period and make sure to provide at least
one patch that does some code change. It does not have to
be a big thing, but should mainly show you have a development
environment set up and are able to read and understand (a
small part) of the existing source code and make changes to
that. Feel free to find us on IRC to discuss details.

Deadline for the patches to be considered for the selection
decision is Monday April 4th 19:00 UTC.

ciao,
Torsten.

The student application period is now over and I first want to thank everybody involved in supporting the students with preparing the applications and of cause the students who applied. We will now review and discuss the final project proposals which will take some time. The list of accepted projects will be published by Google on April 22nd. (https://developers.google.com/open-source/gsoc/timeline) For the students that applied, please continue to be involved in that period and make sure to provide at least one patch that does some code change. It does not have to be a big thing, but should mainly show you have a development environment set up and are able to read and understand (a small part) of the existing source code and make changes to that. Feel free to find us on IRC to discuss details. Deadline for the patches to be considered for the selection decision is Monday April 4th 19:00 UTC. ciao, Torsten.
AK
Amarjeet Kapoor
Mon, Mar 28, 2016 4:40 PM

On Mar 28, 2016 9:59 PM, "Torsten Paul" Torsten.Paul@gmx.de wrote:

For the students that applied, please continue to be
involved in that period and make sure to provide at least
one patch that does some code change. It does not have to
be a big thing, but should mainly show you have a development
environment set up and are able to read and understand (a
small part) of the existing source code and make changes to
that. Feel free to find us on IRC to discuss details.

Deadline for the patches to be considered for the selection
decision is Monday April 4th 19:00 UTC.

Thanks for sharing. I thought we had time till 20th April.

Would you suggest some issue for which I can write a patch because when I
searched for issues which I can solve and submit as patch mainly for which
I feel confident are already solved but not closed or are the one on which
discussion is going on.
At present thinking of doing refactoring of code in mainwindow file (
mentioned in todo list).

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

On Mar 28, 2016 9:59 PM, "Torsten Paul" <Torsten.Paul@gmx.de> wrote: > For the students that applied, please continue to be > involved in that period and make sure to provide at least > one patch that does some code change. It does not have to > be a big thing, but should mainly show you have a development > environment set up and are able to read and understand (a > small part) of the existing source code and make changes to > that. Feel free to find us on IRC to discuss details. > > Deadline for the patches to be considered for the selection > decision is Monday April 4th 19:00 UTC. Thanks for sharing. I thought we had time till 20th April. Would you suggest some issue for which I can write a patch because when I searched for issues which I can solve and submit as patch mainly for which I feel confident are already solved but not closed or are the one on which discussion is going on. At present thinking of doing refactoring of code in mainwindow file ( mentioned in todo list). -- Amarjeet Singh https://amarjeetkapoor1.wordpress.com https://github.com/amarjeetkapoor1 https://bitbucket.org/amarjeetkapoor
TP
Torsten Paul
Mon, Mar 28, 2016 5:15 PM

Deadline for the patches to be considered for the selection
decision is Monday April 4th 19:00 UTC.

Thanks for sharing. I thought we had time till 20th April.

Yeah, for some reason not all of the Google/Org interaction
dates are listed in the timeline. But for Google being able
to give the results on 22th, they need the org feedback quite
a bit earlier for evaluation.

Right, I looked through the list of issues marked as
"LowHanging" on github and that's indeed mostly non-code
issues. I'll have a look if we mark some other issues too
or post some additional ones.

If you like a bit of a challenge, there's a TODO in the
dependency handling code which looks extremely simple at
first glance, it's a bit more tricky due to having three
platforms (MacOS, Linux, Windows) where the behavior might
be slightly different. So it needs some reading of system
documentation.

https://github.com/openscad/openscad/blob/master/src/handle_dep.cc#L25

This should be related to makefile handling which might
not be the most common use case, but probably helps for
bigger projects. I haven't really used that feature myself
yet.

https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Using_OpenSCAD_in_a_command_line_environment#Makefile_example

ciao,
Torsten.

>> Deadline for the patches to be considered for the selection >> decision is Monday April 4th 19:00 UTC. > > Thanks for sharing. I thought we had time till 20th April. > Yeah, for some reason not all of the Google/Org interaction dates are listed in the timeline. But for Google being able to give the results on 22th, they need the org feedback quite a bit earlier for evaluation. Right, I looked through the list of issues marked as "LowHanging" on github and that's indeed mostly non-code issues. I'll have a look if we mark some other issues too or post some additional ones. If you like a bit of a challenge, there's a TODO in the dependency handling code which looks extremely simple at first glance, it's a bit more tricky due to having three platforms (MacOS, Linux, Windows) where the behavior might be slightly different. So it needs some reading of system documentation. https://github.com/openscad/openscad/blob/master/src/handle_dep.cc#L25 This should be related to makefile handling which might not be the most common use case, but probably helps for bigger projects. I haven't really used that feature myself yet. https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Using_OpenSCAD_in_a_command_line_environment#Makefile_example ciao, Torsten.
AK
Amarjeet Kapoor
Tue, Mar 29, 2016 3:11 PM

Being unable to decide to make patch on any exiting issue I have
decide to submit a patch on new feature of git integration i.e. code
changed in .scad file will be directly committed through openscad.

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

Being unable to decide to make patch on any exiting issue I have decide to submit a patch on new feature of git integration i.e. code changed in .scad file will be directly committed through openscad. -- Amarjeet Singh https://amarjeetkapoor1.wordpress.com https://github.com/amarjeetkapoor1 https://bitbucket.org/amarjeetkapoor "knowledge about knowledge is power"
MK
Marius Kintel
Wed, Mar 30, 2016 2:39 PM

On Mar 29, 2016, at 11:11 AM, Amarjeet Kapoor amarjeet.kapoor1@gmail.com wrote:

Being unable to decide to make patch on any exiting issue I have
decide to submit a patch on new feature of git integration i.e. code
changed in .scad file will be directly committed through openscad.

This sounds like a large feature, which is probably comparable to an entire GSoC project itself.
..and which probably requires a fair amount of discussion.
I would suggestion choosing something a lot easier, unless you have an exceptionally good reason for tackling something this large.

-Marius

> On Mar 29, 2016, at 11:11 AM, Amarjeet Kapoor <amarjeet.kapoor1@gmail.com> wrote: > > Being unable to decide to make patch on any exiting issue I have > decide to submit a patch on new feature of git integration i.e. code > changed in .scad file will be directly committed through openscad. > This sounds like a large feature, which is probably comparable to an entire GSoC project itself. ..and which probably requires a fair amount of discussion. I would suggestion choosing something a lot easier, unless you have an exceptionally good reason for tackling something this large. -Marius
AK
Amarjeet Kapoor
Sat, Apr 23, 2016 5:42 AM

Thanks everyone, for showing confidence in me for GSOC project.

Now how we have to move further? so, that we can utilize this period
for better results in coding period.

Again thanks, everyone. Specially, mentor (@Torsten and @Kintel ) for
being so helping.

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

Thanks everyone, for showing confidence in me for GSOC project. Now how we have to move further? so, that we can utilize this period for better results in coding period. Again thanks, everyone. Specially, mentor (@Torsten and @Kintel ) for being so helping. -- Amarjeet Singh https://amarjeetkapoor1.wordpress.com https://github.com/amarjeetkapoor1 https://bitbucket.org/amarjeetkapoor "knowledge about knowledge is power"
AK
Amarjeet Kapoor
Sat, Apr 23, 2016 6:00 AM

On 23 April 2016 at 11:12, Amarjeet Kapoor amarjeet.kapoor1@gmail.com wrote:

Thanks everyone, for showing confidence in me for GSOC project.

Now how we have to move further? so, that we can utilize this period
for better results in coding period.

Again thanks, everyone. Specially, mentor (@Torsten and @Kintel ) for
being so helping.

And Please also give feedback on proposal that you liked or things
that might become reason for my rejection.

--
Amarjeet Singh
https://amarjeetkapoor1.wordpress.com
https://github.com/amarjeetkapoor1
https://bitbucket.org/amarjeetkapoor

"knowledge about knowledge is power"

On 23 April 2016 at 11:12, Amarjeet Kapoor <amarjeet.kapoor1@gmail.com> wrote: > Thanks everyone, for showing confidence in me for GSOC project. > > Now how we have to move further? so, that we can utilize this period > for better results in coding period. > > Again thanks, everyone. Specially, mentor (@Torsten and @Kintel ) for > being so helping. And Please also give feedback on proposal that you liked or things that might become reason for my rejection. -- Amarjeet Singh https://amarjeetkapoor1.wordpress.com https://github.com/amarjeetkapoor1 https://bitbucket.org/amarjeetkapoor "knowledge about knowledge is power"
MK
Marius Kintel
Sat, Apr 23, 2016 7:18 PM

On Apr 23, 2016, at 01:42 AM, Amarjeet Kapoor amarjeet.kapoor1@gmail.com wrote:

Thanks everyone, for showing confidence in me for GSOC project.

Now how we have to move further? so, that we can utilize this period
for better results in coding period.

Welcome!
You should have gotten en email from Sean outlining general expectations.

Torsten and I will both participate in mentoring. We’re both in different timezones (I’m EST/EDT, Torsten is CET), so hopefully this will be helpful in finding each other online.

In terms of your proposal, it’s a bit ambitious. It would be wise to spend the time before full-time coding starts to create a real project plan based on the proposal.
This plan should be much more clear what should be done, how to break down work into components, as well as what kind of support or work you need from others.
This is probably best to discuss in real-time on IRC.
We will help you with the plan, but exactly how this is done really depends on your skill level and comfort with both C++, Qt and OpenSCAD.

Could give us a general outline of what you think your work schedule will look like in the coming weeks (e.g. morning vs. evening), so we have an idea when you’ll be on IRC.

Feel free to reach out, both here and on IRC.
I’m sure other people will engage in discussions as well :)

Kind Regards

-Marius

> On Apr 23, 2016, at 01:42 AM, Amarjeet Kapoor <amarjeet.kapoor1@gmail.com> wrote: > > Thanks everyone, for showing confidence in me for GSOC project. > > Now how we have to move further? so, that we can utilize this period > for better results in coding period. > Welcome! You should have gotten en email from Sean outlining general expectations. Torsten and I will both participate in mentoring. We’re both in different timezones (I’m EST/EDT, Torsten is CET), so hopefully this will be helpful in finding each other online. In terms of your proposal, it’s a bit ambitious. It would be wise to spend the time before full-time coding starts to create a real project plan based on the proposal. This plan should be much more clear what should be done, how to break down work into components, as well as what kind of support or work you need from others. This is probably best to discuss in real-time on IRC. We will help you with the plan, but exactly how this is done really depends on your skill level and comfort with both C++, Qt and OpenSCAD. Could give us a general outline of what you think your work schedule will look like in the coming weeks (e.g. morning vs. evening), so we have an idea when you’ll be on IRC. Feel free to reach out, both here and on IRC. I’m sure other people will engage in discussions as well :) Kind Regards -Marius