Id |
Task |
Description |
% Done |
Due Date |
Assigned |
Notes |
|---|---|---|---|---|---|---|
0 |
Convert to-do items into task list in Jira to track tasks to be done in the code base to ease participation, communication of status, and auditing of work completed. |
|
100% |
11/5/2008 |
Heather |
Completed 10/29/2008 |
1 |
base install |
The base install of COmanage includes a set of packages that will take a vanilla debian system and install and configure the core infrastructure of COmanage (slapd, shib sp, ship 2.0 idp, grouper, mysql, ldappc) |
90% |
|
Scotty |
Grouper 1.3.x last item on list |
2 |
Confluence |
One click Wiki install and integration |
10% |
|
Scotty |
|
|
a. new user interception |
modify the Log In component to stay within COmanage and to create a new user invitation if necessary |
0% |
11/7/2008 |
Scotty |
|
3 |
Sympa |
One click MLM install and integration |
0% |
9/12/2009 |
Jon R. |
|
|
a. figure out how to configure Sympa to work with shib and ldap |
Ask fdivbug@duke.edu for their notes on integration |
0% |
|
Jon R. |
Look at the original COmanage code written by Michael Gettes |
|
b. create the co-sympa package |
|
|
|
Jon R. |
There is a base sympa debian package already available |
|
c. create/delete lists |
API |
|
|
Jon R. |
|
|
d. new user interception |
modify the Log In component to stay within COmanage and to create a new user invitation if necessary |
|
|
Jon R. |
|
4 |
JIRA |
One click JIRA install and integration |
0% |
11/14/2008 |
Scotty |
|
|
a. figure out how to domesticate JIRA |
|
50% |
11/14/2008 |
Scotty |
"manually" domesticated; need to automate |
|
b. create co-jira package |
|
|
11/14/2008 |
Scotty |
|
5 |
Alfresco |
One click Alfresco install and integration |
|
|
|
Need to check with the community - does anyone have more experience with Alfresco? |
|
a. figure out how to domesticate Alfresco |
|
|
|
|
|
|
b. create wizard and integration scripts |
|
|
|
|
|
|
c. create co-alfresco package |
|
|
|
|
|
6 |
Dashboard Design |
The design of the layout of the dashboard, the key instrument used by the COllabmin. This includes the ability to manage basic information about the VO powered by this COmanage box (name, contact info, etc) |
75% |
10/31/2008 |
Digant |
Some pages like invite users, add/edit groups, add/edit privs needs to be done but basics are done. |
|
a. finish subpages |
|
|
10/31/2008 |
Digant |
|
7 |
Access Dashboard |
Configure registration and content access preferences |
30% |
11/7/2008 |
Digant |
|
|
a. create page to make two settings changes via api |
(allow self reg? and publicly viewable by default?) |
|
11/7/2008 |
Digant |
|
8 |
App Dashboard |
Install and remove applications |
0% |
11/26/2008 |
Jon R. |
This depends on the Confluence, Jira, Alfresco, Sympa work being done |
|
a. create backend interface for updates |
|
|
11/26/2008 |
Jon R. |
|
|
b. create backend interface for seeing what is available |
|
|
11/26/2008 |
Jon R. |
|
|
c. implement front-end |
|
|
11/26/2008 |
Jon R. |
|
|
d. need a repository for the apps, separate from base |
|
|
11/26/2008 |
Scotty |
|
9 |
Shib Dashboard |
Manage the SP configuration, including metadata and certs for multiple federations |
0% |
|
Digant |
At this time, all the basic work is done at set up. Propose to defer all items that would require people to change federations in the future and have the beta be "you get what you get when you do the initial install" |
|
a. reverse engineer/doc how the shib wiz pieces work |
|
|
|
Digant |
|
|
b. write backend for metadata management |
|
|
|
Digant |
|
|
c. write back-end for cert management |
|
|
|
|
Deferred |
|
d. write back-end for config management |
|
|
|
Digant |
|
|
e. front-end for managing shib and multiple federations. |
|
|
|
Digant |
|
10 |
User Dashboard |
User invitation and removal |
0% |
12/10/2008 |
Digant / Jon R. |
Will utilize as much of the Guest Accounts code (Stanford code) as possible |
|
a. back-end to create/remove users |
|
|
12/10/2008 |
Digant / Jon R. |
|
|
b. back-end to manage invites |
|
|
12/10/2008 |
Digant / Jon R. |
|
|
c. front-end for invites |
|
|
12/10/2008 |
Digant / Jon R. |
|
|
d. tie in auto-join group for invitees |
|
|
12/10/2008 |
Digant / Jon R. |
|
|
e. tie in auto-assign privs for invitees |
|
|
12/10/2008 |
Digant / Jon R. |
|
|
f. front-end for self registration |
|
|
12/10/2008 |
Digant / Jon R. |
|
11 |
Groups Dashboard |
Group management (grouper) |
0% |
TBD |
|
Can the Grouper team assist here? |
|
a. research API options |
|
|
|
|
|
|
b. ensure ldappc is working |
|
|
|
|
|
12 |
Privs Dashboard |
Privilege management |
0% |
TBD |
|
Need to discuss how we'll do Priv Mgmt without Signet; probably can't do anything, even a simple priv system by December |
|
a. TBD |
|
|
|
|
|
13 |
Status Dashboard |
Page to monitor the status of core applications as well as added domesticated applications |
30% |
TBD |
|
Defer |
14 |
Backups Dashboard |
Backup and restore data |
0% |
|
|
|
13 |
COmanage API |
A set of Perl modules that applications can call to query information from the COmanage environment. |
70% |
11/7/2008 |
Digant |
Initial spec written and code mostly done. For the beta, add a "get config" piece |
|
a. finish ldap add and mysql add functions |
|
|
11/7/2008 |
Digant |
|
|
b. add allow-selfreg? and default-public? api calls for managing these two access settings |
|
|
TBD |
|
Defer |
14 |
COmanage Install Video |
Video showing the base install of a COmanage box |
70% |
12/15/2008 |
Digant |
|
15 |
COllabmin Video |
Video showing the operations a COllabmin would do to administer his/her VO |
10% |
12/15/2008 |
Digant |
We have a script |
16 |
COmanage Roadmap |
Long term roadmap of the project |
0% |
TBD |
Heather |
|
17 |
Integration Docs |
Besides using the API, how should application use groups from grouper, permissions from TBD priv system, information from LDAP, etc., in order to be fully domesticated |
20% |
12/15/2008 |
All |
Base doc started in Wiki |
|
a. document how the installers work (co-base, co-confluence, etc) |
Reverse engineer/document how the current installers work, what they do, where they put things and document those details in the relevant integration docs. |
0% |
12/15/2008 |
All |
|
|
b. document how the wizard works |
Document what pages an app should put to get a page in the wizard, remove itself from the wizard, use input from the wizard to do things, etc. |
0% |
12/15/2008 |
All |
|
|
c. Document existing packages and what they do and how they do it |
|
|
|
|
|
18 |
Stable VM of a complete Beta |
|
0% |
12/24/2008 |
All |
Stuffed in Ken's stocking |
19 |
|
|
0% |
|
|
|
20 |
General install GUI |
|
0% |
9/15/20008 |
|
Added 9/5/2008 call |
Overview
Content Tools