Develop FOSS project using Google Code Hosting
2 likes2,420 views
The document discusses how to develop an open source project using Google Code hosting, including how to create a project, check code in and out of version control, use issue tracking, blogs, and Twitter to engage others. It provides best practices like writing documentation, using labels, and making releases to engage more developers and track popularity. The example used is the development of an SVG vector drawing tool called SVG-Edit that was created and hosted on Google Code.
Develop FOSS project using Google Code Hosting
- 1. How to Develop Open Source Project With Google Code Hosting Ex - SvgEdit By – Narendra Sisodiya http://narendra.techfandu.org (C) Narendra Sisodiya, Licensed under CC-By-Sa 2.5 In
- 2. CC-By-SA 2.5 In This work is Licensed under Creative Common Attribution-Share Alike 2.5 India You have Freedom to Share — to copy, distribute and transmit the work
- 3. to Remix — to adapt the work Share Under the following Conditions Attribution — You must attribute the work by proving the name of author and homepage. (Narendra Sisodiya http://narendra.techfandu.org)
- 4. Share Alike — If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
- 5. Tools i used Google Code hosting SVN Code Repo
- 8. Hosting Web application (without server side processing) Mailing list Google Group Annousment Blogs
- 9. Twitter Editing Tools Terminal, Gedit, Eclipse etc
- 10. 1 Step : Project Idea I wanted to have a lightweight, fast and online svg vector drawing tool.
- 11. I searched for internet but was not happy.
- 12. I wanted to learn SVG, so I made it from scratch
- 13. I thought, Let create a one.
- 14. How to create project Just simple steps at http://code.google.com/hosting/createProject
- 15. Demo Time
- 16. Code Hosting One or more programmer can join a project
- 17. You can create your project without meeting each other.
- 18. Checkout Downloading a perticular version/branch of project
- 19. svn checkout https://PRJ.googlecode.com/svn/trunk/ PRJ --username USER1 Checkin/Commit Uploading changes made in codebase
- 20. It will increment the “ revision number ”
- 21. svn ci <list of files>
- 22. First Checkout code You need to install svn client on your system sudo yum install subversion
- 23. sudo apt-get install subversion You can checkout Trunk , branch Demo Checking out Helloworld project
- 24. Modify and Commit Check status of code base (to see what you have modified) svn status Get updates : getting latest updates available (changes) svn update // update to latest version
- 25. svn update -r45 //this time travel will bring you at revision 45 Check Diff svn diff <list of files> Comit your changes svn ci <list of files> Demo
- 26. Rivision system Everytime you update the codebase, it make a new revision
- 27. Issue Tracking
- 28. blogs
- 29. Twitter
- 30. How Blogs and Tweet Help Nobody can see feature from code, You need to write them on blogs
- 31. User can comment and suggest for features
- 32. You can get new programmer (Ex we got Jeff)
- 33. Posting on twitter with hastags (example #svg) give a easy way to annoucement it to huge audience who follows those tags
- 34. Give a link to bug/issue tracker so anybody may submit new bugs
- 35. Best Practice Write details about project, it help programmer to understand fast.
- 36. Always put labels to project. So it become part of google code search result.
- 37. Must make blog and tweet about project to reach wider audience
- 38. Write full instruction how a user can install your project.
- 39. You can create your Btech/MTech project or assignment codebase using google code hosting to collaboratively with peers.
- 40. Create and merges branches
- 41. Use svn propset for html, css, js and svg files
- 42. Always make version wise tar / zip files and upload them, You can track papularity using number of downloads
- 43. Info Files Add these Files in your project
- 44. README It contains installation detail LICENSE It contains license info CHANGELOG This contain versionwise feature changes done by you AUTHOR List of authors with their mail ids ACKNOWLEDGEMENTS List of all other projects and persons who helped to make it possible
- 45. SVN Propset svn propset svn:mime-type text/html *.html
- 46. svn propset svn:mime-type image/png *.png
- 47. svn propset svn:mime-type image/gif *.png
- 48. svn propset svn:mime-type text/css *.css
- 49. svn propset svn:mime-type text/javascript *.js
- 50. Code Directory - http://svg-edit.googlecode.com/svn/trunk/ will return to files with proper mimetype. Otherwise it will return text file.
- 51. Demo
- 52. View a Perticular version http:// <Project Name> .googlecode.com/svn-history/r <rivistion number> / Example - http://svg-edit.googlecode.com/svn-history/r201/ http:// <Project Name> .googlecode.com/svn/ Ex http://svg-edit.googlecode.com/svn/ View a latest version
- 56. Question ? [Photo credit : alexanderdrachmann ]