Discussions about how to organize further maintenance of this library
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.7k
- Forks
- 579
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Based on the latest commit in master (over a year old) as well as 16 pending pull requests, i assume @smalot is not maintaining this library anymore. That's fine, he will have his reasons.
In this issue i would like to discuss where the community around this library should continue the work? There are some who already developed their own strain, for instance:
- @amooij with https://github.com/amooij/pdfparser
- @gyselroth with https://github.com/gyselroth/pdfparser
@lausek with https://github.com/lausek/pdfparser- @limweb with https://github.com/limweb/pdfparser
Found them using https://github.com/smalot/pdfparser/network
Any ideas?
EDIT: Removed fork from @lausek (ref).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the maintenance discussion, the 16 pending pull requests, and the listed forks: amooij/pdfparser, gyselroth/pdfparser, and limweb/pdfparser. The issue does not identify files, tests, an entry point, or a concrete definition of done, so any next step would require agreeing on the library's future home and maintenance plan first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100