Version 75 (modified by sa2ajj, 5 years ago) (diff) |
---|
Tools
Developer Community
- Subscribe to the buildbot devel mailing list (archives)
- Join us in #buildbot on freenode. IRC logs are available online here.
- BuildbotSummits - get together, meet fellow users and developers, and make Buildbot better
Contributing
- DevelopmentGettingStarted - how to get started developing
- SubmittingPatches - how to get your code into Buildbot
- PatchReview - what makes a good patch
- RunningBuildbotWithVirtualEnv - a quick way to get started
- How to debug Buildbot with pdb
- What needs doing?
- simple bugs - good places to get started
- ProjectIdeas - written for GSoC, but anyone can pick up a project
- LicensingYourContribution - info on licensing
- ReportingVulnerabilities - what to do if you've found a security problem in Buildbot
- Buildbot Tests - writing tests for buildbot
- Coding Style - tips for writing good code
- Sprints - getting together to hack on Buildbot
- GSoC - Google Summer of Code
- ProjectIdeas - GSoC Projects
- BountyProgram
Bug Handling
- BugWrangling - help categorize some bugs!
- tags - all bug tags currently in use
- ReleaseProject - bug tracking for the next release
- PatchReview - checklist for reviewing patches
Plans
- DevelopmentPlan - a sketch of Buildbot's next steps
- ProjectIdeas - good projects (for Google Summer of Code students .. and anyone else!)
Policies and Processes
- security - how we handle security incidents
- compatibility - how we handle compatibility with other tools
- support - support for older versions of Buildbot
- promotion - how and when permissions are granted
- release - how and when releases are made
- eight - maintenance policy for the eight branch
- conduct - code of conduct
- other formal policies ..
Checklists
- CuttingReleases - the release process
- ChangingBotherdersChecklist - giving/revoking botherders' access
- FightingSpam
Misc
- BranchesAndTags - the structure of the VC repository
- Lately we've wanted an RcsTeminologyCrossReference so that different RCS users can converse intelligently.