| 1 |
Thanks for doing this work Michał, |
| 2 |
|
| 3 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 4 |
> Please note that we reserve the right to reject new packages, especially |
| 5 |
> if they would otherwise qualify for removal per our quality standards: |
| 6 |
|
| 7 |
Should we add something about the usefulness of packages for other |
| 8 |
users? As stated earlier, by being in main tree (and in particular part |
| 9 |
of stable set) there is support form other projects, any new package |
| 10 |
addition adds overhead. |
| 11 |
|
| 12 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 13 |
> ===Taking over an existing package=== |
| 14 |
> As a proxied maintainer, you can also (co-)maintain existing Gentoo |
| 15 |
> packages (both those with no maintainer, maintained by other proxied |
| 16 |
> maintainers and maintained by Gentoo developers/projects). In order to |
| 17 |
> take over the maintenance of a package, submit a commit adding yourself |
| 18 |
> to the {{Path|metadata.xml}} files. Usually, this commit will be |
| 19 |
> included along with other changes to the package. |
| 20 |
|
| 21 |
In the case of already maintained packages, they likely should |
| 22 |
communicate with the original maintainers first. Although I see you're |
| 23 |
touching upon it in next paragraph, the workflow seems to be |
| 24 |
communication after having worked up a patch and submitted it? |
| 25 |
|
| 26 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 27 |
> There are a few points to consider: |
| 28 |
> * If the package has an existing maintainer, he will be asked to ACK |
| 29 |
> your changes and approve your request. Gentoo developers can reject a |
| 30 |
> proxied maintainer if they have a good reason to do so. |
| 31 |
|
| 32 |
They don't really need good reasons |
| 33 |
|
| 34 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 35 |
> ===GitHub pull requests=== |
| 36 |
> The preferred way of submitting your contributions is through [https://g |
| 37 |
> ithub.com/gentoo/gentoo/pulls pull requests on our GitHub repository]. |
| 38 |
|
| 39 |
Preferred by whom? (The preferred way to submit patches to gentoo |
| 40 |
proxied maintainer project...?) |
| 41 |
|
| 42 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 43 |
> ===Bug reports=== |
| 44 |
> The classical method of submitting your changes is to attach them to the |
| 45 |
Would likely flip the order, since this is the classical way |
| 46 |
|
| 47 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 48 |
> ==Being a proxied maintainer== |
| 49 |
|
| 50 |
Should we add something on proper commit messages? And atomic changes |
| 51 |
per commit etc. |
| 52 |
|
| 53 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 54 |
> The skipped profiles include: |
| 55 |
... profiles at the time of writing include.. |
| 56 |
|
| 57 |
On 07/20/2017 10:02 AM, Michał Górny wrote: |
| 58 |
> ===Proxied maintainer in metadata.xml=== |
| 59 |
|
| 60 |
mention of bugzilla account requirement? |
| 61 |
|
| 62 |
-- |
| 63 |
Kristian Fiskerstrand |
| 64 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 65 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives