Re: Announcement text for the KDE Applications 19.04 release
El dimarts, 19 de març de 2019, a les 1:32:44 CET, Christoph Feck va escriure: > Hello developers, > > the Applications/19.04 branches have been created, which means the > branches are feature-frozen. Our first release for 2019 is nearing! Christoph made a small mistake reading the schedule here, the feature freeze is still not there and it's coming in 2 days, but yeah you should really really be sure you're commiting all your stuff to Applications/19.04 ASAP otherwise we'll be a bit upset when come friday and we can't build stuff ;) Cheers, Albert > > Please help our promotion team to write an announcement text that > summarizes all the work that went into KDE Applications since our 18.12 > release. > > I created https://phabricator.kde.org/T10636 which has a link for the > Etherpad document at https://notes.kde.org/p/applications_19.04_new_features > > Please fill this document in the next few days. > >
Concluding the Gitlab Discussion
Hi all, Over the past few weeks we've had a discussion on whether we'd like to migrate from Phabricator to Gitlab, for handling both our code reviews as well as internal tasks (user facing bug reports are explicitly out of context at this time) Based on the comments the overall consensus seems to be at this stage to favour switching to Gitlab. This however is subject to a caveat around multiple task boards, which would be needed for larger projects to effectively coordinate amongst the various sub-projects. As part of the transition we will also arrange for the email interface to be enabled (for emailing in patches) and for the default for merges to be rebase when it's not a fast forward merge for all repositories. Does anyone have any final comments? In terms of the steps forward from here, Sysadmin will need a bit of time to prepare various parts of the infrastructure for the transition (such as the anongit network, which will need a full rebuild as part of switching). Once this is complete, we'll be in touch with more information on how the transition will take place. Thanks, Ben Cooksley KDE Sysadmin
Re: [GSoC 2019] KWin Clipboard Management Project
Hey Calvin, nice to see that you're interested in our GSOC project. I'm not sure Roman reads this list so I CC'd him. Could you please point me to an overview of commits you made to Sway? It's not a problem that you haven't contributed to KDE yet, but we'd like to see some activity before considering your proposal. Cheers Nico On Mon, Mar 18, 2019, 00:46 CALVIN SANTIAGO LEE wrote: > Hello, > > I am a student, and I would like to look into working with KDE for the > Google Summer of Code 2019. > I am interested specifically in KDE because I have used it for several > years, and believe that my experience may be useful to the project. > > I have worked on open source projects for almost four years. A large > amount of this time was spent working on the sway[0] window manager and > Wayland compositor. > While working on sway, I developed an interest in Wayland and furthering > the Wayland ecosystem as these were a large interest of the project. > > After I stopped regularly contributing to the project, they developed > the protocol mentioned in the "Clipboard Management Wayland protocol" > GSoC project[1] which is why it interests me. > > I have not contributed code to KDE projects before, but I have been > present in the community to some extent. While I was working on a > feature for sway, I subscribed to and sent several emails to the > mailing lists (this was under my former email, cyrus...@gmail.com). > > Furthermore, I am familiar with mailing list oriented projects. I have a > commit in QEMU, which required me to learn how to communicate well and > send patches over email. > > However, I know that this may not be acceptable, as I have read that a > GSoC proposal to KDE must contain several patches to KDE projects. > > If this is not the case, please feel free to reach out to me, either > through email or IRC (I am "pounce" on freenode) about this project or > others. I would love to work with KDE for the summer, and would be > willing to answer questions or research things to make this happen. > > Finally, as a side note. I am not quite sure whom to contact for this > project, as there are two mentors listed (Roman Gilg and Nicolas Fella), > but I cannot find their emails. > Instead I am just sending an email to the lists. Please let me know if > this is inappropriate. > > Thank you, > Calvin Lee > > [0]: https://swaywm.org/ > [1]: > https://community.kde.org/GSoC/2019/Ideas#Clipboard_Management_Wayland_protocol >
Re: Concluding the Gitlab Discussion
One thing I'd really like to not lose is the review status feature (approved/changes requested/etc). I've head that this is EE only. Is there any word on getting that added to our package? Other than that, I think I think what Gitlab offers over Phabricator is either a significant win or else just something different that you can get used to quickly. Nate On Tue, 19 Mar 2019 02:26:24 -0600 Ben Cooksley wrote > Hi all, > > Over the past few weeks we've had a discussion on whether we'd like to > migrate from Phabricator to Gitlab, for handling both our code reviews > as well as internal tasks (user facing bug reports are explicitly out > of context at this time) > > Based on the comments the overall consensus seems to be at this stage > to favour switching to Gitlab. > > This however is subject to a caveat around multiple task boards, which > would be needed for larger projects to effectively coordinate amongst > the various sub-projects. > > As part of the transition we will also arrange for the email interface > to be enabled (for emailing in patches) and for the default for merges > to be rebase when it's not a fast forward merge for all repositories. > > Does anyone have any final comments? > > In terms of the steps forward from here, Sysadmin will need a bit of > time to prepare various parts of the infrastructure for the transition > (such as the anongit network, which will need a full rebuild as part > of switching). > > Once this is complete, we'll be in touch with more information on how > the transition will take place. > > Thanks, > Ben Cooksley > KDE Sysadmin >
Re: [GSoC 2019] KWin Clipboard Management Project
Hi Nico, > Hey Calvin, > > nice to see that you're interested in our GSOC project. I'm not sure Roman > reads this list so I CC'd him. > > Could you please point me to an overview of commits you made to Sway? Sure! I worked on sway for a bit over a year, so I touched quite a few different parts of the project. For example I have contributed quite a few small bugfixes to the project, like the following: Fixing memory leaks: https://github.com/swaywm/sway/pull/1559 Fixing feature behaviour: https://github.com/swaywm/sway/pull/1155 Furthermore, I have contributed several features to the project: Color configuration to a binary: https://github.com/swaywm/sway/pull/1081/files Marks (an i3 feature): https://github.com/swaywm/sway/pull/1145/files My largest contribution to an open source project so far was the addition of a system tray to sway. This was over the course of several pull requests, and is where I get most of my experience with desktop ipc (the tray used the kde DBus protocol): https://github.com/swaywm/sway/pull/1234 https://github.com/swaywm/sway/pull/1431 > It's not a problem that you haven't contributed to KDE yet, but we'd like > to see some activity before considering your proposal. Also this makes sense. Do you know of any TODOs for KWin I could work on? Of course other projects work too, but I assume that it would be appreciated more if I get to know KWin before working on it. Thank you, Calvin
