| Summary: | Make KDE Connect an independent project | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | carld-87 |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | andrew.g.r.holmes, uwu |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
And yes, this sure spark tons of opinions... Can you be clearer about what you're actually proposing? This isn't the first time something like this has been proposed, but the implications are always rather vague. Are you suggesting... - Re-branding KDE Connect? If so, what is the benefit, given how recognizable it is after 10 years? - Using a common library or service base? If so, what language/platform/IPC are you suggesting? - Does your suggestion account for backwards-compatibility? If so, how? If not, what are the benefits and how do they offset obsoleting devices that won't be able to update? KDE is the community, not the desktop. The same way Microsoft Office is available for non-MS OSes, KDE Connect can be used on any OS and desktop. > 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. (In reply to Albert Vaca from comment #3) > KDE is the community, not the desktop. > > The same way Microsoft Office is available for non-MS OSes, KDE Connect can > be used on any OS and desktop. KDE is an project that mainly develops DE. And anyway KDE Connect is quite tight just for KDE Plasma (see what libs is use and test use it e.g. on GNOME). andrew.g.r.holmes@gmail.com: what do you think? (In reply to carld-87 from comment #6) > andrew.g.r.holmes@gmail.com: what do you think? Sorry, but that just sounds like a re-branding. I'm also not sure what the benefits are intended to be, all things considered. Did you have an answer for these two questions? - Using a common library or service base? **If so, what language/platform/IPC are you suggesting?** - Does your suggestion account for backwards-compatibility? If so, how? If not, what are the benefits and how do they offset obsoleting devices that won't be able to update? |
Could we make KDE Connect an independent project and rename it to e.g. Linux Connect? KDE Connect is amazing software which all Linux users needs (including non-KDE users), so why it have to be only for KDE? Yeah there is ports like GSConnect, but it's still just KDE Connect... You e.g. have to install KDE Connect to your phone. I think KDE Connect backend and mobile apps should be universal for Linux. On top of this backend, everyone can then create their own frontends. Like this: Workstation: connectd UIs: CLI: connect-cli GUI: KDE Connect GNOME Connect Cosmic Connect and so on Mobile: Connect