| 1 | moap is a swiss army knife for project maintainers and developers. |
|---|
| 2 | It aims to help in keeping you in the flow of maintaining, developing and |
|---|
| 3 | releasing, automating whatever tasks can be automated. |
|---|
| 4 | |
|---|
| 5 | FEATURES |
|---|
| 6 | -------- |
|---|
| 7 | The current list of features includes: |
|---|
| 8 | |
|---|
| 9 | - parse DOAP files and: |
|---|
| 10 | - submit releases to Freshmeat |
|---|
| 11 | - send out release announcement mails |
|---|
| 12 | - create iCal and RSS release feeds from DOAP file(s) |
|---|
| 13 | - template them using Genshi or Cheetah |
|---|
| 14 | - look up project home page rank on Google and Yahoo for given queries |
|---|
| 15 | - version control tools: |
|---|
| 16 | - currently supports Bazaar, CVS, Darcs, Git, SVN, git-svn |
|---|
| 17 | - maintain ignore lists |
|---|
| 18 | - prepare ChangeLog entry based on local diff, using ctags |
|---|
| 19 | - check in based on ChangeLog entry |
|---|
| 20 | - show diff based on last ChangeLog entry |
|---|
| 21 | - bug tracker tools: |
|---|
| 22 | - show individual bugs and queries from trac and bugzilla |
|---|
| 23 | - developed in Python, with unit tests and coverage |
|---|
| 24 | - get list of contributors from ChangeLog |
|---|
| 25 | - search through ChangeLog |
|---|
| 26 | - bash completion |
|---|
| 27 | - administering a trac installation |
|---|
| 28 | |
|---|
| 29 | Future features planned include: |
|---|
| 30 | - support for other VCS systems |
|---|
| 31 | - sending patches and attaching them to bug trackers |
|---|
| 32 | - working with quilt |
|---|
| 33 | |
|---|
| 34 | DEPENDENCIES |
|---|
| 35 | ------------ |
|---|
| 36 | moap can make use of: |
|---|
| 37 | - the Redland python bindings (RDF), for parsing of DOAP files |
|---|
| 38 | - bzr, cvs, darcs, git, git-svn, and svn, for handling checkouts |
|---|
| 39 | - Genshi and Cheetah, for templating |
|---|
| 40 | - exuberant-ctags, for tag extraction |
|---|
| 41 | - Twisted's trial, for unit tests |
|---|
| 42 | - epydoc, for API documentation |
|---|
| 43 | - trac, for maintaining a trac installation |
|---|
| 44 | |
|---|
| 45 | GETTING MOAP |
|---|
| 46 | ------------ |
|---|
| 47 | Preferably, install moap from a package supplied by your distribution. |
|---|
| 48 | If no package is available, you can build it from a source tarball. |
|---|
| 49 | If you want to hack on it or want to try the bleeding edge version, you |
|---|
| 50 | can check it out from subversion. |
|---|
| 51 | |
|---|
| 52 | If you are building from a source tarball or checkout, you can choose to |
|---|
| 53 | use moap installed or uninstalled. |
|---|
| 54 | |
|---|
| 55 | - getting: |
|---|
| 56 | - Change to a directory where you want to put the moap source code |
|---|
| 57 | (For example, $HOME/dev/ext or $HOME/prefix/src) |
|---|
| 58 | - source: download tarball, unpack, and change to its directory |
|---|
| 59 | - checkout: |
|---|
| 60 | svn co https://thomas.apestaart.org/moap/svn/trunk moap |
|---|
| 61 | cd moap |
|---|
| 62 | ./autogen.sh |
|---|
| 63 | |
|---|
| 64 | - building: |
|---|
| 65 | ./configure |
|---|
| 66 | make |
|---|
| 67 | |
|---|
| 68 | - you can now choose to install it or run it uninstalled. |
|---|
| 69 | - installing: |
|---|
| 70 | make install |
|---|
| 71 | - running uninstalled: |
|---|
| 72 | ln -sf `pwd`/misc/moap-uninstalled $HOME/bin/moap-trunk |
|---|
| 73 | moap-trunk |
|---|
| 74 | (this drops you in a shell where everything is set up to use moap) |
|---|
| 75 | |
|---|
| 76 | - test basic functionality: |
|---|
| 77 | moap doap show |
|---|
| 78 | (should show you project information for moap itself) |
|---|
| 79 | |
|---|
| 80 | RUNNING MOAP |
|---|
| 81 | ------------ |
|---|
| 82 | moap is self-documenting. |
|---|
| 83 | moap -h gives you the basic instructions. |
|---|
| 84 | |
|---|
| 85 | moap implements a tree of commands; for example, the top-level 'changelog' |
|---|
| 86 | command has a number of sub-commands. |
|---|
| 87 | |
|---|
| 88 | Positioning of arguments is important; |
|---|
| 89 | moap doap -f (file) show |
|---|
| 90 | is correct, while |
|---|
| 91 | moap doap show -f (file) |
|---|
| 92 | is not, because the -f argument applies to the doap command. |
|---|
| 93 | |
|---|
| 94 | EXAMPLES |
|---|
| 95 | -------- |
|---|
| 96 | - to get help on the changelog command: |
|---|
| 97 | moap cl -h |
|---|
| 98 | |
|---|
| 99 | - to create a new ChangeLog entry based on the local modifications: |
|---|
| 100 | moap cl prep |
|---|
| 101 | |
|---|
| 102 | - to check in all files mentioned in the latest ChangeLog entry: |
|---|
| 103 | moap cl ci |
|---|
| 104 | |
|---|
| 105 | - update ignore lists: |
|---|
| 106 | moap ignore |
|---|
| 107 | (then edit the file and keep only the files that need to be ignored) |
|---|
| 108 | |
|---|
| 109 | - show information about your project: |
|---|
| 110 | moap doap show |
|---|
| 111 | |
|---|
| 112 | - submit the 0.2.0 release of your project to freshmeat: |
|---|
| 113 | moap doap -v 0.2.0 freshmeat |
|---|
| 114 | |
|---|
| 115 | DOGFOODING |
|---|
| 116 | ---------- |
|---|
| 117 | moap is hip to the kid's lingo and is 100% dogfoodable. The ChangeLog is |
|---|
| 118 | managed with moap changelog commands. The list of files that SVN should ignore |
|---|
| 119 | is managed with moap ignore. The list of bugs fixed is generated with moap |
|---|
| 120 | doap bug query. The releases are announced to freshmeat with moap doap |
|---|
| 121 | freshmeat. Mails get sent out with moap doap mail. |
|---|
| 122 | |
|---|
| 123 | DEBUGGING |
|---|
| 124 | --------- |
|---|
| 125 | You can set the MOAP_DEBUG environment variable to get debug output. |
|---|
| 126 | The variable takes a comma-separated list of category:value strings. |
|---|
| 127 | |
|---|
| 128 | To get all debugging, set MOAP_DEBUG to *:5 |
|---|
| 129 | |
|---|
| 130 | BUGS, ENHANCEMENTS, ... |
|---|
| 131 | ----------------------- |
|---|
| 132 | All issues can be filed at |
|---|
| 133 | http://thomas.apestaart.org/moap/trac/newticket |
|---|
| 134 | |
|---|
| 135 | DOAP |
|---|
| 136 | ---- |
|---|
| 137 | For more information on DOAP, see http://usefulinc.com/doap/ |
|---|
| 138 | |
|---|
| 139 | You can create a DOAP file easily using the DOAP A Matic website: |
|---|
| 140 | http://crschmidt.net/semweb/doapamatic/ |
|---|
| 141 | |
|---|
| 142 | Python projects using setuptools can easily get a DOAP file generated |
|---|
| 143 | by registering with CheeseShop: |
|---|
| 144 | |
|---|
| 145 | python setup.py sdist register |
|---|
| 146 | |
|---|
| 147 | The DOAP file ends up here: |
|---|
| 148 | http://cheeseshop.python.org/pypi?:action=doap&name=<YOUR_PROJECT_NAME> |
|---|
| 149 | |
|---|
| 150 | CONTACT |
|---|
| 151 | ------- |
|---|
| 152 | The moap project page is http://thomas.apestaart.org/moap/trac/ |
|---|
| 153 | |
|---|
| 154 | There is no mailing list yet. You can mail me at |
|---|
| 155 | thomas <at> apestaart <dot> org for now. |
|---|
