Re: KDE now has its own Matrix infrastructure

[Scott Harvey]

Okay, I can see the point made by Laszlo and Helio. I retract my request
after further consideration.

I'm a part of the community, as is this discussion, and so I suppose it
should stay on the community mailing list.

Apologies for intervening... please continue.

-Scott

On Tue, Feb 26, 2019 at 8:49 AM Laszlo Papp  wrote:

> Hi Scott,
>
> I can see your point, so not trying to challenge it.
>
> I just feel that open means open, not open like in facebook context. In a
> completely open environment, it is not just the success and easiness that
> becomes available, but some respectful and fair arguments, difficulties,
> etc, that need addressing.
>
> I feel that KDE as a community will eventually benefit from feedback and
> discussions like this if the community takes proper actions going forward.
>
> Best regards,
> Laszlo Papp
>
> On Tue, Feb 26, 2019 at 2:31 PM Scott Harvey  wrote:
>
>> Jonathan, et al -
>>
>> Can I respectfully ask that this debate/dispute be moved elsewhere?
>>
>> I've been on hiatus from my role as a minor KDE contibutor for a few
>> months. It's not encouraging to resume paying attention only to find
>> another argument in progress.
>>
>> I suppose it could be argued that this maillist is intended for community
>> discussion and that this is indeed a community issue... I just don't feel
>> it's good for morale (mine, at least).
>>
>>
>> -Scott (sharvey)
>>
>> On Tue, Feb 26, 2019 at 7:34 AM, Jonathan Riddell 
>> wrote:
>>
>> The workboard item is https://phabricator.kde.org/T10477 , it wasn't
>> tagged KDE promo, it wasn't sent to the dot-editors list and I wasn't
>> pinged (I'm the only active volunteer Dot editor). I've tried to discuss
>> problems in promo with the e.V. board and CWG in the past when long term
>> contributors have left, when the team was changed from a community team to
>> a closed access team, when our mailing lists were micro managed or when I
>> was insulted for organising a conference stall but I've only been dismissed
>> or ignored and the community at large seems happy for that to happen so I
>> can't offer any assurances of changes. Jonathan On Tue, 26 Feb 2019 at
>> 11:46, Christian Loosli  wrote:
>>
>> Hi Jonathan, thanks for the wrap-up. I am less interested in pointing
>> blame, and more interested in - how this could have happened - what our
>> learnings are so this doesn't happen again in the future? It still is
>> unclear to me how non-true accusations without further explanation made it
>> into the article. Even for people who are not familiar with the subject,
>> this imho should never happen. If you are not sure, you don't throw around
>> accusations of things being insecure. It bothers me even more that there is
>> a lengthy discussion on the subject (and a follow up survey and result)
>> available to the people who participated in this, the article looked to me
>> like this discussion, survey and result (that we did put a lot of time and
>> effort in) were ignored. From what I gathered it even was given to the
>> right people to proof-read, but the article was released without waiting
>> for a reply. How can that happen, and why was it so urgent to push that
>> article out? So to avoid this in the future, I'd like to see us following a
>> process that does involved proof-reading by people familiar with the
>> subject, so we look as professional as we as KDE should be by now, and
>> usually are. As a last but not least, I'm also not terribly happy when
>> people involved were also the ones still, in public, making statements
>> against one of the technologies we decided to use and support, stating we
>> should abandon them. Together with the flawed article this doesn't look
>> good. I'd love to see people at least try to not let their personal views
>> bias them too much, especially not when a group decision was made. I have
>> my personal views and preferences on this too, but I try my best to accept
>> the decision taken and support it. Thanks and kind regards, Christian
>>
>>

Re: KDE now has its own Matrix infrastructure

[Scott Harvey]

Jonathan, et al -

Can I respectfully ask that this debate/dispute be moved elsewhere?

I've been on hiatus from my role as a minor KDE contibutor for a few 
months. It's not encouraging to resume paying attention only to find 
another argument in progress.


I suppose it could be argued that this maillist is intended for 
community discussion and that this is indeed a community issue... I 
just don't feel it's good for morale (mine, at least).



-Scott (sharvey)

On Tue, Feb 26, 2019 at 7:34 AM, Jonathan Riddell  
wrote:
The workboard item is  ,  it 
wasn't

tagged KDE promo, it wasn't sent to the dot-editors list and I wasn't
pinged (I'm the only active volunteer Dot editor).

I've tried to discuss problems in promo with the e.V. board and CWG in
the past when long term contributors have left, when the team was
changed from a community team to a closed access team, when our
mailing lists were micro managed or when I was insulted for organising
a conference stall but I've only been dismissed or ignored and the
community at large seems happy for that to happen so I can't offer any
assurances of changes.

Jonathan

On Tue, 26 Feb 2019 at 11:46, Christian Loosli > wrote:


 Hi Jonathan,

 thanks for the wrap-up.
 I am less interested in pointing blame, and more interested in

 - how this could have happened
 - what our learnings are so this doesn't happen again in the future?

 It still is unclear to me how non-true accusations without further 
explanation
 made it into the article. Even for people who are not familiar with 
the
 subject, this imho should never happen. If you are not sure, you 
don't throw

 around accusations of things being insecure.
 It bothers me even more that there is a lengthy discussion on the 
subject (and
 a follow up survey and result) available to the people who 
participated in
 this, the article looked to me like this discussion, survey and 
result (that

 we did put a lot of time and effort in) were ignored.

 From what I gathered it even was given to the right people to 
proof-read, but
 the article was released without waiting for a reply. How can that 
happen, and

 why was it so urgent to push that article out?

 So to avoid this in the future, I'd like to see us following a 
process that
 does involved proof-reading by people familiar with the subject, so 
we look as

 professional as we as KDE should be by now, and usually are.

 As a last but not least, I'm also not terribly happy when people 
involved were

 also the ones still, in public, making statements against one of the
 technologies we decided to use and support, stating we should 
abandon them.

 Together with the flawed article this doesn't look good.
 I'd love to see people at least try to not let their personal views 
bias them
 too much, especially not when a group decision was made. I have my 
personal
 views and preferences on this too, but I try my best to accept the 
decision

 taken and support it.

 Thanks and kind regards,

 Christian

Re: Closing NEEDSINFO bugs after 30 days

[Scott Harvey]

Can Bugzilla be configured to add boilerplate to the email that goes out 
with a NEEDSINFO that reads "This bug report will be closed after 30 
days unless blah blah blah"?

Re: Help us with curating store.kde.org

[Scott Harvey]

Hey Nicolas!

Although I haven’t (yet) committed to helping out on this project, I’m still 
offering my opinions.

Personally, I wouldn’t like to see the store curators judging the submissions 
on quality. Our personal tastes might influence our decisions. It would be like 
an art museum curator not displaying a work because he doesn’t think anyone 
would like it.

I think the curators should focus on keeping the store clean of things that 
_don’t work_, look out for obvious copies of other people’s code, etc.

If someone puts up something that’s “stupid” or worthless, it’ll get voted down 
by other users. My own two Plasmoids are hovering at exactly 2.5 stars each. 
Maybe they’re not so useful after all. :D

-Scott (sharvey)
On Jul 19, 2018, 1:14 PM -0500, Nicolas Fella , wrote:
> Hi,
>
> I'd like to offer my help as well :)
>
> Specifically I'd like to ensure that only content of decent quality and
> of actual worth to the user are available in the store, e.g. by
> suggesting/requesting changes to the author.
>
> Cheers
>
> Nicolas
>
>
> On 16.07.2018 11:39, Dan Leinir Turthra Jensen wrote:
> > Hello chums :)
> >
> > One of the challenges of having a library of resources is to maintain it
> > clean of spam and in general any content that doesn't comply with what we 
> > want
> > to have there.
> >
> > The software running store.kde.org recently gained the possibility to have a
> > group of people who can moderate contents and reviews.
> >
> > This is a call for action for those of you would like to contribute to KDE
> > by helping to make sure our users have the best resources selection 
> > available,
> > free of worry to find undesired contents.
> >
> > Please reply if you'd like to help, either with the store as a whole, or
> > even just a specific category, and we will see together what's the best way 
> > to
> > proceed.
> >
> > Thank you! :D
> >
>

Re: Help us with curating store.kde.org

[Scott Harvey]

Will it be possible to curate-separate things that are not compatible 
with Plasma 5? There's a lot of ancient stuff out there that's 10 years 
old and really shouldn't show up as available in the KNewStuff offerings 
for Plasma 5.13. Icon sets are the most visible example.


On 07/16/2018 11:17 AM, Dan Leinir Turthra Jensen wrote:

On Monday, 16 July 2018 17:01:59 BST Nate Graham wrote:

I would like to be a moderator!

   Hi Nathan, and thanks for stepping up! :D Do you have an opendesktop.org
account, and in that case could you send me the ID, so we can get you set up
with the right rights? :)


It might be a good idea to post this
publicly somewhere too; I've encountered a number of KDE users who have
asked how they can help clean up store.kde.org content.

   Not a bad idea at all, there! :) I'm pondering on doing a blog post on the
topic, so i might just go ahead and do that ;)


We could even make
this a new entry point on https://community.kde.org/Get_Involved.

   Ooh... Yes, perhaps that first, then blog post pointing to it :)


Nate


   On Mon, 16 Jul 2018 02:39:25 -0700 Dan Leinir Turthra Jensen
 wrote 
  > Hello chums :)
  >
  >   One of the challenges of having a library of resources is to maintain
  >   it
  >
  > clean of spam and in general any content that doesn't comply with what we
  > want to have there.
  >
  >   The software running store.kde.org recently gained the possibility to
  >   have a >
  > group of people who can moderate contents and reviews.
  >
  >   This is a call for action for those of you would like to contribute to
  >   KDE
  >
  > by helping to make sure our users have the best resources selection
  > available, free of worry to find undesired contents.
  >
  >   Please reply if you'd like to help, either with the store as a whole,
  >   or
  >
  > even just a specific category, and we will see together what's the best
  > way to proceed.
  >
  >   Thank you! :D
  >
  > --
  > ..dan / leinir..
  > http://leinir.dk/

Re: Anyone going to OSCON?

[Scott Harvey]

I’d love to attend (O’Reilly books are still my publication of choice), but 
it’s a bit pricey for a mere mortal. Plus the NSA is one of the sponsors.

But at least it’s on my continent!

-sharvey
On Jun 28, 2018, 4:11 PM -0500, Scarlett Clark , wrote:
> When is it? I need to pick up some stuff in Oregon, if timing is right...
> Scarlett
>
>
> > On Thu, Jun 28, 2018 at 1:42 PM Paul Brown  wrote:
> > > On jueves, 28 de junio de 2018 22:16:41 (CEST) Lydia Pintscher wrote:
> > > > Hey folks :)
> > > >
> > > > Is anyone going to OSCON? We have the opportunity to take part in
> > > > OSI's 20th birthday celebrations there. If someone is going anyway
> > > > it'd be good to take up this offer. Let me know if you're going and we
> > > > can talk details.
> > >
> > > Shall we include it in the "External Events" task, Lydia?
> > >
> > > >
> > > >
> > > > Cheers
> > > > Lydia
> > >
> > >
> > > --
> > > Promotion & Communication
> > >
> > > www: http://kde.org
> > > Mastodon: https://mastodon.technology/@kde
> > > Facebook: https://www.facebook.com/kde/
> > > Twitter: https://twitter.com/kdecommunity
> > >

Re: Neon Pinebook Remix as part of KDE

[Scott Harvey]

On 04/17/2018 08:27 AM, Jonathan Riddell wrote:

Seems nobody is too fussed about this and since KDE already has done
this for some years I'll release it

Jonathan


I can't speak for the legalities, but it seems like a project that's too 
intriguing to let slip away. I'd buy one, just for my own entertainment. 
And probably a second one for my parents. As long as they can get on the 
web and my dad can play KMahjongg... anything to save me from being 
Win10 tech support.


It's not as glamorous or powerful as the Slimbook, but it doesn't need 
to be. It's an inexpensive way to spread the good word.

Janitor container dev environment

[Scott Harvey]

On 03/19/2018 08:33 AM, Adriaan de Groot wrote:
So in first instance, I'll be aiming for an up-to-date (-ish) Plasma 
desktop with dev tools installed ready to work on KMyMoney and Okular 
(an arbitrary selection).


I got my invitation to the Janitor Alpha yesterday. Had a look around. 
It's definitely an interesting idea. I successfully compiled and 
installed Okular in my container (albeit without Breeze icons; it's a 
work in progress).


I could see the appeal for people who just want to hack on something to 
see how it works. It's a nice sandbox environment. It's definitely an 
easy way to give someone their first taste of exploring KDE source code 
and compiling one of the applications. And it's almost certainly tidier 
than my virtual machine instance currently named "Neon Dev Ultra Unstable".


It's an alpha-within-an-alpha, but there might be something here worth 
pursuing. Plenty of work still ahead, but good job to Adriaan and 
Raphael for getting it updated and workable.


-Scott _sharvey_


ps: we can also use the VNC connection option to demonstrate lynx, 
something I bet most new contributors can't even wrap their minds around.

Re: KDE goals IRC office hour

[Scott Harvey]

Whether it’s Docker or this new Janitor thingy, we’re going to want decent 
documentation on how to use it. I’m a newly-minted newcomer and find the whole 
“container” concept confusing and complicated. (Is that enough ‘C’s for one 
message?)

-sharvey

On Mar 16, 2018, 5:30 AM -0500, Adriaan de Groot , wrote:
> On Friday, 16 March 2018 09:20:26 CET, Ilmari Lauhakangas wrote:
> > KDE
> >
> > Efforts:
> > None
> > WANTED: Maintaining KDE development environment image
> > WANTED: Hosting Janitor containers for KDE
> > Benefits:
> > Development environments for KDE (hosted by IRILL)
> >
> > It seems the ball was dropped regarding this. Why? Should be a
> > perfect fit for the onboarding goal, no?
>
>
> I think there was also:
>
> Efforts:
> Missing: telling KDE that this thing exists
>
> Maybe that's a bit snarky, but I can't find any previous mention of janitor
> on any KDE mailing lists. Is it possible that they set this up and then
> forgot to inform anyone? Maybe just the Mozilla tools list? I'm happy *you*
> know about it, and now think "this should be updated, and quick". There
> doesn't seem to be any way to quickly log in -- seems it's still in the
> alpha-invite-only phase.
>
> [ade]
>

Re: Mock-up of revised KDE Store

[Scott Harvey]

Ok, I did a morning's worth of revisions and adding of new products, based
on today's feedback. As for...

*Adriaan*: I added a small Applications section with a few app icons. I
personally think Konversation looks good on a mug.
*Andy*: With the background white, all the elements floated in space.
Instead, I ran the wallpaper through a softening filter and now the
background is a gentle blend of pastel colors, but the header image is
still nice and crisp. I think it'll be up to the VDG folks to make the
final call. I'm just making suggestions.

There's one item I added under Miscellaneous that isn't politically
correct, but I think it's funny and it's also a fact of KDE life. It's the
Dr. Konqi "sad face" in big block pixels.

I'm going to contact the VDG folks now and send them the link.

-Scott

On Thu, Mar 1, 2018 at 9:03 AM, Andy B  wrote:

> 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: Mock-up of revised KDE Store

[Scott Harvey]

On Thu, Mar 1, 2018 at 7:54 AM, Adriaan de Groot  wrote:

>   - Gosh, it looks all very square and blocky. I think that's because of
> the
> square-and-sharp-cornered K-logo.
>

I can use the variants of the K-logo without the background, too. That
might improve the overall "square" feeling of the shop. I can also tinker
with the CSS to perhaps add a radius to some of the corners and soften up
the appearance.


>  - It'd be nice if the wallpaper behind the "KDE Store" label somehow
> matched
> the wallpaper background of the whole page.
>

That can be done. I was just throwing things together with what resources I
had at hand. I'll give it a bump with a matching background.


>  - Perhaps a category "Applications" would work, too, to make some space
> for,
> say, sporting a Falkon t-shirt or drinking from a KWin mug (if KWin has a
> logo).
>

KWin does have a logo, of sorts. I found the attached image hiding in the
Git repository. Mind you, I've never seen it displayed anywhere, and it's
not all that fascinating, but it proves there's always an option. I'll get
the Falkon logo and render it out. I'll also look through the Breeze icons
and see which ones jump out. The orange-black-cyan "desktop" icon is great,
in my opinion. It's instantly recognizable as part of Plasma.

I should also add the Neon logo. It's pretty spiffy and colorful. I
personally like the "black disc" image for the Developer edition. I set it
as my App Launcher icon.  :-)

Speaking of Plasma, does anyone know if the Plasma logo (dots-and-pointer)
officially has colored dots? I've seen both here and there.

I've yet to reach out to the Visual Design Group for input. Imagery is
their domain, and I'm not a member. I'm just a bit handy with design tools
and know how to configure a Cafe Press store.

As for how to distinguish this from the downloads "store", I would be so
bold as to suggest a link for "Merchandise" on the header of kde.org,
perhaps just before "Donate". And also something on the lower section of
the "Products" page, again labeled "Merchandise".

Thanks for the feedback, [ade]. I'll do some updating today, then I'm off
for a journey to your region of the world, a vacation to Denmark and
Sweden. Hello in advance to any KDE'ers in Copenhagen and Stockholm!


-Scott (became _sharvey_ on IRC and is sharvey on Phab and related places)


​

Re: Proposal for a poll to users about bug triaging

[Scott Harvey]

As the former manager of an IT help desk (back in the olden days), my input
on some of this. I'm only a junior developer who's offered up a few minor
patches thus far and have done a bit of bug triaging.

We need to back up and remember the definition of the word triage:

(in medical use) the assignment of degrees of urgency to wounds or
> illnesses to decide the order of treatment of a large number of patients or
> casualties.
>

The former help desk manager in me says that's the key and that's what's
not happening - severity sorting. An ordinary user will be able to help
tell you if a bug can be reproduced, but it'll take someone more
experienced to set the priority. Twenty years ago, I was sorting help desk
tickets for Novell Groupwise and Windows 95. My staff of techs needed to be
told what takes priority. As in, if the company preident's secretary can't
access her email, head to the 6th floor immediately. That person with the
sticky spacebar can tough it out a bit longer.

Those of you who are high-level developers or maintainers are still going
to need to do this. An ordinary user who's "triaging" bugs can only tell
you if they can reproduce a specific problem. It's going to be up to the
gurus to shuffle things by priority. Someone like me, who's maybe more
experienced than some - at age 48 - can help out a bit and retry a problem
scenario, but I don't have the familiarity with the code, the frameworks,
not even C++, to tell you what's top priority and what's not. Sure, if
duplicating a bug brings down my whole system like the bug report says, I'm
going to get someone's attention. But in between that and a minor
annoyance... I can't decide that.

-Scott, graybeard wannabe junior developer

On Wed, Feb 28, 2018 at 7:54 AM, Ilmari Lauhakangas <
ilmari.lauhakan...@libreoffice.org> wrote:

> I would argue this is not the most important thing, at least not before
> recruiting a proper QA team for your application. It does help with
> noticing duplicate reports, but it is quite work-intensive. In LibreOffice
> we currently have 657 meta reports to categorise everything. Yet, we also
> have 20-30 active QA persons shuffling things around.
>
> Assigning correct components can very well be done gradually by
> increasingly educated and experienced non-developer QA contributors.
>
> Having a lot of components makes it obvious that the Bugzilla interface
> needs some tweaking, at least Advanced search. The component selection
> field in there feels cramped and its width does not even resize to show the
> longer component names.
>
> Red Hat has customised their BZ and added sub-components (so you have
> Product -> Component -> Sub-component). Their code is not yet public.
>
> I think when wanting to have a fine-grained categorisation, it would be
> better to have only a handful of components and then a lot of *optional*
> sub-components. Bug reporters not knowing what to pick could skip the
> sub-component step.
>
> I do not advise KDE to copy the LibreOffice model of meta reports. Meta
> reports don't live in the bug creation/search interface and are thus
> difficult to discover.
>
> Ilmari
>
> On 28.02.2018 13:49, Gilles Caulier wrote:
>
>> Hi,
>>
>> Instead to start to talk with users about bugzilla, I recommend to
>> separate well the project with bugzilla sub-components.
>>
>> In digiKam, i pass a lots of time to create sub-sections. This is the
>> most important task to do before triaging.
>>
>> Remember that users are not developers. Some sections can be relevant of
>> some technical info from source code, so the developers must prepare the
>> sections before to delegate triaging to users. If users process a wrong
>> re-routage, this will be complex later to maintain a project.
>>
>> See the sections created in bugzilla about digiKam project for example :
>>
>> https://bugs.kde.org/editcomponents.cgi?product=digikam&showbugcounts=1
>>
>> Best
>>
>> Gilles Caulier
>>
>> 2018-02-28 12:35 GMT+01:00 Ilmari Lauhakangas <
>> ilmari.lauhakan...@libreoffice.org > reoffice.org>>:
>>
>> I am personally convinced that users do not know bug triaging is a
>> thing and certainly not how much they could help developers by doing
>> it. It would be very useful to test this by running a poll on
>> https://blogs.kde.org/ or somewhere.
>>
>> Questions could be something along the lines of
>> "Did you know you can help KDE by analysing bug reports?"
>> "Did you know you can analyse most bug reports with regular user
>> skills?"
>>
>> Ilmari
>>
>>
>>

Re: Let's get rid of UNCONFIRMED/CONFIRMED

[Scott Harvey]

As a newcomer, I didn't realize I was allowed to change UNCO to CONF and
did so only when absolutely positive the issue existed. But I've already
seen issues like a user who continually reports bugs (often enough that I
recognize the name from among thousands).

When I triage something and find it confirmed, I try to report all the
details of my system and the methods I used to recreate the problem.

Maybe all we need is a little more education and advice for users. Maybe a
popup when changing UNCO to CONF that reads "By doing this, you're going to
alert the very busy development team that you've confirmed a bug in
. Are you positive you want to do this? Please think it through
before continuing."

Or nicer words to the same effect.


On Tue, Feb 27, 2018 at 6:43 AM, Boudewijn Rempt  wrote:

> On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
>
> > Is it true that users get confused by the bugtracking system? If so,
> this is
> > an issue, right?
>
> Well, users can get confused by _everything_. Though I probably have more
> absolutely non-technical users reporting bugs than most other KDE
> projects. I
> haven't seen many signs of users being confused by UNCONFIRMED vs
> CONFIRMED,
> though.
>
> I'm all for making the initial reporting of bugs as smooth as possible for
> users... Though really, I don't need any more bug reports. And after that,
> giving me more information when I ask for it, that would be useful as well.
>
> * It would be useful if users could embed images and videos instead of
> creating attachments.
> * It would be useful if users could use rich text in their reports.
> * It would be useful if users could sign in with their cloud identities
> (horrible though that idea is).
> * It would be useful if bugzilla and the forum used the same login.
> * It would even be useful if we could add badges or something like that to
> tell the reporter "thank you for your report" with a nice graphic
>
> But messing with the statuses that basically define the workflow for the
> developer because we think that users will feel happier seeing NEW than
> UNCONFIRMED doesn't sound too useful to me.
>
> If we want to change that, let's change it in a way that will support
> people
> triaging a thousand bugs or so a year.
>
> --
> Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
>
>
>

Re: new KDE e.V. office

[Scott Harvey]

When and if I get the chance to visit Berlin, can I stop in and say hello? :-) 
Because yes, I would put the KDE e.V. headquarters on my sightseeing list! (My 
wife thinks I’m crazy.)

On Feb 19, 2018, 4:17 PM -0600, Lydia Pintscher , wrote:
> Hey folks :)
>
> KDE e.V. has been looking for a new office over the past weeks. Petra
> has been doing a lot of work scouting suitable locations and found a
> very nice place for us. Last Thursday we moved in.
>
> The new office is in the Aufbau Haus in Berlin. The new address is:
> KDE e.V.
> Prinzenstraße 85 F
> 10969 Berlin
>
> We will do a small house-warming party as part of the next board
> meeting on the weekend of April 28th.
>
>
> Cheers
> Lydia
>
> PS: if you see the old address anywhere please add the place to
> https://phabricator.kde.org/T7931 so we can update them all.
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors
> http://kde.org - http://open-advice.org

Re: Mock-up of revised KDE Store / KDE Cafe Press store / Organic cotton

[Scott Harvey]

They have an organic option, at least. I will try to find out about any
certifications. I added the Home Folder design as an organic variation -
it's significantly more expensive.

https://www.cafepress.com/bdtokde/15230068

The problem with sites like those on the Ohio Fair Trade site is that
they're bulk-order for someone to resell. Cafe Press is no-inventory,
print-on-demand. I'm willing to keep the shop updated, but I don't have the
room in my house to warehouse KDE merchandise. :-)

I'll do some more research and see what I can dig up. I like the sentiment,
I just hope we can make it practical.


-Scott

On Sat, Feb 17, 2018 at 7:43 AM, gregor.mi.sw  wrote:

> Hello Scott,
>
> thanks to your post to the kde-promo list I got reminded that we have KDE
> promotional T-Shirts. I like this shirt, for example:
> https://www.cafepress.com/bdtokde.224580619
>
> However, I could not easily find out if the shirt is organic and
> sweatshop-free or not. The description does not mention it, therefore I
> assume it is at least not organic, right?
>
> It would be nice if we could also offer our KDE t-shirts in an organic
> (with GOTS certification) and fair trade variant (see e.g.
> http://ohiofairtrade.com/shop-fair-trade/fair-trade-apparel/)? If we not
> already do it somewhere I did not find it yet I am willing to help to make
> it possible.
>
> Gregor
>
>

Mock-up of revised KDE Store

[Scott Harvey]

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)

Re: Volunteering to update the KDE Cafe Press Meta-Store

[Scott Harvey]

One regrettable fact about using Cafe Press is that they’re not cheap. But I 
did research last summer when I was trying to sell some novelty t-shirts 
(sales: zero, let’s speak of it no more). CP’s prices are high, but they’re 
probably also the highest quality on the market. The truth is that none of the 
print-on-demand services are cheap. That’s the trade-off for not having to 
order in bulk and resell things yourself.

They might have a price break for a non-profit organization like KDE. I’ll 
check into it.

I should have the mock-up store ready to share later today.

-Scott


> By the way, note what we need is to make sure that the KDE merchandise
> is available and affordable, whether it's in cafepress or anywhere is
> probably anecdotal.

Re: Volunteering to update the KDE Cafe Press Meta-Store

[Scott Harvey]

I've got a Cafe Press shopkeeper account of my own. I might toss together a
quick prototype store (hidden, private) just for feedback and idea-sharing.
Once we get some consensus on what kinds of products we'd like, we can
contact the Visual Design gurus and let them tear it apart. But at least
we'll have something that's more substantial than just a good idea.

I'm reasonably competent at graphic design - I speak fluent Adobe
Illustrator (although I should learn Inkscape as well). Maybe the graphics
guys would trust me to pitch in with them as well. The shop needs
custom-sized logos and header graphics. If they're too busy to make
something grand for the little store, I could certainly make something
presentable.

Meanwhile, I think my Kubuntu machine needs a swift kick to get running
again (I work by remote), so it's off to the basement for a power-cycle.


-Scott

On Thu, Feb 15, 2018 at 5:10 AM, Adriaan de Groot  wrote:

8<--- snip --- <8


> CafePress can do all of those, and slapping the KDE logo on everything is
> quite straightforward. Medium-term, we should do better than that. We have
> some t-shirt designs kicking around, like the Akademy T-shirts we do each
> year, and the KDE India shirt is a perennial popular item.  So working
> towards
> more designs, or more item-suitable designs, is something that can be done.
>
> Well, *I* think it's a worthwhile goal.
>
> Heck, just a decent clear-hard-plastic KDE coffee mug could be a nice
> thing to
> have (as an environmental statement?) at an event. We had them at some
> Akademy
> (Mechelen?), years ago, lasted for years.
>
> [ade]

Volunteering to update the KDE Cafe Press Meta-Store

[Scott Harvey]

Hi KDE'ers!

I sent a similar message to the Community Working Group a few days ago, but
I think that might have been a little too high-level.

Anyway, I'm a newcomer to the KDE community, but I'm a believer. Having
chatted on IRC about plasmoid programming issues with the actual Plasma
maintainers is "community" like I haven't seen before.

I'm probably too old to contribute new C++ code to any of the major
projects, so I thought I'd volunteer to do something I know I can do:
create and update a Cafe Press store. I've done several, for groups of
people taking a cruise together, for my own meager design work, etc. I'm
pretty familiar with how the site works.

As it stands now, the KDE store is a little sparse. We need to have the
blue K-Gear and Plasma icon available on everything from mousepads to
t-shirts to stickers for our laptops. I'm willing to put in the time to get
those products set up on Cafe Press. Plus, whatever markup is charged can
go back to the KDE mothership as a simple form of fundraising.

What do you think? Is this a worthwhile goal? I don't work, so I've got the
time. Heck, I'd probably buy a coffee mug for myself.

-Scott Harvey
 Chicago