Re: kdev-python: plans to add support for PyQt6 & PySide2/6 ?
Björn Strömberg <[email protected]> Wed, 3 Jan 2024 11:20:20 +0100
| Newsgroups | gmane.comp.kde.devel.kdevelop |
|---|---|
| Message-ID | <CAHo5mS0eChGmCfuQYybWfbUwBBidX-xH-7_qk=2tOQVLVpmxFg@mail.gmail.com> |
--0000000000000d138b060e07f7b8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > > > this is the reason for this mailing list 'thread', to find out of this > > project actually still is viable or if a fork is the only way forward. > > Please don't fork things, I'm more than happy to work with you to > upstream any reasonable patches you have to make things work better. > > Greetings, > Sven > > Sounds good, what process do we have for this? I've already created a working copy on invent.kde.org for the project, do we use gitlab (issues / merge requests) to collaborate the process from me -> upstream (you) or is the mailing list + patches workflow perfered? I'm sure there will be a learning curve to match the current kdev-python plugin codebase, and especially kdevelop codebase since i have barely looked at it before, so i guess there will be a few bumps in the road to getting the code production quality.. /Bj=C3=B6rn --0000000000000d138b060e07f7b8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><br> > this is the reason for this mailing list 'thread', to find out= of this <br> > project actually still is viable or if a fork is the only way forward.= <br> <br> Please don't fork things, I'm more than happy to work with you to <= br> upstream any reasonable patches you have to make things work better.<br> <br> Greetings,<br> Sven<br> <br></blockquote><div><br></div><div>Sounds good, what process do we have f= or this?=C2=A0</div><div><br></div><div>I've already created a working = copy on <a href=3D"http://invent.kde.org">invent.kde.org</a> for the projec= t, do we use gitlab (issues / merge requests) to collaborate the process fr= om me -> upstream (you) or is the mailing list=C2=A0+ patches workflow= =C2=A0perfered?</div><div><br></div><div>I'm sure there will be a learn= ing curve to match the current kdev-python plugin codebase, and especially = kdevelop codebase since i have barely looked at it before, so i guess there= will be a few bumps in the road to getting the code production quality..</= div><div><br></div><div>/Bj=C3=B6rn</div><div><br></div><div><br></div></di= v></div> --0000000000000d138b060e07f7b8--