This is just my opinion, but I think the people in question should be nominated individually and based on merit besides having prior write access to the repo. The decisions to grant write access were likely made for a variety of reasons. I think those people should continue to have write access, but I would still like see the "significant contribution" demonstrated before they be given member status. Of course, the rules say only three additional affirmative votes are required after nomination, so if others feel differently, they should act on it.BrittonOn Wed, Sep 3, 2014 at 4:29 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Oh, that's not what I meant, I meant more like, "I want to nominate
some of these people too!"
On Wed, Sep 3, 2014 at 10:22 AM, Michael Zingale
<michael.zingale@stonybrook.edu> wrote:
> If people don't like a blanket nomination like this (I think there are 8
> there who are not members), we can put them one-by-one. Otherwise I think
> it is sporting to ask for seconds and thirds on this list.
>
>
> On Wed, Sep 3, 2014 at 10:33 AM, Matthew Turk <matthewturk@gmail.com> wrote:
>>
>> It is, but don't hog all the nominations, Mike! :)
>>
>> On Wed, Sep 3, 2014 at 8:55 AM, Michael Zingale
>> <michael.zingale@stonybrook.edu> wrote:
>> > I think that this is the list of people with repo access:
>> >
>> > https://bitbucket.org/yt_analysis/profile/members
>> >
>> >
>> > On Wed, Sep 3, 2014 at 9:54 AM, Michael Zingale
>> > <michael.zingale@stonybrook.edu> wrote:
>> >>
>> >> Britton, I believe that there are yt developers who already have access
>> >> to
>> >> the main yt_analysis repo and are able to merge, etc., but who did not
>> >> make
>> >> the initial cut in the ytep for "member" status. If someone can get a
>> >> list
>> >> of these people, I would like to nominate all of those who have
>> >> previously
>> >> enjoyed the power of member status to be members.
>> >>
>> >> Mike
>> >>
>> >>
>> >> On Wed, Sep 3, 2014 at 7:35 AM, Britton Smith <brittonsmith@gmail.com>
>> >> wrote:
>> >>>
>> >>> Greetings everyone,
>> >>>
>> >>> It's official, the YTEP on yt team structure has been accepted,
>> >>> thereby
>> >>> establishing the status of "yt member" as someone who has made
>> >>> significant
>> >>> contribution to the project. Thanks to everyone who contributed to
>> >>> making
>> >>> this happen.
>> >>>
>> >>> Now for the first items of business:
>> >>> 1. We need representatives for the five subcomponents laid out in the
>> >>> YTEP: infrastructure, testing, plotting, analysis modules, and
>> >>> documentation. Members, please volunteer to represent one of these in
>> >>> regular team meetings. Let's get at least a few for each so the
>> >>> burden
>> >>> doesn't continually fall on one person. You should have write access
>> >>> to the
>> >>> YTEP repository, so clone the repo, add your name, and push the change
>> >>> directly to the main repo: https://bitbucket.org/yt_analysis/ytep. I
>> >>> have
>> >>> just signed up for analysis modules and have agreed to take the first
>> >>> shift
>> >>> as meeting coordinator. If you're the first to sign up for one,
>> >>> consider
>> >>> reaching out to specific people that you think would also be good for
>> >>> that
>> >>> role.
>> >>>
>> >>> 2. We need people to act as liaisons for the various frontends. This
>> >>> should be anyone very familiar with that code and who can serve as a
>> >>> knowledge-base. The more the merrier for any frontend, in my opinion.
>> >>> If
>> >>> you're willing, please add yourself as above.
>> >>>
>> >>> 3. The floor is now open for nominations of new members. Members,
>> >>> look
>> >>> around you and pick out the people you think have made significant
>> >>> contribution, tangible or otherwise, and nominate them. Just send an
>> >>> to yt-dev with a couple sentences on why you think they deserve it.
>> >>> Three
>> >>> affirmative votes and they're in.
>> >>>
>> >>> 4. Go live with the yt member page. There is an open PR to the
>> >>> website
>> >>> repo to add this. Please have a look here and offer your comments.
>> >>> Once
>> >>> that's in, members should feel free to start adding bios for
>> >>> themselves.
>> >>> Have a look at that here.
>> >>>
>> >>> Once the representative table fills out, I will try to schedule the
>> >>> first
>> >>> team meeting.
>> >>>
>> >>> It's a new day for yt. Keep up the good work, everyone.
>> >>>
>> >>> Britton
>> >>>
>> >>> _______________________________________________
>> >>> yt-dev mailing list
>> >>> yt-dev@lists.spacepope.org
>> >>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Michael Zingale
>> >> Associate Professor
>> >>
>> >> Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY
>> >> 11794-3800
>> >> phone: 631-632-8225
>> >> e-mail: Michael.Zingale@stonybrook.edu
>> >> web: http://www.astro.sunysb.edu/mzingale
>> >
>> >
>> >
>> >
>> > --
>> > Michael Zingale
>> > Associate Professor
>> >
>> > Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY
>> > 11794-3800
>> > phone: 631-632-8225
>> > e-mail: Michael.Zingale@stonybrook.edu
>> > web: http://www.astro.sunysb.edu/mzingale
>> >
>> > _______________________________________________
>> > yt-dev mailing list
>> > yt-dev@lists.spacepope.org
>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev@lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
>
>
> --
> Michael Zingale
> Associate Professor
>
> Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY
> 11794-3800
> phone: 631-632-8225
> e-mail: Michael.Zingale@stonybrook.edu
> web: http://www.astro.sunysb.edu/mzingale
>
> _______________________________________________
> yt-dev mailing list
> yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org