Re: [kde-community] Closing the kde-core-devel mailing list

2014-08-12 Thread Sebastian Kügler
On Tuesday, August 05, 2014 21:28:14 Kevin Krammer wrote:
 On Tuesday, 2014-08-05, 20:29:05, Albert Astals Cid wrote:
  El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
  
   Random Idea: How about we close the k-c-d mailing list? It's main
   purpose
   used to be to discuss kdelibs changes, but now since we have
   kde-frameworks, the mailing list seems less useful. We already have
   kde-devel for other generic kde stuff.
 
  kde-core-devel main purpose may had been discuss kdelibs changes, but it
  has trascended that purspose a while ago.
 
 I agree with Albert.
 
 k-c-d is the list to for things that happen in development, like kde-review 
 requests, inter-module coordination, etc.
 It is more like a kde-community-technical list.
 
 kde-devel is more a list for question regarding developing with the KDE 
 platform.
 If there is really a need to fold one list with kde-frameworks its this one.

Assuming you mean folding frameworks-devel, I'd agree. (We could merge 
these lists, of course.)
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9


Re: Closing the kde-core-devel mailing list

2014-08-12 Thread Marco Martin
On Monday 04 August 2014, Vishesh Handa wrote:
 Hello people
 
 Random Idea: How about we close the k-c-d mailing list? It's main purpose
 used to be to discuss kdelibs changes, but now since we have
 kde-frameworks, the mailing list seems less useful. We already have
 kde-devel for other generic kde stuff.

hmm, I would maybe have seen a reason in doing like the other way around, 
closing kde-frameworks, merge the mails and move all on k-c-d, since 
frameworks is released and is the main target of development now

-- 
Marco Martin


Re: [kde-community] Closing the kde-core-devel mailing list

2014-08-05 Thread Albert Astals Cid
El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
 Hello people
 
 Random Idea: How about we close the k-c-d mailing list? It's main purpose
 used to be to discuss kdelibs changes, but now since we have
 kde-frameworks, the mailing list seems less useful. We already have
 kde-devel for other generic kde stuff.

kde-core-devel main purpose may had been discuss kdelibs changes, but it has 
trascended that purspose a while ago.

Let's see email threads that were sent here that don't belong to frameworks-
devel, please tell me what list would replace k-c-d in this regard

 * Pushing AppStream data to KDE project's master branches
 * KDE Applications December 2014 release: which apps are targeting Qt4/Qt5?
 * Oxygen Fonts kdereview
 * Default wallpapers should go in svn or git?
 * Move of KXStitch to Extragear/Graphics 
 * Kronometer now in KDE Review 
 * Move of SymbolEditor to Extragear/Graphics 
 * Moving plasma-nm to extragear  
 * Talks @Akademy  
 * KBibTeX in KDE Review   
 * Freedesktop summit 2014 
 * kde-workspace split incoming!   

As you see these have nothing to do with kdelibs. Sure i understand lib 
development moved to frameworks-devel, that's fine, but until you have a place 
to discuss core stuff I don't see why we should close our core-devel list.

Cheers,
  Albert


Re: [kde-community] Closing the kde-core-devel mailing list

2014-08-05 Thread Matthias Klumpp
2014-08-05 20:29 GMT+02:00 Albert Astals Cid aa...@kde.org:
 El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
 Hello people

 Random Idea: How about we close the k-c-d mailing list? It's main purpose
 used to be to discuss kdelibs changes, but now since we have
 kde-frameworks, the mailing list seems less useful. We already have
 kde-devel for other generic kde stuff.

 kde-core-devel main purpose may had been discuss kdelibs changes, but it has
 trascended that purspose a while ago.

 Let's see email threads that were sent here that don't belong to frameworks-
 devel, please tell me what list would replace k-c-d in this regard

  * Pushing AppStream data to KDE project's master branches
  * KDE Applications December 2014 release: which apps are targeting Qt4/Qt5?
  * Oxygen Fonts kdereview
  * Default wallpapers should go in svn or git?
  * Move of KXStitch to Extragear/Graphics
  * Kronometer now in KDE Review
  * Move of SymbolEditor to Extragear/Graphics
  * Moving plasma-nm to extragear
  * Talks @Akademy
  * KBibTeX in KDE Review
  * Freedesktop summit 2014
  * kde-workspace split incoming!

 As you see these have nothing to do with kdelibs. Sure i understand lib
 development moved to frameworks-devel, that's fine, but until you have a place
 to discuss core stuff I don't see why we should close our core-devel list.
I agree with this - but do we have a list where we can discuss
project-wide technical changes? The kde-core-devel list so far is one
of the few lists where you can reach most developers to discuss some
of this global stuff.
Cheers,
Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/


Re: [kde-community] Closing the kde-core-devel mailing list

2014-08-05 Thread Kevin Krammer
On Tuesday, 2014-08-05, 20:29:05, Albert Astals Cid wrote:
 El Dilluns, 4 d'agost de 2014, a les 20:36:44, Vishesh Handa va escriure:
  Hello people
  
  Random Idea: How about we close the k-c-d mailing list? It's main purpose
  used to be to discuss kdelibs changes, but now since we have
  kde-frameworks, the mailing list seems less useful. We already have
  kde-devel for other generic kde stuff.
 
 kde-core-devel main purpose may had been discuss kdelibs changes, but it has
 trascended that purspose a while ago.

I agree with Albert.

k-c-d is the list to for things that happen in development, like kde-review 
requests, inter-module coordination, etc.
It is more like a kde-community-technical list.

kde-devel is more a list for question regarding developing with the KDE 
platform.
If there is really a need to fold one list with kde-frameworks its this one.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


signature.asc
Description: This is a digitally signed message part.


Closing the kde-core-devel mailing list

2014-08-04 Thread Vishesh Handa
Hello people

Random Idea: How about we close the k-c-d mailing list? It's main purpose used 
to be to discuss kdelibs changes, but now since we have kde-frameworks, the 
mailing list seems less useful. We already have kde-devel for other generic 
kde stuff.

-- 
Vishesh Handa


Re: [kde-community] Closing the kde-core-devel mailing list

2014-08-04 Thread Milian Wolff
On Monday 04 August 2014 20:36:44 Vishesh Handa wrote:
 Hello people
 
 Random Idea: How about we close the k-c-d mailing list? It's main purpose
 used to be to discuss kdelibs changes, but now since we have
 kde-frameworks, the mailing list seems less useful. We already have
 kde-devel for other generic kde stuff.

So far, kdelibs is still open for patches, no? So I'd say let's keep it until 
we stop accepting patches for kdelibs.

Bye
-- 
Milian Wolff
m...@milianw.de
http://milianw.de


Re: [kde-community] Closing the kde-core-devel mailing list

2014-08-04 Thread Aleix Pol
On Tue, Aug 5, 2014 at 1:17 AM, Milian Wolff m...@milianw.de wrote:

 On Monday 04 August 2014 20:36:44 Vishesh Handa wrote:
  Hello people
 
  Random Idea: How about we close the k-c-d mailing list? It's main purpose
  used to be to discuss kdelibs changes, but now since we have
  kde-frameworks, the mailing list seems less useful. We already have
  kde-devel for other generic kde stuff.

 So far, kdelibs is still open for patches, no? So I'd say let's keep it
 until
 we stop accepting patches for kdelibs.

 Bye


Well, we can use the kde-frameworks mailing list for those reviews I'd say.
Anything that is committed to kdelibs should be forward-ported to KF5
anyway, or it gets lost.

It's not like it's 2 different projects, kdelibs and kde frameworks.

Aleix