| 1 |
Dnia 2015-10-02, o godz. 00:57:33 |
| 2 |
"Robin H. Johnson" <robbat2@g.o> napisał(a): |
| 3 |
|
| 4 |
> From this, I have a rough plot of a data model that tries to take it |
| 5 |
> into account. It doesn't cover where to store it, other than it needs to |
| 6 |
> be private. |
| 7 |
|
| 8 |
Just to be clear, do all the mail aliases get auto-generated in this |
| 9 |
model? Can we still have non-project aliases? Can we add members to |
| 10 |
project aliases externally? |
| 11 |
|
| 12 |
> = Projects have members |
| 13 |
> == members fall into two groups: developers, contributors |
| 14 |
> == members can be public or private, this controls if they are shown on the wiki etc. |
| 15 |
> == developers are public members by default |
| 16 |
> == contributors are private members by default |
| 17 |
|
| 18 |
I'm not sure if this isn't extending past project membership scope. Do |
| 19 |
private members have any significance besides receiving mail? Does that |
| 20 |
mean that anyone can join a project as a contributor (or a developer -- |
| 21 |
private member)? |
| 22 |
|
| 23 |
Again reaching into package maintainership, let's assume that package P |
| 24 |
is maintained by project P2, and developer D gives me ok to commit |
| 25 |
a change. Now, how can I check if developer D is allowed to do that? |
| 26 |
I would guess only developers who are public project members would be |
| 27 |
the official members who have that privilege. |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny |
| 32 |
<http://dev.gentoo.org/~mgorny/> |
Archives