Closed vcoisne closed 5 years ago
JFYI as we know from https://github.com/src-d/reading-club#past-papers - code2seq
is a followup paper from the same authors with improved architecture and better results.
@bzz should it be a code2seq paper review then? Do you or someone on your team has bandwidth to write it ?
I would be happy to take a stab as this next week, before/after FOSDEM as it is a fairly low-hanging fruit (comparing e.g \w refactoring one) and if @creachadair agrees.
Writeup like that usually takes about 2 days of work.
JFYI It's a really good time to do that right now, as https://code2seq.org/ was just released on top of already existing https://code2vec.org/
@bzz awesome, so the plan is to publish the week after Fosdem?
@bzz awesome, so the plan is to publish the week after Fosdem?
would be happy to start putting together a draft asap, but as mentioned in https://github.com/src-d/blog/issues/272#issuecomment-457130117 - only after @creachadair 👍
This sounds like a good idea to me. I do want to make sure we can still make timely progress on C# until that's stable, but otherwise I have no concerns.
I have started the draft last week and I would say it's half-ready. Will try to find time, finish and share it for early review by the end of this week.
@vcoisne do you want it on medium or a company blog?
@bzz company blog + medium as a syndication platform :) Hopefully the migration to Ghost will be completed by then cc @marnovo
Asking, as so far I only posted to one OR another - formatting is different and takes a lot of time for me for each of those.
So, please let me know if that is not the case, but so far I'm planing to:
@bzz we can do the formatting for you. No need to submit a PR to https://github.com/src-d/blog, just share with me the gdoc and we'll take it from there!
Initial blog post draft moved to DevRel/Blog on Team's GDrive.
It's still WIP but I hope to have some spare cycles next week to finish it!
@bzz thanks! Did you get a chance to work on it some more ? should we review it ?
Sorry for delay - this is the first time that I want to also include a notebook with the official code to reproduce the whole model right in the text of the blog post (in the spirit of the web-first, participatory science) and I've been spending all my cycles to get the Notebook running, which is now in reasonable state to share.
I will get back to the text and make a final pass over it this week and ping for review. Thank you for the patience!
At last! Had some time this week to work on this and feel that it's almost ready 🎉🎉🎉 The latest draft in this doc.
Mad props to @m09 @creachadair and @Jan21 for proof-reading, copy-editing and otherwise improving it - please let me know if any of you guys would be open to co-author it on company's blog this and I'll be happy to add you!
One last thing that is left to improve later this week (and before publication) - I need to update the notebook to reproduces code2seq with a prep-process dataset that I already have, otherwise it's too CPU intensive and never finishes with correct results on Collab.
Per our conversation @bzz let's set the deadline to 7/29
Thanks
@vcoisne done, I think it is ready for the publication:
From what I can tell, this is also the first blog post that we release accompanied by an interactive notebook where the reader can, in a spirit of the web-first, participatory science, play with the tech underneath the paper (using the OSS code, publish by original authors).
@bzz sorry about dropping the ball on this. Scheduled for tomorrow
Management
This section will be filled by @campoy.
NOTE Please write in short lines so the review is easier to do.