You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the idea is awesome and would benefit the framework
I have searched in the issue tracker for similar requests, including closed ones
Description
This is something I've been thinking about for quite some time now.
Pyrogram is an amazing project, with a really clean code, great docs and a really supportive community. But with the project not being updated for a year now, I think it's time to pass the project to someone else.
Why ?
Pyrogram not being updated alone wouldn't be an issue. The real problem is that Telegram's Bot API is constantly updated with new features, and we can't keep up with a library that stays stale.
Some would argue :
well just switch libraries.
While other libraries do exists (Telethon, python-telegram-bot and many others), switching library for a big project isn't an easy task, and can be quite discouraging.
Designate someone which is motivated enough and have a really good understanding of the existing code to take the project under new horizons. Someone who created one of the forks above could be a great suggestion. This person should be responsible for the administration of the @pyrogram organization, as well as the pyrogram.org website. This person should also be responsible of the Telegram channel and the group. The group's issue where new members can't join due to the bot not verifying them in time should also be fixed.
Speaking of the website, I think it could be great to open-source its code under its own repository.
Along the new owner, the organization should hold several members who have direct push access to its repos, this way even if one member have to stay offline for a while or other reasons, updates and pull requests could continue to work properly.
TgCrypto should also be handled by the new team, as for example it can't be installed on Python > 3.11 for Windows.
I'm not expert in how these things work, but a kind of "committee" (excuse me if I'm using the wrong term) would be beneficial for pyrogram, whereas willing contributors of the community could later join the team, and "meetings" where the team can discuss about future goals of the project and the direction it's taking.
What's next ?
Well, this is only a proposal. @delivrance isn't dead ! Check his profile, he's still doing updates to private repos.
In the end we're stuck with his decisions (or here, rather absence of decisions).
If you agree/disagree with my proposal, feel free to react with emojis (the smiley button just under this text) 👍/👎
Also, I would be really curious to hear your opinion on this, so don't hesitate to comment :)
If the awesome contributors behind the forks could look into this as well, I'd be glad to read what they think about it.
That's all for me, after all I'm just a random guy 👀
The text was updated successfully, but these errors were encountered:
I'd like to point out that the creator of this project, Dan, has withdrew $645 from Open Collective during March 2024. This was pretty much all the funding the project received ($649.26 in total). The purpose of the withdrawals are stated as "Development and Maintenance". Interesting as the last commit Dan made was in April 2023.
I'm not saying Dan doesn't deserve the $645 that was donated. But it seems disingenuous to see Dan make commits on GitHub to other projects and see him withdraw money from a project he's been neglecting in the name of "Development and Maintenance".
I get people are busy and move on with their lives, but Dan has clearly not forgotten about Pyrogram's existence. Of course as this is opensource, we're not entitled to anything. Simply just asking to pass the torch onto the community, as this is a project that many of us depend on.
If Dan required financial support for the project, they could have made a plea to the community. I'm sure most of us reading this thread would have donated.
I indeed saw this while writing the issue, although I didn't thought it was necessary to mention it
The amount of money withdrew is lower than the total amount of money funded because of "payment processor fees"
I also think than Dan deserves it, especially considering that he spent 6 years on this project (45ee7aa)
and I agree with you, most of us would have donated, including me, especially since this project helped me over the past 3 years :)
I would also like to add that forks are not doing anything apart from replace compiler/source/main_api.tl and recompile the project, and all new Telegram features just work like magic.
Checklist
Description
This is something I've been thinking about for quite some time now.
Pyrogram is an amazing project, with a really clean code, great docs and a really supportive community. But with the project not being updated for a year now, I think it's time to pass the project to someone else.
Why ?
Pyrogram not being updated alone wouldn't be an issue. The real problem is that Telegram's Bot API is constantly updated with new features, and we can't keep up with a library that stays stale.
Some would argue :
While other libraries do exists (Telethon, python-telegram-bot and many others), switching library for a big project isn't an easy task, and can be quite discouraging.
Yes, they indeed exists (Mayuri-Chan/pyrofork, KurimuzonAkuma/pyrogram, TelegramPlayGround/pyrogram, hydrogram/hydrogram, eyMarv/pyroblack, ...). But choosing between these projects can be a rough decision, and having everything streamlined under one project would be easier for newcomers.
How ?
I'm not expert in how these things work, but a kind of "committee" (excuse me if I'm using the wrong term) would be beneficial for pyrogram, whereas willing contributors of the community could later join the team, and "meetings" where the team can discuss about future goals of the project and the direction it's taking.
What's next ?
Well, this is only a proposal. @delivrance isn't dead ! Check his profile, he's still doing updates to private repos.
In the end we're stuck with his decisions (or here, rather absence of decisions).
If you agree/disagree with my proposal, feel free to react with emojis (the smiley button just under this text) 👍/👎
Also, I would be really curious to hear your opinion on this, so don't hesitate to comment :)
If the awesome contributors behind the forks could look into this as well, I'd be glad to read what they think about it.
That's all for me, after all I'm just a random guy 👀
The text was updated successfully, but these errors were encountered: