Final evaluations, end of GSoC

[Aman Kumar Gupta]

Yes, I'm submitting the status report itself. I was asking about our code's
links that we'll include in the status report. I've created the diifs on
phabricator and attached the links to them in the Status report. That's
fine?

Aman



On Sat, Aug 11, 2018 at 3:12 PM, Valorie Zimmerman <
valorie.zimmerman at gmail.com> wrote:

> Please use the link that was created for you: your Status Report on the
> wiki
>
> Valorie
>
> On Fri, Aug 10, 2018 at 11:50 PM, Sagar Hani <sagarhani.kde at gmail.com>
> wrote:
> > Hi Aman,
> >
> > Yeah, once your branch is merged to master, we may not be able to access
> > your branch.
> > Providing phabricator diff links makes sense to me.
> >
> > Thanks,
> > Sagar
> >
> > On Fri, Aug 10, 2018 at 5:50 PM, Aman Kumar Gupta <gupta2140 at gmail.com>
> > wrote:
> >>
> >> We are thinking if the phabricator diff links would be good? As they are
> >> always valid (open-able) even when closed.
> >>
> >>
> >> On Fri, Aug 10, 2018 at 4:25 PM, Aman Kumar Gupta <gupta2140 at gmail.com>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I have a doubt regarding submitting the overall work and commit link.
> >>>
> >>> Is it fine to give the branch link where I'm working, in the status
> >>> report?
> >>>
> >>> I and my mentors were discussing on it and have a concern that the
> branch
> >>> will not remain forever..when it'll be merged into master later, the
> branch
> >>> will be deleted and the URL to the branch won't be valid anymore.
> >>> So this may cause some difficulties if someone (a recruiter) in future
> >>> may want to have a look at the commits link and land on an invalid URL.
> >>>
> >>> What should we do? How should we preserve it?
> >>>
> >>> Thanks,
> >>> Aman Kumar Gupta
> >>>
> >>> On Thu, Aug 9, 2018 at 4:59 PM, Valorie Zimmerman
> >>> <valorie.zimmerman at gmail.com> wrote:
> >>>>
> >>>> Hi again students,
> >>>>
> >>>> On Wed, Aug 1, 2018 at 12:29 AM, Valorie Zimmerman
> >>>> <valorie.zimmerman at gmail.com> wrote:
> >>>> > Hi students!
> >>>> >
> >>>> > I can't believe, but we're already nearing the end of GSoC for the
> >>>> > year.  According to a recent email from GSoC staff to me:
> >>>> >
> >>>> > "Next week students will begin submitting their Final Evaluations
> for
> >>>> > GSoC 2018 (starting Monday, August 6). We have encouraged students
> to
> >>>> > reach out to you to share a preview of their submission URL and let
> >>>> > you verify it meets Google's and your requirements before they
> submit.
> >>>> > Students can not edit their evaluations once they have submitted
> them
> >>>> > — it's in their best interest to have you review the link first.
> >>>> > Students must submit their Final Evaluations (with the submission
> URL)
> >>>> > before Tuesday, August 14 at 16:00 UTC."
> >>>> >
> >>>> > Please do share your final with your mentors ASAP. Many of them will
> >>>> > be traveling to Akademy (along with some of you) so don't wait! If
> you
> >>>> > aren't quite done, still ask them to look, and listen to their
> >>>> > suggestions.
> >>>> >
> >>>> > All the best wishes for a successful conclusion,
> >>>> >
> >>>> > Valorie for the KDE GSoC admins
> >>>>
> >>>> Update: now is the time to finish your evaluation. Please remember to
> >>>> update your Status Page first, because once you submit it the URL will
> >>>> be locked. Once the program is over you can continue to update with
> >>>> more screenshots etc. as you support your code, and will be able to
> >>>> use this link in uni situations and applications for employment.
> >>>>
> >>>> Some of your mentors are now in transit to Akademy -- along with some
> >>>> of you! So please get the evaluation done soon. If you do not finish
> >>>> it before the deadline you will fail yourself, which would be a
> >>>> terrible pity.
> >>>>
> >>>> All the best,
> >>>>
> >>>> Valorie
> >>>
> >>>
> >>
> >
>
>
>
> --
> http://about.me/valoriez
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-soc/attachments/20180811/3b7a4247/attachment.html>