About the Foundation for Public Code

Milestones

We use milestones to plan our work around and set priorities. Milestones replace what other organisations would call ‘projects’ by focussing on the key achievements over certain deliverables.

Milestones have an owner and can have a due date.

Upcoming milestones:

  • Hire codebase steward for community @bvhme
  • Hire codebase steward for quality @bvhme
  • Hire codebase steward for support @bvhme
  • Found association 2019-05-30 @bvhme
  • Standard v0.2.0 @elenafdr
  • First member @nebster
  • First national-level intention agreement @nebster
  • First national-level member @nebster
  • First supranational-level intention agreement @nebster
  • First supranational-level member @nebster
  • First non-European intention agreement @nebster
  • First non-European member @nebster
  • First Public Code conference @elenafdr
  • First business case and value/impact model published @clausmullie
  • First codebase in Assessment @clausmullie
  • First codebase in Incubation @clausmullie
  • Standard v1.0.0 @elenafdr
  • First codebase in Mature / Product @elenafdr
  • First reuse of Mature codebase or product @clausmullie
  • First third party contributor on a codebase @clausmullie
  • First third party maintainer on a codebase @clausmullie
  • First member contribution @nebster
  • First non-director gift @nebster
  • First non-director grant @nebster
  • Standard v2.0.0 @elenafdr

How to use milestones

Milestones can be used in GitHub, they can be added to issues as well as pull requests which makes it easier to find and version things.

In our office we have a wall with the milestones on it.

How to add a milestone

  1. Add a milestone to the GitHub repository where possible
    • Mention the owner in the description
    • Set the due date if available
  2. Add the milestone to the list above
    • Add an owner
    • Add a due date if available
    • Link to the repository milestone
  3. Update the milestone wall in the office