> ok, let's try another analogy:
> does this help?
Yeap, got it, thanks. :)
In my proposal I wrote only about the users that Clio will be aware of.
I have one last question. Clio stands for "Components, Licenses, Ip and
Other information".
Yet, I don't see a single reference to IPs in the description. How are IPs
related to the project?
2017-03-25 22:44 GMT+02:00 Alexios Zavras <zvr+eellak [ at ] zvr [ dot ] gr>:
> Ηλίας Σταμάτης wrote [edited]:
> >> the person who adds users is not the same as the person who configures
> >> where the database is,
> > The person who configures the database and does administrative tasks on
> the
> > server is the sysadmin. I don't think that Clio, the software, has to
> know
> > anything about sysadmins. So, I don't think that any special user
> category
> > needs to exist in the database for system administrators. Do you agree
> with
> > that?
>
> ah, so in your mind there is yet another set of people
> that you call "sysadmins"...
> try to think that there might be more (as is often the case):
> people who mantain the database systems, people who maintain
> other parts of the operating system, people who maintain
> the network -- and people who will install and manage Clio.
>
> I never said that all these sets have to be known to Clio.
>
> I do not know whether the underlying system (django, in your case)
> makes use of its own set of users.
>
>
> > Could you please give me the rationale behind the following? "some users
> > will be able to create simple components, some other category of users
> will
> > be able to create complex components". Why do we need different
> categories
> > of users since it seems to be the exact same action?
>
> going back to the spreadsheet analogy,
> - people who create spradsheets; and
> - people who add functions like SUM() to be used in all spreadsheets
> are not usually considered to do "the exact same action"
>
>
> ok, let's try another analogy:
> - CLIO is like a system for managing online recipes.
> - each recipe uses a set of ingredients.
> - the ingredients are chosen from a common list of ingredient ("catalog")
>
> many can create (and own) a recipe;
> few can modify the catalog of ingredients to be used.
>
> does this help?
>
>
> > Also, another question: The information of who's owning a component will
> be
> > visible to the rest?
>
> yes, it's one of the attributes of the complex component.
> ideally information about changes is also kept
> (because owners might change over time, etc.).
>
>
> --
> -- zvr --
> -- +---------------------------+ Alexios Zavras (-zvr-)
> | H eytyxia den exei enoxes | zvr [ at ] zvr [ dot ] gr
> +-----------------------zvr-+
>
----
Λαμβάνετε αυτό το μήνυμα απο την λίστα: Γενική λίστα αλληλογραφίας που απευθύνεται σε developers/contributors έργων ανοικτού λογισμικού - A general discussion list for developers/contributors of open-source projects,
https://lists.ellak.gr/opensource-devs/listinfo.html
Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. ταχυδρομείου στη διεύθυνση <opensource-devs+unsubscribe [ at ] ellak [ dot ] gr>.