# 2022 CoCo Election: Pey Lian Lim **URL:** \ **Category:** Astropy\ **Tags:** astropy, coco-election\ **Created:** [September 24, 2022, 8:14am UTC](https://community.openastronomy.org/t/2022-coco-election-pey-lian-lim/462 "2022-09-24T08:14:07Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![pllim](https://dub1.discourse-cdn.com/flex005/user_avatar/community.openastronomy.org/pllim/32/51_2.png) [@pllim](https://community.openastronomy.org/u/pllim)\ **Post date:** [September 24, 2022, 8:14am UTC](https://community.openastronomy.org/t/2022-coco-election-pey-lian-lim/462/1 "2022-09-24T08:14:07Z")
Hello! I am honored to accept the nomination for the Astropy Coordination Committee. I am a Software Engineer at STScI, specializing in data analysis tools in the open-source world. I think my first real involvement with Astropy was when Perry Greenfield asked me to open a PR to add conesearch to the core library all those years ago and then I just stayed on and ended up working on different parts of the project over the years. Fun fact: I had since moved conesearch to astroquery and now Tom Donaldson is looking into taking it out of astroquery and integrating/replacing with pyvo. 😃 Currently, I am active in operations/infrastructure (or maybe I will say “devops” when I want to be hip or “please rebase” when I want to be scary) and a core maintainer (general, io.votable, utils), as you can see over at [Astropy Team](https://www.astropy.org/team) page. I am also an Astropy Affiliated Package co-editor alongside Derek Homeier. If I were to be elected into CoCo, I would advocate for Astropy to work with larger OSS efforts, where the goals align; For instance, collaborating with the new [Scientific Python](https://discuss.scientific-python.org/) coalition (it is under NumFOCUS too) and maybe adopting/contributing to Numpy’s [Contributor Experience Handbook](https://github.com/contributor-experience/handbook) that is under development. Other things on my wish list (though I do not have clear solutions for) include but not limited to onboarding/retaining software developers from other institutions/universities that also heavily use Astropy, helping graduate students convince their advisors that their Astropy contributions is just as valuable as traditional research, having a pathway to train the next generation of CoCo and core maintainers, and more bots. The Astropy Project has grown so much that I realize I often have quite a narrow view of the whole picture. For instance, I recognize the importance of tutorials and financial handling but working on them is just not as great a passion for me. Thus, in the areas I am lacking, I would need to rely on others in the Project to fill those gaps. I would like to disclose that I do work at the same institution as Erik Tollerud, another CoCo member. [APE 0](https://github.com/astropy/astropy-APEs/blob/main/APE0.rst) does say, “Unless it would be short of candidates otherwise, it should not have more than one member from any particular employer.” I also apologize for all the stress I have caused by saying, “Please rebase and squash.” tl;dr – YMMV