Comments (14)
migrated from Trac, where originally posted by marko_lipo on 15-Sep-2010 9:34pm
Source ticket: #14
from netbout.
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 3:23pm
Good correction, and I think we should go a bit further. Every user should have an ability to define a number of identifies for himself. See the example: http://linux.fazend.com/p/netbout/trunk/start. When he starts a new bout he selects the identity to be used in the bout.
When he is talking in a bout (see http://linux.fazend.com/p/netbout/trunk/b/3) he always know what is the identity used now (top right corner - it's his picture).
Thus, we need to specify the functionality in SRS that will allow ActorUser to define identities, and use them when starting a new bout.
from netbout.
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 3:24pm
Yuri, see the explanation about. This ticket is for you. Please, make changes to the SRS accordingly.
from netbout.
migrated from Trac, where originally posted by y.vedenin on 5-Oct-2010 3:01pm
I assume that identity here is avatar + name + bio + signature.
Please, approve.
I assume that the following changes should be made:
- I propose to add the following page:
UserIdentity is a user's identity to be used in a bout.
UserIdentity includes:
- avatar: "PNG image with maximum height/width of 300px";
- name: text "user's name, surname or his company name";
- bio: text "optional text about the user, visible to his contacts";
- signature: text "to be used in emails sent from this user to others";
Please, approve.
- The ActorUser page should be updated as follows:
id: text "conditionally optional unique identifier of the user, which is very similar to user name in emails; id or email is sure to be specified";
password: text "5+ symbols password";
email: text "conditionally optional unique email according to RFC5322; id or email is sure to be specified";
UserIdentity-s: user's identities;
delivery method: "how we should deliver data updates to this user: email, SMS, nothing";
bill-s: "monetary value to be paid to an owner of ActorHelper";
balance: "total amount to be paid after the end of next billing period, equals to SUM(bills) - SUM(payments)";
payment-s: "online payment made by the user to the SUD through ActorBank";
status: "either active or pending, which means that ActorBank failed to process the latest payment";
bout-s: NetBout "where the user is a participant";
contact-s: ActorUser "who had been with the user in the same bout, ever";
tag-s: "which was used by the user at least once".
Please, approve.
- The UC should be updated as follows:
- The user identifies himself. (UC6)
- The user selects UserIdentity.
- The user creates the bout.
- The user accepts invitation. (UC7)
Does it make sense?
- I assume that the UC7 should be updated as well:
UC7 where ActorUser accepts invitation: "When the user receives a notification about an invitation into a NetBout, he has an option to accept it or decline. If he doesn't accept it during 7 days, it means he declines it. When invitation is accepted the user starts talking in the NetBout.".
should be replaced with:
UC7 where ActorUser accepts invitation: "When the user receives a notification about an invitation into a NetBout, he has an option to accept it or decline. If he doesn't accept it during 7 days, it means he declines it. When invitation is accepted and UserIdentity is selected the user starts talking in the NetBout.".
Please, approve.
from netbout.
migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 4:56pm
-
and 2) -- agree
-
We don't need to add this line here explicitly.
the user creates the bout
means that a new object (the bout
) is instantiated with all its internal properties. One property of the bout participant should beidentity
.
Thus, we don't change the UC. We change the definition of NetBout, in particular we add one more property to the participant of NetBout
: identity
.
- The same story here. You don't need to mention
identity
here explicitly. Instead, we should say inparticipant of NetBout
thatidentity
is set whenstatus
of participant isaccepted
.
Makes sense?
from netbout.
migrated from Trac, where originally posted by yegor256 on 21-Feb-2011 7:36am
Yuri, any news here? Please update. If we have no answer in the next 7 days I will have to assign the ticket to someone else.
from netbout.
migrated from Trac, where originally posted by y.vedenin on 22-Feb-2011 11:53am
I'll update the tickets till Wednesday, February 23, 2011
from netbout.
migrated from Trac, where originally posted by y.vedenin on 25-Feb-2011 6:30pm
The following pages were updated/created:
- [wiki:BoutParticipant@4]
- [wiki:ActorUser@16]
- [wiki:UserIdentity@1]
Please, check.
from netbout.
migrated from Trac, where originally posted by yegor256 on 28-Feb-2011 5:28pm
Looks good, but we need to remove avatar
, bio
, and signature
from ActorUser. They are in UserIdentity now.
from netbout.
migrated from Trac, where originally posted by y.vedenin on 4-Mar-2011 6:02pm
The [wiki:ActorUser@18] page was updated.
Please, check.
from netbout.
migrated from Trac, where originally posted by yegor256 on 7-Mar-2011 6:00pm
Small fix applied: ActorUser@19 (actually this should be automatically caught by RQDQL).
Everything is fine for me. Marko, take a look. Did we resolve the problem?
from netbout.
migrated from Trac, where originally posted by marko_lipo on 7-Mar-2011 8:42pm
yes it is fine now.
from netbout.
migrated from Trac, where originally posted by yegor256 on 8-Mar-2011 7:42am
Thanks all, the ticket is closed.
from netbout.
migrated from Trac, where originally posted by yegor256 on 23-Nov-2011 9:06am
Milestone JUN11 deleted
from netbout.
Related Issues (20)
- migrate to Dokku HOT 11
- Dependency conflicts on com.jcabi:jcabi-log, leading to inconsistent program behaviors HOT 3
- ruby release HOT 21
- Dependency Dashboard
- Testcontainers configuration for database bootstrapping HOT 2
- login fails due to lack of tests HOT 3
- simple search should work HOT 3
- Login does not work HOT 8
- search parsing
- permissions HOT 5
- extra restrictions HOT 3
- search doesn't work for flags and tags HOT 3
- login via token HOT 3
- token login is not tested well HOT 3
- JSON API is not tested well HOT 3
- more details in JSON API HOT 3
- Codecov check doesn't work HOT 1
- offset and limit don't work in search API HOT 6
- `absent` doesn't work HOT 6
- move to heroku HOT 18
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from netbout.