7 Jun
2010
7 Jun
'10
12:21 p.m.
Hello all,
First my proposal:
I propose we add the invitation application to platform/applications and give it a jira
top level project
name, I further propose we add a dependency to the Enterprise pom.xml and merge the UI
tests which I have
wrote into the Enterprise UI tests.
I would rather not move the translation keys into the default document bundle until nearer
release time
because it would be nice to use the new internationalization module if possible and as
development is still
going fast, there will be changes to translations.
The state of the invitation application:
All major refactoring is finished and I am now just squashing bugs and adding new
features.
Lately I have been debugging using tests rather than manual debugging, So far I have 7 UI
tests which
with framework comprise 1207 lines in 8 files. Maintaining a fork of the UI tests is
becoming
burdensome and I think the invitation application is ready to be included.
Improvements since the version which is on the incubator:
* Each message has a "history", a list of status changes, the user who made the
change and a log
(if any) which they left regarding the change.
* An invitation sent to multiple addresses is handled as a group of invitations each of
which may
be accepted/declined individually, the sender or admin can view the group and see all of
the
messages in it as a table.
* Users see an info macro at the bottom of the screen telling them how many pending
invitations
they have (if any).
* Admins see a warning macro at the bottom of the page telling them how many message have
been
reported as spam (if any have).
* Templates are translatable and (should be) compatible with more email clients.
Tasks still to be done include:
* A means by which invitees can be allowed into a closed wiki.
* Invitation of a mailing list.
* Handling "join requests".
* Use javascript to make it easier to use and implement livetable
* Improve CSS.
WDYT?
Caleb