R-yan/l1ving_youtube-dl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update ENTREGA1.md

Browse Source 
minor text fixes
This commit is contained in:
Vitor Esteves 2016-10-16 22:41:56 +01:00 committed by GitHub
parent a273cbe368
commit 47f5b5ddf6
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ESOF-Docs/ENTREGA1.md
View File

@ -11,11 +11,11 @@ Once the video is fully downloaded, use any video player, such as **mpv**, **vlc
## Development Process
In order to know more about the development process of this project, we decide to inquire some of the top contributors (past and present) in order to try and acquire a closer and more personal to the project look on the way it was developed.
In order to know more about the development process of this project, we decide to inquire some of the top contributors (past and present) to try and acquire a closer and more personal look on the way it was developed.
After meeting with the workgroup members we wrote an email directed to them and awaited response. We were later contacted by the project founder and one of the main contributors of **Youtube-DL** [Ricardo Gonzalez](https://github.com/rg3) .
He went on to explain that the project started as a very short script to download videos from **Youtube**, it had no process model to follow, and no long term development plan. So with lack of organization or any sort of software development process soon Ricardo ran into an unanticipated issue **modularity**, after receiving some feedback he quickly realized adding support to new websites was crucial. This raised some problems as the application was conceived only to download videos from *youtube*.Ricardo started to separate the operation into modules like: the downloader and the info extractor. The second one would find metadata from the video URL and the first one would download it in the user selected format.
He went on to explain that the project started as a very short script to download videos from **Youtube**, it had no process model to follow, and no long term development plan. So with lack of organization or any sort of software development process soon Ricardo ran into an unanticipated issue :**modularity**. After receiving some feedback he quickly realized adding support to new websites was crucial. This raised some problems as the application was conceived only to download videos from *youtube*.Ricardo started to separate the operation into modules like: the downloader and the info extractor. The second one would find metadata from the video URL and the first one would download it in the user selected format.
After some time, things kept evolving in the same direction. The new developers separated the earlier designed code into modules, improving future error spotting, practicality and made it easier to add user requested features as download options, even though none of these were projected features and the project never really did fit any concrete design process some correct decisions were taken in an organic way. Some features however continue missing such as the a validation activity or a defined evolution plan.