Differences between revisions 6 and 7
Revision 6 as of 2004-07-19 17:45:07
Size: 5498
Editor: 206
Comment: Spelling
Revision 7 as of 2004-07-23 11:47:15
Size: 5500
Editor: 195
Comment: spelling only
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * leasury reading  * leisurely reading

Work in progress

This paper is not even close to being finished or readable. Please move along...or help write it!

Some things I want to pursue here...

  • leisurely reading
  • broad overview
  • read it once, get an idea of everything
  • read it once, get the desire to join the collective
  • community-edited vapourware
  • ...
  • don't really know that well yet, actually...

Draft TOC

  • welcome
  • intro
  • what
    • tech overview
    • social blah blah
  • when
    • oss history
    • java oss
    • gump 1.0
    • gump 2.0
    • gump 3++?
  • why
    • social pressure
    • tech benefits of continous integration
    • other cool stuff
      • javadocs
      • junit reports
      • jar repository
      • statistics
    • computation power and bandwidth
    • feature comparison
  • where
    • asf
    • private machines
    • in cvs, in svn
    • across the web
  • how
    • take a look
    • add your project
    • incremental fixes and additions
    • respond to e-mail
    • feel good about yourself
    • ask questions, improve documentation
    • request features and improvements
    • help maintain descriptors
    • answer questions, spread the word
    • become a developer

Welcome to gump!

"Welcome to gump". If you came here from the FrontPage of our wiki, or from the [http://gump.apache.org/ front page] of our web site, you'll probably have read that phrase half a dozen times by now. This is because gump is very much about the social aspects of open source development, and we would really like you to become an active part of the big and diverse community gump is. We won't say it again in this paper. Promised.

Long-winded introduction, part 1

Do you write open source software? If so, you're it. You're our audience. You don't need to be a java programmer, C programmer or python programmer. You don't need to know what [http://ant.apache.org/ Ant] or [http://maven.apache.org/ Maven] is. You probably do need to know a little about [http://www.w3.org/XML/ XML]. And it wouldn't hurt to help to share our sense of humor. Otherwise this paper will be a pain in the ####. Sorry.

This is not a hands-on howto-style document with lots of samples. It is also not a high-level architectural overview. It's a little bit of those, with some philosophy, ideals, policy description, misplaced quotes and open source history thrown into the mix.

Long-winded introduction, part 2

This paper is not really intended for screen reading between lots of open code editor windows and three half-finished e-mails. It's intended for printing (there's a print icon in the top right corner, clicking on it should take you to a [http://wiki.apache.org/gump/NewUserIntroduction?action=print printable version], then reading it while enjoying a cup of coffee, and some chocolate. Go ahead and print this now. See you on paper.

Got yourself that box of chocolates? Might want to take off those shoes as well. Never mind the smell. We're on the other side of the world, so it won't bother us.

What is gump?

  • some python scripts
  • a whole lot of project descriptors
  • an ASF TLP with PMC, P&P, etc

  • a build tool
    • --- nah... ---
  • a community of open source enthousiasts
    • pretty java-centric and asf-oriented, but hoping to change some of that
  • a social experiment
    • programmers communicate through code, e-mail, blogs
      • web-like nature of blog communication
      • group-like nature of e-mail communication
      • lack of code communication, actually
    • give programmers insight into what happens when they change something
      • expose the dependency web and the big ball of mud
        • so a tool to improve the ball a little
    • what makes you itch
      • try and make your build system itch you a little, in a good way
  • a reflection of the state of OSS software

Why you should care

  • here's us trying to get you all itchy...
    • its the social thing to do
      • I scratch your back, you scratch mine
    • saves headache later on
      • catch bugs early on
    • your users are doing it, too
      • and need you to do it!
    • biggest integration test on the planet
      • value of integration increases with size

Feature comparison with other systems

  • no fancy web GUI
    • but power of python+xml
  • no fancy CVS, SVN or triggers
    • but emulation of your actual build habits
  • not easy to install
    • but easy to configure in the way you like
  • not easy to administer
    • but people are doing that for you
  • no feature X
    • but you have the power to add it
  • no big company support
    • but a very dedicated community
  • ASF branded for quality

    it's not about features, it's about community.

Summary: "What is Gump?"

Gump emulates a rabid developer; attempting to automate the discovery/communications processes of OSS interacting with other OSS (ASF or otherwise). Gump keeps interactions fresh and healthy, via dispassionate critical feedback. You can use Gump for your own (private or OSS) projects against OSS projects or not.

Alt Summary: "What is Gump?"

Gump is a Early Warning System for project incompatablities. Gump does this by building everything from CVS/SVN everytime. When things break, (and they do, often), gump tries to notify the communities that can take [http://gump.chalko.com/gb/blog/SuccessStories/ action].

NewUserIntroduction (last edited 2009-09-20 23:49:37 by localhost)