Interested in contributing to KDE

[Abhishek Sood.A]

*Abstract:*  I plan to design an interface for Youtube integration with
KMplayer by writing a separate KMplayer interface-plugin that can be
minimized and the uploading runs as a background process while KMplayer can
be used to watch the video in foreground process. This feature is similar to
the video upload on the facebook. Thus it allows the user continue using
KMplayer player while the upload happens in the background.ontent:








 Content: *Personal Information
*

First Name: Abhishek

Surname: Sood

*Project*

**

*Summary: *

I plan to design an interface for Youtube integration with KMplayer by
writing a separate KMplayer interface-plugin that can be minimized and the
uploading runs as a background process while KMplayer can be used to watch
the video in foreground process.  This feature is similar to the video
upload on the facebook. Thus it allows the user continue using KMplayer
while the upload happens in the background.



*Details: *

*Youtube data APIS*

The YouTube Data API allows applications to perform functions normally
executed on the YouTube website. The API enables the application to search
for YouTube videos and to retrieve standard video feeds, comments and video
responses. In addition, the API lets the application upload videos to
YouTube or update existing videos. The application can also retrieve
playlists, subscriptions, user profiles and more. Finally, the application
can submit authenticated requests to enable users to create playlists,
subscriptions, contacts and other account-specific entities.

The YouTube Data API provides two methods for uploading videos to YouTube. A
newly uploaded video will be included in a user's uploaded videos feed a few
minutes after the upload completes and YouTube finishes processing the
video. In addition, a newly uploaded video will typically be included in
search results a couple of hours after the upload completes and YouTube
finishes processing the video. However, this delay may be longer during
periods of heavy API server loads.

   -

   *Browser-based uploading* allows you to accept video uploads from The
   users without having to handle, host or proxy the actual video files. You
   should choose a browser-based uploading process if you do not want to host
   or store the uploaded video files.
   -

   *Direct uploading* allows you to add videos that are in The video library
   to YouTube. You should choose a direct-upload implementation if you want to
   host or store videos uploaded through The site and also add those videos to
   YouTube. In a direct-uploading scenario, when a user uploads a video through
   The site, the video will be sent to The servers. The application will
   subsequently send an API request to upload the video from The server to
   YouTube.


Browser-based upload

The following diagram illustrates the browser-based uploading process. The
application might have already completed the authentication process before
these steps occur. However, you could also choose to have the user provide
the video metadata before completing the authentication process.

The image shows the following steps:

   1.

   The site displays a form in which the user will enter details about the
   video being uploaded.
   2.

   The user enters the video details, such as the title, description and
   category for the video.
   3.

   The site sends an HTTP POST request to YouTube that contains the
   authentication token and the video details that the user submitted in the
   previous step.
   4.

   YouTube returns a one-time upload token, an encrypted value containing
   authentication information and video details for the video being uploaded.
   5.

   The site displays a form where the user can select his video file and
   upload it to YouTube. The form will submit directly to YouTube and must
   contain a hidden input field that specifies the upload token obtained in the
   previous step.
   6.

   The user selects his video and submits the form, sending his video and
   the upload token directly to YouTube. YouTube verifies the token is valid
   and adds the video to the user's YouTube channel. During this process,
   YouTube assigns the video a unique ID, which will be used to identify the
   video on YouTube.
   7.

   YouTube redirects the user back to The site.

Direct upload

The following diagram illustrates the direct
uploading<http://code.google.com/apis/youtube/2.0/developers_guide_protocol.html#Direct_uploading>process.
The application might have already completed the authentication
process before these steps occur. However, you could also choose to have the
user provide the video metadata before completing the authentication
process.

The image shows the following steps:

   1.

   The site displays a form in which the user will enter details about the
   video being uploaded and select the actual video file to upload.
   2.

   The user selects the video file and enters the video details, such as the
   title, description and category for the video.
   3.

   The site sends an HTTP POST request to YouTube that contains the
   authentication token as well as the video file and the video details that
   the user submitted in the previous step.
   4.

   YouTube returns an API response describing the new video.
   5.

   You display a confirmation to the user that the video was uploaded
   successfully.


I would like to go forward with the browser based upload
Technical requirements for uploaded videos

You must be either the copyright holder or the authorized representative of
the copyright owner for all video files that you deliver to YouTube.
Similarly, users who upload videos to YouTube from The site must be either
the copyright holder or the authorized representative of the copyright owner
for all videos that they upload. We encourage you and The users to provide
the highest quality video possible.

In addition to these guidelines, please note that video files must be 1 GB
or smaller and that videos may not be longer than 10 minutes. You may
compress API requests using gzip transfer-encoding. However, please note
that the 1 GB size restriction still applies to the uncompressed video file.

*Experience*

Known programming languages (more than 1y of experience): C, C++, JAVA

So can anyone please let me know the feasibility and guide me briefly?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde/attachments/20100824/be5c0cde/attachment.htm>
-------------- next part --------------
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.