Re: VDG application design sprint?

[Andy B]

Are there any updates on this?

On Thu, May 2, 2024 at 1:16 PM Andy B  wrote:

>
> On Wed, May 1, 2024 at 8:12 PM Nicolas Fella  wrote:
>
>> On 11.04.24 16:25, Nicolas Fella wrote:
>> > On 1/24/23 00:43, 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.
>> >
>> > Hi,
>> >
>> > I'd like to pick up this topic again since it's as relevant as ever.
>> >
>> > I have a possible venue in central Germany where I live (in an old
>> > castle, so in good KDE tradition). We could accomodate up to 10 people
>> > there, and more people nearby if needed.
>> >
>> > For those interested, what would be a good timeframe in terms of dates
>> > and duration?
>>
>> Hi,
>>
>> based on the feedback I got I would aim for a 4-day sprint.
>>
>> Please add your availability to
>> https://nuudel.digitalcourage.de/Lv5ti5n1hVOCXlsa
>>
>> If you have any questions, concerns, or suggestions please reach out.
>>
>> Cheers
>>
>> Nico
>>
>>
> Done!
>
> --
> Andy (anditosan)
>


-- 
Andy (anditosan)

Re: VDG application design sprint?

[Andy B]

On Wed, May 1, 2024 at 8:12 PM Nicolas Fella  wrote:

> On 11.04.24 16:25, Nicolas Fella wrote:
> > On 1/24/23 00:43, 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.
> >
> > Hi,
> >
> > I'd like to pick up this topic again since it's as relevant as ever.
> >
> > I have a possible venue in central Germany where I live (in an old
> > castle, so in good KDE tradition). We could accomodate up to 10 people
> > there, and more people nearby if needed.
> >
> > For those interested, what would be a good timeframe in terms of dates
> > and duration?
>
> Hi,
>
> based on the feedback I got I would aim for a 4-day sprint.
>
> Please add your availability to
> https://nuudel.digitalcourage.de/Lv5ti5n1hVOCXlsa
>
> If you have any questions, concerns, or suggestions please reach out.
>
> Cheers
>
> Nico
>
>
Done!

-- 
Andy (anditosan)

Re: VDG application design sprint?

[Andy B]

What else is missing to put together this sprint? I can facilitate.


On April 17, 2024 at 1:40:09 PM, Noah Davis (noaha...@gmail.com) wrote:

Any month except for April (too soon) and September (Akademy 2024), up
to 1 week in duration

On Thu, Apr 11, 2024 at 10:26 AM Nicolas Fella 
wrote:
>
> On 1/24/23 00:43, 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.
>
> Hi,
>
> I'd like to pick up this topic again since it's as relevant as ever.
>
> I have a possible venue in central Germany where I live (in an old
> castle, so in good KDE tradition). We could accomodate up to 10 people
> there, and more people nearby if needed.
>
> For those interested, what would be a good timeframe in terms of dates
> and duration?
>
> Cheers
>
> Nico
>

Re: Help KDE apps comply with FlatHub's new guidelines

[Andy B]

On Thu, Apr 11, 2024 at 7:15 AM Paul Brown  wrote:

> Dear Fellow Community Members,
>
> FlatHub is changing how it will display apps on its site and has issued
> guidelines to help project maintainers adapt the look and descriptions of
> their apps to FlatHub's new design and layout:
>
>
> https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/quality-guidelines/
>
> Not that these are **guidelines**, not **rules**. Apps that do not adapt
> will
> not be removed or penalised, except they may just not show up on the front
> page, as they would not fit in the aesthetic FlatHub is looking for.
>
> We have started a task here:
>
> https://phabricator.kde.org/T17275
>
> and we are calling on app maintainers and any other contributor with a
> developer account to help us update apps distributed via FlatHub.
>
> If you would like to lend a hand, subscribe to the task, read the report
> for
> each app supplied by FlatHub, and help us bring them up to date.
>
> Thanks!
>
> Paul
> --
> Promotion & Communication
>
> www: https://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
>
>
>
Thank you for making us aware of this change. I wanted to ask that we work
closely together with the VDG designers to help in this process. If you
can't get the original authors or app maintainers in the work, or even if
you do, we can help adapt the icons to the standards required when it comes
to graphics.

Thank you

-- 
Andy (anditosan)

Re: VDG application design sprint?

[Andy B]

On Thu, Apr 11, 2024 at 1:32 PM Nicolas Fella  wrote:

> On 1/24/23 00:43, 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.
>
> Hi,
>
> I'd like to pick up this topic again since it's as relevant as ever.
>
> I have a possible venue in central Germany where I live (in an old
> castle, so in good KDE tradition). We could accomodate up to 10 people
> there, and more people nearby if needed.
>
> For those interested, what would be a good timeframe in terms of dates
> and duration?
>
> Cheers
>
> Nico
>
>
For me, anything that is 2-3 months in the future for less than 1 week
works. (US time off is pretty short)

-- 
Andy (anditosan)

Re: Help KDE apps comply with FlatHub's new guidelines

[Andy B]

On Thu, Apr 11, 2024 at 9:32 AM Paul Brown  wrote:

> On Thursday 11 April 2024 14:44:00 CEST Andy B wrote:
> > On Thu, Apr 11, 2024 at 7:15 AM Paul Brown  wrote:
> > > Dear Fellow Community Members,
> > >
> > > FlatHub is changing how it will display apps on its site and has issued
> > > guidelines to help project maintainers adapt the look and descriptions
> of
> > > their apps to FlatHub's new design and layout:
> > >
> > >
> > >
> https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/quality->
> > guidelines/
> > >
> > > Not that these are **guidelines**, not **rules**. Apps that do not
> adapt
> > > will
> > > not be removed or penalised, except they may just not show up on the
> front
> > > page, as they would not fit in the aesthetic FlatHub is looking for.
> > >
> > > We have started a task here:
> > >
> > > https://phabricator.kde.org/T17275
> > >
> > > and we are calling on app maintainers and any other contributor with a
> > > developer account to help us update apps distributed via FlatHub.
> > >
> > > If you would like to lend a hand, subscribe to the task, read the
> report
> > > for
> > > each app supplied by FlatHub, and help us bring them up to date.
>
> > Thank you for making us aware of this change. I wanted to ask that we
> work
> > closely together with the VDG designers to help in this process. If you
> > can't get the original authors or app maintainers in the work, or even if
> > you do, we can help adapt the icons to the standards required when it
> comes
> > to graphics.
>
> That would be great! What do you suggest? What other ML do you think we
> should
> crosspost this to? Maybe you can post and coordinate things in the VDG
> Matrix/
> Telegram channels.
>
> Also please feel free to add stuff to the task. Maybe add VDG-specific
> tasks to
> the TODO list so we can all keep track.
>
>
>
Probably like this:

1. We want to understand if any of our Flathub apps are already in
compliance vs others that are not. We focus on the ones that need fixing.
2. Check with a maintainer or person responsible for the app to see how
they could meet the criteria.
3. Determine who will do the work, if needed
4. Work with the VDG when all other steps are not possible

I realize this is a bit of a project, would Adam Szopa be available to
coordinate some of this?

Thank you,

Andy


-- 
Andy (anditosan)

Re: Join the Goals sprint in Berlin!

[Andy B]

Oh man, I would have loved to participate. I totally missed this. Kinda too
late for me to make arrangements. Will there be any online sessions?

On Sun, Mar 31, 2024 at 10:50 PM Nate Graham  wrote:

>
>
> On 3/30/24 11:03, Albert Astals Cid wrote:
> > El dissabte, 30 de març de 2024, a les 16:01:57 (CET), Adam Szopa va
> escriure:
> >> Hi everyone,
> >>
> >> In a couple of weeks (20-24th of April, arrivals on the 19th) there is a
> >> Goals sprint happening in Berlin.
> >
> > A couple of weeks is not enough time for most people to be able to
> attend an
> > event that is in possibly another country and on top of that happens
> during
> > the work-days.
> >
> > I know organizing events is hard, but please next time let's try to
> organize
> > things with more time :)
>
> For what it's worth, this was first announced in January:
> https://mail.kde.org/pipermail/kde-devel/2024-January/002390.html
>
> I agree that it's a bit late for the venue though. :/
>
> Nate
>


-- 
Andy (anditosan)

Re: SCALE 21x talk looking for NA KDE speaker

[Andy B]

I would like to throw my hat on the ring to travel there and participate.
>From the talk title it seems like something I can expand on.

Let me know.

Andy (anditosan)


On January 11, 2024 at 5:42:14 PM, Joshua Goins (j...@redstrate.com) wrote:

>
> Hi Josh,
>
> Thanks for the heads up. We're on it.
>
> We have several people planning to attend SCALE to staff the booth. We'll
> check with them.
>

Thanks Paul! Me and my schedule will be very glad 

Josh

Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos

[Andy B]

I side with the comments made by Niccolo and Abert. We have some 300
users in Telegram vs about 170 on Matrix for the visual design
channel. Our audience, being a graphical design and user experience
channel, tends to attract users who are more inclined to the arts and
may be less technical than other users. For these users the experience
needs to be a good one, frictionless.

I feel that removing the bridge will negatively impact these users who
likely will have to jump through hoops to set up applications with
sub-par experiences.

I understand the argument of wanting to use open source software. It's
an objective of our community. It is also true that our open source
alternatives do not match commercial applications. It is also true
that it might also be an unreliable experience overtime as well.

What are our alternatives should we keep the bridge? Would we expect
it to break at some point? What are the certainties of this happening?

Thank you,

Andy

On Tue, Aug 22, 2023 at 4:09 PM Albert Vaca Cintora
 wrote:
>
> KDE Connect has a Telegram group with 660 members (vs 100 on matrix). I don't 
> know if we are the exception with such a big group on Telegram, but this is 
> going to be a hit to our community :(
>
> On Tue, 22 Aug 2023, 09:02 Joseph P. De Veaugh-Geiss,  wrote:
>>
>> Hello KDE community,
>>
>> apologies for cross-posting!
>>
>> The time has finally come: both Telegram <-> Matrix bridges will be shut
>> down in 4 weeks on *Wednesday 20 September*. Let's start the
>> co-ordination process now so everything goes as smoothly as possible.
>>
>> For all KDE contributors: please read at least the "Five To-Dos" below
>> to be informed about what will happen and what needs to be done.
>>
>> Below that there is some additional information about the bridging
>> situation at KDE. Consult these notes if you want more background
>> information about why the Telegram bridge is being retired.
>>
>> Cheers,
>> Joseph
>>
>> _Five To-Dos_
>>
>>1. *General*: On Wednesday 20 September the Telegram bridging to KDE
>> Matrix rooms will be shut down. To make the transition go smoothly,
>> teams should start co-ordinating for the shutdown now. The Matrix room
>> for co-ordination is "Telegram shutdown co-ordination" at
>> https://go.kde.org/matrix/#/#telegram-shutdown:kde.org.
>>
>>2. *Co-ordination*: This includes: (i) migrating all contributors to
>> Matrix, and (ii) deleting the Telegram rooms before the bridge is
>> shutdown or -- at most -- one day after the shutdown. Keeping Telegram
>> rooms open when they are no longer being used will cause unnecessary
>> confusion. Importantly, do not later add a non-KDE Telegram bridge to
>> KDE's Matrix rooms as that will not solve the problems from doubled user
>> accounts and lack of control over Telegram; see below for operational
>> issues with Telegram bridging.
>>
>>3. *Action needed by Telegram room admins*: Due to the unexpected
>> shutdown of the public Libera.Chat bridge, we will have to move rooms
>> over to the matterbridge (ircsomebot) bridge as we work through moving
>> channels over to our own Libera.Chat IRC bridge. This will require
>> someone with admin in the Telegram room to ensure @ircsomebot is in the
>> Telegram room with admin. This needs to be done after we unbridge the
>> Matrix bridge from the Matrix side, so the room can continue to be
>> bridged until the Telegram shutdown on 20 September.
>>
>>4. *Are there exceptions?": There /may/ be some rooms that focus on
>> interacting with people external to the KDE Community who would benefit
>> by having a Telegram bridge. We are thinking teams like those involved
>> in the KDE Network program: https://community.kde.org/The_KDE_Network.
>> Not all will need an exception, and it may turn out most don't. We would
>> like to start putting together a list of these rooms so we can review
>> for potential exceptions and estimate the scale of how much support is
>> needed. However, this should be kept to a minimum; see below for
>> operational issues with Telegram bridging. We understand that there are
>> large internal KDE communities which rely heavily on Telegram, and we
>> understand that shutting down the Telegram bridge is less than ideal for
>> these rooms, but the issues we have with the Telegram bridge mean we
>> need to keep exceptions to a minimum and only for those teeams whose
>> work has a primarily external focus.
>>
>>5. *Getting a Matrix account*: We can offer KDE Contributors (usually
>> those in the developers group, but will consider other requests) a
>> Matrix account on our KDE Matrix Homeserver. To request an account
>> please file a sysadmin ticket https://go.kde.org/systickets. However, as
>> Matrix is federated you do not need to have an account on our homeserver
>> to access KDE's Matrix rooms -- you can use any homeserver! A list of
>> some alternative Matrix servers is available on
>> https://joinmatrix.org/servers/.
>>
>> To co-ordinate with other teams 

Invitation to Participate in the Community Working Group

[Andy B]

Dear community,

We would like to extend an invitation to participate in the Community
Working Group. We are in need of members who want to help our community
healthy and vibrant.

You will be required to be sensible to difficult situations, use mediation
skills, craft messages to community members, represent the CWG in KDE
channels, etc.

As such, if you have experience in these areas, let us know. We also offer
a training program and steps that can get you ready for the work.

Simply reply to this email with your intentions to participate and one of
our team members will contact you back for further steps.


To learn more about the Community Working Group and our functions, please
go to: https://ev.kde.org/workinggroups/cwg/


Thank you

Community Working Group

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)

Re: VDG application design sprint?

[Andy B]

I am very interested! Count me in!

Thank you,

Andy


On January 23, 2023 at 7:17:25 PM, Nate Graham (n...@kde.org) wrote:

Very interested!

Ever since the GNOME folks created Libadwaita, I feel like their
3rd-party app ecosystem has really taken off, and it seems like
something they put a lot of planning and foresight into making happen.
In KDE land we have a lot of 1st-party apps but not as much on the
3rd-party side, and I'd like for us to have an equally compelling story
there. I think the design, HIG, and UX perspectives--both user and
developer--are key to making this happen, and a VDG sprint would be the
perfect place to discuss those topics.

Nate



On 1/23/23 16:43, 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
>

Re: [Important] changes to our Matrix homeserver

[Andy B]

Thank you Kenny. It worked this time.


On September 8, 2022 at 10:55:06 AM, Kenny Duffus (ke...@kde.org) wrote:

On Thursday, 8 September 2022 15:35:26 BST Andy B wrote:
> I tried adding the matching email address but Matrix says that this is
not
> an authorized email address on the server. What should I do in this case
if
> I want my email addresses to match on invent and matrix?
>

Hi

Unfortunately that error was due to a config setting, you should now be
able to set any email address

-- 

Kenny
(Pronouns: he/him)

Re: [Important] changes to our Matrix homeserver

[Andy B]

I tried adding the matching email address but Matrix says that this is not
an authorized email address on the server. What should I do in this case if
I want my email addresses to match on invent and matrix?


On September 8, 2022 at 10:24:45 AM, Kenny Duffus (ke...@kde.org) wrote:

Hi

We are moving to use our SSO (gitlab) for authentication to the KDE Matrix
homeserver

To be able to retain access to your matrix account you need to ensure on
the matrix side that you have set in your account the email address
matching that in KDEgitlab

On https://webchat.kde.org/ you can access your settings in the bottom left
hand corner ⚙ then as shown in the screenshot

Please do this as soon as you can

Thanks

-- 

Kenny
(Pronouns: he/him)

Re: KDE now has its own Matrix infrastructure

[Andy B]

Andy Betts
KDE Board
On Feb 28, 2019, 5:13 AM -0700, Jonathan Riddell , wrote:
> On Wed, Feb 27, 2019 at 03:06:22PM -0800, Valorie Zimmerman wrote:
> > Hey Jon, I hope that the CWG response was not dismissive, and you were
> > certainly not ignored. We always listen and try to help when possible. If 
> > you
> > didn't feel at the very least listened to, we failed there.
> >
> > You are one of the most stalwart and longest-serving volunteers, so when you
> > are unhappy and angry, I don't think anyone is happy about that. That 
> > doesn't
> > mean that all of us see your list above as an accurate statement.
>
> Thanks :)
>
> In over a decade of helping promo in KDE it was always the case that
> someone could come in and show willingness and competance and be given
> access to the accounts needed to be a full member. When I left the
> team in 2017 and came back in 2018 this had changed and I was told I
> could not get access to accounts, a decision which seems to have been
> taken by the e.v. board. We fixed this after Akademy 2018 with a
> formal policy. Will the CWG now look into why this change happened
> against the norms everywhere else in KDE?
>
> Jonathan


There has to be context to this, now that we have moved from the main topic and 
now dedicate this thread to solve issues that Jonathan has expressed. Maybe we 
can start a new thread.

To be clear, Jonathan has repeatedly used little tact when releasing 
information to the public. The e.V. Board received complaints and requests to 
manage the situation. We decided to do so and work with Jonathan to review his 
publication practices in social media. On his insistence, we worked to have a 
more clear policy of access to social media. Policy that Jonathan himself would 
follow. The Board agreed that this could help shape the way that Jonathan and 
others provide public, WIP information to the general public and have more tact 
when doing so.

Why is this still an issue that requires the CWG? I am not even sure. I thought 
Jonathan was over this when we did as he required, create an access policy 
within Promo.

Thank you,

Andy

Re: KDE now has its own Matrix infrastructure

[Andy B]

On February 27, 2019 at 4:36:52 AM, Jonathan Riddell
(j...@jriddell.org(mailto:j...@jriddell.org)) wrote:

> On Tue, Feb 26, 2019 at 11:22:03AM -0700, Nate Graham wrote:
> > It's no great secret that Paul and Jonathan don't have a great working 
> > relationship, but this problem needs to be addressed openly.
>
> Au contrate, we have spent many a fine night drinking beer and whisky
> together from Edinburgh to Sarajevo. The issue I have is when we have
> structures intended to resolve issues like the e.v. board or the CWG
> and they choose not to.
>
> Jonathan

I will disagree with this point. In many cases, timing is important
and things are not “secret”. Prudence is a valuable skill too. What if
I was to mention something that I wasn’t 100% clear on, I put this on
you and you pass it on as truth? Then we have a problem, because in my
desire to keep things not a “secret” I misled you.

Many of the things the e.V. Board does have to be thought out, done
with prudence, and wait for the right time, when we have made sure
that things are for certain. I am sure our community would not
appreciate communication mistakes. This whole thread is evidence of
that. Therefore, the best possible way to tackle this is to retract,
be thoughtful, think of your audience and learn to communicate in a
timely manner.

This is is the whole point why companies, for example, have
communication departments, public relations departments, etc.

At the same time, the e.V. does not necessarily “choose” not to do
something about a situation. What is important is that members of the
community also learn to work with each other, as adults, contributing
project members. We can’t play parent at every turn. You would get
pretty annoyed at that. I got annoyed of my parents correcting my
every move, that’s why I joined this team. Just kidding!

The point is, if community members have issues, community members
should deal with those issues. If you have a problem with someone,
talk to that someone. We as the e.V. Board would probably review
situations that are too disruptive to the community and help with
those. If you want the e.V. Board to participate of a certain
situation and help, make it known. We are humans and don’t have
understanding of every little event that happens in the community 100%
of the time. We rely on you to cultivate an open communication channel
with the e.V. Board when you think it is necessary.

However, I recommend to always assume best intentions in everything.
Once we deride, criticize and slander, we stop the e.V. Board’s
ability to help. We walk into the battle wounded. Assuming best
intentions will also help you remove the pressure that suspicion
creates. I tell that to our engineers at my work all the time. I think
it is sound advice.

With that said, is there anything that we can help with in this
particular instance? Do we feel that we are satisfied with the answers
provided?

Re: KDE now has its own Matrix infrastructure

[Andy B]

On February 26, 2019 at 11:22:27 AM, Nate Graham
(n...@kde.org(mailto:n...@kde.org)) wrote:

>  On Tue, 26 Feb 2019 10:37:56 -0700 Christian Loosli wrote 
> > That all in mind is why I think the approach was maybe not the best one and
> > should be reconsidered for future events and articles.
> >
> > Thanks and kind regards,
> >
> > Christian
>
>
> I'm in agreement with Christian about this. Conducting this process behind 
> closed doors seems to have backfired, as evidenced by the technical problems 
> that happened anyway and the controversy and drama that we're all now 
> embroiled in. Regardless of intentions, these results should be a clear sign 
> that the process didn't work and needs to be re-examined. And it's very 
> disappointing to hear that a part of the reason for this process was 
> specifically to exclude a particular person. It's no great secret that Paul 
> and Jonathan don't have a great working relationship, but this problem needs 
> to be addressed openly. The two of you trying to work around one another, 
> occasionally writing passive aggressive emails on the mailing list is not how 
> the problem will get solved; instead it will just get bigger over time.
>
> We don't need secrecy, politicking, and personality-driven conflicts like 
> this in KDE. When there's a problem, let's handle it like adults so we can 
> all get back to the business of making the finest open-source software the 
> world has ever seen.
>
> Nate
>

Thank you all for your comments. I am sure now it is a lesson learned
and we will be more vigilant of these situations in the future. It is
part of the challenge of working with a large community across many
countries.

We all make assumptions that we feel are right but when placed in a
larger context they don’t always work the way it was intended.

I feel the community has spoken and we are in agreement. Let’s learn
from it and now move forward with the amazing work we deliver to many
people in the world.

Hugs.

Andy
KDE Board Member

Re: Call for contributors for Fixture [ Qt5 based raster graphics editor ]

[Andy B]

Wherever it may be, good or bad, just not in this list. It seems this
discussion will go for long and it is probably best for the contributors to
have a separate discussion elsewhere where they can dive into details.

On September 22, 2018 at 7:38:03 AM, Luigi Toscano (luigi.tosc...@tiscali.it)
wrote:

> Andy B ha scritto:
>
> Can you guys maybe now move this discussion to telegram or phabricator? It
> seems that there is good debate and good will.
>
>
> I'm not sure why this discussion should be diverted from a mailing list to
> a
> messaging system (*) and a planning and development system like
> phabricator.
>
> Maybe (just maybe) it can be be moved to a more appropriate mailing list.
>
> (*) let's not use "telegram" as synonym for "messaging system", please.
>
> --
> Luigi
>

Re: Call for contributors for Fixture [ Qt5 based raster graphics editor ]

[Andy B]

Can you guys maybe now move this discussion to telegram or phabricator? It
seems that there is good debate and good will.

Thank you

Andy

On September 22, 2018 at 6:37:13 AM, Boudewijn Rempt (b...@valdyas.org)
wrote:

> On zaterdag 22 september 2018 10:18:22 CEST Kuntal Majumder wrote:
>
> Someone in reddit was also saying that, the UI is built on plugins so
> practically we can scrap the UI and use Krita as a base to develop it
> further. Would be helpful if someone can shed some light onto it.
>
>
> Sorry, that's just something you'll have to dig in for yourself. It's not
> worth my time at least to get you started on something like that: it will
> not
> help me achieve my goals.
>
> --
> https://www.krita.org
> --
>

Re: Twitter access

[Andy B]

On July 19, 2018 at 9:26:03 AM, David Narvaez (david.narv...@computer.org)
wrote:

On Thu, Jul 19, 2018 at 11:05 AM, Jonathan Riddell  wrote:
> I did but I see nobody has an interest in me being a full part of it

That's simply not true: we have all seen Paul Brown's message where
you are invited to participate in the promo team. What you mean to say
is that you are not allowed to be part of the promo team under your
own rules and conditions, but when you put it like that you do not
sound much like a victim and you lose some negotiation power.

While I personally have no position regarding your one-man charge
against the promo team (I do not have enough information to pick a
side here), I am very much against your theatrical portrayal of the
issue when we can all clearly see what is going on here. If you want
to do promo under your own terms like back in the ol' days 15 years
ago, then just say so, no need to play victim.

David E. Narvaez

Before we are too flustered by this interaction, let’s see what we can do
now. Jon, does the team need to post anything to our twitter account? Is
there something that needs to be out soon?

Re: The VDG

[Andy B]

No worries David. The situation is past now. Let me know if you have any
questions.

Andy

On July 10, 2018 at 4:38:15 PM, David Wright (david.wright12...@gmail.com)
wrote:

> Hi all,
>
> From reading this and the linked discussion I'm unsure what the problem
> is?
>
> KDE does not in majority of cases ship directly to users, it does through
> distros.
>
> Surely the goal is to speak to distros, even the esoteric ones like
> kxstudio and find out what they and their users would like and work from
> there?
>
> On Sun, 3 Jun 2018, 21:24 Andy B,  wrote:
>
>> Hello team,
>>
>> Given recent events and decisions (
>> https://mail.kde.org/pipermail/plasma-devel/2018-June/086117.html) I
>> feel it important to bring more to the table.
>>
>> Martin’s decision is an unfortunate one. Martin has been with KDE through
>> thick-and -hin and has earned the respect and love from many members in the
>> community. He has also earned my respect.
>>
>> I can’t help but think that the VDG is a tremendously influential group
>> within KDE. I personally take this as a huge responsibility and a call to
>> do even better in our approach. We ourselves have also seen the departures
>> of many influential members. We have lost leaders one after the other and
>> we have tried to cope with that. Martin’s and others’ comments about the
>> VDG are welcomed and noted in this regard.
>>
>> I share the feeling. The VDG has strived to bring design back to the
>> table after we started the Plasma 5 cycle, discussing design, debating
>> direction, etc. However, the VDG has no leader, no vision, no strong
>> direction. I took these thoughts seriously last year when I first attended
>> Akademy. I realized that the VDG has a strong voice, but it was just that,
>> a voice.
>>
>> I think we are still feeling the fallout from Aaron Siego’s exit from the
>> community. He provided strong vision, made developers excited once again
>> for their work, designers rallied behind the visual vision we had. It felt
>> as though nothing could stop us because we had a guide to follow. Nothing
>> else mattered.
>>
>> I think the VDG needs vision and guidance desperately. I am guilty myself
>> of not providing this. However, I have taken steps to mitigate this
>> problem. Last year, I decided to engage myself in revamping System
>> Settings. We are still working through it but strong work has been done in
>> this past year from me that I have ever done before.
>>
>> My basic idea was to provide an easier way to interact with the thousands
>> of options that System Settings provides. By doing this work, I discovered
>> that much more could be sprung up and done for the entire interface. I also
>> discovered that I cannot take a hard line on everything that I do. We have
>> been able to deliver more KCMs by steering design rather than dictating
>> design. My affiliation with developers in the team has been one of the most
>> enriching experiences of my life. I feel the VDG will do well in
>> approaching our developer team the same way. Don’t be married to a design,
>> learn from technical challenges to your work, adapt quickly and move on.
>> VDG members will see that by doing this, we open the door to even more
>> possibilities than we ever thought.
>>
>> Our developers are the ones putting out thousands of lines of code,
>> reading on a computer screen all day, and Plasma ones do this all night as
>> well. They are the foundation of the project. Without our developers, the
>> VDG can never hope to deliver anything to the public. Our developers area
>> cautious, full of ideas and a guiding voice for contributors. We will do
>> well in partnering with a developer as we work and listen carefully to
>> their counsel.
>>
>> I feel that our team in the VDG generally receives many newcomers to the
>> world of Linux and Open Source communities. This is a challenge for the VDG
>> as we must be open to new contributors but also need to curve contributions
>> to the right places. For some, this makes it feel to them that “anything
>> goes”. This is simply not the case. We ask that if you are a new
>> contributor to the VDG, start small, learn from others and ask questions.
>> We cannot take the hard line that our designs are above the project. They
>> are simply not.
>>
>> The VDG also gathers a crowd that is passionate about design but doesn’t
>> always provide direction. I will take fault for that. Having been here a
>> while I feel it is my responsibility to provide more direction to new
>> contributors. I have opened d

Re: The VDG

[Andy B]

Thanks for that Lays!

Hugs!

Andy

On July 10, 2018 at 4:06:16 PM, Lays Rodrigues (lays.rodrig...@kde.org)
wrote:

> Just a thought:
> "If you want to point a finger, do it at me. I am at fault for not guiding
> sooner."
>
> I don't think that we need to point fingers here. Or that we need a leader.
>
> What we need is a guideline that everyone can *understand* and *follow*.
> We need to be a *team*. We need to put our pride by the side and discuss
> every view that one has on the subject.
>
> Isn't just 'we don’t dimension that a graphic design that took us 2 hours
> to make will take 6 months to deliver'.
> It's to understand the macro view of a project, it's to understand how
> everything is affected by that change. We need to measure that, and that is
> where I do +1 on your comment about a Project Management. The Agile Method
> has a lot of good practices that we can study and adapt for our use case.
>
> Also, if we start to follows 'one leader', that can cause us future
> problems, as if the burden gets too heavy and so on, or as starting
> pointing fingers on stuff that we lost track just to have a 'fall guy'.
> We need to *share* *our* *knowledge* and build the common base of that.
> We can't rely upon one person for that. Otherwise, all the history or the
> background will get to dust when 'the leader' gets out of the community.
>
> We can have guidance, but I think that you don't need to take all of that
> upon you Andy.
>
> Best regards,
>
>
>
> On Tue, Jul 10, 2018 at 6:38 PM, Stef Bon  wrote:
>
>> Hi,
>>
>> my idea for the kde plasma desktop: create a 3d desktop. There are
>> already 3d effects,
>>
>> Make it possible to put windows far away (= 3d effect), and others closer.
>>
>> Stef
>>
>
>
>
> --
>
> *Lays Rodrigues*
>
> *KDE*
>
> *Atelier - atelier.kde.org *
>
> *Fundraising WG*
> *http://lays.space *
> *Telegram: @lays147*
>

The VDG

[Andy B]

Hello team,

Given recent events and decisions (
https://mail.kde.org/pipermail/plasma-devel/2018-June/086117.html) I feel
it important to bring more to the table.

Martin’s decision is an unfortunate one. Martin has been with KDE through
thick-and -hin and has earned the respect and love from many members in the
community. He has also earned my respect.

I can’t help but think that the VDG is a tremendously influential group
within KDE. I personally take this as a huge responsibility and a call to
do even better in our approach. We ourselves have also seen the departures
of many influential members. We have lost leaders one after the other and
we have tried to cope with that. Martin’s and others’ comments about the
VDG are welcomed and noted in this regard.

I share the feeling. The VDG has strived to bring design back to the table
after we started the Plasma 5 cycle, discussing design, debating direction,
etc. However, the VDG has no leader, no vision, no strong direction. I took
these thoughts seriously last year when I first attended Akademy. I
realized that the VDG has a strong voice, but it was just that, a voice.

I think we are still feeling the fallout from Aaron Siego’s exit from the
community. He provided strong vision, made developers excited once again
for their work, designers rallied behind the visual vision we had. It felt
as though nothing could stop us because we had a guide to follow. Nothing
else mattered.

I think the VDG needs vision and guidance desperately. I am guilty myself
of not providing this. However, I have taken steps to mitigate this
problem. Last year, I decided to engage myself in revamping System
Settings. We are still working through it but strong work has been done in
this past year from me that I have ever done before.

My basic idea was to provide an easier way to interact with the thousands
of options that System Settings provides. By doing this work, I discovered
that much more could be sprung up and done for the entire interface. I also
discovered that I cannot take a hard line on everything that I do. We have
been able to deliver more KCMs by steering design rather than dictating
design. My affiliation with developers in the team has been one of the most
enriching experiences of my life. I feel the VDG will do well in
approaching our developer team the same way. Don’t be married to a design,
learn from technical challenges to your work, adapt quickly and move on.
VDG members will see that by doing this, we open the door to even more
possibilities than we ever thought.

Our developers are the ones putting out thousands of lines of code, reading
on a computer screen all day, and Plasma ones do this all night as well.
They are the foundation of the project. Without our developers, the VDG can
never hope to deliver anything to the public. Our developers area cautious,
full of ideas and a guiding voice for contributors. We will do well in
partnering with a developer as we work and listen carefully to their
counsel.

I feel that our team in the VDG generally receives many newcomers to the
world of Linux and Open Source communities. This is a challenge for the VDG
as we must be open to new contributors but also need to curve contributions
to the right places. For some, this makes it feel to them that “anything
goes”. This is simply not the case. We ask that if you are a new
contributor to the VDG, start small, learn from others and ask questions.
We cannot take the hard line that our designs are above the project. They
are simply not.

The VDG also gathers a crowd that is passionate about design but doesn’t
always provide direction. I will take fault for that. Having been here a
while I feel it is my responsibility to provide more direction to new
contributors. I have opened doors, but I have not learned how to shut them.
If our dev team has anything they want to say, please bring this to me and
I will work with you.

If anything, I feel that our developer team, the VDG and the Plasma team in
general currently lacks “visual direction”. I say this very carefully of
everyone’s feelings. We maintain our software without stretching ourselves
too far. After all, major changes also mean major work. By the same token,
sometimes as VDG, we don’t dimension that a graphic design that took us 2
hours to make will take 6 months to deliver. We must think deeper, less
like a graphic artist and more like a project manager. This will bring
perspective to our work.

I ask that instead of diving into power struggles and control over code and
design, let’s direct that energy into developing a visual direction. We
worked hard on this a couple of years ago. We developed “simple by default,
powerful when needed.” I love that motto. It drives my thinking when
designing for the project. However, we needed more than that. We started
working on developing our human interface guidelines and the team delivered
a strong set. After the advent of Kirigami, the team needed to revise our
HIGs, a new 

Re: Mock-up of revised KDE Store

[Andy B]

Can you maybe just use the background image on the top banner instead?
Keep the background white.

On Fri, Feb 16, 2018 at 11:28 AM, Scott Harvey  wrote:
> Here you go - a (very) rough draft of what kinds of things we can sell.
>
> https://www.cafepress.com/bdtokde
>
> I edited the CSS to add the background image (instead of the drab khaki the
> template used) and threw together a quick header graphic. The Miscellaneous
> section are a few icons from the default Breeze theme. I know they're not
> very "KDE"-flavored, but I figured - why not.
>
> For someone who asked (can't recall who) - Cafe Press does not have
> embroidery-style patches. Sorry.
>
> All the prices are shown with zero markup, by the way.
>
> Feedback and (hopefully) constructive criticism welcomed.
>
>
> -Scott (aka bundito on IRC)



-- 
Andy (anditosan)

Re: Babe project - Legal feedback

[Andy B]

On February 3, 2018 at 1:19:33 PM, Camilo Higuita Rodriguez (
chigui...@unal.edu.co) wrote:

My case is the following, let's say that there's a feature for streaming
audio, and the users stream the song they are listening to, what would go
down in that case? Who's in legal troubles?

 Also if I were to send an mp3 over email to a few friends, where's the
illegal stand point there? The platform has some fault for allowing to
"distribute" the file? Or the user who emailed the content?

And yes, so far the platform only shares the playlist info, and if there
are matches with your collection then you can listen to it.

This is where you might be in territory that you don’t want to cross. You
have to make sure that the files being listened to are streamed P2P only.
Don’t post any of them anywhere, not even a list that can be accessed on
the web. Don’t allow access unless expressly requested. Otherwise you
become a streaming service like Pandora, Spotify, Google Music and those
are services that pay royalties to the artists for having their music on
their platform.



But it would be really cool to be able to somehow share your music...
tipping around those copyright issues. What if the case is that the user
has some kind of music cloud and gives access to that cloud to another
user, still illegal?

There is really nothing wrong here, because for example, in the case of
Google, they pay the artists to allow their music on their service and they
don’t make themselves responsible to police the music you upload on their
service. But the accounts are personal. They generally don’t intend for
them to be shared. However, in Google Music, they allow you to recommend
music to others with similar accounts and they don’t share the files but a
snippet of the song so you would buy it.



Lol as I see this it seems like the answer is : "don't you mess with music
copyrights, whatever you do will get you in trouble somehow"

I don’t think so. Here the thing is that you want to offer a streaming
option. There is nothing wrong with that. But care for making it very
personal, not like a broadcast radio station or TV. It has to be personal
and streaming from one device to another and not sharing the file to
another device.



Does anybody know of any KDE community member who is could ask these legal
questions?

On Feb 3, 2018 3:07 PM, "Albert Astals Cid"  wrote:

> El dissabte, 3 de febrer de 2018, a les 18:07:27 CET, Camilo Higuita
> Rodriguez
> va escriure:
> > Hi,everyone
> >
> > I'd like to discuss something with the community, and maybe get some
> legal
> > input:
> >
> > As some of you might already know I'm working on a open online platform
> to
> > share music information between users, such as public playlists, comments
> > on tracks and on the playback progress like soundcloud, share popular
> music
> > suggestions, metadata, and discovery of new music from another users with
> > integration with YouTube and Spotify etc... the platform will be
> integrated
> > into Babe music player and could be use in any other music player
> >
> > The legal matter comes here:
> > 1- I would like to either have the option to *stream live* the music an
> > user is currently listening to to a group of friends. here the music file
> > isn't being storaged in the audience computer...
> > How ilegal is it? How illegal is to stream live, but privately,
> copyrighted
> > music?  and how illegal is it to stream owns music content to a selected
> > group of friends?
> >
> > 2- If the stream part wouldn't be enought problem, I'd also like to sync
> a
> > user playlist marked as public to some other friends, that would mean to
> > share music files between users, and technically downloading another
> users
> > music files. How illegal is this part? how illegal is to share a music
> file
> > for example, in a conversation in telegram or whatsapp, or even how
> illegal
> > is it to send a mp3 to a friend over an email or even over google drive?
> >
> > I'd like to get feedback about this issues.
> >
> > As the project is going to be hosted by the KDE community this streaming
> > part won't be implemented to avoid legal issues, but however I would like
> > to have this discussion to get as many feedback as possible.
>
> I am not sure you're approaching this the right way.
>
> For me it doesn't really matter if users can do illegal stuff with our
> software, what matters is that the software is legal and that it has legal
> uses (see KTorrent).
>
> What I think you should be asking yourself is "will I/KDE be in problems
> for
> shipping this sofware?" more than "can my user pontentially get in trouble
> for
> using my sofware to do illegal stuff?".
>
> Cheers,
>   Albert
>
> >
> > Thank you.
> >
> > Camilo
>
>
>
>
>

Re: Please help us push the fundraiser with a blog post about your work in 2017

[Andy B]

It looks like on mobile it is missing the blue shade box that is on top of
the image. It seems to be a bug.

Anyone that could take a look?

Thank you,

Andy


On December 26, 2017 at 10:16:20 AM, Clemens Toennies (
starb...@netrunner-os.com) wrote:

Hi Andy,

not on a computer right now, but on mobile it looks like this.


On Dec 26, 2017 08:31, "Andy B" <anditosan1...@gmail.com> wrote:

> You mean this?
>
> Thank you,
>
> Andy
>
>
> On December 26, 2017 at 9:30:01 AM, Clemens Toennies (
> starb...@netrunner-os.com) wrote:
>
> I think it has been mentioned before, but the white text on parts of the
> background image makes it hardly readable. Is there someone who can fix
> this?
>
> Happy holidays, Clemens.
>
>
>
> On Dec 26, 2017 04:25, "Lydia Pintscher" <ly...@kde.org> wrote:
>
> Hey folks :)
>
> https://www.kde.org/fundraisers/yearend2017/
> We're now at 28% of our fundraiser goal. This isn't bad but we could
> use another push.
> It'd be lovely if you could take the time to write a blog post about
> your work around KDE in 2017 and ask people to support KDE's work
> through the fundraiser.
> I'd love to read more about your work of the past year and I am sure
> so would our users and fellow contributors.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors
> http://kde.org - http://open-advice.org
>
>
>

Re: KDE Community Goals: 2017 voting has started

[Andy B]

Thank you Lydia.

I voted.

Andy

On Mon, Nov 6, 2017 at 1:15 AM, Lydia Pintscher  wrote:
> Hey folks :)
>
> We are really close to having our goals for the next 3 to 4 years
> figured out. The only remaining step is the voting. I am sorry this
> was a bit delayed because of trouble getting the system set up.
>
> You can see the latest state of all goal proposals at
> https://phabricator.kde.org/project/board/244/
>
> I just send out a voting invitation email to the following groups as
> that is the closest I can get to reaching active KDE contributors:
> * everyone subscribed to the KDE Community mailing list
> * everyone with a KDE developer account on identitiy.kde.org
> That gives us 2709 people. If you know someone who is an active
> contributor and does not fall into either of those groups please ask
> them to send me an email and I will add them still.
>
> The voting will be open for 2 weeks. Please do take part. This is an
> important step in helping us work together in the next years.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors
> http://kde.org - http://open-advice.org



-- 
Andy (anditosan)

Re: Let's set some goals

[Andy B]

Thanks Lydia! :)

On September 30, 2017 at 10:05:13 AM, Lydia Pintscher (ly...@kde.org) wrote:

> On Sat, Sep 30, 2017 at 3:48 PM, Andy B <anditosan1...@gmail.com> wrote:
>
> Are you ok that I submit my proposals on Monday? I am traveling at the
> moment, but I really want to turn something in.
>
> Thank you
>
>
> Ok. But please get it in on Monday.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors / KDE Community Working Group
> http://kde.org - http://open-advice.org
>

Re: Let's set some goals

[Andy B]

Are you ok that I submit my proposals on Monday? I am traveling at the
moment, but I really want to turn something in.

Thank you

Andy

On September 30, 2017 at 5:06:37 AM, Lydia Pintscher (ly...@kde.org) wrote:

> Hey folks :)
>
> This is the final reminder to get your goal proposals in. Today is the
> last day. Then we'll go to the discussion/improvement phase.
> If you need any help let me know. If you are unsure if you should
> submit something lean towards doing it! We have a month to fine-tune
> it.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors / KDE Community Working Group
> http://kde.org - http://open-advice.org
>

Re: Spreading Randa stories II

[Andy B]

Done!


On September 12, 2017 at 2:17:21 PM, elcaseti . (elcas...@gmail.com) wrote:

done.

On Tue, Sep 12, 2017 at 11:28 AM, Paul Brown  wrote:

> Hello,
>
> Again we call open you to help us give a push to the Randa funding
> campaign.
> We need you to give us hand with a story on the subject by posting the
> news to
> Facebook groups, G+ communities, re-tweeting and re-tooting it, drawing
> other
> communities attention to it, upvoting on Reddit, and so on.
>
> The story is here:
>
>   https://dot.kde.org/2017/09/12/randa-roundup-part-ii
>
> And we have shared it via social media in these places:
>
>   https://twitter.com/kdecommunity/status/907558044153860096
>
>   https://www.facebook.com/kde/posts/10155177490873918
>
>   https://plus.google.com/b/105126786256705328374/+KdeOrg/
> posts/8aFWD9zyKqC
>
>   https://www.reddit.com/r/linux/comments/6zm9n0/
> stuff_going_on_during_kdes_randa2017_development/?ref=
> share_source=link
>
>   https://www.reddit.com/r/kde/comments/6zm9ei/
> stuff_going_on_during_kdes_randa2017_development/?ref=
> share_source=link
>
>   https://mastodon.technology/@kde/3499989
>
> Can you guys help us with this?
>
> Paul
>
>

Re: Spreading Randa stories

[Andy B]

Done!


On September 5, 2017 at 7:55:49 AM, Scarlett Clark (
scarlett.gately.cl...@gmail.com) wrote:

Done.

On Sun, Sep 3, 2017 at 3:24 PM, elcaseti .  wrote:

> Done.
>
> On Sat, Sep 2, 2017 at 1:11 AM, Paul Brown  wrote:
>
>> Good morning,
>>
>> As we are desperately trying to give a push to the Randa funding
>> campaign, I
>> was wondering if you could give me hand with a story on the subject by
>> posting
>> the news to Facebook groups, G+ communities, re-tweeting and re-tooting
>> it,
>> drawing other communities attention to it, and so on.
>>
>> The story is here:
>>
>>   https://dot.kde.org/2017/09/02/randa-roundup-part-i
>>
>> And I have shared it via social media in these places:
>>
>>   https://twitter.com/kdecommunity/status/903884412684836864
>>
>>   https://www.facebook.com/kde/posts/10155151318078918
>>
>>   https://plus.google.com/b/105126786256705328374/+KdeOrg/post
>> s/E6iaaMMzKxd
>>
>>   https://www.reddit.com/r/kde/comments/6xki2h/
>> more_stuff_developers_will_be_working_on_during/?st=j730jx2c=9f2efc5b
>>
>>   https://mastodon.technology/@kde/3334391
>>
>> Can you guys help me with this?
>>
>> Paul
>> --
>> Promotion & Communication
>>
>> www: http://kde.org
>> Mastodon: https://mastodon.technology/@kde
>> Facebook: https://www.facebook.com/kde/
>> Twitter: https://twitter.com/kdecommunity
>>
>>
>