Move python_cmr to earthaccess-dev GitHub organization

[chuckwondo]

We have previously discussed options for managing python_cmr. Now that we have moved earthaccess out of nsidc into earthaccess-dev, there was a recent suggestion for moving python_cmr under earthaccess-dev as well.

I would like to lead this effort, so I plan to start reaching out to the folks that @frankinspace recently mentioned:

• GitHub move: PO.DAAC (Thomas Loubrieu perhaps) because they use python_cmr in several components
• PyPI: James Wood or Simon Liu to request that @chuckwondo be added as a maintainer

Of course, if there are any comments, suggestions, or objections to the above, please add to this discussion.

[frankinspace]

I'm in the process of recovering my PyPi account as well; once that is done I can add you as maintainer for the pypi artifact.

[chuckwondo]

Hi Frank. Just checking it to see if you've had any luck with this.

Also, at today's earthaccess Collaboration Cafe, we noticed that nasa/python_cmr was copy from an individual's previously open repo, so we were wondering if that might ease our ability to move it back out of the nasa GitHub org (and into the earthaccess-dev org). Do you know who we should contact about such a move?

@itcarroll mentioned that Darith Yim had previously helped him transfer some other repo into the nasa org. Do you know offhand if Darith might also be the right person to ask about going the reverse direction? (I can just contact Darith, but if you know of someone more appropriate, let us know.)

[frankinspace]

I'm making progress, I have a support ticket open with PyPi support and have given them everything they need so it is just a waiting game at this point. I will check in with them again.

As for the move itself, it depends on what we want that to look like exactly. I think it makes sense to just update the README.md in the nasa repo indicating the location of the new code and then marking the nasa repo as archived (similar to how it was copied into the nasa org in the first place).

[frankinspace]

@chuckwondo you should have an invite now.

[chuckwondo]

Received and accepted. Thank you @frankinspace!

[chuckwondo]

Hi @owenlittlejohns! @itcarroll suggested that I make sure this was visible to you, in case you want to weigh in with any concerns or support for this effort.

[itcarroll]

In particular because you're the only member of https://github.com/orgs/nasa/teams/python-cmr-maintainers!

[owenlittlejohns]

Thanks for the tag - a couple of quick thoughts on this:

• python-cmr-maintainers - the idea there was to create a GitHub group to easily add folks and allow for easier contributions in that repository directly (particularly folks who weren't able to go through the NAMS workflow to request maintainer access to python_cmr). When that group was created, I wasn't given sufficient privilege to start adding people to that group, though. (I can make second request to explicitly say I need that level of permission on the group, and see if I actually get it this time)
• Concerns: I want to make sure that folks on EED are aware of this proposal, in case there's some weird contractual thing that we are meant to be maintaining it. I don't know that there is, but I want to make sure we know that. If there is some complication there, then transfer of ownership might not be possible (but in that case, just forking from the original seems like a possibility)
• Would I like to support this effort: I'd definitely like to. But I'm also aware that I will probably struggle to give it a decent amount of time.

[frankinspace]

Hi @owenlittlejohns.

If I recall correctly the nasa org admins explicitly denied our request to be able to add folks to that team as they wanted to maintain control over access via the NAMS process. Maybe they've changed their mind though?

I doubt there are any contractual obligations for this repo as it was just me who took it on when I noticed a need for a python api to cmr. I did put it in some PO.DAAC work plans that we were maintaining it but I was never aware of anything more 'official' happening with it.

I think all we really need to do is

1. Fork the repo in earthaccess-dev. Not strictly necessary but would probably help keep track of the lineage
2. Get @chuckwondo maintainer access to the pypi project. I'm working on that
3. Push a commit to README noting where the code has moved to
4. Someone with a NASA badge file a NAMS request asking the admins to set the repo to archived.

[owenlittlejohns]

If I recall correctly the nasa org admins explicitly denied our request to be able to add folks to that team as they wanted to maintain control over access via the NAMS process. Maybe they've changed their mind though?

You are probably right. I think I have permissions on other repositories to directly add individuals or teams, but from a quick skim of the various NASA org teams I'm a part of, it looks like I don't have the ability to amend who is in those teams.

I doubt there are any contractual obligations for this repo

I'm pretty sure you are right. But I would like to get confirmation. I'll work on that now.

Generally, though, if we can't transfer ownership of the repository out of the NASA GitHub org, your four steps sound right to me.

[mfisher87]

Thanks y'all for figuring this out ❤️