On Fri, Nov 11, 2011 at 4:47 AM, curtis Hovey <curtis.ho...@canonical.com> wrote: >> Why Librarian? >> >>> * Create a new model to access the agreement. >>> * Update the existing signed agreements to know the team and >>> agreement that was signed. >>> * Add UI to upload an agreement. >> >> As I say, I don't think that's needed right at the start, and perhaps >> it's easier to shake it down just with some semi-hard-coded cases like >> the CA. I would focus on just adding the db tables, and then doing >> click-through signing to get membership, and then go from there. > > The librarian and the DB are the only two things I know of that Lp uses > to store documents. The DB handles text, where as the librarian can > handle other document types.
Also the librarian is strongly preferred for non-trivial content (more than a few hundred bytes). -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
