Stand-Up

What have you done, what are you doing, what are you yet to do? 

Adam, Moad

• Allow to use middle mouse click to open from viewlets pinned #14453 [3]

James, Myoran

• Ctrl-Up and Ctrl-Down don’t advance cursor when hits page limit #2091 [5]

• Support to print the editor contents #5953 [10]

Luke, Adam

• Automatically assign tab name from file content #12017 [5]

Luke

• Introduce Google Search functionality when console throws compiler error [7]

Retrospective

The board at the end of the second sprint.

As a reminder:

The group decided to run their retrospectives using a traffic light system.

Green – Things that went well, the types of things we want to replicate
Amber – Things that went okay, but definitely need improving. Also, things that we learned that we must remember for the next sprint.
Red – Things that went badly. Issues that occurred that we must ensure are never repeated again.

Green

– Idea communication continued to be good. The discussion of potential problems and the way in which we assigned those problems was good.
– Trello board was consistently used and updated.
– Continued use of Discord allowed for effect pair programming.
– Lack of pair programming was good, allowed the group to be more efficient
– Not using pair programming logs again allowed for more efficient programming
– Posting of potential solution attached as a .txt file on the Trello board was excellent. It conceptualised the problem and acted as pseudo-code.
– Discussion between teams on potential ways to get around JSON configuration issue was a good example of collaboration.
– Adaptions to Trello board in terms of monitoring workflow were used effectively.

Amber

–  GitHub continues not to be particularly been used well, it has been used to pull down the code but nothing else. This is mainly due to the constraints of the project.
– Getting an actual debug instance running for the project continues to be an issue. Moving from machine to machine can become time consuming. This can only be resolved by using the same machine, or developers become to familiar with the process they can resolve the issue(s) straight away.
– UML diagrams should be completed. Difficult to conceptualise the whole project as VSCode is such a wide scale thing.
– UML for the issues/features the group is working on aren’t wholly appropriate as scale of problem is so small.

Red

–  Burndown chart for sprint cycle 2, in terms of workload was way too ambitious, especially considering the amount of story points the group got through in the first sprint.
– Continued work from last sprint seriously hindered overall progress of the project. Could’ve been handled much better.
– Sizing has been way too small for tasks undertaken.

Burndown Chart – Sprint Cycle 2

Stand-Up

What have you done, what are you doing, what are you yet to do?

Adam, Moad and Luke

James, Myoran

Sprint Board

Issue: https://github.com/Microsoft/vscode/issues/2091

Task Breakdown:
1) Allow cursor to follow the page when scrolling up or down using ctrl+up or ctrl+down
2) Allow it to be configurable

This task was assigned to Myoran Mathusuthan and James Middleton

Issues
Due to the extensive code base, it took some time for us to learn how the code worked and where we should focus are attention on in solving the issue.
To solve the first component of the task it took some time to find the correct variable to change.

The second component was never completed, as our lack of knowledge on how the code interacts made it difficult to find the correct way in implementing this feature. Ultimately we tried several methods, that did not end up working, before time ran out.
Any method that made the option configurable would not have been accepted by the handlers of vscode, as it would not have complied to their standards and so this issue is left uncompleted.

Documentation

Stand-Up

What have you done, what are you doing, what are you yet to do? 

Adam and Moad

• Allow to use middle mouse click to open from viewlets pinned #14453 [3]

James, Myoran

• Ctrl-Up and Ctrl-Down don’t advance cursor when hits page limit #2091 [5]

Retrospective

The board at the end of the first sprint.

Points to note: A ‘Rejected by Admin’ category was added to board. It is important to consider that the work completed may well not be accepted by the VSCode team.

The group decided to run their retrospectives using a traffic light system.

Green – Things that went well, the types of things we want to replicate
Amber – Things that went okay, but definitely need improving. Also, things that we learned that we must remember for the next sprint.
Red – Things that went badly. Issues that occurred that we must ensure are never repeated again.

Green

– Pair programming within a formal environment produced a high work output.
– Idea communication was good. The discussion of potential problems and the way in which we assigned those problems was good. Group discussion!
– The setup and use of the Trello board was good.
– Keeping the Trello cards up-to-date was fantastic. The use of check-lists to monitor workflow was highly effectively. The useof the comments section to engage in a discussion regarding the issue at hand was also excellent.
– The use of Discord for James and Myoran to work was good. No issues and when remote working is recommended over Skype and Slack.

Amber

– Trello board was good, but adaptions needed to be made. A rejection category needed to be added as well as adaptions to ‘current sprint’ category to aid workflow for the following sprints.
– Pair programming for exploration and discussion around resolving an issue, but actual programming/implementation could be done singularly, as in, by ourselves.
– GitHub hasn’t particularly been used well, it has been used to pull down the code but nothing else (see GitHub point in red section)
– Points scaling needs re-thinking. Need a way that contextualises workflow within a student schedule. This means lower points, and more accurately reflecting the hours of put into the work. Developers put in around a normal days work (6-7 hours) on a 3 pointer. We need to consider accurately predicting the tasks.
– Getting an actual debug instance running for the project can be an issue. Moving from machine to machine can become time consuming. This can only be resolved by using the same machine, or developers become to familiar with the process they can resolve the issue(s) straight away.

Red

– Lack of pizza/free stuff from SCRUM master
– Create branch and actually utilise GitHub. We need a commit/push history going to accompany our workflow. This is key for the assessment.
– Actual pair programming seemed ineffective. The actual resolution of bug fixes is better resourced by a single developer,  the scale of the problem does not give itself to pair programming practices.
– Pair programming logs, seemed totally useless. Comments on Trello card were used instead.
– UML, seemed pointless due to scaling of problem again. The problems are already well defined, and we’re mainly completing bug fixes/side features. These do not require UML diagrams.

Kicking off Sprint 2

The new Trello board:

Burndown Chart – Sprint Cycle 1

Sprint 1 Review

Sprint 2 Predictions 

Original Issue

Allow to use middle mouse click to open from viewlets pinned #14453 [3]

Already able to set up by changing a variable in vsCode, so Microsoft wanted to give the middle mouse button.

Initial Task Breakdown

Task was taken up by Adam Plunkett, Moad Zardab and Luke Exton.

After deliberation, several idea’s were formed, two leading ones being middle mouse button clicked on extension installs it, or middle mouse button clicked on a highlighted section searches it in google on the default browser.

Team decided to go for the search function.

To Do List:

• Determine source script for mouse controller/services
• Examine current implementations of middle mouse button events in existing features
• Find example code of browser being opened from vsCode
• Input sanitation for highlighted text query
• Find text highlighting script
• Find appropriate location to dump new code functionality
•  Get search functionality passed to opened browser window with highlighted text.

Task Modifications

After deliberation, it was decided that rather than highlighted section, would just search the word which the cursor is on when middle mouse button is clicked.

Documentation:

Trello: https://trello.com/c/MHWDjT0X/3-allow-to-use-middle-mouse-click-to-open-from-viewlets-pinned-14453-3

Task List

Activity Log 1

Activity Log 2

Activity Log 3