Tagged: instructions Toggle Comment Threads | Keyboard Shortcuts

  • Andrea Middleton 7:55 pm on June 7, 2011 Permalink | Reply
    Tags: , instructions   

    Student Status 

    We are two weeks into the coding period, and I thought I’d give everyone a sense of where they stand at this time. These are not official grades and will not be reported – these are imaginary grades.  We made them up to give you an idea of how you’re doing so far.

    The intention here is not to frighten or shame anyone, but rather give you each a sense of where you stand right now.  In years past, one or two students have been surprised to learn they were failing at midterm and said they didn’t know why.  If you don’t have an A or B right now, you need to step up your efforts: maintain regular communication with your mentors and make sure your weekly update is detailed and posted on time.

    As a reminder, this program is a full-time job, and you should be putting in full-time hours. If you are not on track to have a functioning prototype by midterm, you should contact your mentors and me immediately so we can help you determine your best course of action so you can make that deadline.

    A = students who completed all assigned tasks on time
    B = students who completed all assigned tasks, but have posted late at least once
    C = students who missed a weekly update or other task before coding began
    D = students who missed a weekly update after coding began
    F = students who missed multiple weekly updates

    A = Mert, Jacob, Ben, Marko
    B = Stas, Kuba, Jakub
    C = Prasath, David, Lucasz
    D = Mihai
    F = Anirudh

    Incomplete = Wojtek (due to illness)

    If you have a question about what task you have missed or completed late, please email me at andrea@automattic.com for clarification.

     
    • Stas Sușcov 9:37 am on June 8, 2011 Permalink | Reply

      Nice idea, I like that!
      @andreamiddleton could you add the tags widget to our p2.
      Thanks in advance.

      • Andrea Middleton 12:29 pm on June 8, 2011 Permalink | Reply

        Done! 🙂

    • Anirudh 4:45 pm on June 8, 2011 Permalink | Reply

      Thanks for the update! I will surely increase my working hours and try to be ahead of schedule from now on, so that I can still be on track. Will take this in the right spirit and work harder.

    • Andrew Nacin 6:01 pm on June 8, 2011 Permalink | Reply

      Looks like you have Jacob but are missing Jakub. Or are missing Jacob and spelled Jakub wrong. 🙂

      • Andrea Middleton 6:05 pm on June 8, 2011 Permalink | Reply

        Oops! Jakub now has his very own imaginary grade.

  • Andrea Middleton 12:49 am on May 7, 2011 Permalink | Reply
    Tags: instructions   

    Students and mentors, please find below a draft schedule for your IRC chats. All chats will be scheduled for 17:00 UTC; if you are unable to attend a chat at this time or on your scheduled day, please leave a comment on this post by Saturday 22:00 UTC so we can revise the schedule over the weekend to publish it by Monday.

    Chat windows will be one hour and will include three students. They’ll be held at irc.freenode.net #wordpress-gsoc, just like the pre-selection chats.

    Tuesday:
    Anirudh S. (Refresh Android UI) – Dan Roundhill, Isaac
    Mert Yazicioglu (WordPress Move) – Pete Mall, Brian Layman
    Wojtek Szutnik (Enhanced emails) – Aaron Campbell, Justin

    Wednesday:
    David Julia (Template Versioning) – Ocean90, Nacin, Koop
    Jakub Tyrcha (Full-throttle Trac Annihilation) – Dion, duck_, scribu, Nacin
    Marko Novakovic (Language Packs) – Nacin, Nikolay

    Thursday:
    Jacob Gillespie (File uploader Upgrade) – Koop, azaozz
    Lukasz Koprowski (Threaded comments) – Westi, Koop
    Mihai Chereji (Local Storage Drafts backup) – Filosofo, mitcho, azaozz and Koop

    Friday:
    Ben Balter (Document Revisions) – Mitcho, duck_, Jorbin
    Prasath Nadarajah (Extending WP Webservices) – Thorsten, Eric Mann
    Stas Suscov (learn.wordpress.org) – Jtrip, Jeremy Boggs

    Again, if your assigned chat creates a schedule conflict, please comment no later than Saturday 22:00 UTC.

     
    • Dion Hulse (dd32) 1:16 am on May 7, 2011 Permalink | Reply

      3-4 AM I won’t be able to do if it requires any input. latest I could do would be starting at 12:00UTC, or after, 20:00UTC

    • Andrew Nacin 2:33 am on May 7, 2011 Permalink | Reply

      I would like the Wednesday chat to start at 1800 UTC, at the very least. As Wednesday is the main dev chat (and this one is a major one for the dev cycle) it will likely run long and then involve tickets and triage. (And then heavy core work for the next few hours.) I won’t be able to handle the overlap.

      I think it’s understandable that even with just a time change I will not be looking forward to Wednesday. 🙂 As Wednesday and Thursday are loaded with core developers, perhaps it would be okay to also just switch the Wednesday schedule with Tuesday (I have a company meetup come Friday).

    • Dion Hulse (dd32) 3:18 am on May 7, 2011 Permalink | Reply

      Perhaps we can do Wednesday at 15:00UTC? That would require a hard-end to the SoC chat @ 1hr to allow for the Dev chat though. That would suit me as well, as I can then make it to both chats if they’re the same night (But past 1700UTC is really pushing it for me esp. if it gets swapped for Tuesday as there’s no way I’ll make it 2 nights at early AM)

      • Kuba Tyrcha 7:53 am on May 7, 2011 Permalink | Reply

        15:00 UTC is just a little too late for me, I would need the chat to be at least 30 mins earlier if it’s supposed to last ~1hr.

        • Dion Hulse (dd32) 8:08 am on May 7, 2011 Permalink

          No problem for me, earlier obviously suits better. I’ve just realised I’ll be unavailable Thursday/Friday as well.

        • Kuba Tyrcha 8:23 am on May 7, 2011 Permalink

          The earlier, the better. 13 UTC = best time for me, 14 UTC is great, too.

    • Kuba Tyrcha 7:50 am on May 7, 2011 Permalink | Reply

      I would like to chime in about Wednesday: I must leave around 15, maybe 16 UTC, and I will be back around 21:30 UTC. Tuesday is fine for me, as well as Thursday.

    • ocean90 7:53 pm on May 7, 2011 Permalink | Reply

      Are these dates only for one chat or is it each Wednesday for me?

      • andreamiddleton 11:03 pm on May 7, 2011 Permalink | Reply

        These dates are only for one chat.

        • ocean90 11:19 am on May 8, 2011 Permalink

          Thanks.
          The next two weeks I can’t be available for a chat.

    • Justin Shreve 4:27 am on May 8, 2011 Permalink | Reply

      I’m actually out all this week – I will catch up from the logs though and possibly try to pop in from my phone.

  • Jane Wells 9:41 pm on May 3, 2011 Permalink | Reply
    Tags: , instructions,   

    Week 3 Instructions 

    Week 1: You wrote intros, and filled in your project pages (if you still haven’t done this, seriously, do it right now)

    Week 2: You are talking about your scope and schedule with your mentors. You will update your project pages by Friday based on these discussions.

    Week 3: We will be setting up an IRC chat for each of you to tell the dev community about your project, get feedback on any ideas you’re still considering, etc. Chats should be relatively short (15-30 minutes) in most cases, though if you have gotten a lot of people excite with your project, it may go longer. We’ll post a schedule next week; since most of the dev community is trained to attend the dev chats in IRC on Wednesdays, we will probably try to schedule most of the chats around the time period, but on different days.

    For some people this will be an inconvenient time. That’s something we have to deal with in an open source project. If anyone is not able (vs it being inconvenient) to attend a chat around 16:00 UTC-ish, please leave a comment giving your schedule restrictions so we can try to schedule appropriately. Andrea will post a draft schedule here later this week to get everyone confirmed before we publish it on wpdevel on Friday. Once it’s published, people will follow the links back here to read about the projects, so make sure you have updated your page here based on the talks with your mentors by then.

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel