mirror of
https://github.com/qmlnet/qmlnet.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #233] Joining KDE #150
Labels
No labels
bug
enhancement
help wanted
help wanted
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/qmlnet#150
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sowelipililimute on GitHub (Mar 6, 2021).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/233
Preface: I am a KDE developer, so obviously I'm biased about the awesomeness of KDE :)
I think it would be pretty neat for this project to come join KDE. You can read about that process here: https://community.kde.org/Incubator
Why:
I'd love to see you join KDE and definitely would sponsor you through the incubation process
@vadi2 commented on GitHub (Mar 6, 2021):
As a user my concern is - does it drag in KDE dependencies?
@sowelipililimute commented on GitHub (Mar 6, 2021):
What? Joining KDE wouldn't cause that to happen; you shouldn't expect any substantial changes to the codebase simply because of the project joining a larger organisation.
@vadi2 commented on GitHub (Mar 6, 2021):
Dodging the question... I'd be concerned about a move in this direction.
@sowelipililimute commented on GitHub (Mar 6, 2021):
The short/blunt answer is "no"
@pauldotknopf commented on GitHub (Mar 10, 2021):
Is joining GitLab and moving documentation there a requirement?
@pauldotknopf commented on GitHub (Mar 10, 2021):
Let me ask this, are there any requirements from us, as opposed to just "joining"?
@sowelipililimute commented on GitHub (Mar 14, 2021):
Largest requirement would be moving infrastructure under KDE's umbrella, e.g. git repos, CI, etc.
Licensing stuff seems compatible w/ our licensing policies at an overview.
I don't recall any other large requirements.
@sowelipililimute commented on GitHub (Oct 7, 2021):
ping, i would really like to see this awesome project move under KDE's umbrella :)
@prokopst commented on GitHub (Nov 15, 2021):
@pontaoski frankly it doesn't seem like the owner is interested in continuing the project in the first place. See #240. Also qmlnet formally seems to be only one developer.
(I'm just a random guy who got discouraged to use Qml.Net due to #230 and #240 )
@RokeJulianLockhart commented on GitHub (Jun 12, 2022):
@pontaoski, that is reason enough for this to be the last thing for @pauldotknopf to do, because it would allow the project to continue, whereas currently, it shall merely be forked into oblivion.
@thegrasshopper104 commented on GitHub (Dec 31, 2024):
FYI, KDE now has supporting more languages as an explicit goal, to make it easier to develop KDE Apps.
qmlnet joining KDE would fit right into the "Streamlined Application Development" goal.
https://kde.org/goals/
@RokeJulianLockhart commented on GitHub (Dec 31, 2024):
@thegrasshopper104, specifically, it appears to be part of the “Streamlined Application Development Experience” goal: 1
I've mentioned your proposal. 2
phabricator.kde.org/T17396↩︎phabricator.kde.org/T17396#314682↩︎@pauldotknopf commented on GitHub (Jan 6, 2025):
I'm open to contributing the project to KDE. Have someone reach me via email.
pauldotknopf at gmail
@MV10 commented on GitHub (Nov 23, 2025):
@pauldotknopf @sowelipililimute ... is this happening?