If you're aiming to compete with Krita and try to siphon users away from
it and towards your fork instead, then you are producing what's known as
a "hostile fork" and I very much doubt that Krita's developers will be
interested in helping you with it.
If on the other hand your fork is simply a development area for you to
send merge requests to Krita's main repo, then relations are likely to
be friendly and they will probably be much more open to your proposals
and merge requests.
Nate
On 6/1/22 12:26, Bourumir Wyngs wrote:
Sorry, I was not expecting that my message will go to the big mailing
list, initially assumed this will be directed to some person responsible
for handling the new project proposals. The request to send the message
to this address can be found at https://community.kde.org/Incubator
<https://community.kde.org/Incubator>.
Speaking about the "big button", I am a Krita contributor and already
have the fork with multiple branches containing my merge requests under
review and others. I wanted to keep this existing fork separate from the
much more independent project, there is nothing pretty in branches from
the two projects in one repository. Because of that I have registered
the proposed project separately but you are right, one of the ways to
proceed would be to take a master branch of my fork as a master of the
independent project.
I would be surprised if Krita developer team would be willing to help me
reach the users but who knows? It is obviously possible to post to they
mailing list as well. The C++20 code, they are unlikely to merge any
time soon.
On Wed, Jun 1, 2022 at 2:45 AM Aleix Pol <aleix...@kde.org
<mailto:aleix...@kde.org>> wrote:
There's a big "Fork" button on top here:
https://invent.kde.org/graphics/krita/
<https://invent.kde.org/graphics/krita/>
That said, please coordinate with krita devs to make sure your work is
ever going to reach users.
Best,
Aleix
On Tue, May 31, 2022 at 9:10 AM Bourumir Wyngs
<bourumir.wy...@gmail.com <mailto:bourumir.wy...@gmail.com>> wrote:
>
> Hello, KDE team,
>
> I would like to create the independent fork of Krita that would
allow to use all modern features of C++, up till that is supported
by the latest GCC release, 12.1 at the time of writing.
>
> The current Krita development rules are capped by C++11 that is
now the ten years old standard. Even that is limited by the lengthy
list of restrictions. The rules also require using deprecated
features of the Qt framework like Q_FOREACH. I understand the care
of the community not to spoil anything and to preserve the beauty of
the existing code. This means, radical changes should be done in a form.
>
> I tried to setup the project on KDE myself
(https://invent.kde.org/bourumir/kreed
<https://invent.kde.org/bourumir/kreed>) but for some reason was not
able to push Krita code (about 1 Gb) into repository - hangs at the
end of the push. It may have something to do with quotas or things
the like. It may be that I need more assistance from your side to
setup the project. I decided to contact you first before starting
the work on GitHub or independent server instead.
>
> I, the project initiator, am currently 54 year old. I am robotic
engineer with very long programming experience, including
significant industrial experience with C++. In the past I made
notable contribution to GNU Classpath project, providing them a
fully functional and interoperable implementation of CORBA. It is
obviously sad there are no other contributors so far but I expect
some people to come. I also made several contributions for Krita so
have some understanding about code base and architecture of this
project. My real name is Audrius Meskauskas.
>
>
>
