It would hardly be convenient for me to maintain several similar
repositories in parallel, so if it is located in the KDE infrastructure,
I will commit there for sure.
But could you please specify more precisely where the requirement to
"kill" forks is described? It seems that I looked through the entire
tree of links that drop down to the one you specified, and did not find
any prohibitions. And the GPL* license does not seem to prohibit the
existence of forks.
This is important because in particular [1] is a special repository with
instructions for building packages into an ALT repository, "Sisyphus"
(located in the .gear folder), and it must continue to exist in some
form. If the project develops inside KDE, will I be able to merge the
changes back to [1]?
On 11/25/23 02:14, Albert Astals Cid wrote:
El dimecres, 22 de novembre de 2023, a les 9:48:21 (CET), Anton Golubev va
escriure:
Hello!
I am involved in the development of the ALT Linux distribution. Some
time ago we started developing the lightdm-kde-greeter fork and I am
currently maintaining it[1]. I also push it on gitlab[2]. In addition to
porting to Qt5, some features have been added, such as choosing a
keyboard layout and connecting to the network. This greeter is currently
used by default in our KDE-based builds.
I was given the idea to revive this project in the upstream[3].
Personally, I like the idea, and might look into it if someone else
finds it useful, and I will be given appropriate access.
Since you don't seem to be a KDE devel just yet this would probably have to go
through the https://community.kde.org/Incubator program.
Have you read https://manifesto.kde.org/ specially the parts that say you'd
have to "kill" your forks in [1] and [2] ?
Cheers,
Albert
Regards,
[1]: https://git.altlinux.org/gears/l/lightdm-kde-greeter.git
[2]: https://gitlab.com/golubevan/lightdm-kde-greeter
[3]: https://invent.kde.org/unmaintained/lightdm
