Is this project dead / abandoned ??

[AmmarHaddadi]

The owner is not updating the files even if people are still pushing good edits

[ChrisKnott]

I would say it's semi-abandonned. My life circumstances don't give me any time to work on it unfortunately. If there is anyone, or a set of people, who want to take the project over I am happy to give them permissions to the repo. The project's continued popularity took me by surprise. It makes me feel bad to constantly get email alerts that I can't look into :/ Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Ammar Haddadi ***@***.***> Sent: Saturday, 23 July 2022, 12:39 To: ChrisKnott/Eel ***@***.***> Cc: Subscribed ***@***.***> Subject: [ChrisKnott/Eel] Is this project dead / abandoned ?? (Issue #600) The owner is not updating the files even if people are still pushing good edits — Reply to this email directly, view it on GitHub<#600>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHKLKULBPLRLOUCBAQAFVTVVPKYBANCNFSM54N4CKZQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[manecosta]

I just found out about eel a couple of days ago and it's by far one of the most useful projects I've seen in a while.
It is is too good of an idea to allow it to die. I really hope there's someone with enough knowledge on it that can keep moving it forward. I also hope your life changes in a positive way that allows you to dedicate some time to it again.

In the meantime, I'll keep experimenting with it and if I ever feel like I'm in a good position to lend a hand, I'll definitely propose myself. To everyone in the community that has a good grasp on it and has the will and time to devote, please do consider becoming a maintainer!

[dstricks]

I really like Eel and don't want to see it officially abandoned. I can help out on a limited basis. My only request is that @ChrisKnott provisionally agree to either a) package up and deploy out new releases to PyPI with new contributions I assist with OR b) eventually give me the permissions to do so. I wouldn't want any invested time to go to waste if no new releases are pushed out to the community.

If any bona fides are desired... I've answered several Eel tagged questions on Stack Overflow (https://stackoverflow.com/search?q=user:464504+eel&s=3c4736c0-4565-4005-b5e9-6b4e0024ceff). And I've been a full-time Python developer for many years (https://www.linkedin.com/in/dstricks).

[dardevelin]

I think becoming a maintainer of a branch at first and ramping up would be a good way to get the ball rolling. Python is great that you can easily use a repo in pip pointing to a branch release. I certainly would be more comfortable that way, but it’s not like I have say on the matter.

…

On Mon 22. Aug 2022 at 01:40 dstricks ***@***.***> wrote: I *really* like Eel and don't want to see it officially abandoned. I can help out on a limited basis. My only request is that @ChrisKnott <https://github.com/ChrisKnott> provisionally agree to either a) package up and deploy out new releases to PyPI with new contributions I assist with OR b) eventually give me the permissions to do so. I wouldn't want any invested time to go to waste if no new releases are pushed out to the community. If any bona fides are desired... I've answered several Eel tagged questions on Stack Overflow ( https://stackoverflow.com/search?q=user:464504+eel&s=3c4736c0-4565-4005-b5e9-6b4e0024ceff). And I've been a full-time Python developer for many years ( https://www.linkedin.com/in/dstricks). — Reply to this email directly, view it on GitHub <#600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAK32Y3K7EZ4RRBN24IEOOTV2LD6DANCNFSM54N4CKZQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dstricks]

I think becoming a maintainer of a branch at first and ramping up would be
a good way to get the ball rolling.

TBH, I don't care about the mechanics of how the code gets released, only that someone agrees to release it. I'd be fine submitting PR's like the rest of the general public and not even having commit access so long as someone is there to merge and release. That's my main concern... doing things that nobody will use.

Python is great that you can easily use a repo in pip pointing to a branch
release.

Pip is versatile for sure. If people are willing to install an unofficial version, then they could clone the code, make whatever updates they wanted, and then pip install <path-to-your-version> and they'd be good to go. Or install a fork (there are 500+ of them). But IMHO these options don't support the larger community... 50K downloads last month alone per https://pypistats.org/packages/eel.

[samuelhwilliams]

Hey @dstricks - just heard from Chris that you've offered to pick up maintaining Eel which is super exciting, thanks! Like Chris I feel bad seeing how active the community still is despite our lack of time to maintain the repo.

Happy to have a chat and hopefully get you setup and in a place where you can maintain Eel and release new versions :)

[dstricks]

Heya @samuelhwilliams, yeah it's true! Chris made me a collaborator recently and I've been trying to get up to speed. I'd appreciate any handover tips or advice you're willing to give. I'm very familiar with Python, but not so much maintaining open source on GitHub or publishing to PyPI, so that's where guidance would be very useful. I can be reached at dstricks@gmail.com or more recently dstricks#0510 on Discord.

At a minimum, I think either you or @ChrisKnott will need to add me to the PyPI project for when a new release is built and ready to be distributed. That may be a little while depending on how much I want to try to fit into a v0.15.0. Anyway, any guidance would be much appreciated. Cheers!

[ChrisKnott]

@dstricks Yep I will add you to PyPI and also transfer ownership of the repo (unless you think it's better to set up an "organisation" account?). Beware that you will probably start getting automated hacking attempts on your account so maybe set up 2FA or at least pick a strong password!

[dstricks]

I will add you to PyPI and also transfer ownership of the repo (unless you think it's better to set up an "organisation" account?).

I'm fine with taking ownership. To be honest... whatever is easiest for you so long as I can publish :)

Beware that you will probably start getting automated hacking attempts on your account so maybe set up 2FA or at least pick a strong password!

I think I have 2FA enabled, but I'll double-check that now! Thanks for the tip.

[samuelhwilliams]

You shouldn't need to be added to PyPi immediately or do anything custom - when you want to release a new version, run the 'Publish' github action in this repo and it should go straight out.

We can get you switched over on there eventually but it's not something that needs to happen immediately :)

[samuelhwilliams]

@dstricks Sounds exciting that you have lots planned for v0.15.0, but I would definitely recommend taking it slow in the beginning and publishing smaller more incremental updates just while you get your head around things - eg to get familiar with the publishing/versioning process, etc. Priority should obviously be to not break anything and to keep broadly following semver, ie don't mess too much with backwards compatibility without going to v1 (although v0.x generally doesn't indicate API stability, it's still nice to not mess around too much obviously).

[dstricks]

when you want to release a new version, run the 'Publish' github action in this repo and it should go straight out.

@samuelhwilliams That sounds brilliant! I see the Publish workflow, along with the previous runs that were successful for v0.14.0 and below, but there's no "Run Workflow" button for me that most github guidance suggests should be there. I'll keep poking around, but do you know if there are any permissions or similar that would need to be tweaked to enable that for me? It could totally be my lack of understanding of how these things work... there are so many bells and whistles enabled now :)