List view
This is a temporary milestone to hold all issues due for the next release
No due date•1/1 issues closedWe need to create Python packages available on [Cheese shop aka PyPI](http://pypi.python.org/) to facilitate the installation/deployment process. Probably we'll have two packages: `pypln.backend` (that instantiates pypelinin and have all workers and store) and `pypln.web` (the frontend, web interface). Maybe a third package will be needed (`pypln.util`) to have everything other packages need. Should we have a `pypln` package?
No due date•4/4 issues closedWe need to create the infrastructure that will host the pypln web interface and an the staging version of it. After the deploy is fully automatic we should only need a couple of VMs and one user with root access.
No due date•4/4 issues closedWe need to implement a full-text search in the Web interface using Sphinx-search. This search should: - Search in document's `text` property (created by `Extractor` worker) - Show a concordance in the results page - The results page must have pagination - The Sphinx query language must be supported in the query box - Search form should be in every page There is a code implemented by @fccoelho and @turicas in repository history, but it does not have tests and is not generic (have hard-coded Sphinx configurations and things like that). More information on #22.
No due date•3/3 issues closedA lot of the code base is still not tested. The worst offenders are the django project that provides the web interface and the utils, but we should still find out which other areas are in the same situation. This milestone replaces #48
No due date•7/7 issues closedIn this history we need to: - Rearrange files and directories - Add LICENSE file - Add copyright information on every file in the repository - Organize the settings structure for the django project
No due date•8/8 issues closedWe need to provide a documentation for who will use the Web interface. It needs to have screenshots and (maybe) a video explaining how to use the software. It should only cover basic aspects, as a "getting started" tutorial. We need to host it somewhere (maybe in the same place API documentation will be hosted). The website pypln.org should be modified to accomplish these changes and have links to everything. This milestone was broken down from #34
No due date•5/5 issues closedWe need to have the API documentation accessible somewhere, so in this history we need to: - List all undocumented modules/classes/methods - Document everything not documented - Define which software/method we'll use to generate API documentation - Define where we'll host it - Create a script to automate generation and deployment of API documentation This milestone was broken down from #34
No due date•12/12 issues closedCurrently our deployment process is manual. We need to improve it by automating everything related to deployment. Our goal is to start from a fresh Debian/Ubuntu machine to a full-PyPLN environment running just running a script. The first steps will create this script to install everything in a single machine but then we need to have this process splitted in many machines, so we can run MongoDB in a dedicated machine, for example. This milestone was expanded from #19 The issues in this milestone are mostly being worked on in [flavioamieiro/feature/deploy](https://github.com/flavioamieiro/pypln/tree/feature/deploy) but, since this milestone depends on lots of issues from other milestones, this branch will probably only be merged in after most of them are ready.
No due date•10/10 issues closedThis will be the first version with a functional version of the Web interface as well and a clear definition of a pipeline for processing documents.
Overdue by 13 year(s)•Due by December 15, 2012•30/30 issues closed