Re: Frameworks Overview
On Wed, Sep 25, 2013 at 8:22 AM, Alexander Neundorf neund...@kde.org wrote: On Tuesday 24 September 2013, Ben Cooksley wrote: On Sep 24, 2013 7:33 AM, Alexander Neundorf neund...@kde.org wrote: On Monday 23 September 2013, Sebastian Kügler wrote: Hey, On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote: On Thursday 19 September 2013 Sebastian Kügler wrote: http://community.kde.org/Frameworks/Overview I have put the data on Inqlude (see http://inqlude.org/edge.html). Thanks. One issue though, we're duplicating incomplete information that is in flux. (For example, I know of at least one framework that has been added to tier2 (I think) since last week. The information will need constant updating for a few more months. Having it in to places doesn't make that easier. Can I update the info on inqlude.org somehow, so we can ditch the wiki version? It would be nice, if we could improve the presentation of the different libraries along with the code. The goal of Inqlude is to make them easily accessible not only to us, but also to Qt developers who don't necessarily know anything about KDE or might have (more or less founded) objections against using KDE libraries. To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. Technically, this is the current focus. We're splitting kdelibs. As to communication, it probably needs a bit of boilerplate. (Which the bits I wrote don't contain purposefully.) Otherwise, you're right, we need to work on the presentation side here. IMO, if projects.kde.org would have the wiki enabled, the project pages there could be an easy way to have simple homepages for all the frameworks: https://projects.kde.org/projects/kdesupport/attica Due to maintenance and performance concerns, sysadmin would like to move away from Chiliproject. Oh, really ? What alternatives are you looking at ? Personally I like redmine/chili a lot. Yep. At the moment there are no real contenders as such - which is why it has not yet been replaced. Phabricator is being monitored for progress on a blocking issue however. The primary issues are those of performance ( Enabling the wiki would complicate this when a replacement is found. It would also create competition with the main wikis. I don't think so. As Cornelius put it To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. IMO a kind of separate home page for each library is part of that. Would something similar to the Manifesto site fit this? Alex Regards, Ben ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Friday 27 September 2013, Ben Cooksley wrote: ... Yep. At the moment there are no real contenders as such - which is why it has not yet been replaced. Phabricator is being monitored for progress on a blocking issue however. The primary issues are those of performance ( That's a pity. Enabling the wiki would complicate this when a replacement is found. It would also create competition with the main wikis. I don't think so. As Cornelius put it To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. IMO a kind of separate home page for each library is part of that. Would something similar to the Manifesto site fit this? You mean http://manifesto.kde.org ? Are these plain html pages, or is it using some CMS or wiki ? Alex ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Monday 23 September 2013 11:43:58 Sebastian Kügler wrote: On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote: On Thursday 19 September 2013 Sebastian Kügler wrote: http://community.kde.org/Frameworks/Overview I have put the data on Inqlude (see http://inqlude.org/edge.html). Thanks. One issue though, we're duplicating incomplete information that is in flux. (For example, I know of at least one framework that has been added to tier2 (I think) since last week. The information will need constant updating for a few more months. Having it in to places doesn't make that easier. Don't worry, I'm perfectly fine with maintaining the information on Inqlude, so if there is a reference location somewhere else, I'll take care of keeping them in sync. Can I update the info on inqlude.org somehow, so we can ditch the wiki version? You can easily update the information. There are instructions on the web site. We could also think about some automation depending on where it is most convenient to maintain the reference data. One way would be to include some machine-readable meta data in the git repository, so we could generate other representations from that, be it a dedicated web site or the info on Inqlude, or something different. -- Cornelius Schumacher schumac...@kde.org ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Mon, Sep 23, 2013 at 11:43 AM, Sebastian Kügler se...@kde.org wrote: Technically, this is the current focus. We're splitting kdelibs. As to communication, it probably needs a bit of boilerplate. (Which the bits I wrote don't contain purposefully.) Otherwise, you're right, we need to work on the presentation side here. Anything I can help with? Having some time off so I can do some writing or even hacking on a site* where it makes sense ;-) * I can handle some web stuff provided it ain't too complicated ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Monday, September 23, 2013 15:08:57 Jos Poortvliet wrote: On Mon, Sep 23, 2013 at 11:43 AM, Sebastian Kügler se...@kde.org wrote: Technically, this is the current focus. We're splitting kdelibs. As to communication, it probably needs a bit of boilerplate. (Which the bits I wrote don't contain purposefully.) Otherwise, you're right, we need to work on the presentation side here. Anything I can help with? Having some time off so I can do some writing or even hacking on a site* where it makes sense * I can handle some web stuff provided it ain't too complicated I think a critical look what exactly needs doing is needed. Probably Cornelius has more detailed ideas. Right? -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Tuesday 24 September 2013, Ben Cooksley wrote: On Sep 24, 2013 7:33 AM, Alexander Neundorf neund...@kde.org wrote: On Monday 23 September 2013, Sebastian Kügler wrote: Hey, On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote: On Thursday 19 September 2013 Sebastian Kügler wrote: http://community.kde.org/Frameworks/Overview I have put the data on Inqlude (see http://inqlude.org/edge.html). Thanks. One issue though, we're duplicating incomplete information that is in flux. (For example, I know of at least one framework that has been added to tier2 (I think) since last week. The information will need constant updating for a few more months. Having it in to places doesn't make that easier. Can I update the info on inqlude.org somehow, so we can ditch the wiki version? It would be nice, if we could improve the presentation of the different libraries along with the code. The goal of Inqlude is to make them easily accessible not only to us, but also to Qt developers who don't necessarily know anything about KDE or might have (more or less founded) objections against using KDE libraries. To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. Technically, this is the current focus. We're splitting kdelibs. As to communication, it probably needs a bit of boilerplate. (Which the bits I wrote don't contain purposefully.) Otherwise, you're right, we need to work on the presentation side here. IMO, if projects.kde.org would have the wiki enabled, the project pages there could be an easy way to have simple homepages for all the frameworks: https://projects.kde.org/projects/kdesupport/attica Due to maintenance and performance concerns, sysadmin would like to move away from Chiliproject. Oh, really ? What alternatives are you looking at ? Personally I like redmine/chili a lot. Enabling the wiki would complicate this when a replacement is found. It would also create competition with the main wikis. I don't think so. As Cornelius put it To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. IMO a kind of separate home page for each library is part of that. Alex ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Thursday 19 September 2013 Sebastian Kügler wrote: http://community.kde.org/Frameworks/Overview I have put the data on Inqlude (see http://inqlude.org/edge.html). It would be nice, if we could improve the presentation of the different libraries along with the code. The goal of Inqlude is to make them easily accessible not only to us, but also to Qt developers who don't necessarily know anything about KDE or might have (more or less founded) objections against using KDE libraries. To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. -- Cornelius Schumacher schumac...@kde.org ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
Hey, On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote: On Thursday 19 September 2013 Sebastian Kügler wrote: http://community.kde.org/Frameworks/Overview I have put the data on Inqlude (see http://inqlude.org/edge.html). Thanks. One issue though, we're duplicating incomplete information that is in flux. (For example, I know of at least one framework that has been added to tier2 (I think) since last week. The information will need constant updating for a few more months. Having it in to places doesn't make that easier. Can I update the info on inqlude.org somehow, so we can ditch the wiki version? It would be nice, if we could improve the presentation of the different libraries along with the code. The goal of Inqlude is to make them easily accessible not only to us, but also to Qt developers who don't necessarily know anything about KDE or might have (more or less founded) objections against using KDE libraries. To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. Technically, this is the current focus. We're splitting kdelibs. As to communication, it probably needs a bit of boilerplate. (Which the bits I wrote don't contain purposefully.) Otherwise, you're right, we need to work on the presentation side here. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: Frameworks Overview
On Sep 24, 2013 7:33 AM, Alexander Neundorf neund...@kde.org wrote: On Monday 23 September 2013, Sebastian Kügler wrote: Hey, On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote: On Thursday 19 September 2013 Sebastian Kügler wrote: http://community.kde.org/Frameworks/Overview I have put the data on Inqlude (see http://inqlude.org/edge.html). Thanks. One issue though, we're duplicating incomplete information that is in flux. (For example, I know of at least one framework that has been added to tier2 (I think) since last week. The information will need constant updating for a few more months. Having it in to places doesn't make that easier. Can I update the info on inqlude.org somehow, so we can ditch the wiki version? It would be nice, if we could improve the presentation of the different libraries along with the code. The goal of Inqlude is to make them easily accessible not only to us, but also to Qt developers who don't necessarily know anything about KDE or might have (more or less founded) objections against using KDE libraries. To reach this we'll need to present KF5 in a bit more independent way, and make sure that each library can stand on its own. Technically, this is the current focus. We're splitting kdelibs. As to communication, it probably needs a bit of boilerplate. (Which the bits I wrote don't contain purposefully.) Otherwise, you're right, we need to work on the presentation side here. IMO, if projects.kde.org would have the wiki enabled, the project pages there could be an easy way to have simple homepages for all the frameworks: https://projects.kde.org/projects/kdesupport/attica Due to maintenance and performance concerns, sysadmin would like to move away from Chiliproject. Enabling the wiki would complicate this when a replacement is found. It would also create competition with the main wikis. I'm open to suggestions though - perhaps something like the manifesto site would work for this. Alex Regards, Ben ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
