Re: [ease-dev] GSoC Final Work Submission, Sign and Verify Script

[<Christian.Pontesegger@xxxxxxxxxxxx>]

Hi Varun,

 

regarding Googles requirements both ways of publishing your results are fine. Also the content should be sufficient. For your personal merits I would choose the blog post as it is public and will show up in google searches for your name after some time.

 

Christian

 

From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Varun Raval
Sent: Monday, August 22, 2016 7:22 PM
To: ease developer discussions; Christian Pontesegger
Subject: [ease-dev] GSoC Final Work Submission, Sign and Verify Script

 

Hi Christian,

As part of GSoC Work submission, we needed to prepare a documentation containing all the things we have done as part of GSoC. These things has to be mentioned in such a way that anyone reading it is clear to use and extend the work done. See Work Product Submission Guidelines.

I have created following documents. [1] is a Google Word Document shared online. [2] is a blog post. Both contain the same content and we can submit anyone of them.

What are your suggestions regarding the format and which one to share?

[1]: https://docs.google.com/document/d/1xWA3TiPQVgPvY_f-DPPJYihptfG4L92_3zb0vA6VVf8/edit?usp=sharing
[2]: https://varunravalblog.wordpress.com/2016/08/22/gsoc-project-overview/

Thanks,

--

Varun Raval

Attachment: smime.p7s
Description: S/MIME cryptographic signature