Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Google Summer of Code 2010 Ideas"
(→Ideas) |
m (→Ideas) |
||
Line 18: | Line 18: | ||
!width="10%"|Potential student(s) | !width="10%"|Potential student(s) | ||
|- | |- | ||
− | | | + | | |
Create a provider for Google Buzz | Create a provider for Google Buzz | ||
− | | | + | | |
− | | | + | | |
Google Buzz is a new way to share updates, photos, videos etc., and start conversations about the things you find interesting. It is the latest social network / microblogging mechanism introduced by Google and its usage has spread widely in a very small time period. But a big drawback of google buzz as of now is lack of applications for it (in comparison to twitter). Integrating Google buzz to eclipse communication framework will extend ECF quite vastly, since buzz itself can be linked to many information sources such as twitter, RSS feeds, google status messages, youtube, picasa etc. Therefore creating a provider for Google buzz will help eclipse users connect to vast number of sources through a single provider. In addition to that, it would be a more convinient way for users to access Google Buzz, since they will not have to constantly go to their gmail page and check for new buzzes, and thus, will enhance the usability of Google Buzz as well. | Google Buzz is a new way to share updates, photos, videos etc., and start conversations about the things you find interesting. It is the latest social network / microblogging mechanism introduced by Google and its usage has spread widely in a very small time period. But a big drawback of google buzz as of now is lack of applications for it (in comparison to twitter). Integrating Google buzz to eclipse communication framework will extend ECF quite vastly, since buzz itself can be linked to many information sources such as twitter, RSS feeds, google status messages, youtube, picasa etc. Therefore creating a provider for Google buzz will help eclipse users connect to vast number of sources through a single provider. In addition to that, it would be a more convinient way for users to access Google Buzz, since they will not have to constantly go to their gmail page and check for new buzzes, and thus, will enhance the usability of Google Buzz as well. | ||
− | | | + | | |
N.J. Samarasekera [nuwansam@gmail.com] | N.J. Samarasekera [nuwansam@gmail.com] | ||
− | | | + | | |
Marcelo Mayworm, James Sugrue, Scott Lewis | Marcelo Mayworm, James Sugrue, Scott Lewis | ||
− | | | + | | |
− | + | ||
| <br> | | <br> | ||
|- | |- |
Revision as of 09:36, 3 March 2010
Rules
- Be creative
- Be specific: what do you want to be implemented
- If you are willing to mentors those ideas, add your name and email to the idea.
- It is ok to have a project idea without parent project
- If you're an interested student, add your name and email next to the idea. It is ok to have several students interested by one idea.
- Aspiring students and mentors need to register and submit their proposals or request on the Soc app
Ideas
Title | Project | Abstract - links to details/bugs/etc | Reporter | Possible mentor(s) | Comments | Potential student(s) |
---|---|---|---|---|---|---|
Create a provider for Google Buzz |
Google Buzz is a new way to share updates, photos, videos etc., and start conversations about the things you find interesting. It is the latest social network / microblogging mechanism introduced by Google and its usage has spread widely in a very small time period. But a big drawback of google buzz as of now is lack of applications for it (in comparison to twitter). Integrating Google buzz to eclipse communication framework will extend ECF quite vastly, since buzz itself can be linked to many information sources such as twitter, RSS feeds, google status messages, youtube, picasa etc. Therefore creating a provider for Google buzz will help eclipse users connect to vast number of sources through a single provider. In addition to that, it would be a more convinient way for users to access Google Buzz, since they will not have to constantly go to their gmail page and check for new buzzes, and thus, will enhance the usability of Google Buzz as well. |
N.J. Samarasekera [nuwansam@gmail.com] |
Marcelo Mayworm, James Sugrue, Scott Lewis |
|
Old ideas can be found at Google Summer of Code 2007 ideas, Google Summer of Code 2008 ideas and Google Summer of Code 2009 ideas .