Re: New repo in kdereview: kclock

[Devin]

Hi everyone,

Is there any feedback left for KClock? If not, I will consider it to
have passed kdereview.

Thanks,
Devin

On Fri, Dec 30, 2022 at 2:27 AM Justin  wrote:
>
> Thanks for the quick reply Albert. I'm not a developer but I've gone
> over much of the comments from previous:
>
> Tested on 22.11
>
>  > New Timer doesn't work? Ah it's because it needs kclockd running for
> that, would it be very hard to give a warning if it isn't running?
>
> Seems kclockd is now running automatically. If it is not automatically
> running that would (in my opinion) be a packaging issue on the distro side.
>
>  > Is that kirigamiaddons thing released? Seems to be the reason i can't
> add new Alarms
>
> Kirigami Addons has now passed KDE review and has stable releases
>
>  > Not an expert in UI but for stopwatch having Start/Pause on the top
> left feels a bit unnatural, maybe would make sense swapping reset and
> Start? Ask the VDG i guess.
>
> In the version I'm running it's centered nicely and I think works well.
> If you can check this against latest git master to confirm the UI is
> still the same.
>
>  > Also in stopwatch for me it'd make a lot of sense if pressing the
> time starts/pauses, what do you think?
>
> This is functioning now.
>
>  > Silence Alarm After shows an horizontal scrollbar that doesn't to be
> very useful https://i.imgur.com/7O8DBJc.png
>
> This is now called Ring Duration and has no horizontal scroll bar even
> at the minimum window width.
>
>  > It's even worse in Alarm Snooze Length where it goes over existing text
>
> Same as above, now fixed.
>
>  > You're missing Messages.sh in kclockd
>
> I see this now in the kclockd folder
>
>  > Please check i18n in your qml files, these seem like need i18n
>  > ...
>
> Lots of this i18n stuff appears to have been moved and will need a new
> review
>
>
> Justin
>
> On 30/12/22 20:44, Albert Astals Cid wrote:
> > El divendres, 30 de desembre de 2022, a les 8:46:56 (CET), Justin va 
> > escriure:
> >> Hey Team,
> >>
> >> This was last posted about on October 18 2021. I looked at the three
> >> items that were needed for kirigami-addons:
> >>
> >> * Missing is REUSE compliance:
> >> https://invent.kde.org/libraries/kirigami-addons/-/merge_requests/13
> >> * Hanyoung is working on a better time picker:
> >> https://invent.kde.org/libraries/kirigami-addons/-/merge_requests/17
> >> * And Clau is working on a better date picker:
> >> https://invent.kde.org/libraries/kirigami-addons/-/merge_requests/20
> >>
> >> They have all now been merged. Can we resume the review on
> >> kirigami-addons so we can continue on kclock?
> >>
> >> Thanks everyone and have a enjoyable and safe holiday!
> > I gave a long list of comments back in the day that were never answered, do
> > that first and maybe i give it another look.
> >
> > Cheers,
> >Albert
> >
> >> Justin
> >
> >
> >

[ANNOUNCE] CMake 3.26.0-rc1 is ready for testing

[John Parent]

I am proud to announce the first CMake 3.26 release candidate.
  https://cmake.org/download/

Documentation is available at:
  https://cmake.org/cmake/help/v3.26

Release notes appear below and are also published at
  https://cmake.org/cmake/help/v3.26/release/3.26.html

Some of the more significant changes in CMake 3.26 are:

* The "ASM_MARMASM" language was added to support the Microsoft ARM
  assembler language.

* CMake now writes a YAML log of configure-time checks to
  "CMakeFiles/CMakeConfigureLog.yaml" under the top of the build tree.
  See the "cmake-configure-log(7)" manual.

* The "cmake-file-api(7)" "codemodel" version 2 "target" object gained
  a new "fileSets" field and associated "fileSetIndex" field to
  "sources" objects.

* The "$" generator expression was added to
  prevent usage requirements from being exported to dependent
  projects.

* Language Standard Flags, such as "-std=c++11", when generated due to
  "target_compile_features()" or "CMAKE__STANDARD", are now
  placed before flags added by "target_compile_options()", rather than
  after them.

* The top-level "project()" call will now emit an author warning if
  the documented command order in relation to
  "cmake_minimum_required()" is not respected.


CMake 3.26 Release Notes


Changes made since CMake 3.25 include the following.


New Features



Languages
-

* The "ASM_MARMASM" language was added to support the Microsoft ARM
  assembler language.


Command-Line


* The "cmake -E copy" command-line tool now supports a "-t" argument.

* The "cmake -E copy_directory_if_different" command-line tool was
  added.


Configure Log
-

* CMake now writes a YAML log of configure-time checks to
  "CMakeFiles/CMakeConfigureLog.yaml" under the top of the build tree.
  See the "cmake-configure-log(7)" manual.


File-Based API
--

* The "cmake-file-api(7)" "codemodel" version 2 "version" field has
  been updated to 2.5.

* The "cmake-file-api(7)" "codemodel" version 2 "target" object gained
  a new "fileSets" field and associated "fileSetIndex" field to
  "sources" objects.

* The "cmake-file-api(7)" gained a new "configureLog" object kind that
  enables stable access to the "cmake-configure-log(7)".


Commands


* The "add_custom_command()" and "add_custom_target()" commands now
  support "generator expressions" in their "COMMENT" option.

* The "message()" command gained a "CONFIGURE_LOG" mode to record an
  entry in the "cmake-configure-log(7)".

* The "string(TIMESTAMP)" and "file(TIMESTAMP)" commands now support
  the "%z" and "%Z" specifiers for the time zone.

* The "try_compile()" and "try_run()" commands gained a
  "LOG_DESCRIPTION" option specifying text to be recorded in the
  "cmake-configure-log(7)".

* The "try_compile()" and "try_run()" commands gained a "NO_LOG"
  option to skip recording a "cmake-configure-log(7)" entry.


Variables
-

* The "CMAKE__COMPILER_FRONTEND_VARIANT" variable is now set for
  "GNU", "MSVC", and "AppleClang" compilers that have only one
  frontend variant.

* A "CMAKE_VS_VERSION_BUILD_NUMBER" variable is now set by Visual
  Studio Generators for VS 2017 and above to report the four-component
  Visual Studio version number.


Properties
--

* The "_CLANG_TIDY_EXPORT_FIXES_DIR" target property was added
  to allow the "clang-tidy" tool to export its suggested fixes to a
  set of ".yaml" files. A new
  "CMAKE__CLANG_TIDY_EXPORT_FIXES_DIR" variable was created to
  initialize this property.

* The "XCODE_EMBED_EXTENSIONKIT_EXTENSIONS" target property was added
  to tell the "Xcode" generator to ExtensionKit-based extensions such
  as extensions using the Background Assets framework.  Aspects of the
  embedding can be customized with:

  * "XCODE_EMBED_EXTENSIONKIT_EXTENSIONS_PATH"

  * "XCODE_EMBED_EXTENSIONKIT_EXTENSIONS_CODE_SIGN_ON_COPY"

  * "XCODE_EMBED_EXTENSIONKIT_EXTENSIONS_REMOVE_HEADERS_ON_COPY"


Modules
---

* The "ExternalProject" module "ExternalProject_Add()" command gained
  an "INSTALL_BYPRODUCTS" option to specify files generated by the
  "install" step.

* The "FindCUDAToolkit" module:

  * gained support for the "sbsa-linux" cross compilation target, and

  * now provides an imported target for "nvrtc_static", if found.

* The "FindImageMagick" module now provides imported targets.

* The "FindPython3" and "FindPython" modules gained support for the
  Stable Application Binary Interface.

* The "UseSWIG" module gained the support for the "perl5" language.


Generator Expressions
-

* The "$" generator expression was added to
  prevent usage requirements from being exported to dependent
  projects.


CTest
-

* The "CTEST_NO_TESTS_ACTION" environment variable was added to
  provide a default value for the "--no-tests=" command line
  argument of "ctest(1)".


Deprecated and Removed Features
===

* The 

Fwd: [GSoC Mentors] GSoC Org Applications are now open (and close Feb 7 1800 UTC)

[Johnny Jazeix]

Hi,

a kind reminder: we need to fill an application in the GSoC website before
the 7th with the ideas page (https://community.kde.org/GSoC/2023/Ideas) and
the mentors count.
For now, we have 5 mentors (and 8 ideas) and we have to write a number in
our application before the 7th (so let's make the deadline this Sunday).
If we only write 5 mentors and we decide of more ideas later, I'm not sure
Google will provide us more slots.

If you want to mentor please reach your team and write an idea with mentors
in the ideas page before the 5th so we can have a clean filled page when
Google checks on it to provide us the number of slots we will ask.

Cheers,

Johnny

-- Forwarded message -
De : 'sttaylor' via Google Summer of Code Mentors List <
google-summer-of-code-mentors-l...@googlegroups.com>
Date: mar. 24 janv. 2023 à 00:58
Subject: [GSoC Mentors] GSoC Org Applications are now open (and close Feb 7
1800 UTC)
To: Google Summer of Code Mentors List <
google-summer-of-code-mentors-l...@googlegroups.com>


Hi all,

GSoC 2023 Organization Applications are now open at g.co/gsoc! You can
scroll to the middle of the homepage and click the ‘Register your
organization’ button and start registration.

For those orgs that applied in 2022 your information (org profile, org
details) are still in the GSoC webapp so you will have a super quick
application for 2023. But please don’t wait until the final hours to submit
your application, all org applications are due by Tuesday, February 7 at
1800 UTC.
...
Best,

Stephanie Taylor

GSoC Program Lead

-- 
You received this message because you are subscribed to the Google Groups
"Google Summer of Code Mentors List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-summer-of-code-mentors-list+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/4bd620f0-9dfe-4733-95ec-31a71a5d8db5n%40googlegroups.com

.

Re: VDG application design sprint?

[Andy B]

This is something I would love to discuss. I have asked others for
ideas and mockups when they have some suggestions. However, until now,
I haven't seen or received any comprehensive design idea we would want
to seek for the future. Maybe I can come up with some ideas and bring
them to the table if we meet.

Thank you,

Andy

On Thu, Feb 2, 2023 at 12:52 AM Nicolas Fella  wrote:
>
> Hi,
>
> I think it would make sense for us to have a VDG sprint of sorts in the
> near-ish future. This would allow to discuss some larger design topics
> and set a vision for the longer-term future. I believe this is important
> for us to be able to work together effectively.
>
> I'd suggest to focus on application design topics, like layout,
> structure, and arrangement of apps, and less on things like Plasma and
> styles/themes. I'd also suggest to approach this more from a design/UX
> PoV and don't let us be driven by implementation details. But these are
> just my suggestions that are subject to debate.
>
> Time/place/modality is all to be discussed, I'm mainly writing this to
> gauge interest, so if you are interested let me know.
>
> Cheers
>
> Nicolas
>


-- 
Andy (anditosan)