20 Apr
2010
20 Apr
'10
2:58 p.m.
On Apr 20, 2010, at 2:45 PM, Caleb James DeLisle wrote:
Thanks
-Vincent
Another matter is what should it be named, I have been
calling it "friendInviter" which is an awkward name
but invitation manager is a name which will lead to confusion since it does not use the
invitation manager
plugin.
Since it's meant to replace the existing invitation manager so it seems a good name
for me. It's the invitation manager plugin done using the component architecture.
It could also simply be called xwiki-invitation, i.e. the "Invitation" module.
Vincent Massol wrote:
Jerome, Caty: do you think you could comment on that?
- I'm mentioning Jerome since he's the one who coded the invitation manager for
XWS. We need to make sure it's not missing anything important in term of features or
ease of use
- I'm mentioning Caty since she's been participating a lot to our XE design for a
while
Everyone should participate of course! Please all voice your opinions about what the
invitation module should have both in term of features and UI.
On Apr 20, 2010, at 12:42 PM, Caleb James DeLisle
wrote:
I described what I
hoped to achieve here:
http://www.pubbs.net/201001/xwiki/60333-xwiki-devs-proposal-allow-users-to-…
and show a mockup of its UI so that we can agree about it and get help for our community
designers
There has been one here for a while, I rewrote the code but the UI is the same.
http://incubator.myxwiki.org/xwiki/bin/view/InvitationMail/FriendInviter I have a working prototype of the invitation mail
sender and I would like to put it in the sandbox.
I need to know how that should be done and should this be a separate top level project on
jira?
Some guidance here would be great.
+1 for a top level app in platform/applications (which means a jira for it too).
As for the process, I'm proposing:
1) explain what this app would do (maybe you already did?) 2) send a vote
mail to include the invitation manager in XE by default (if not already done)
I'd like to have something concrete in the sandbox to vote on.
3) code it, you could start in the sandbox indeed
or directly in platform/applications if 1) and 2) have been agreed on.
I will
commit to the sandbox later today.