I'd like to nominate Brian O'Shea for yt membership. Brian has supported
yt development through funding of multiple developers and for a number of
years has been very active in publicizing yt and in getting people to adopt
it for their science.
Ben has been very helpful in improving the tipsy frontend and providing
documentation optimized for people used to thinking about SPH data. He's
also a valuable source of information about how to handle SPH data in
I was originally interested in developing a frontend for the pluto code (http://plutocode.ph.unito.it/) since I am a regular user of this code, and I saw that many things for pluto were already there in yt but the pluto fronted was not activated in the frontends/api.py file (the line with ‘pluto’ is commented out). Do you know if in a more recent version of yt this has been finished up, or if it still in the process of being implemented? Thanks in advance,
It's official, the YTEP on yt team structure
<http://ytep.readthedocs.org/en/latest/YTEPs/YTEP-1776.html> 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
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 email
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
It's a new day for yt. Keep up the good work, everyone.
I've heard from the OLCF that yt is installed on titan now. The
installation was done by Fernanda Foertter (foertterfs(a)ornl.gov). She is
happy to hear about issues, and relayed that a known issue is that the
LaTeX portion of the dependencies is broken. I haven't gotten on and tried
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY
I just wanted to thank Britton for all his hard work on the issue of
governance of the project. I think it's one of the key issues that
guides a project, and I think we are going to be all the better for
it. In addition, seems like it's pretty thankless -- and so I think
it's appropriate to thank him for this hard work.
Greeting yt developers,
First, I want to congratulate everyone here on the successful release
of yt-3.0. This was a massive effort on the part of so many and a
true testament to the strength of this team.
At the time of writing this, there are 78 members of the yt-dev
mailing list. As someone who does most of their work in very small
collaborations, this amazes me and make me very proud. In case you're
wondering, the yt-users list has 268 members.
As a project, yt has a significant amount of infrastructure: code
review with pull requests, issue tracking, automated testing, emails
lists, an IRC channel, enhancement proposals, workshops. All of this
is evidence of our legitimacy as a Real Thing. However, one big
missing piece is a system of governance. I don't know exactly what
this means, but I have some ideas, which I will share below. What I
want to do right now is to start a discussion that will, hopefully,
include as many people as possible on this list.
For me, governance means (roughly) the following:
- a set of procedures in writing for how various things are to be
done, such as acceptance of pull requests, releases, designating
developers as core contributors, etc.
- a governing body to make decisions and help guide the project.
This accomplishes a number of things, which as a project I think we
need, such as:
- overall stability of the project.
- providing a system for conflict resolution.
- maintaining the spirit of yt as a team effort.
- providing a way for active contributors to get credit for their
contribution in the form of official recognition.
So, these are my initial thoughts, but I really think this deserves a
thorough discussion with as many people participating as possible.
Please, think about what governance means to you, whether we need it,
what it should be, and what we might get out of it, and share your
thoughts over the next few days. I look forward to this discussion.