Send Dev-flock mailing list submissions to
dev-flock@mit.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/dev-flock
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dev-flock digest..."
Today's Topics:
1. database docs (Lucy Mendel)
2. r850 - in huginmunin/trunk: . doc ([EMAIL PROTECTED])
3. r851 - huginmunin/trunk/doc ([EMAIL PROTECTED])
4. status (Lucy Mendel)
----------------------------------------------------------------------
Message: 1
Date: Tue, 1 Jul 2008 13:33:58 -0400
From: "Lucy Mendel" <[EMAIL PROTECTED]>
Subject: [Dev-flock] database docs
To: Dev-Flock <dev-flock@mit.edu>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
yo,
I updated the database page with 'entity relationship diagrams'
http://bilumi.org/trac/wiki/Database
Mostly I'm wondering what tools we have in place for documentation.
In particular, are we still using epydoc--- Dan, what are you using?
pydoc? I can see lots of great documentation on the code itself, just
wondering if there's an easy HTML translation.
Solr is still a black hole for me.
L.
------------------------------
Message: 2
Date: Tue, 1 Jul 2008 17:45:42 -0400 (EDT)
From: [EMAIL PROTECTED]
Subject: [Dev-flock] r850 - in huginmunin/trunk: . doc
To: dev-flock@mit.edu
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
Author: lucy
Date: 2008-07-01 17:45:42 -0400 (Tue, 01 Jul 2008)
New Revision: 850
Commit message:
epydoc config file updated (and docs generated). doc generated errors might be
relevant to development; see epydoc.out
Added:
huginmunin/trunk/doc/
huginmunin/trunk/doc/README.txt
huginmunin/trunk/doc/epydoc.config
huginmunin/trunk/doc/epydoc.out
------------------------------
Message: 3
Date: Tue, 1 Jul 2008 18:06:49 -0400 (EDT)
From: [EMAIL PROTECTED]
Subject: [Dev-flock] r851 - huginmunin/trunk/doc
To: dev-flock@mit.edu
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
Author: lucy
Date: 2008-07-01 18:06:49 -0400 (Tue, 01 Jul 2008)
New Revision: 851
Commit message:
docs are now more complete (db, apps/view and apps/lib, no db/solr)
Modified:
huginmunin/trunk/doc/epydoc.config
huginmunin/trunk/doc/epydoc.out
------------------------------
Message: 4
Date: Wed, 2 Jul 2008 09:58:30 -0400
From: "Lucy Mendel" <[EMAIL PROTECTED]>
Subject: [Dev-flock] status
To: Dev-Flock <dev-flock@mit.edu>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
yo,
summary: Xplanner is updated; wiki and code documentation is
progressing; Monday meeting went great.
Did I tell you that xplanner has been updated? It has. Our goal this
iteration was to have a few focussed stories. I've consolidated
stories into Engines:
http://whynoti.org:8080/xplanner/do/view/iteration?projectId=0&returnto=%2Fdo%2Fview%2Fprojects&oid=842
The phone stuff is hanging around in Specialized Technology, though
the request handling/information system will eventually move into the
engine code base.
http://whynoti.org:8080/xplanner/do/view/iteration?projectId=0&returnto=%2Fdo%2Fview%2Fprojects&oid=1087
Nothing is in UI for now. The community page stuff is hanging out in
Community Information Platform. Last Monday Shaunalynn and I worked
out a concrete plan for community discussion in our site. We're adding
a new node type in addition to General, Product, Company and Source:
Community. Shaunalynn is working out the system, but to give ya'll an
idea of the kinds of Community nodes: Help, Voting Culture, Community
Discussion, etc. Each node is like a discussion forum, and each top
level review is a new topic.
Dan and I are working on the code cleanup; the more the merrier, since
a big part of code cleanup is improving overall team understanding of
the codebase, getting the status of modules documented and then
cleanup, standardize, remove cruft, and fix those modules.
I updated some wiki documentation on the database
http://bilumi.org/trac/wiki/Database
as well as the epydocs
http://bilumi.org/epydoc/
Big ups to Dan for getting the epydoc graphs (eg:
http://www.thoughtandmemory.org/epydoc/hm.db.graph.Node-class.html
) to work and for being our number one in-code documenter. We could
still stand for more code documentation; in particular, the why's of a
class or module, and the input/output/usecase of methods. Let me know
if you have questions or suggestions.
I've also documented the phone stuff on the wiki, though the pydoc is
still to come. The wiki documentation does not reflect the current
status of the code (eit-- really should say something to that effect),
but I will check in as soon as possible.
http://thoughtandmemory.org/trac/wiki/cellphone_install
The information system and request handler wiki pages are a hodge
podge right now.
Info Sys contains scraping stuff, which I need to add to xplanner
since it is an important story to complete this summer. It will jump
start the quick rate or news aggregator applications
http://thoughtandmemory.org/trac/wiki/informationsystem
The wiki user Locke, in real life one of our adviser board members,
Fritz Knabe, added some thoughts to the Rate It news aggregator page.
So there's lots of potential here, and once we get through some of the
more foundational stories the possibilities will grow.
Keep in touch,
L.
------------------------------
_______________________________________________
Dev-flock mailing list
Dev-flock@mit.edu
http://mailman.mit.edu/mailman/listinfo/dev-flock
End of Dev-flock Digest, Vol 11, Issue 2
****************************************
