<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 30, 2014 at 9:50 AM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
</div></div>I want to emphasize that the initial list of members Britton came up<br>
with (as he noted in the proposal) is only an *initial* list, and will<br>
hopefully very quickly expand to include less active "developers" who<br>
are nonetheless embedded in the community.<br>
<br>
-Matt<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>And this is why I think we need a list of people who are regarded as "core" developers, to differentiate them from the what will likely be a very large list of "members". Right now from a professional standpoint, there is very little benefit from contributing to the code base, in that very few people recognize your contributions (ie a handful of other developers). Aside from a list of core developers that are highlighted on the webpage, or having a new yt paper come out, I don't see any other way in which this can be remedied. Perhaps others have ideas?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
><br>
> Brian<br>
><br>
><br>
><br>
> On Sat, Aug 30, 2014 at 9:30 AM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
> wrote:<br>
>><br>
>> HI Brian,<br>
>><br>
>> I couldn't agree more on having a documentation representative present at<br>
>> team meetings. In fact, I think this was even in my original draft, but I<br>
>> somehow lost track of it. Thanks for bringing it up. I will get that back<br>
>> in there. A community representative is also a good idea, but I'm less sure<br>
>> how that role would be filled. If anyone has any thoughts on that, please<br>
>> do share. If it can't be figured out before the YTEP is accepted, we can<br>
>> definitely amend it. Thanks, Brian!<br>
>><br>
>> Britton<br>
>><br>
>><br>
>> On Fri, Aug 29, 2014 at 10:16 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi Brian,<br>
>>><br>
>>> On Fri, Aug 29, 2014 at 3:32 PM, Brian O'Shea <<a href="mailto:bwoshea@gmail.com">bwoshea@gmail.com</a>> wrote:<br>
>>> > Hi folks,<br>
>>> ><br>
>>> > Chiming in as somebody who is on the far periphery of yt development<br>
>>> > (having<br>
>>> > only contributed a couple of bug fixes/minor updates), I think that<br>
>>> > creation<br>
>>> > of a formal governance structure is a significant positive step. Given<br>
>>> > the<br>
>>> > distributed nature of the development team some level of coordination<br>
>>> > is<br>
>>> > critical, and I also think that having a set of carefully-considered<br>
>>> > standards about who gets a vote in terms of code direction, and how<br>
>>> > many of<br>
>>> > these votes are needed to enact substantial change (as opposed to the<br>
>>> > ad-hoc<br>
>>> > "preponderance of +1s from the mailing list" method) is an exceedingly<br>
>>> > good<br>
>>> > idea, as it will hopefully enhance the group's decision-making and make<br>
>>> > it<br>
>>> > more reflective.<br>
>>> ><br>
>>> > I also want to comment on the monthly team meetings. In addition to<br>
>>> > posting<br>
>>> > meeting minutes, perhaps the meeting coordinator or secretary could<br>
>>> > organize<br>
>>> > an agenda for the meeting and post it to the yt-dev mailing list a<br>
>>> > couple of<br>
>>> > days ahead of time? That way, people who are not participating in the<br>
>>> > meeting, but who may have some input on the issues at hand, have an<br>
>>> > opportunity to email suggestions.<br>
>>> ><br>
>>> > Finally, one other point: I can't help but notice that while the<br>
>>> > technical<br>
>>> > aspects of yt will be represented in these team meetings, there is no<br>
>>> > *explicit* representation of the yt user community or yt documentation.<br>
>>> > While in principle this isn't a problem -- Matt has made the point many<br>
>>> > times that the difference between user and developer isn't necessarily<br>
>>> > meaningful in our context -- I do think that having somebody involved<br>
>>> > whose<br>
>>> > explicit responsibility is to consider the questions "how will this<br>
>>> > impact<br>
>>> > the broader yt user community?" and "what's missing from the<br>
>>> > documentation<br>
>>> > that could be added or improved?" may be beneficial.<br>
>>><br>
>>> Yes, I agree. I actually have a few people I would submit as<br>
>>> nominations for this role, but it seems to me it's certainly one that<br>
>>> should be represented.<br>
>>><br>
>>> ><br>
>>> > Anyway, small nit-picks aside, I think this is a great idea. Thanks to<br>
>>> > Britton for starting the ball rolling!<br>
>>> ><br>
>>> > --Brian<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > On Tue, Aug 26, 2014 at 4:20 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> Hi Britton,<br>
>>> >><br>
>>> >> I think this is really, really important, and I'm really happy with<br>
>>> >> the YTEP as it stands.<br>
>>> >><br>
>>> >> We've only gotten feedback from a few people. I think it's really<br>
>>> >> important to get both positive and negative feedback from people on<br>
>>> >> this -- even to the level of "geez, stop taking yourselves so<br>
>>> >> seriously!" :) Do you think maybe an email to the yt-users mailing<br>
>>> >> list would be productive? Or even directly writing to the people<br>
>>> >> identified as "founding" members?<br>
>>> >><br>
>>> >> -Matt<br>
>>> >><br>
>>> >> On Mon, Aug 25, 2014 at 4:50 PM, Britton Smith<br>
>>> >> <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>> >> wrote:<br>
>>> >> > Hi everyone,<br>
>>> >> ><br>
>>> >> > I have just issued a pull request to the YTEP repository containing<br>
>>> >> > an<br>
>>> >> > initial draft of yt team guidelines. I encourage everyone to take a<br>
>>> >> > look at<br>
>>> >> > it and offer their feedback. In case you don't get the<br>
>>> >> > notification,<br>
>>> >> > the PR<br>
>>> >> > can be viewed here:<br>
>>> >> ><br>
>>> >> ><br>
>>> >> > <a href="https://bitbucket.org/yt_analysis/ytep/pull-request/40/ytep-1776-team-infrastructure/diff" target="_blank">https://bitbucket.org/yt_analysis/ytep/pull-request/40/ytep-1776-team-infrastructure/diff</a><br>
>>> >> ><br>
>>> >> > Britton<br>
>>> >> ><br>
>>> >> ><br>
>>> >> > On Mon, Aug 18, 2014 at 12:24 PM, Britton Smith<br>
>>> >> > <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>> >> > wrote:<br>
>>> >> >><br>
>>> >> >> Hi Sam,<br>
>>> >> >><br>
>>> >> >> This is an excellent point. I think it's important not to<br>
>>> >> >> overburden a<br>
>>> >> >> single person by being forever responsible for a large chunk of the<br>
>>> >> >> code. I<br>
>>> >> >> also think it's good to give as many as are willing an opportunity<br>
>>> >> >> to<br>
>>> >> >> share<br>
>>> >> >> the role. Perhaps there is a team of people or subcommittee that<br>
>>> >> >> is<br>
>>> >> >> responsible for figuring out who their representative is. This can<br>
>>> >> >> be<br>
>>> >> >> ironed out.<br>
>>> >> >><br>
>>> >> >> I think we've gotten enough positive response to start thinking<br>
>>> >> >> about a<br>
>>> >> >> YTEP that lays it all out. I will start something this week, ask<br>
>>> >> >> for<br>
>>> >> >> feedback, and we can all develop this together.<br>
>>> >> >><br>
>>> >> >> In the mean time, if you would still like to chime in on this<br>
>>> >> >> discussion,<br>
>>> >> >> please do so.<br>
>>> >> >> Thanks, everyone.<br>
>>> >> >><br>
>>> >> >> Britton<br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> On Sun, Aug 17, 2014 at 4:20 PM, Sam Skillman<br>
>>> >> >> <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>><br>
>>> >> >> wrote:<br>
>>> >> >>><br>
>>> >> >>> Hi all,<br>
>>> >> >>><br>
>>> >> >>> Britton -- I really like these ideas, and I like the member level<br>
>>> >> >>> being<br>
>>> >> >>> defined as write access.<br>
>>> >> >>><br>
>>> >> >>> I'm a bit more concerned about the officers designation in terms<br>
>>> >> >>> of<br>
>>> >> >>> the<br>
>>> >> >>> logistics of matching people with sections of the code. I could<br>
>>> >> >>> see<br>
>>> >> >>> something working where on a 6-month basis, each of the main areas<br>
>>> >> >>> in<br>
>>> >> >>> yt are<br>
>>> >> >>> assigned a lead. That lead isn't necessarily the person who has<br>
>>> >> >>> written the<br>
>>> >> >>> most in the area, but rather a person who is willing to keep track<br>
>>> >> >>> of<br>
>>> >> >>> that<br>
>>> >> >>> area of the codebase for the next 6 months, so that when it comes<br>
>>> >> >>> to<br>
>>> >> >>> doing<br>
>>> >> >>> releases, they are the ones that know what has changed and where<br>
>>> >> >>> things are<br>
>>> >> >>> not working well. Maybe that's too much of a process, but I also<br>
>>> >> >>> think we<br>
>>> >> >>> should be wary of assigning potentially long-lasting labels to<br>
>>> >> >>> either<br>
>>> >> >>> people<br>
>>> >> >>> or code. Semi-regular meetings for this set of people would be<br>
>>> >> >>> great.<br>
>>> >> >>><br>
>>> >> >>> Anyways, I'm definitely a +1 on a YTEP for all of this, and look<br>
>>> >> >>> forward<br>
>>> >> >>> to hearing more!<br>
>>> >> >>><br>
>>> >> >>> Cheers,<br>
>>> >> >>> Sam<br>
>>> >> >>><br>
>>> >> >>><br>
>>> >> >>> On Sat, Aug 16, 2014 at 7:08 PM, B.W. Keller<br>
>>> >> >>> <<a href="mailto:kellerbw@mcmaster.ca">kellerbw@mcmaster.ca</a>><br>
>>> >> >>> wrote:<br>
>>> >> >>>><br>
>>> >> >>>> +1, absolutely. Right now, yt has a really high bus factor. I<br>
>>> >> >>>> think<br>
>>> >> >>>> this would help that a lot.<br>
>>> >> >>>><br>
>>> >> >>>><br>
>>> >> >>>> On Fri, Aug 15, 2014 at 7:40 PM, Chris Malone<br>
>>> >> >>>> <<a href="mailto:chris.m.malone@gmail.com">chris.m.malone@gmail.com</a>><br>
>>> >> >>>> wrote:<br>
>>> >> >>>>><br>
>>> >> >>>>> +1 as well on all suggestions<br>
>>> >> >>>>><br>
>>> >> >>>>> > On Aug 15, 2014, at 5:32 PM, Kenza Arraki <<a href="mailto:karraki@nmsu.edu">karraki@nmsu.edu</a>><br>
>>> >> >>>>> > wrote:<br>
>>> >> >>>>> ><br>
>>> >> >>>>> > I wanted to put my strong +1 out there even though I don't<br>
>>> >> >>>>> > respond<br>
>>> >> >>>>> > often to dev emails. This sounds like a great direction for<br>
>>> >> >>>>> > yt!<br>
>>> >> >>>>> ><br>
>>> >> >>>>> > -Kenza<br>
>>> >> >>>>> ><br>
>>> >> >>>>> > ---<br>
>>> >> >>>>> > Kenza Arraki<br>
>>> >> >>>>> > PhD candidate<br>
>>> >> >>>>> > New Mexico State University<br>
>>> >> >>>>> > Department of Astronomy<br>
>>> >> >>>>> ><br>
>>> >> >>>>> ><br>
>>> >> >>>>> > On Fri, Aug 15, 2014 at 4:06 PM, Michael Zingale<br>
>>> >> >>>>> > <<a href="mailto:michael.zingale@stonybrook.edu">michael.zingale@stonybrook.edu</a>> wrote:<br>
>>> >> >>>>> >> these all sound like good ideas to me. Some simply operating<br>
>>> >> >>>>> >> procedures,<br>
>>> >> >>>>> >> like "don't merge your own pull requests" might be good too.<br>
>>> >> >>>>> >><br>
>>> >> >>>>> >><br>
>>> >> >>>>> >> On Fri, Aug 15, 2014 at 3:50 PM, Britton Smith<br>
>>> >> >>>>> >> <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>> >> >>>>> >> wrote:<br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>> I'm very in favor of putting some official procedures into a<br>
>>> >> >>>>> >>> YTEP.<br>
>>> >> >>>>> >>> Having<br>
>>> >> >>>>> >>> a codified process may also help with conflict resolution as<br>
>>> >> >>>>> >>> well.<br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>> Apache does something with their projects where developers<br>
>>> >> >>>>> >>> who<br>
>>> >> >>>>> >>> make<br>
>>> >> >>>>> >>> sustained contribution are made "members" after nomination<br>
>>> >> >>>>> >>> by<br>
>>> >> >>>>> >>> another member<br>
>>> >> >>>>> >>> and are given write access to the main repo. It's a small<br>
>>> >> >>>>> >>> thing,<br>
>>> >> >>>>> >>> but if we<br>
>>> >> >>>>> >>> perhaps have an official definition of "yt member" in a YTEP<br>
>>> >> >>>>> >>> with a<br>
>>> >> >>>>> >>> posted<br>
>>> >> >>>>> >>> list of members, it can be something people can point to as<br>
>>> >> >>>>> >>> a<br>
>>> >> >>>>> >>> way<br>
>>> >> >>>>> >>> of<br>
>>> >> >>>>> >>> demonstrating that they've done significant work on the<br>
>>> >> >>>>> >>> project.<br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>> I think it might also be good to have officer-like positions<br>
>>> >> >>>>> >>> where<br>
>>> >> >>>>> >>> people<br>
>>> >> >>>>> >>> are representatives for various areas of the code, such as<br>
>>> >> >>>>> >>> data<br>
>>> >> >>>>> >>> structures,<br>
>>> >> >>>>> >>> visualization, analysis_modules, etc. and to have<br>
>>> >> >>>>> >>> semi-regular<br>
>>> >> >>>>> >>> meeting of<br>
>>> >> >>>>> >>> these people. This may be as much leadership as we need for<br>
>>> >> >>>>> >>> now,<br>
>>> >> >>>>> >>> just a<br>
>>> >> >>>>> >>> group that meets on a schedule to make sure everyone's on<br>
>>> >> >>>>> >>> the<br>
>>> >> >>>>> >>> same<br>
>>> >> >>>>> >>> page with<br>
>>> >> >>>>> >>> releases and major development efforts.<br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>> What do people think of something like this?<br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>> On Wed, Aug 13, 2014 at 4:58 PM, Matthew Turk<br>
>>> >> >>>>> >>> <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>> >> >>>>> >>> wrote:<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> Hi Britton,<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> Thanks for bringing this up -- it's a tough topic, but also<br>
>>> >> >>>>> >>>> I<br>
>>> >> >>>>> >>>> think<br>
>>> >> >>>>> >>>> really important. At the WSSSPE conference last year, a<br>
>>> >> >>>>> >>>> paper<br>
>>> >> >>>>> >>>> was<br>
>>> >> >>>>> >>>> submitted talking about the Apache model:<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> <a href="http://figshare.com/articles/Sustainable_Cyberinfrastructure_Software_Through_Open_Governance/790761" target="_blank">http://figshare.com/articles/Sustainable_Cyberinfrastructure_Software_Through_Open_Governance/790761</a><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> which talks about a lot of related topics. Apache does<br>
>>> >> >>>>> >>>> some<br>
>>> >> >>>>> >>>> interesting things. They use the word "meritocracy" which<br>
>>> >> >>>>> >>>> I am<br>
>>> >> >>>>> >>>> rather<br>
>>> >> >>>>> >>>> -1 on using (see, for instance,<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> <a href="http://www.ashedryden.com/blog/the-ethics-of-unpaid-labor-and-the-oss-community" target="_blank">http://www.ashedryden.com/blog/the-ethics-of-unpaid-labor-and-the-oss-community</a><br>
>>> >> >>>>> >>>> ) but I do think there is something to be said for a large<br>
>>> >> >>>>> >>>> part<br>
>>> >> >>>>> >>>> of<br>
>>> >> >>>>> >>>> their methods of organization.<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> Like you, I think we are overdue. I would like to point<br>
>>> >> >>>>> >>>> out<br>
>>> >> >>>>> >>>> that,<br>
>>> >> >>>>> >>>> for<br>
>>> >> >>>>> >>>> all intents and purposes, you are *already* the ombudsman<br>
>>> >> >>>>> >>>> for<br>
>>> >> >>>>> >>>> the<br>
>>> >> >>>>> >>>> yt<br>
>>> >> >>>>> >>>> community. I don't think you're proposing we have a<br>
>>> >> >>>>> >>>> committee<br>
>>> >> >>>>> >>>> that<br>
>>> >> >>>>> >>>> bosses everyone around, but rather one that enables a<br>
>>> >> >>>>> >>>> larger<br>
>>> >> >>>>> >>>> number of<br>
>>> >> >>>>> >>>> people to have a say, particularly because yt has become<br>
>>> >> >>>>> >>>> embedded<br>
>>> >> >>>>> >>>> in<br>
>>> >> >>>>> >>>> many of our scientific workflows and it touches a lot of<br>
>>> >> >>>>> >>>> research<br>
>>> >> >>>>> >>>> activities now. I like the idea of members. I like the<br>
>>> >> >>>>> >>>> idea<br>
>>> >> >>>>> >>>> of a<br>
>>> >> >>>>> >>>> project management committee, but it's not clear to me how<br>
>>> >> >>>>> >>>> that<br>
>>> >> >>>>> >>>> would<br>
>>> >> >>>>> >>>> work, or which decisions we have made recently that they<br>
>>> >> >>>>> >>>> would<br>
>>> >> >>>>> >>>> weigh<br>
>>> >> >>>>> >>>> in on. I also really like the idea of having "code<br>
>>> >> >>>>> >>>> liasons" to<br>
>>> >> >>>>> >>>> different data platforms and/or communities, and the idea<br>
>>> >> >>>>> >>>> of<br>
>>> >> >>>>> >>>> having<br>
>>> >> >>>>> >>>> people who are responsible for many different areas of the<br>
>>> >> >>>>> >>>> code<br>
>>> >> >>>>> >>>> and<br>
>>> >> >>>>> >>>> codifying that in some way is quite attractive to me.<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> For what it's worth, a few weeks ago I gave a presentation<br>
>>> >> >>>>> >>>> on<br>
>>> >> >>>>> >>>> my<br>
>>> >> >>>>> >>>> "vision" for the future of yt (<a href="http://goo.gl/JKt6MA" target="_blank">http://goo.gl/JKt6MA</a>). The<br>
>>> >> >>>>> >>>> thing<br>
>>> >> >>>>> >>>> is,<br>
>>> >> >>>>> >>>> while I gave this presentation, it's just *my* vision -- it<br>
>>> >> >>>>> >>>> is<br>
>>> >> >>>>> >>>> not<br>
>>> >> >>>>> >>>> necessarily anyone else's vision. And I think it's time we<br>
>>> >> >>>>> >>>> have<br>
>>> >> >>>>> >>>> some<br>
>>> >> >>>>> >>>> method of taking into account a diverse set of opinions for<br>
>>> >> >>>>> >>>> what<br>
>>> >> >>>>> >>>> we as<br>
>>> >> >>>>> >>>> a community can emphasize, how we resolve conflicts, and so<br>
>>> >> >>>>> >>>> on<br>
>>> >> >>>>> >>>> and<br>
>>> >> >>>>> >>>> so<br>
>>> >> >>>>> >>>> forth.<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> Again, thanks for bringing this up. We need to have this<br>
>>> >> >>>>> >>>> conversation.<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> -Matt<br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> On Tue, Aug 12, 2014 at 4:11 PM, Britton Smith<br>
>>> >> >>>>> >>>> <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>> >> >>>>> >>>> wrote:<br>
>>> >> >>>>> >>>>> Greeting yt developers,<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> First, I want to congratulate everyone here on the<br>
>>> >> >>>>> >>>>> successful<br>
>>> >> >>>>> >>>>> release<br>
>>> >> >>>>> >>>>> of yt-3.0. This was a massive effort on the part of so<br>
>>> >> >>>>> >>>>> many<br>
>>> >> >>>>> >>>>> and<br>
>>> >> >>>>> >>>>> a<br>
>>> >> >>>>> >>>>> true testament to the strength of this team.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> At the time of writing this, there are 78 members of the<br>
>>> >> >>>>> >>>>> yt-dev<br>
>>> >> >>>>> >>>>> mailing list. As someone who does most of their work in<br>
>>> >> >>>>> >>>>> very<br>
>>> >> >>>>> >>>>> small<br>
>>> >> >>>>> >>>>> collaborations, this amazes me and make me very proud. In<br>
>>> >> >>>>> >>>>> case<br>
>>> >> >>>>> >>>>> you're<br>
>>> >> >>>>> >>>>> wondering, the yt-users list has 268 members.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> As a project, yt has a significant amount of<br>
>>> >> >>>>> >>>>> infrastructure:<br>
>>> >> >>>>> >>>>> code<br>
>>> >> >>>>> >>>>> review with pull requests, issue tracking, automated<br>
>>> >> >>>>> >>>>> testing,<br>
>>> >> >>>>> >>>>> emails<br>
>>> >> >>>>> >>>>> lists, an IRC channel, enhancement proposals, workshops.<br>
>>> >> >>>>> >>>>> All<br>
>>> >> >>>>> >>>>> of<br>
>>> >> >>>>> >>>>> this<br>
>>> >> >>>>> >>>>> is evidence of our legitimacy as a Real Thing. However,<br>
>>> >> >>>>> >>>>> one<br>
>>> >> >>>>> >>>>> big<br>
>>> >> >>>>> >>>>> missing piece is a system of governance. I don't know<br>
>>> >> >>>>> >>>>> exactly<br>
>>> >> >>>>> >>>>> what<br>
>>> >> >>>>> >>>>> this means, but I have some ideas, which I will share<br>
>>> >> >>>>> >>>>> below.<br>
>>> >> >>>>> >>>>> What I<br>
>>> >> >>>>> >>>>> want to do right now is to start a discussion that will,<br>
>>> >> >>>>> >>>>> hopefully,<br>
>>> >> >>>>> >>>>> include as many people as possible on this list.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> For me, governance means (roughly) the following:<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> - a set of procedures in writing for how various things<br>
>>> >> >>>>> >>>>> are to<br>
>>> >> >>>>> >>>>> be<br>
>>> >> >>>>> >>>>> done, such as acceptance of pull requests, releases,<br>
>>> >> >>>>> >>>>> designating<br>
>>> >> >>>>> >>>>> developers as core contributors, etc.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> - a governing body to make decisions and help guide the<br>
>>> >> >>>>> >>>>> project.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> This accomplishes a number of things, which as a project I<br>
>>> >> >>>>> >>>>> think<br>
>>> >> >>>>> >>>>> we<br>
>>> >> >>>>> >>>>> need, such as:<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> - overall stability of the project.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> - providing a system for conflict resolution.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> - maintaining the spirit of yt as a team effort.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> - providing a way for active contributors to get credit<br>
>>> >> >>>>> >>>>> for<br>
>>> >> >>>>> >>>>> their<br>
>>> >> >>>>> >>>>> contribution in the form of official recognition.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> So, these are my initial thoughts, but I really think this<br>
>>> >> >>>>> >>>>> deserves a<br>
>>> >> >>>>> >>>>> thorough discussion with as many people participating as<br>
>>> >> >>>>> >>>>> possible.<br>
>>> >> >>>>> >>>>> Please, think about what governance means to you, whether<br>
>>> >> >>>>> >>>>> we<br>
>>> >> >>>>> >>>>> need<br>
>>> >> >>>>> >>>>> it,<br>
>>> >> >>>>> >>>>> what it should be, and what we might get out of it, and<br>
>>> >> >>>>> >>>>> share<br>
>>> >> >>>>> >>>>> your<br>
>>> >> >>>>> >>>>> thoughts over the next few days. I look forward to this<br>
>>> >> >>>>> >>>>> discussion.<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> Britton<br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> _______________________________________________<br>
>>> >> >>>>> >>>>> yt-dev mailing list<br>
>>> >> >>>>> >>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>>> >>>>><br>
>>> >> >>>>> >>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>>> >>>> _______________________________________________<br>
>>> >> >>>>> >>>> yt-dev mailing list<br>
>>> >> >>>>> >>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>>> >>>><br>
>>> >> >>>>> >>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>><br>
>>> >> >>>>> >>> _______________________________________________<br>
>>> >> >>>>> >>> yt-dev mailing list<br>
>>> >> >>>>> >>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>>> >>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>>> >><br>
>>> >> >>>>> >><br>
>>> >> >>>>> >><br>
>>> >> >>>>> >> --<br>
>>> >> >>>>> >> Michael Zingale<br>
>>> >> >>>>> >> Associate Professor<br>
>>> >> >>>>> >><br>
>>> >> >>>>> >> Dept. of Physics & Astronomy • Stony Brook University • Stony<br>
>>> >> >>>>> >> Brook,<br>
>>> >> >>>>> >> NY<br>
>>> >> >>>>> >> 11794-3800<br>
>>> >> >>>>> >> phone: <a href="tel:631-632-8225" value="+16316328225">631-632-8225</a><br>
>>> >> >>>>> >> e-mail: <a href="mailto:Michael.Zingale@stonybrook.edu">Michael.Zingale@stonybrook.edu</a><br>
>>> >> >>>>> >> web: <a href="http://www.astro.sunysb.edu/mzingale" target="_blank">http://www.astro.sunysb.edu/mzingale</a><br>
>>> >> >>>>> >><br>
>>> >> >>>>> >> _______________________________________________<br>
>>> >> >>>>> >> yt-dev mailing list<br>
>>> >> >>>>> >> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>>> >> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>>> > _______________________________________________<br>
>>> >> >>>>> > yt-dev mailing list<br>
>>> >> >>>>> > <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>>> _______________________________________________<br>
>>> >> >>>>> yt-dev mailing list<br>
>>> >> >>>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>><br>
>>> >> >>>><br>
>>> >> >>>><br>
>>> >> >>>> _______________________________________________<br>
>>> >> >>>> yt-dev mailing list<br>
>>> >> >>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>>><br>
>>> >> >>><br>
>>> >> >>><br>
>>> >> >>> _______________________________________________<br>
>>> >> >>> yt-dev mailing list<br>
>>> >> >>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> >>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> >>><br>
>>> >> >><br>
>>> >> ><br>
>>> >> ><br>
>>> >> > _______________________________________________<br>
>>> >> > yt-dev mailing list<br>
>>> >> > <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> >> ><br>
>>> >> _______________________________________________<br>
>>> >> yt-dev mailing list<br>
>>> >> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> >> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > yt-dev mailing list<br>
>>> > <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>> ><br>
>>> _______________________________________________<br>
>>> yt-dev mailing list<br>
>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> yt-dev mailing list<br>
> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Cameron Hummels<div>Postdoctoral Researcher</div><div>Steward Observatory</div><div>University of Arizona</div><div><a href="http://chummels.org" target="_blank">http://chummels.org</a></div>
</div></div>