https://bugs.kde.org/show_bug.cgi?id=474601
carld...@outlook.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |---
Status|RESOLVED |REPORTED
--- Comment #4 from carld...@outlook.com ---
> Can you be clearer about what you're actually proposing?
I proposing making an independent project called "Linux Connect", "connectd" or
something that will develop connect system for whole Linux. To be clear:
Take kdeconnectd codebase, rename it and develop under that new project
Take kdeconnect-cli codebase, rename it and develop under that new project
Take kdeconnect mobile apps, rename them and develop under that new project
kdeconnect-app could continue (with name KDE Connect) as frontend for new
backend by that new project.
Note: As far I know KDE Connect consist of kdeconnectd backend and
kdeconnect-cli and kdeconnect-app frontends. There is also GSConnect that
implement is backend and frontend in one. GSConnect could continue just
frontend for new backend by that new project.
> - Re-branding KDE Connect? If so, what is the benefit, given how
> recognizable it is after 10 years?
Frontend can keep KDE Connect name.
> - Using a common library or service base? If so, what language/platform/IPC
> are you suggesting?
Service.
--
You are receiving this mail because:
You are watching all bug changes.
