-
Notifications
You must be signed in to change notification settings - Fork 7.8k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
【疑难解决】解决PaddleOCR历史存在的疑难Issue #11906
Comments
【报名】:5 |
【报名】:2、8 |
【报名】:9、12 |
This was referenced Apr 13, 2024
Closed
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
The dedicated team from the community picked long standing issues , please help to solve, this is a community effort to improve PaddleOCR maintenance.
背景
飞桨套件曾经凭借其出色的性能吸引了诸多的开发者,但随着社区发展,这些套件中的一些历史问题也暴露出来,例如代码Bug没有及时处理、功能缺失、兼容性不足等。以PaddleOCR 项目为例,该套件有非常多的使用者,在 issue 区的讨论也很多。甚至有不少 issue 已经是长期存在的 issue。这些 issue 缺少诊断,复现,以及修复。因此,期望能够挑选部分长期存在的,讨论较多的issue,能够进行分析、复现并解决。
更多关于此Issue的信息可以参考 PaddlePaddle/community#859 。
现状
我们对部分Issue进行了统计和分类,根据这些Issue,当前的PaddleOCR Issue中存在的问题主要由以下几部分组成:
为了促进PaddleOCR的发展,提高框架的稳定性和可维护性,我们希望基于当前的Issue对PaddleOCR的文档、依赖关系、Bug等方面进行完善。欢迎有兴趣的开发者一起参与开发~
任务划分
当前计划解决的Issue如下表所示:
Update 2024-4-26: 为了更好地促进PaddleOCR的发展,我们不仅仅针对过往Issue进行解决,还增加了一些新的更新目标,见问题11、12。
另:大家也可以从这个更大的池子里来认领: long standing issues。
认领方式
请大家以 comment 的形式认领任务,如:
多个任务之间需要使用中文顿号分隔,报名多个连续任务可用横线表示,如 2-5
PR 提交格式:在 PR 的标题中以 【OCR Issue No.】 开头,注明任务编号
看板信息
统计信息
The text was updated successfully, but these errors were encountered: