ical since 2012.
--
Alexander Potashev
report is rejected
because of invalid platform.
--
Alexander Potashev
2016-10-29 23:06 GMT+03:00 Ben Cooksley <bcooks...@kde.org>:
> On Sun, Oct 30, 2016 at 4:59 AM, Alexander Potashev
> <aspotas...@gmail.com> wrote:
>> 2016-10-25 23:18 GMT+03:00 Ben Cooksley <bcooks...@kde.org>:
>>> Hi all,
>>>
>>> The
2016-10-31 9:28 GMT+03:00 Ben Cooksley <bcooks...@kde.org>:
> On Sun, Oct 30, 2016 at 9:48 AM, Alexander Potashev
> <aspotas...@gmail.com> wrote:
>> 2016-10-29 23:06 GMT+03:00 Ben Cooksley <bcooks...@kde.org>:
>>> On Sun, Oct 30, 2016 at 4:59 AM, Alexander Po
attendee or not
> ** Arrival & Departure Date
>
> See you in Vienna,
> Stefan
>
--
Alexander Potashev
ts from the rest of the community?
>
> TLDR: if the original reporter comments on a needsinfo bug it gets
> automatically switched back to whatever the state before needsinfo was
Hi Harald,
You only considered to case when human sets NEEDSINFO. If NEEDSINFO is
set by a script, we may have the same problem, would you suggest
implementing the same behaviour?
--
Alexander Potashev
пт, 16 нояб. 2018 г. в 16:35, Boudewijn Rempt :
>
> On vrijdag 16 november 2018 14:31:39 CET Alexander Potashev wrote:
>
> > You only considered to case when human sets NEEDSINFO. If NEEDSINFO is
> > set by a script, we may have the same problem, would you suggest
>
release notes and
> other features supported by appstream. Workboard at
> https://phabricator.kde.org/project/board/196/
>
> KDE needs to up its game for the support it provides for our applications,
> here's to a great future for them :)
>
> Jonathan
>
--
Alexander Potashev
Thank you Lydia!
What is the deadline for the "ballot" to be considered/counted?
On Thu, Aug 22, 2019, 22:42 Lydia Pintscher wrote:
> Hey folks,
>
> I have just sent out the emails with links to this year's goal survey.
> All the final proposals are here:
>
"newprojectwizard" - all it
could do were "svn checkout" and "svn update". Once there is an SVN
conflict, you are doomed to using fully functional SVN clients.
--
Alexander Potashev
SVN accounts.
2. Translation memory. Boost productivity, improves consistency of
translations.
3. Other features that improve productivity (insertion of XML/HTML
tags, source string diffs, ...)
--
Alexander Potashev
pre-receive-reject-merge-commit
> >> - Experiment conversion to git and see if the resulting repo(s) are of
> >> a reasonable size (I vaguely recall seeing bad results with this)
I expect that a single Git repository would be several GBs in size.
Cloning the whole repo would be too much for some translators, however
the new Git feature "git clone --filter" might be a solution:
https://unix.stackexchange.com/a/468182
Shall I create a new Phabricator task "[WIP] Migrate translations from
SVN to Git" so we can put relevant ideas in one place?
--
Alexander Potashev
describe the current situation (where to find source
code, how many servers, etc) in new Phabricator tasks like you did for
identity.kde.org in https://phabricator.kde.org/T8449 ?
P.S. Complicated legacy systems can be easy to replicate once you
automate their deployment by using Docker containers and/or
configuration management software like Ansible.
--
Alexander Potashev
org/?view=revision=1555342
--
Alexander Potashev
пн, 11 нояб. 2019 г. в 17:02, Luigi Toscano :
>
> Alexander Potashev ha scritto:
> > вс, 10 нояб. 2019 г. в 18:09, Luigi Toscano :
> >> Most of translators are not so technical as the developers. And even
> >> developers can shoot them in the foot with git, I see
пт, 15 нояб. 2019 г. в 15:46, Harald Sitter :
>
> On Sat, Nov 9, 2019 at 11:37 PM Alexander Potashev
> wrote:
> >
> > сб, 9 нояб. 2019 г. в 02:51, Ben Cooksley :
> > > In the category of no longer in use, we have the compatibility
> > >
пт, 15 нояб. 2019 г. в 22:05, Ben Cooksley :
>
> On Sat, Nov 16, 2019 at 3:27 AM Alexander Potashev
> wrote:
> >
> > пт, 15 нояб. 2019 г. в 15:46, Harald Sitter :
> > >
> > > On Sat, Nov 9, 2019 at 11:37 PM Alexander Potashev
> > > wrote:
d of just fetching kde_projects.xml,
however it would be more complicated.
Is there any good reason for killing kde_projects.xml? Would that
really reduce the workload on Sysadmin team?
I can't suspect any "moving parts" in the generator that may require
maintenance.
[1] https://
e:
> > > >
> > > > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va
> > > > escriure:
> > > > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev
> > > > > wrote:
> > > > > >
> > >
es made in
November. Should we say "last month" everywhere instead?
--
Alexander Potashev
чт, 5 дек. 2019 г. в 02:45, Alexander Potashev :
>
> вт, 3 дек. 2019 г. в 19:59, Jonathan Riddell :
> >
> > Our monthly apps update story is being moved onto kde.org for December and
> > being make to match the release from the release service (previously KDE
> >
5: release/19.12
trunk_kf5: master
The idea is to insert the data from i18n.json into the main YAML under
i18n.branches. Also, the "none" values can be omitted, I guess.
[1]
https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects/kde/applications/konsole
--
Alexander Potashev
the project moves to another group, for example
https://invent.kde.org/unmaintained/knetwalk
--
Alexander Potashev
On Fri, May 1, 2020 at 10:14 PM Ben Cooksley wrote:
> On Sat, May 2, 2020 at 6:17 AM Alexander Potashev
> wrote:
> > I have a similar use case. Sometimes I need to share a URL to a
> > project. For this purpose I used to share e.g.
> > https://cgit.kde.org/releasem
ntity_and_intent
Disclaimer: My personal views, thoughts, and opinions expressed in the
text above belong solely to me, and not necessarily my employer,
organization, committee or other group or individual.
--
Alexander Potashev
On Wed, Mar 31, 2021 at 12:54 AM Luigi Toscano wrote:
>
> Alexander Potashev ha scritto:
> > The https://community.kde.org/Policies/Licensing_Policy says I can't
> > do this because (according to this policy) the MIT License is only
> > allowed for parts of the "KDE
ot;:
- https://invent.kde.org/network/kaidan (at least two files are under MIT)
- http://invent.kde.org/sdk/cutehmi (dual-licensed, including MIT)
--
Alexander Potashev
Thanks for the effort Aleix!
It would be nice to clarify whose opinions this linked message represents.
If this is something that the KDE e.V. Board voted for, then probably a
signature "KDE e.V. Board of Directors" on the bottom of the page would
make sense.
--
Alexander Potashev
O
runtime and KDE
Frameworks) must be licensed under:
...
[new bullet point] * Apache-2.0: Apache License 2.0 as listed below.
"""
What do you think?
--
Alexander Potashev
Thank you Volker!
On Thu, Sep 23, 2021 at 6:01 PM Volker Krause wrote:
>
> done
>
> On Mittwoch, 22. September 2021 23:20:56 CEST Alexander Potashev wrote:
> > Thanks!
> >
> > Could you please update the changelog section
> > https://community.kde.org
gt; >
> > Regards,
> > Volker
> >
> > [1] https://invent.kde.org/frameworks/ki18n/-/merge_requests/19
> > [2] https://spdx.org/licenses/ODbL-1.0.html
> > [3] https://invent.kde.org/pim/kitinerary/-/blob/master/src/lib/knowledgedb/
> > timezonedb_data.cpp
> > [4] https://invent.kde.org/libraries/kpublictransport/-/blob/master/src/lib/
> > knowledgedb/linemetadata_data.cpp
>
--
Alexander Potashev
Option 3: create a dedicated mailing list for job openings.
On Thu, Nov 25, 2021, 17:18 Ingo Klöcker wrote:
> Hi Albert,
>
> On Donnerstag, 25. November 2021 14:44:56 CET Albert Astals Cid wrote:
> > I know a company that would like to hire people with a skill set that
> > is relatively common
otion & Communication
>
> www: http://kde.org
> Mastodon: https://floss.social/@kde
> Facebook: https://www.facebook.com/kde/
> Twitter: https://twitter.com/kdecommunity
> LinkedIn: https://www.linkedin.com/company/kde
>
>
>
--
Alexander Potashev
33 matches
Mail list logo
