find a new and better home for this project about micropython-esp32-ulp HOT 40 CLOSED

I have now made @ThomasWaldmann and @wnienhaus administrators of this repo. You should now be able to do anything...!

I'm happy with the proposed change to micropython-esp32-ulp. If anything, it's shorter and simpler (that with the extra -py). But no strong feelings (I have very little experience with this project).

from micropython-esp32-ulp.

Thank you @dpgeorge for the admin access to this repo.

I have now updated the repo to its new name and merged the PR, which updates source and documentation to use the new name. I released this as version 1.2.0 to PyPI and documented this (non-functional) change in the CHANGES file.

(As part of this, I have updated the API tokens for publishing to test-pypi and pypi. I have also invited @ThomasWaldmann to those PyPi projects with "owner" rights, so I am not a single point of failure here. Perhaps I should invite you @dpgeorge too?)

@mattytrentini you may now announce the project. Thank you for helping to spread the news!

from micropython-esp32-ulp.

I tried to transfer, but getting:

You don’t have the permission to create public repositories on micropython

@dpgeorge I'll just give you full access here, so you can initiate the transfer of this repo/issues/etc. to micropython organization.

from micropython-esp32-ulp.

I sent you an invite to the micropython org. Once you accept I need to give you sufficient access to transfer the repo.

from micropython-esp32-ulp.

Ok, let me try something else. I'll let you know when to try again.

from micropython-esp32-ulp.

BTW, thanks for micropython. Loved how easy it is nowadays to use microcontrollers thanks to it!

from micropython-esp32-ulp.

Please give @wnienhaus full access here.

from micropython-esp32-ulp.

Guess you need to do that, i do not have "settings" here.

from micropython-esp32-ulp.

@dpgeorge gtg now. thanks for helping!

from micropython-esp32-ulp.

I would propose the name change, yes. But I'm happy to hear more opinions on this too.

But practically, I would need @dpgeorge to either give me (and TW) full access to this repo, or to change the name for us and then (potentially) update the API tokens for pypi once I created the new projects there.

from micropython-esp32-ulp.

Good work!

I think this issue can be closed now.

from micropython-esp32-ulp.

https://github.com/micropython

https://github.com/espressif

or create a new org just for this (overkill?)

from micropython-esp32-ulp.

@mattytrentini said: https://twitter.com/matt_trentini/status/1496827362830602240

Yeah, see above. @wnienhaus what do you think?

from micropython-esp32-ulp.

I brought this up with Damien during the meetup; he seemed open to the idea of moving py-esp32-ulp to the MicroPython organization and giving you full access. If that was something you wanted...

from micropython-esp32-ulp.

@ThomasWaldmann @mattytrentini I think that sounds great. It would give the project a life of its own without being directly connected to TW and me. I'm still happy to help maintain it - like fixing issues, improving docs, encouraging/reviewing PRs, etc

from micropython-esp32-ulp.

OK, so we'll move this to MicroPython organization. \o/

from micropython-esp32-ulp.

According to github docs, only @ThomasWaldmann can transfer this repo. To do that you need to be a member of the micropython org and have sufficient rights.

@ThomasWaldmann let me know when you're online and we can run through the process together (using the micropython slack channel?)

from micropython-esp32-ulp.

I'm not on slack, but I'll try to transfer again now...

from micropython-esp32-ulp.

You don’t have the permission to create public repositories on micropython

from micropython-esp32-ulp.

Can you DM me on slack?

from micropython-esp32-ulp.

Oh, sorry, I see you said you are not on slack

from micropython-esp32-ulp.

Guess you either need to initiate the transfer yourself (added you as a collaborator, not sure if that is enough) or give me permission to create a repo at micropython org.

from micropython-esp32-ulp.

Accepted invite, it said "you're a member now...", but it still does not let me transfer. Same error msg as above.

from micropython-esp32-ulp.

Do your org permissions let members create repos?

from micropython-esp32-ulp.

I added you to a team that should have permissions to push a repo.

from micropython-esp32-ulp.

Ah, you need to adjust it first, sorry, overread that. OK, trying again...

from micropython-esp32-ulp.

Still same error msg.

from micropython-esp32-ulp.

Ok, please try again.

from micropython-esp32-ulp.

Looks like it worked! :-) Great new home!

from micropython-esp32-ulp.

Looks like that worked!

Did you want to rename the repo to match other ones there, like micropython-esp32-ulp?? I don't know the history of this repo so I'm probably not in a good position to suggest a name change, but if you wanted to do that, now would be the best time.

from micropython-esp32-ulp.

Does @wnienhaus want push access to this repo?

from micropython-esp32-ulp.

https://pypi.org/project/micropython-py-esp32-ulp/ this is our pypi package.

Options for repo name:

• micropython-py-esp32-ulp (same as on pypi)
• micropython-esp32-ulp (shorter)

Now is a good time to rename as it moved anyway. When chosing the 2nd option, we would need to rename more stuff, like the pypi package and guess also the package name.

from micropython-esp32-ulp.

@dpgeorge let's rename to 1st option now (less stuff to adjust).

In case @wnienhaus and me decide differently later, we'ld need to change quite some more stuff anyway.

from micropython-esp32-ulp.

let's rename to 1st option now (less stuff to adjust).

That sounds good.

You don't need to rename it, there are other repos in this org which are not prefixed with micropython-. The micropython- prefix means it's intended for use with MicroPython only, which is probably true for this repo. And renaming it to match the PyPI package makes sense as well.

So rename if you feel it makes sense. If you don't have permissions let me know and I'll do it.

from micropython-esp32-ulp.

I renamed it.

from micropython-esp32-ulp.

Yup, that worked, I already forked a private clone from it from the new location.

I'll advertise the new location on twitter / mastodon. Can you write something on micropython's channels?

from micropython-esp32-ulp.

TODO: change project URL in setup.py / pypi metadata and maybe other docs.

And create a new release, so it gets out there...

from micropython-esp32-ulp.

Great work moving the repo to its new home.

I quite like the shorter "micropython-esp32-ulp". In the long name, the "py" feels redundant. The shorter name would also align nicely with the "esp32_ulp" module name inside the repo, i.e. micropython-esp32-ulp is the "esp32_ulp" module for micropython.

I made a PR (#68) with the adaptation to the shorter name, to "get a feel" for the different name. We can use it to decide which looks/feels better. If we choose the existing name, then PR #67 is good to merge as is, and we simply throw away my PR.

If we do go the route of the changed name, I think the only thing that's needed more, is to create a pypi package with the new name on both the main pypi and the test pypi. I can do that, but I have no access to the Github repo settings, so updating the API keys would need to be done by someone still (wondering though, if I should have access to the settings).

Let me know which name feels nicer to go forward with, and I can create the pypi repos if necessary.

from micropython-esp32-ulp.

I also do not have access to the repo settings here. So guess you'ld need to do that together with damien.

I do not have strong opinions about the name, your approach is maybe slightly nicer, mine was a bit easier to do. But if you like to change it, just do it together with damien and create a new release so everything is consistent and uptodate.

from micropython-esp32-ulp.

So is the intent to use micropython-esp32-ulp? Are we waiting for @dpgeorge to make that change?

I want to announce the project (forum, slack, twitter...) but would prefer to do so after a name change 😜

from micropython-esp32-ulp.