[GSoC '17] Colander Serialization

[Parth Verma]

Hi,

I am Parth Verma, a Maths and Computing student from IIT Kharagpur, India. I am interested in pursuing the project 'Colander Serialization'  in Colander for GSoC 2017. I have started looking at issues #133 and #80 for the same. Is there any pointers that have to be kept in mind while doing it?

Please reply.

Parth Verma.

[Michael Merickel]

Hey Parth!

The biggest issue is that we want to improve Colander but we don't want to leave current users in a pickle so compatibility is a big concern. Colander is heavily used by a few different projects that we care a lot about. Cornice and Deform are the first 2 that come to mind. Research will need to be done here to evaluate a path forward for the library. My initial thought is to add support behind a flag in the 1.0 branch and then release a 2.0 branch where we switch the defaults. We would also warn users and work with Cornice and Deform to update their code to work with the 2.0 branch. There are several users on those issues you mentioned that have tackled this problem and we would also probably to get some insights from them on their use-cases and solutions.

Please keep in mind that you're not the first student to express interest in this project and we still need to evaluate proposals and likely only one student will get accepted through GSoC so you may want to apply to multiple projects.

- Michael

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/c758a23f-721e-4641-8ee1-6bd005fe21df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Parth Verma]

Thanks for the reply Michael.

You talked about also applying for other projects. Does that mean other pylons projects or other orgs?

On Friday, 10 March 2017 01:45:04 UTC+5:30, Michael Merickel wrote:

Hey Parth!

The biggest issue is that we want to improve Colander but we don't want to leave current users in a pickle so compatibility is a big concern. Colander is heavily used by a few different projects that we care a lot about. Cornice and Deform are the first 2 that come to mind. Research will need to be done here to evaluate a path forward for the library. My initial thought is to add support behind a flag in the 1.0 branch and then release a 2.0 branch where we switch the defaults. We would also warn users and work with Cornice and Deform to update their code to work with the 2.0 branch. There are several users on those issues you mentioned that have tackled this problem and we would also probably to get some insights from them on their use-cases and solutions.

Please keep in mind that you're not the first student to express interest in this project and we still need to evaluate proposals and likely only one student will get accepted through GSoC so you may want to apply to multiple projects.

- Michael

On Wed, Mar 8, 2017 at 10:05 PM, Parth Verma <vermap...@gmail.com> wrote:

Hi,

I am Parth Verma, a Maths and Computing student from IIT Kharagpur, India. I am interested in pursuing the project 'Colander Serialization'  in Colander for GSoC 2017. I have started looking at issues #133 and #80 for the same. Is there any pointers that have to be kept in mind while doing it?

Please reply.

Parth Verma.

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.

[Michael Merickel]

On Thu, Mar 9, 2017 at 10:57 PM, Parth Verma <vermap...@gmail.com> wrote:

You talked about also applying for other projects. Does that mean other pylons projects or other orgs?

Both!