| 1 |
On Thu, 19 Jan 2017 15:47:46 -0500 |
| 2 |
"William L. Thomson Jr." <wlt-ml@××××××.com> wrote: |
| 3 |
|
| 4 |
> If it is just one person, it is not really a project or team. Just |
| 5 |
> someone scratching their itches. |
| 6 |
|
| 7 |
A project reducing itself to one person is not grounds for dissolution |
| 8 |
of a project. |
| 9 |
|
| 10 |
Even if that project is inactive, it is not grounds for dissolution of the project. |
| 11 |
|
| 12 |
Because sometimes there is no work to be done. |
| 13 |
|
| 14 |
And sometimes the reduction to 1 is not long term. |
| 15 |
|
| 16 |
And projects serve more than a grouping of people. |
| 17 |
|
| 18 |
Projects serve as a proxy for ownership of packages, allowing |
| 19 |
smooth transfer of maintainership of a collection of related packages |
| 20 |
between maintainers. |
| 21 |
|
| 22 |
Otherwise, some really large projects with lots of packages would |
| 23 |
have dissolved to a single maintainer, somebody would have had to go |
| 24 |
through and change hundreds of metadata.xml files, only to later acquire |
| 25 |
a new member, requiring a reformulation of the project, and a repeat of |
| 26 |
going through and flipping the metadata.xml for no benefit. |
| 27 |
|
| 28 |
Projects serve as a structure to make development easier and possible. |
| 29 |
|
| 30 |
Not a structure to rap us over the knuckles. ( Though sometimes both happens, |
| 31 |
its important to know which one happens in service of the other ) |
Archives