Re: Proposal unify back our release schedules
Hello Carl, Promotion-wise it makes sense. We always have difficulty explaining and, hence, making the general public feel excited about the new versions of Plasma, as the concept of "desktop environment" is a concept that escapes (and bores) most people. But promoting a bunch of new apps, and a new set of configuration tools, and a new wallpaper and widgets is a much easier thing to do. Also new versions of things like Dolphin and Spectacle, which are closely associated with Plasma, are released with Gear, while System Monitor and Discover are released with Plasma. This makes zero sense to outsiders. Tl;DR: Sounds good to me. Cheers 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
Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos
Dear All,
Sorry for being a pain in the neck about this, but the more I read the plan to
migrate, the less it seems a plan at all. It just boils down to a deadline.
There is no contingency, nobody has considered what the people who use
Telegram to interact with us want, nobody has opened any kind of brainstorming
so we may come up with a way of nudging instead of forcing users to migrate.
Yes, we all want everybody to use FLOSS, but while some parts of the community
can avoid proprietary software and platforms completely, we ("we" being the
people carrying out promotional and outreachy tasks) can't.
Our main mission is to grow KDE's user base. This means we have to go where we
can find new users and communities we can grow into. That is why we still have
Facebook, Xitter, Reddit and Telegram.
When communities organically take hold on these platforms and start to grow,
we cannot afford to cut them off just because we don't like where they are
growing. Do that often enough and KDE and all its software becomes irrelevant
and loses what tiny portion of the market share it currently has.
Getting back to the topic at hand, there will be channels we will be able to
migrate in the time frame proposed (the Promo channel on Telegram itself can
probably be closed down within days, as can Atelier 3D Printing), there are
channels which will take much longer and need a much more tactful approach
(and I suggest we include "brainstorm ways we can facilitate the migration"
into the plans TODOs).
And then there are channels which we will never be able to migrate.
We will actively support Sysadmin in the task of migrating as many channels as
we can in the given time frame; but I believe it is only reasonable to expect
that we get some degree of support from others for our task of growing and
maintaining KDE's user base where we find it.
If that means coming up with a solution to the bridge problem, well, solving
technical problems to provide for users is KDE's thing, right?
We can figure it out.
Cheers
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
Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos
Dear All,
Sorry for being a pain in the neck about this, but the more I read the plan to
migrate, the less it seems a plan at all. It just boils down to a deadline.
There is no contingency, nobody has considered what the people who use
Telegram to interact with us want, nobody has opened any kind of brainstorming
so we may come up with a way of nudging instead of forcing users to migrate.
Yes, we all want everybody to use FLOSS, but while some parts of the community
can avoid proprietary software and platforms completely, we ("we" being the
people carrying out promotional and outreachy tasks) can't.
Our main mission is to grow KDE's user base. This means we have to go where we
can find new users and communities we can grow into. That is why we still have
Facebook, Xitter, Reddit and Telegram.
When communities organically take hold on these platforms and start to grow,
we cannot afford to cut them off just because we don't like where they are
growing. Do that often enough and KDE and all its software becomes irrelevant
and loses what tiny portion of the market share it currently has.
Getting back to the topic at hand, there will be channels we will be able to
migrate in the time frame proposed (the Promo channel on Telegram itself can
probably be closed down within days, as can Atelier 3D Printing), there are
channels which will take much longer and need a much more tactful approach
(and I suggest we include "brainstorm ways we can facilitate the migration"
into the plans TODOs).
And then there are channels which we will never be able to migrate.
We will actively support Sysadmin in the task of migrating as many channels as
we can in the given time frame; but I believe it is only reasonable to expect
that we get some degree of support from others for our task of growing and
maintaining KDE's user base where we find it.
If that means coming up with a solution to the bridge problem, well, solving
technical problems to provide for users is KDE's thing, right?
We can figure it out.
Cheers
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
Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos
Dear All,
Sorry for being a pain in the neck about this, but the more I read the plan to
migrate, the less it seems a plan at all. It just boils down to a deadline.
There is no contingency, nobody has considered what the people who use
Telegram to interact with us want, nobody has opened any kind of brainstorming
so we may come up with a way of nudging instead of forcing users to migrate.
Yes, we all want everybody to use FLOSS, but while some parts of the community
can avoid proprietary software and platforms completely, we ("we" being the
people carrying out promotional and outreachy tasks) can't.
Our main mission is to grow KDE's user base. This means we have to go where we
can find new users and communities we can grow into. That is why we still have
Facebook, Xitter, Reddit and Telegram.
When communities organically take hold on these platforms and start to grow,
we cannot afford to cut them off just because we don't like where they are
growing. Do that often enough and KDE and all its software becomes irrelevant
and loses what tiny portion of the market share it currently has.
Getting back to the topic at hand, there will be channels we will be able to
migrate in the time frame proposed (the Promo channel on Telegram itself can
probably be closed down within days, as can Atelier 3D Printing), there are
channels which will take much longer and need a much more tactful approach
(and I suggest we include "brainstorm ways we can facilitate the migration"
into the plans TODOs).
And then there are channels which we will never be able to migrate.
We will actively support Sysadmin in the task of migrating as many channels as
we can in the given time frame; but I believe it is only reasonable to expect
that we get some degree of support from others for our task of growing and
maintaining KDE's user base where we find it.
If that means coming up with a solution to the bridge problem, well, solving
technical problems to provide for users is KDE's thing, right?
We can figure it out.
Cheers
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
Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos
On Tuesday, 22 August 2023 22:08:34 CEST 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 It's not. Kdenlive is another example where most users on both the Spanish and English channels are largely on Telegram. I think you will find that developers tend to gravitate towards IRC and maybe Matrix, but end users gravitate towards Telegram and don't really want to open another account on yet another IM platform. But let me try to highlight some of the issues with this proposed plan (as is) with some questions: If we cut off hundreds of users from the rest of the community, will this action help or damage KDE's relevancy among end users? Will it increase or decrease the rate of adoption of our software? It has been mentioned that this was discussed at a BoF and on a mailing list. How many end users, say, from the KDE Connect and Kdenlive user channels on Telegram do you estimate attended the Bof and how many do you estimate regularly read the mailing lists? Is it right to make this decision behind the backs of the people who will be most affected? How does this plan fit in with KDE's vision, mission and manifesto, all three of which insist we take into account the users and their needs over most other things? As a reminder: https://community.kde.org/KDE/Vision https://community.kde.org/index.php?title=KDE/Mission https://manifesto.kde.org/ If you have a healthy growing community of end users, already in the hundreds, probably surpassing a thousand users, is it sensible to cut it off? Moving on to the schedule, do you think, we, the channel mods and admins, can realistically migrate hundreds of people to a completely new platform they probably even haven't heard of in less than a month? Do we get time to eat and sleep? Do you think cutting users off will be a convincing argument that will encourage most of the people to migrate? Have you thought of other strategies we can use that will render better results? If so, would you mind sharing them? How many of the links to Telegram peppered all through our web pages have you removed and changed to point to Matrix? If none (it is none, isn't it?), shouldn't have this been one of your first actions, to curb incoming new users away from Telegram to Matrix? Why did you not think of this? In view of your prior answers, do you think maybe this "plan" may not be much of a plan at all, that maybe it is simplistic, even harebrained, unrealistic and insensitive, and, if forced through, you may hurt the community in ways that will take years to repair? Cheers Paul > 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
Please help us collect material for the KDE Gear 23.08 announcement
Hello, We are putting together the information that will go into the KDE Gear 23.08 announcement here: https://phabricator.kde.org/T16761 We have some information, but there are still a lot of gaps. If you have news about your own project and would like to see them featured, please leave a comment in the task with a description of what changed. It would be helpful if you describe it in non-technical terms. A good way to do this is to describe how the change will benefit the end user. For example: "It makes X more performant", "This new feature allows the user to import files in format Y", "Now users can do K in app L", etc.. Links to the commit, animations or screencaps are also very useful. Note that bugfixes, although all-important, generally don't make for good announcement material unfortunately. Thank you for your help! Cheers 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
Re: Files on Collaborate
On Saturday, 28 August 2021 06:28:24 CEST Ben Cooksley wrote: > Hi all, > > This morning Sysadmin was informed by a member of the community that a > substantial number of files had been removed from the shared "Community > Notes" folder. Hi, I apologise. I'm pretty sure that was me. I use the Nextcloud desktop client most of the time and made the double mistake of moving (instead of copying) several files and folders (when I only wanted to copy one) using Dolphin. I must've distractedly selected a folder containing my _collaborate_ shared folder and then scrolled down so it was off screen, and then selected the file I really wanted to copy while holding down Ctrl . I have no idea what I was thinking. I thought I had caught it in time when I realised something was not right and before any major damage was done. I killed the process and stopped the synch and even erased the account from the client so it wouldn't try and resume synching when I restarted the client. But clearly I was not fast enough. Either way, I am deeply embarrassed and very sorry for the trouble I have caused and will be extra cautious from now on. Paul Brown -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity LinkedIn: https://www.linkedin.com/company/kde
Re: Migration to collaborate.kde.org
On Sunday, 8 August 2021 20:35:48 CEST Ben Cooksley wrote: > On Mon, Aug 9, 2021 at 4:15 AM Paul Brown wrote: > > Hi Ben, > > Hi Paul, > > > Another problem: 10 MBs is not enough for non-shared stuff. The stuff I > > had in > > my "personal" folder (nothing in it was really "personal", but more like > > travelling details, or presentations, etc.) far exceed that. > > > > If I remember right, we used to have 100 MBs for personal stuff. Can we > > have > > that space back? > > For quota increase requests, please file a Sysadmin ticket. Ok. > The original intended purpose of share.kde.org (and it's successor > collaborate.kde.org) is to store files for the wider community rather than > for people individually - hence the default quota limits. > (We have quite a bit more space available on collaborate vs. share, so that > isn't the problem) This is not a perk or a favour I am asking for. I was using that storage for work-related stuff. I was using it as instructed by the Board. I used that space for work files I needed replicated on my other devices, or needed to share with Board members, or my colleagues, but that were not to be available to the rest of Promo because they may have contained sensitive or personal information. And this is how my colleagues were using that space also. Making the space and the files contained within inaccessible negatively impacts our work. Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity LinkedIn: https://www.linkedin.com/company/kde
Re: Migration to collaborate.kde.org
On Sunday, 8 August 2021 20:38:56 CEST Ben Cooksley wrote: > On Sun, Aug 8, 2021 at 11:25 PM Paul Brown wrote: > > Hello Ben, > > Hi Paul, > > > I am missing a bunch of calendars and my personal calendar has been > > emptied of > > events and tasks. To be precise, I am missing > > > > * Attend External Events: List of events to attend (Aniqa Khokhar) > > * Promo > > > > calendars, and, as mentioned, my Personal calendar has lost most (not all) > > events and TODOs. > > > > As share is not up anymore, I don't know how to recover them. > > Calendars and any data other than files were not migrated over as part of > this move. > Please contact us on IRC and we'll temporarily re-enable share.kde.org to > allow you to export this data. > > (Note: this also applies to anyone else who used this functionality on > share.kde.org - it would be appreciated if you made contact sooner rather > than later however as we would like to archive the old instance) That is... not good. Thankfully I was able to replicate calendars because I had them synched with Kontact and recover my files because I had them synched to my local file system. I feel for the people who did not do that and who now have to jump through hoops to get their stuff back. Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity LinkedIn: https://www.linkedin.com/company/kde
Re: Migration to collaborate.kde.org
Hi Ben, Another problem: 10 MBs is not enough for non-shared stuff. The stuff I had in my "personal" folder (nothing in it was really "personal", but more like travelling details, or presentations, etc.) far exceed that. If I remember right, we used to have 100 MBs for personal stuff. Can we have that space back? Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity LinkedIn: https://www.linkedin.com/company/kde
Re: Migration to collaborate.kde.org
Hello Ben, I am missing a bunch of calendars and my personal calendar has been emptied of events and tasks. To be precise, I am missing * Attend External Events: List of events to attend (Aniqa Khokhar) * Promo calendars, and, as mentioned, my Personal calendar has lost most (not all) events and TODOs. As share is not up anymore, I don't know how to recover them. Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity LinkedIn: https://www.linkedin.com/company/kde
Re: GSoC org application time
On Thursday, 17 January 2019 08:24:37 CET Valorie Zimmerman wrote: > Hi all, I've started our application. > > The deadline for applications: February 6, 2019 at 12:00 (PST). > > By the deadline, we need to have an absolutely *splendid* Ideas page (1). > Before the deadline, I'll remove all the placeholders such as teams with no > Ideas listed, or ideas with no mentors listed. Teams which have > participated in the past but are empty still: KDE Partition > Manager, Kopete, Choqok, Peruse, KGpg, KWin, Plasma, WikiToLearn, KDevelop > and Xdg-desktop-portal-kde. > > So far, I'm the only admin listed. Anyone game to help administer this > year? It works well when we have a team, so that any of us can have an > off-week (or week off) sometimes. There are two aspects to being an org > admin: working with mentors, and working with students. "Paperwork" is a > very small part of the job. > > The mentor work is all about helping mentors and their teams work well with > their student. Some need coaching on communication, poking to do their > evaluations, etc. > > The student work in the beginning is coaching students in getting involved, > creating their devel environment, helping them craft their proposals and > get linked into the teams, and so forth. Later, it will be helping them > through the tough spots, especially when their mentors aren't being > helpful, or even helping withdraw gracefully. Hi Valorie, Apologies for asking what may be obvious to others, but what sort of technical knowledge does a mentor require to carry out the job effectively? Would posting something like this to the Dot help to get the word out do you think? How else can Promo help? Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity
Re: Upcoming change to mail infrastructure
On martes, 3 de julio de 2018 13:12:56 (CEST) Ben Cooksley wrote: > On Tue, Jul 3, 2018 at 11:11 PM, Paul Brown wrote: > > On martes, 3 de julio de 2018 12:59:49 (CEST) Ben Cooksley wrote: > >> On Tue, Jul 3, 2018 at 10:44 PM, Paul Brown wrote: > >> > On martes, 3 de julio de 2018 12:29:41 (CEST) Ben Cooksley wrote: > >> >> Hi all, > >> >> > >> >> We've recently completed configuration of a new mail server which will > >> >> be replacing the current system which handles kde.org mail. This > >> >> system will be assuming responsibility for mailing lists as well as > >> >> authenticated mail sending for those who require that service. > >> >> > >> >> To ensure a smooth transition however some changes may be needed on > >> >> your side, especially if you are using our authenticated mail sending > >> >> service. > >> >> > >> >> As part of the new system, we have configured updated filters which > >> >> will begin enforcing DMARC policies for domains which have specified > >> >> these, along with improved SPF verification. As a consequence, if you > >> >> are forwarding mail from another provider to your kde.org or > >> >> kdemail.net address, this may cease working following the transition. > >> >> We recommend you configure these services to instead forward directly > >> >> to your final mail provider should this impact on you. > >> >> > >> >> For those users of the authenticated mail service: please change your > >> >> mail client to use the server "letterbox.kde.org" instead of the > >> >> current server "postbox.kde.org". Additionally, if you are currently > >> >> using port 588 to send mail, this should now be changed to the > >> >> standard submission port, 587. > >> >> > >> >> As part of this setup we have also completely reworked our > >> >> SpamAssassin setup. As a consequence of this, we are now looking for > >> >> spam mail to begin training the filter to ensure it is ready to begin > >> >> filtering the substantial mail volumes Postbox handles. > >> >> > >> >> Mailing list moderators whose lists receive significant quantities of > >> >> spam are therefore requested to not discard this, and instead let us > >> >> know so we can use the spam from your moderation queue to train the > >> >> filter. Please note that we can grab the mail directly from the queue, > >> >> so forwarding it elsewhere is not required. > >> >> > >> >> Once the filter has been sufficiently trained, we will commence the > >> >> cutover and transfer handling of kde.org mail, including mailing > >> >> lists, to the new system. > >> >> > >> >> Should anyone have any questions regarding this process, please let us > >> >> know. > >> >> > >> >> Regards, > >> >> Ben Cooksley > >> >> KDE Sysadmin > >> > > >> > When do you plan to finalise the transition and flip the switch? > >> > >> Once the Bayes filter has been sufficiently trained, which may take a > >> few days depending on how much spam we collect. > >> I've no other clearer timeline than that at this stage i'm afraid. > > > > Sure. I ask so that, when you do, we know and can check things are working > > and we are not left sitting around oblivious and wondering why everybody > > has suddenly gone awfully quiet. > > > > To avoid this I suppose that, when you do know the exact time and date, > > you > > will make it public, right? > > Yes, there will be a notification made when the changeover is done, If you send a notification via email (how else?) and people on the other side are not receiving email because something went wrong, how are they going to know? Wouldn't it be better to send a message out, say, a couple of hours *BEFORE* you change over and then flip the switch? Then users can test sending and receiving when the time comes. Paul > and Letterbox (the new system) will be monitored extensively for the > first hour or so to ensure everything is working as expected. > > Cheers, > Ben > > > Cheers > > > > Paul > > -- > > Promotion & Communication > > > > www: http://kde.org > > Mastodon: https://mastodon.technology/@kde > > Facebook: https://www.facebook.com/kde/ > > Twitter: https://twitter.com/kdecommunity -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity signature.asc Description: This is a digitally signed message part.
Re: Upcoming change to mail infrastructure
On martes, 3 de julio de 2018 12:59:49 (CEST) Ben Cooksley wrote: > On Tue, Jul 3, 2018 at 10:44 PM, Paul Brown wrote: > > On martes, 3 de julio de 2018 12:29:41 (CEST) Ben Cooksley wrote: > >> Hi all, > >> > >> We've recently completed configuration of a new mail server which will > >> be replacing the current system which handles kde.org mail. This > >> system will be assuming responsibility for mailing lists as well as > >> authenticated mail sending for those who require that service. > >> > >> To ensure a smooth transition however some changes may be needed on > >> your side, especially if you are using our authenticated mail sending > >> service. > >> > >> As part of the new system, we have configured updated filters which > >> will begin enforcing DMARC policies for domains which have specified > >> these, along with improved SPF verification. As a consequence, if you > >> are forwarding mail from another provider to your kde.org or > >> kdemail.net address, this may cease working following the transition. > >> We recommend you configure these services to instead forward directly > >> to your final mail provider should this impact on you. > >> > >> For those users of the authenticated mail service: please change your > >> mail client to use the server "letterbox.kde.org" instead of the > >> current server "postbox.kde.org". Additionally, if you are currently > >> using port 588 to send mail, this should now be changed to the > >> standard submission port, 587. > >> > >> As part of this setup we have also completely reworked our > >> SpamAssassin setup. As a consequence of this, we are now looking for > >> spam mail to begin training the filter to ensure it is ready to begin > >> filtering the substantial mail volumes Postbox handles. > >> > >> Mailing list moderators whose lists receive significant quantities of > >> spam are therefore requested to not discard this, and instead let us > >> know so we can use the spam from your moderation queue to train the > >> filter. Please note that we can grab the mail directly from the queue, > >> so forwarding it elsewhere is not required. > >> > >> Once the filter has been sufficiently trained, we will commence the > >> cutover and transfer handling of kde.org mail, including mailing > >> lists, to the new system. > >> > >> Should anyone have any questions regarding this process, please let us > >> know. > >> > >> Regards, > >> Ben Cooksley > >> KDE Sysadmin > > > > When do you plan to finalise the transition and flip the switch? > > Once the Bayes filter has been sufficiently trained, which may take a > few days depending on how much spam we collect. > I've no other clearer timeline than that at this stage i'm afraid. Sure. I ask so that, when you do, we know and can check things are working and we are not left sitting around oblivious and wondering why everybody has suddenly gone awfully quiet. To avoid this I suppose that, when you do know the exact time and date, you will make it public, right? Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity signature.asc Description: This is a digitally signed message part.
Re: Upcoming change to mail infrastructure
On martes, 3 de julio de 2018 12:29:41 (CEST) Ben Cooksley wrote: > Hi all, > > We've recently completed configuration of a new mail server which will > be replacing the current system which handles kde.org mail. This > system will be assuming responsibility for mailing lists as well as > authenticated mail sending for those who require that service. > > To ensure a smooth transition however some changes may be needed on > your side, especially if you are using our authenticated mail sending > service. > > As part of the new system, we have configured updated filters which > will begin enforcing DMARC policies for domains which have specified > these, along with improved SPF verification. As a consequence, if you > are forwarding mail from another provider to your kde.org or > kdemail.net address, this may cease working following the transition. > We recommend you configure these services to instead forward directly > to your final mail provider should this impact on you. > > For those users of the authenticated mail service: please change your > mail client to use the server "letterbox.kde.org" instead of the > current server "postbox.kde.org". Additionally, if you are currently > using port 588 to send mail, this should now be changed to the > standard submission port, 587. > > As part of this setup we have also completely reworked our > SpamAssassin setup. As a consequence of this, we are now looking for > spam mail to begin training the filter to ensure it is ready to begin > filtering the substantial mail volumes Postbox handles. > > Mailing list moderators whose lists receive significant quantities of > spam are therefore requested to not discard this, and instead let us > know so we can use the spam from your moderation queue to train the > filter. Please note that we can grab the mail directly from the queue, > so forwarding it elsewhere is not required. > > Once the filter has been sufficiently trained, we will commence the > cutover and transfer handling of kde.org mail, including mailing > lists, to the new system. > > Should anyone have any questions regarding this process, please let us know. > > Regards, > Ben Cooksley > KDE Sysadmin When do you plan to finalise the transition and flip the switch? Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity signature.asc Description: This is a digitally signed message part.
Re: Babe project - Legal feedback
Hello Camilo, Not a lawyer either and you would need confirmation from a legal expert, but you questions are not hard: > 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? This is illegal in most countries, since it is akin to file-sharing. In Germany they can fine private users up to € 1,000 euros for this. Solution: Build in a license-identifier and allow streaming of music only under permissive licenses or in the public domain. > 2- If the stream part wouldn't be enough 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? Illegal in most countries because it is actual file-sharing of copyrighted material. Solution 1: see above and only allow sharing of music distributed under permissive licenses. Solution 2: allow sharing the playlist, only the list, but not the files themselves. Excuse me because I don't know much about your software, but, if you share the list, surely there would be a way to allow the receiving users to compile the list from their existing collection and complete it legally by facilitating purchasing of the missing songs from a store or using an online streaming service like Spotify (or whatever kids use nowadays). There is a silver-lining though: If you do implement a license identifier (I have no idea how that would work) and users see the additional advantage of listening to free (as in freedom) because of the extra features they can enjoy, you will be helping the Free Culture movement. Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://mastodon.technology/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity signature.asc Description: This is a digitally signed message part.
