| 1 |
So, just to double check, and for the purpose of verification, what is the |
| 2 |
exact step by step method for becoming a "developer" of the kind that has a |
| 3 |
@g.o, and not necessarily a developer with full commit access? |
| 4 |
|
| 5 |
And more to the point, is current documentation on the subject accurate and |
| 6 |
up to date? |
| 7 |
|
| 8 |
|
| 9 |
On Thu, Jan 5, 2017 at 2:54 PM, Rich Freeman <rich0@g.o> wrote: |
| 10 |
|
| 11 |
> On Thu, Jan 5, 2017 at 5:20 PM, Raymond Jennings <shentino@×××××.com> |
| 12 |
> wrote: |
| 13 |
> > I personally oppose merging the foundation and dev community. |
| 14 |
> > |
| 15 |
> > As someone else pointed out, there are ways to contribute to gentoo that |
| 16 |
> do |
| 17 |
> > not involve developing. |
| 18 |
> |
| 19 |
> Developer = having an @gentoo.org email address. People who are |
| 20 |
> significant contributors in any way should be able to apply to get |
| 21 |
> these, and the process already exists for this. |
| 22 |
> |
| 23 |
> We used to make a distinction between "developers" and "staff." Now |
| 24 |
> it seems the preferred terms are developers with and without commit |
| 25 |
> access. |
| 26 |
> |
| 27 |
> -- |
| 28 |
> Rich |
| 29 |
> |
| 30 |
> |
Archives