Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Purpose

Jenkins needs an umbrella foundation of some sort, at a minimum to provide a legal home for the Jenkins trademark/IP, a place to properly handle donations, etc. How much more than that is needed is an open question. This page is intended to provide a venue for discussing the pros and cons of each of the possible homes.

When adding a pro or con, or commenting on existing ones, please make sure to leave your name/username.

Foundations

Foundations are in alphabetical order.

Apache

  • Pros
    • Well know and respected (pablaasmo)
    • Gives good freedom to community to decide framework/design etc.(pablaasmo)
    • real community over code mind (olamy)
    • trademark and legal help possible (olamy)
  • Cons
    • Release process ? (weekly release will be more complicated due to vote process) (olamy)
    • new committer entry (olamy : IHMO not a real issue as the goal is to probably to move only core)
    • back to svn (AFAIK asf use a central svn repo) (olamy)
    • legal issues regarding gpl libs (olamy : btw same for eclipse)

Eclipse

  • Pros
    • Gets the possibility to join with Hudson again (pablaasmo)
  • Cons
    • Might have more restrictions on how the framework should bee. OSGI etc (pablaasmo).

SFC

  • Pros
  • Cons

SPI

  • Pros
  • Cons
  • No labels