Running a Project with Github

  • 4,915 views
Uploaded on

Slides from the unconference talk at phpuceu in Manchester, February 2011

Slides from the unconference talk at phpuceu in Manchester, February 2011

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,915
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
39
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Running a Project with Github
  • 2. About Me● Lorna Jane Mitchell● Co-Project Lead on Joind.In● Freelance PHP Consultant/Evangelist● Twitter: @lornajane● Site: http://www.lornajane.net
  • 3. The Project: Joind.In● Instant, public feedback for events● http://joind.in● Open source - hosted on github
  • 4. GitHub● http://github.com● "Online project hosting using Git. Includes source-code browser, in-line editing, wikis, and ticketing. Free for public open-source code."
  • 5. Version Control● Keeping-place● Collaboration tool● History
  • 6. Centralised Version Control
  • 7. Distributed Version Control
  • 8. GitHub● Provides supporting tools to track ● users ● repos ● changes ● documents ● source code● http://github.com/joindin/joind.in
  • 9. Joind.In on Github● Wiki● Source Code● Bug tracking is actually on JIRA● Mailing lists and IRC
  • 10. Wiki● Overview● Contributors guide● Roadmap
  • 11. Source Code● One main repo ● project leads have commit access● Users fork to own github repo● Changes come back via pull requests
  • 12. Source Code Contributions● One branch per changeset● Branch naming conventions● Guidelines from ZF: ● http://framework.zend.com/wiki/display ZFDEV2/Zend+Framework+Git+Guide
  • 13. Bug Tracking: JIRA● Migrated away from github● Atlassian offers free accounts for open source● Issue owners● Issue status
  • 14. Mailing Lists● Key link to community● Transparency● Users as well as developers
  • 15. IRC● Developers mostly● #joind.in on freenode
  • 16. Openness● IRC + mailing lists● Features under consideration● Platform/hosting changes
  • 17. Projects on GitHub● Great central resource● Maturing tool● Technology is not the whole answer
  • 18. Thanks!