In T15087#267587, @dcahal wrote:This was mentioned as a recommended vendor for a banner:
https://www.bannersonthecheap.com/
- Queries
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
Dec 15 2021
Dec 15 2021
Thanks Paul for creating this task. I am so excited to be part of this event with Drew.
Drew I was curious to know few things about this event:
- What exactly do you promote about KDE ?
- From your past experience in this event what do you think attracts the audience and what should we work on for this event ?
Mar 18 2021
Mar 18 2021
Hi David, yes we definitely can, infact I loved the "Magical Rope" clip.
Mar 16 2021
Mar 16 2021
Yes Paul, I will work with the promovideo people.
Mar 15 2021
Mar 15 2021
Thanks Allyson. Yes Allyson we can, I will start working on the video and share the concept with you all.
Hello everyone, I know I am late to submit my idea for kde's 25th bday but if you all like it then I can start working on it..
Nov 21 2020
Nov 21 2020
One more thing that we discussed on 19th Nov 2020 meeting:
In the month of April-May 2021 there will be Teachers' Training Program in Kerala, if the Kerala team is ready with the tutorials and documentation then the team would think of doing some workshop or training in this program.
Oct 27 2020
Oct 27 2020
bdhruve added a comment to T13773: Promote diversity within KDE: Help increase the participation of women.
In T13773#243777, @aniqakhokhar wrote:In T13773#243511, @bdhruve wrote:For an instance : If we are planning to focus on school girls we could start as a career counselling.
I like the idea of career counselling maybe we can add this as one of the things we can do under the KDE Network platform. I think the KDE Network can be a very good opportunity to increase diversity.
Oct 21 2020
Oct 21 2020
bdhruve added a comment to T13773: Promote diversity within KDE: Help increase the participation of women.
Thank you Paul for adding me in this group. As an industry, yes we do seem to have a problem attracting women to this field, especially in the open source community. I haven't done my research properly but had a thought, what if we do some kind of Mentor-ship program.
For an instance : If we are planning to focus on school girls we could start as a career counselling.
In India schools assign few days for career counselling, where there are lots of people from MBA, Medical, Accountancy field. But it is very rare that a software developer give any routine sessions. It is a sort of Guest Lecture and depending on the enthusiasm of students they have a workshop for a day. All these guests lectures I have attended are very monotonous, students participate because it is compulsory, very few are interested in these lectures.
Sep 21 2020
Sep 21 2020
Aug 28 2020
Aug 28 2020
Suggestions for Advisory Committee's List:
- Lydia
- Valorie
- Neofytosk
- Paul
- Adriaan
- Eike
- Jonathan
- Tomaz
- Nate
Jul 16 2020
Jul 16 2020
For creating an association or chapter we could host a BoF during this Akademy and ask the GSoC and SoK 2019-2020 students to join us.
We could host some random small KDE related events by asking university students to do a day or two event where there would be trainings and workshops, and after corona our Ambassador program team could also be part of these events.
May 11 2020
May 11 2020
Nov 8 2019
Nov 8 2019
Update the kcm-screenlocker image
Jun 14 2019
Jun 14 2019
Hello, there is a slight change in my travel dates I will be able to make the sprint anytime after Mid-October.
May 3 2019
May 3 2019
Hi, I am fine with Malaga and any date in month of October or first week of November is fine with me.
Apr 26 2019
Apr 26 2019
Hello everyone, any updates about the sprint's date and place?
Apr 8 2019
Apr 8 2019
Hello, I am fine with both dates for Malaga, and even I am fine with the Athens Idea.
Mar 15 2019
Mar 15 2019
In T10580#178135, @skadinna wrote:My suggestion is to look into whether this can be co-organized with the Onboarding sprint in Athens, which is taking place in May. (https://phabricator.kde.org/T8623)
Mar 13 2019
Mar 13 2019
I totally agree with all your ideas Neo, and i have a few which i would like to share:
- We can add a page showing all the FAQ
- We should even include all the latest projects that are going on, maybe create a kind of news tab, where they can see some videos and announcements of current work going on
- We all know that no one is a born programmer, we all learn in the course of actually doing code, all newcomers are hesitant when they are starting to contribute for the first time, I feel we need to keep a page where we can share our coding experience and how we started and now how easy we get along with coding. This page would make them feel better and would give them a kind of boost to start contributing.
- Teams description, be it any team we should have a page where we give some details about the team and what projects they work on. People like to choose their team, we should give them some knowledge about how the team is and how do they work, so they can plan accordingly.
- Let in images as images speak more than words, we need to make our page attractive.
Nov 15 2018
Nov 15 2018
In T8712#167290, @ngraham wrote:In T8712#167153, @bdhruve wrote:Hello Everyone,
We have created a Matrix group: https://matrix.to/#/#kde-welcome:matrix.org
Anyone interested to be part of the team, please feel free to join :)Awesome!
Is this Matrix-only, or is it bridged to IRC?
Nov 14 2018
Nov 14 2018
Hello Everyone,
Oct 13 2018
Oct 13 2018
In T8712#163193, @neofytosk wrote:Hi @bdhruve , before responding to your suggestions, I would like to be sure if you are referring to this guide: https://community.kde.org/Plasma/DeveloperGuide
Or is it about something else?
Oct 3 2018
Oct 3 2018
Well from my end i was going through the Kde-dev-guide, and i offered a few suggestions to Valorie would love to share here as well,
ln the Dev guide it states KDE from developers viewpoint, we could add some thing like KDE from a new contributor point of view or some other nice term, and in this we could give information about:
In T8712#159843, @ngraham wrote:A good next step might be creating a formal Phabricator group for this, to which people could add themselves. Then for example we could document that new contributors should add the group as a reviewer for their first patches, which could help make sure that those critical first patches don't get lost and always have someone available who can help. Thoughts?
Jul 19 2018
Jul 19 2018
bdhruve committed R1005:035fa0ecccf0: Verify if favorite and alternative changes persist across session restart. (authored by bdhruve).
Verify if favorite and alternative changes persist across session restart.
bdhruve updated the diff for D13560: Verify if favorite and alternative changes persist across session restart..
Removed kicker-logout needle.
bdhruve updated the diff for D13560: Verify if favorite and alternative changes persist across session restart..
Rebase to master branch and remove wait_still_screen.
Jul 16 2018
Jul 16 2018
bdhruve updated the diff for D13560: Verify if favorite and alternative changes persist across session restart..
Add Logout function using krunner in basetest
Jul 5 2018
Jul 5 2018
bdhruve added a comment to D13560: Verify if favorite and alternative changes persist across session restart..
In D13560#279877, @sitter wrote:Does this really need a test? Did this ever break?
It appears to me this is essentially doing a test of kconfig/plasmashell's use of kconfig, which should be much more efficiently tested via a unit test (and likely already is)
bdhruve updated the diff for D13560: Verify if favorite and alternative changes persist across session restart..
Add logout function in basetest
Jun 15 2018
Jun 15 2018
Jun 12 2018
Jun 12 2018
bdhruve committed R1005:073e6da1e9fc: Add test to verify the Alternative Menu (authored by bdhruve).
Add test to verify the Alternative Menu
In D13410#277096, @sitter wrote:As @bshah pointed on IRC this may or may not need updating of the needles.
The plasma-folder test now switches the background to a constant color. Some of the needle failures were due to plasma being partially translucent and thus the wallpaper bleeding into the needles. As we didn't want to disable all desktop effects, I instead opted to fixate the color. As a result your new needles might not match. However, out of the existing needles only one had a problem there, so you may be fine.
In any case, I am fine with landing it and fixing it through jenkins if redoing the needles locally seems like too much work.
Jun 11 2018
Jun 11 2018
Reset back to kickoff at end of test
Jun 7 2018
Jun 7 2018
To explain the comment in test plan, while testing it in plasma_desktop suite it is not able to assert the folder_desktop screen even though the last screen-shot in plasma-favorites.pm is folder-desktop screen. However test itself works fine individually.
Jun 5 2018
Jun 5 2018
bdhruve committed R1005:7f0128f74f24: Extended test for verifying the Remove from Favorite option. (authored by bdhruve).
Extended test for verifying the Remove from Favorite option.
Jun 2 2018
Jun 2 2018
Fixed issues mentioned by sitter
Jun 1 2018
Jun 1 2018
Fixed issues mentioned by bshah
May 31 2018
May 31 2018
May 29 2018
May 29 2018
bdhruve committed R1005:ff63650c9dfc: Add test to verify the Add to Favorite option. (authored by bdhruve).
Add test to verify the Add to Favorite option.
May 28 2018
May 28 2018
- Added plasma_favorite.pm in the main plasma test suite
- Get rid of fractional pixel values
- Fixed coding style issue
May 26 2018
May 26 2018
Jan 29 2018
Jan 29 2018
Oct 27 2017
Oct 27 2017
Fixed the Font Size issue.
Oct 26 2017
Oct 26 2017
Fix crash on koko startup.
Oct 25 2017
Oct 25 2017
Aug 14 2017
Aug 14 2017
Ping @graesslin @davidedmundson, should I do any more changes or this can be submitted?
May 4 2017
May 4 2017
Ping. Do i have to make any more changes?
Apr 25 2017
Apr 25 2017
This patch is follow-up of D1989.
This revision was started last year which had lot of discussions. Had a few of unfinished issues to be fixed as well.
So creating a new one which has fixed the last few issues addressed by @graesslin and @davidedmundson. And i am extremely apologetic for such a long delay.
Aug 22 2016
Aug 22 2016
In D1989#46775, @graesslin wrote:I would like to see this integrated. But I think a few things need to be done:
- I would love to see the example you had in your blog post added to tests
- I'm still unhappy about the name KWinQml - it's just not saying what it is. And actually it's not Qml at all. It's a declarative implementation. Might need brainstorming, maybe even broader on the mailinglist.
Aug 10 2016
Aug 10 2016
Mark comments as done.
Fix keyEvent code for non-X11 platforms.
Aug 9 2016
Aug 9 2016
In D1989#44453, @graesslin wrote:I just remembered: on X11 one needs to subtract 8 from the key code...
Added back the keyEvent handling and works perfectly now.
Remove keyEvent handling.
Aug 8 2016
Aug 8 2016
In D1989#44333, @graesslin wrote:
- KeyPress events to send keys.
However, keyevents are not working as it should, if i press 'a' it types something different.might be that this is just not possible to send key events like that. In general QKeyEvent delivers the keysym. That is the scan code translated through the keyboard layout. The nativeSccanCode should have the original value but I would not trust it completely.
Maybe leave key events out for the moment as an we don't necessarily need key events.
Aug 7 2016
Aug 7 2016
Pass different input events from QML to Kwin,
Jul 21 2016
Jul 21 2016
- Performed the nullptr check for the buffer attached to the surface.
- Removed qDebug() statements.
- Fixed coding style.
- Fixed issue of only first frame rendering.
Jul 19 2016
Jul 19 2016
- Fixed automatic selection of backend to look for WAYLAND_SOCKET also
- Rendering kwin instance
- Fixed minor issues.
Jul 12 2016
Jul 12 2016
In D1989#38998, @bdhruve wrote:In D1989#38844, @graesslin wrote:Looks good now and I think we can look into the next steps: rendering the KWin instance you launch. The launched KWin instance connects to your Wayland server, binds to the Shell and will create a ShellSurface. That you will get through a signal on m_shell - compare wayland_server.cpp:148. I would as a next step try to hook into this and see whether the surface gets created. Once you have that you can look into rendering it.
For that the ShellSurfaceInterface is connected to a SurfaceInterface. The rendering happens on the SurfaceInterface. There's a damaged signal which you should use to trigger a repaint of your QQuickItem. When rendering you can access the buffer on the SurfaceInterface. If KWin uses KWIN_COMPOSE=Q you can access the buffer as a QImage and just render it. Pretty straight forward - hopefully. But first try to see whether you get the ShellSurface created. If not we need to look into what goes wrong.
I've added the slot for checking if surface gets created but signal doesn't get emitted. Would you please show me the way to proceed further now.
Jul 8 2016
Jul 8 2016
In D1989#38844, @graesslin wrote:Looks good now and I think we can look into the next steps: rendering the KWin instance you launch. The launched KWin instance connects to your Wayland server, binds to the Shell and will create a ShellSurface. That you will get through a signal on m_shell - compare wayland_server.cpp:148. I would as a next step try to hook into this and see whether the surface gets created. Once you have that you can look into rendering it.
For that the ShellSurfaceInterface is connected to a SurfaceInterface. The rendering happens on the SurfaceInterface. There's a damaged signal which you should use to trigger a repaint of your QQuickItem. When rendering you can access the buffer on the SurfaceInterface. If KWin uses KWIN_COMPOSE=Q you can access the buffer as a QImage and just render it. Pretty straight forward - hopefully. But first try to see whether you get the ShellSurface created. If not we need to look into what goes wrong.
Fixed issues mentioned by @graesslin and connect to surfaceCreated.
Jul 6 2016
Jul 6 2016
Fixed issues mentioned by @graesslin.
Jul 4 2016
Jul 4 2016
Fixed issues mentioned by @graesslin.
In D1989#38023, @graesslin wrote:I would like to see a test case which verifies that it starts the kwin_wayland instance and terminates it again.
Jul 1 2016
Jul 1 2016
Fixed code as per mentioned by @bshah.
Jun 29 2016
Jun 29 2016
Fixed copyright header.
Fixed issues mentioned by @bshah
Jun 28 2016
Jun 28 2016
Fixed issues addressed by @graesslin
Jun 24 2016
Jun 24 2016
bdhruve retitled D1989: Introduce QQuickItem to nest kwin_wayland from to Introduce QQuickItem to nest kwin_wayland.
Jun 3 2016
Jun 3 2016
bdhruve committed R108:6cae5f7ab925: Integrated FakeInput touch events into InputRedirection. (authored by bdhruve).
Integrated FakeInput touch events into InputRedirection.
bdhruve retitled D1758: Integrated FakeInput touch events into InputRedirection. from to Integrated FakeInput touch events into InputRedirection..
May 31 2016
May 31 2016
bdhruve committed R127:7d460ed00254: Add support for touch events in fakeinput protocol and interface. (authored by bdhruve).
Add support for touch events in fakeinput protocol and interface.
bdhruve added a comment to D1672: Add support for touch events in fakeinput protocol and interface..
Thank you @graesslin and @bshah
bdhruve added a comment to D1672: Add support for touch events in fakeinput protocol and interface..
In D1672#31870, @bshah wrote:Looks good.
bdhruve updated the diff for D1672: Add support for touch events in fakeinput protocol and interface..
Fixed the coding style issue.
May 30 2016
May 30 2016
bdhruve updated the diff for D1672: Add support for touch events in fakeinput protocol and interface..
Track touchIds and update autotests.
(I am not sure if i did correctly or not.)
May 26 2016
May 26 2016
bdhruve added a comment to D1672: Add support for touch events in fakeinput protocol and interface..
In D1672#31141, @graesslin wrote:In D1672#31140, @bdhruve wrote:In D1672#31046, @graesslin wrote:I'm wondering: should we ensure that the ids are correct. E.g. a touchUp for id 1 doesn't make sense if we never got a touchDown for id 1. This would require tracking the used ids in FakeInputInterface. But it must be done somewhere - either in the library or by the user of the library.
Martin, do you prefer this change to be done in this review only or in separate review.
I think it would be better to directly integrate it here.