nextcloud / nextcloud/contacts
Auto convert from vcf 2.1 while importing [$10]
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
FEATURE REQUEST:
I know you dropped <3.0 support recently as stated here: https://github.com/nextcloud/contacts/issues/433
While in general it is a good thing to remove old standards to force users to do migration to newer standards, to keep a maintainable software solution, but in case of a sync solution like nextcloud/contacts a wide format support is (or should be) a essential attribute of that infrastructure service. My2ct.
Please re-add vcf 2.1 support again (or integrate at least a 2.1to3.0 converter), because 2.1 it is wide spread and still in heavy use.
For example used by:
- Google Mail Contacts Exporter
- Android-based Smartphones: e.g. Samsung Galaxy S5 mini, and other devices of the Galaxy family
- LineageOS (7.1.2)
- MyPhoneExplorer (1.8.8)
- Thunderbird (52.6)
- [Please add further devices in the comments below]
There is a $10 open bounty on this issue. Add to the bounty at Bountysource.
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 locating the contact import entry point and the existing vCard 3.0 handling; the issue names no file or test. Compare the requested vCard 2.1 inputs with the supported format, and consider the work complete when the listed legacy exports can be imported or converted successfully with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100