Re: (low-frequency) mailing lists | suggestions & summary of prior thread

[Shantanu Tushar Jha]

Hi Joseph,

Thanks a LOT for summarizing the discussions, it really helps.

@Bhushan Shah  Since there is a KDE India already on
Discourse[1], I propose we remove/archive the kde-india mailing list.

Cheers,
Shantanu

https://discuss.kde.org/c/local-communities/kde-india/19

On Tue, 23 May 2023 at 14:10, Joseph P. De Veaugh-Geiss 
wrote:

> Follow-up discussion to the post "Inactive mailing lists".
>
> tl;dr There are three topics discussed here:
>
>1. For mailing list admins: *Suggestions For Information To Add To
> Mailing List Descriptions*
>2. For mailing list communities: *Moving Certain Groups To Discourse?*
>3. For everyone: *Summary Of Prior Discussion About Inactive /
> Infrequently Used Lists*
>
> As always, the discussion is open for your feedback and ideas!
>
> _1. Information To Add To Mailing List Descriptions_
>
> If you are a list admin, consider adding the following to the mailing
> list description. This way subscribers are well-informed about the
> communication channels used for your project/community:
>
>* Other communication channels for this project and their intended
> use (e.g., for announcements, user support, live chat, etc.)
>* Relevant links for the project (e.g., website, wiki, etc.)
>* Intended scope for the list (i.e., what it is for / not for)
>* Policies regarding moderation, code of conduct, etc.
>
> For examples, see:
>
>* Energy-efficiency:
> https://mail.kde.org/cgi-bin/mailman/listinfo/energy-efficiency
>* Kde-soc: https://mail.kde.org/mailman/listinfo/kde-soc
>* Visual-design: https://mail.kde.org/mailman/listinfo/visual-design
>
> _2. Moving Certain Groups To Discourse?_
>
> Beyond typical forum functionality, Discourse integrates well with email
> and RSS. Something to consider for low-frequency mailing list groups:
> there may be projects and communities that benefit by officially moving
> communication to Discourse. Although I have no data to back up the
> claim, I suspect having users interact on a more active platform could
> generally increase engagement within KDE.
>
> A nice feature of Discourse is: for mailing list subscribers who wish to
> continue receiving posts in their mail clients, it is possible to follow
> discussions via RSS or by enable mailing list mode in Discourse. It
> takes some setting up; see below for more.
>
> A few language and country-specific communities already have made a move
> to Discourse. See:
>
> https://discuss.kde.org/c/local-com.munities/
> 
>
> Some of these groups also have low traffic mailing lists. Unless current
> list subscribers also move to Discourse, there is the risk of fracturing
> the community as list subscribers are seperated from the people at the
> forum. In this case, archiving and closing the infrequently-used mailing
> list might be beneficial. Of course, that is for the list admin and
> relevant community to decide.
>
> Info about using Discourse with email and RSS:
>
>* Users can enable "Mailing list mode", which allows one to receive
> and respond to posts via email (i.e., just like a mailing list). By
> default, users receive posts to /all/ categories -- limiting posts to
> specific categories requires manually "muting" the other categories. See
> the community wiki for more detail, including how to mute categories:
>
>  https://community.kde.org/KDE.org/KDE_Forums#Mailing_List_Mode
>
>* Alternatively, one can follow specific categories, tags, etc. as an
> RSS feed. Again, see the community wiki for details:
>
>  https://community.kde.org/KDE.org/KDE_Forums#Following_RSS_Feeds
>
> _3. Summary: Prior Discussion About Inactive Mailing Lists_
>
> Here are some bullet points from the discussion about inactive /
> infrequently used mailing lists. For the full thread, go to:
>
> https://mail.kde.org/pipermail/kde-community/2023q2/007577.html
>
>* Some lists deliberately have archiving disabled, so an empty
> archive is not necessarily an indicator of no activity.
>* Some lists are primarily used for following bug reports (e.g.,
> *-bugs) or commits.
>* Subscribing to a low traffic email list is rarely something people
> notice, and the UI of mail clients rarely gets in the way. By contrast,
> the UI of e.g. Matrix very much gets in the way of staying in 200 low
> traffic channels.
>* Low email traffic does not mean subscribers will not answer
> appropriate posts sent to it.
>* Unless current subscribers also make the move to a new channel,
> moving discussion to a new platform risks separating the people who have
> answers (the current subscribed people) with the people who have the
> questions (the people redirected elsewhere).
>* For lists that are unquestionably no longer in use, please file a
> sysadmin ticket and they will get removed.
>* See this ticket for mailing lists that have been or will be removed
> as a result of the discussion: https://phabricator.kde.org/T16

Re: [kde-community] Official KDE mirror on github

[Shantanu Tushar Jha]

Its sad that this got completely ignored by the members of this discussion,
the argument is very valid.

On Sat, Sep 19, 2015 at 3:47 PM, Luigi Toscano 
wrote:

> Il 19 settembre 2015 12:00:11 CEST, Vishesh Handa  ha
> scritto:
> > On Sat, Sep 19, 2015 at 11:44 AM, Luca Beltrame 
> > wrote:
> > >
> > > And besides... hasn't the BitKeeper story taught us *anything*?
> > >
> >
> > I don't know about you guys, but it has taught me that we can be
> > pragmatic and use proprietary software when the need arises.
>
>
> There is a big FLOSS project I spend my daily work for, called OpenStack.
> Given its target, contributions comre from companies and certainly normal
> users are not too interested about it and even more about how it is
> developed. Despite this, it has a strong manifesto with interesting values:
> https://wiki.openstack.org/wiki/Open
>
> and that extends to the infrastructure too. Leaving aside the usage of
> launchpad for bugs (there is a replacement which is advanced state of
> development), guess what? Infra team has an own git, contributions go to
> the internal gerrit. Github is just a mirror and I didn't hear anyone
> screaming or complaining about loss of contributions.
>
> Now, if they can do that, why can't we do it?
>
> Ciao
>
> --
> Luigi
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>



-- 
Shantanu Tushar(UTC +0530)
http://www.shantanutushar.com
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Official KDE mirror on github

[Shantanu Tushar Jha]

On Sat, Sep 19, 2015 at 1:12 PM, Martin Graesslin 
wrote:

> On Friday, September 18, 2015 5:29:01 PM CEST Albert Vaca wrote:
> > From my experience, I was already mirroring KDE Connect in Github and
> I've
> > received valuable patches there. That's a big enough reason for me to
> want
> > Github's pull requests (and to spend 15 minutes learning how to use
> them),
> > but I understand not everybody wants to learn a new and non-free tool.
>
> I'm subscribed to kde-connects review requests for reviewboard. How am I
> as an
> interested developer able to follow the code review for github pull
> requests
> if I don't want to use them?
>
> Basically by the decision to opt-in for pull requests you force the
> complete
> team to follow them. Otherwise not-reviewed code gets in.
>
> We really need to think in the big picture of what means this to KDE. We
> shouldn't go the "selfish" road and think of your own project. By allowing
> github pull-requests we are pushing out the contributors who don't want to
> use
> it. You make it impossible for those contributors to comment on review
> requests, thus you have split the development.
>
> This is scary. Please don't think "selfish". Let people create the pull
> request and answer it with:
> "Sorry we do not support git hub pull request. To submit code please use
> reviewboard.kde.org. Here's how you do it..."
>
> The point is we want to get to the people on github. That's why we mirror.
> It's not about getting pull requests. We want the people! They already
> spent
> the effort to create the patch, they will spent the additional time to get
> to
> reviewboard of phabricator in future. I have so often got patches on
> bugzilla
> and it never was a problem to tell them "please use reviewboard for the
> patch
> submission as the UI is more streamlined for code review". We always got
> the
> patch into reviewboard. The aim of the people is not to use pull requests,
> the
> aim is to submit their patch!
>

+1 to that. And adding to it, IMO the most important thing here is
consistency. The last thing we want to have is newcomers getting confused
"erm, so for this KDE project do I use reviewboard? or do I create a pull
request?".


>
> Cheers
> Martin
>
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>

Cheers,

-- 
Shantanu Tushar(UTC +0530)
shantanu.io
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] HIG compliance testing via Google Code-in

[Shantanu Tushar Jha]

Hmm a tough question indeed :/ If I had to choose, I'll go with Desktop. If
you think the Desktop HIG is too limited to windowed apps with toolbars
etc, then we might have to drop the idea.


On Thu, Dec 5, 2013 at 11:42 PM, Thomas Pfeiffer wrote:

> On Thursday 05 December 2013 10:16:56 Shantanu Tushar Jha wrote:
> > Plasma Media Center would love to have more usability feedback, as usual
> :)
>
> PMC would surely be interesting to test. The only issue I see is: Which
> HIGs
> should it be tested against? It's neither really a Desktop nor an Active
> application, and we don't have HIGs for "Plasma applications".
> So: Which HIGs would PMC like to comply to?
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>



-- 
Shantanu Tushar(UTC +0530)
http://www.shantanutushar.com
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] HIG compliance testing via Google Code-in

[Shantanu Tushar Jha]

Plasma Media Center would love to have more usability feedback, as usual :)


On Thu, Dec 5, 2013 at 4:31 AM, Thomas Pfeiffer wrote:

> Hey everyone,
> as you know from Lydia's recent mail on this list, we need some more Google
> Code-in tasks.
> So far we had two tasks for testing KDE applications for compliance with
> the
> KDE Human Interface Guidelines
> (http://techbase.kde.org/Projects/Usability/HIG). Both tasks have been
> completed very successfully, yielding a detailed spreadsheet of violations
> for
> each HIG area with basically zero effort from our side. Therefore I'd like
> to
> post and mentor more of these tasks. However I don't want students to
> create
> lists of problems with no chance of them ever being fixed, so I won't post
> any
> compliance test tasks without buy-in from the respective application's
> developers.
> So, who would like to have their application HIG-compliance-tested? Just
> reply
> here and I'll set a task up. It will help you identify potential usability
> problems in your applications without any effort from your side except for
> the
> commitment to look at the lists and see if you can fix the issues there
> after
> task completion.
> Cheers,
> Thomas
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>



-- 
Shantanu Tushar(UTC +0530)
http://www.shantanutushar.com
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community