Re: Discourse
Why not use bbpress / buddypress as the main websites are now powered by WordPress I believe? You can import too: https://codex.bbpress.org/getting-started/importing-data/import-forums/ On Mon, 29 Oct 2018, 20:56 Luca Beltrame, wrote: > Il giorno Mon, 29 Oct 2018 18:31:54 + > Jonathan Riddell ha > scritto: > > contributors not wanting to get into them. Our KDE Forums also look > > quite old school. In Fedora they moved to Discourse and mailing > > lists and forums and saw a marked increase in engagement. > > "Old school" because few people are willing (if any) to put up with > maintenance. This has been going for quite a while, unfortunately. > > I have my fair share of issues with Discourse (I run into it daily when > checking the support forum of my router): > > - As far as I remember, they *only* supported deployment with Docker. > This is is IMO a terrible and black-magic approach > - It uses (used to use?) PostgreSQL as database, for which Sysadmin > isn't really keen on using unless absolutely necessary > - The UX is not as best as it looks, hijacks stuff like the back button > on the browser and what not > - The "app" on mobile is a joke, basically a web view of the mobile page > > > I think KDE should consider moving away from mailman and onto > > Does Discourse have a mail interface to avoid breaking user workflows? > How should a migration be handled? Don't forget we'll lose distributed > archiving of the mailing lists as well (very useful). > > > Discourse and at the same time forum.kde.org could move to this more > > What about the old posts? Did anyone consider a migration? We don't want > to lose old content, after all. > > Also, don't forget that "should", to quote a seminar I was at recently, > should become "I/we/they will". If no one is willing to put support > with the (aged! I'm not saying it's perfect) forum infrastructure why > do you think one would put up with the new? > > > >
Re: The VDG
Hi all, >From reading this and the linked discussion I'm unsure what the problem is? KDE does not in majority of cases ship directly to users, it does through distros. Surely the goal is to speak to distros, even the esoteric ones like kxstudio and find out what they and their users would like and work from there? On Sun, 3 Jun 2018, 21:24 Andy B, wrote: > Hello team, > > Given recent events and decisions ( > https://mail.kde.org/pipermail/plasma-devel/2018-June/086117.html) I feel > it important to bring more to the table. > > Martin’s decision is an unfortunate one. Martin has been with KDE through > thick-and -hin and has earned the respect and love from many members in the > community. He has also earned my respect. > > I can’t help but think that the VDG is a tremendously influential group > within KDE. I personally take this as a huge responsibility and a call to > do even better in our approach. We ourselves have also seen the departures > of many influential members. We have lost leaders one after the other and > we have tried to cope with that. Martin’s and others’ comments about the > VDG are welcomed and noted in this regard. > > I share the feeling. The VDG has strived to bring design back to the table > after we started the Plasma 5 cycle, discussing design, debating direction, > etc. However, the VDG has no leader, no vision, no strong direction. I took > these thoughts seriously last year when I first attended Akademy. I > realized that the VDG has a strong voice, but it was just that, a voice. > > I think we are still feeling the fallout from Aaron Siego’s exit from the > community. He provided strong vision, made developers excited once again > for their work, designers rallied behind the visual vision we had. It felt > as though nothing could stop us because we had a guide to follow. Nothing > else mattered. > > I think the VDG needs vision and guidance desperately. I am guilty myself > of not providing this. However, I have taken steps to mitigate this > problem. Last year, I decided to engage myself in revamping System > Settings. We are still working through it but strong work has been done in > this past year from me that I have ever done before. > > My basic idea was to provide an easier way to interact with the thousands > of options that System Settings provides. By doing this work, I discovered > that much more could be sprung up and done for the entire interface. I also > discovered that I cannot take a hard line on everything that I do. We have > been able to deliver more KCMs by steering design rather than dictating > design. My affiliation with developers in the team has been one of the most > enriching experiences of my life. I feel the VDG will do well in > approaching our developer team the same way. Don’t be married to a design, > learn from technical challenges to your work, adapt quickly and move on. > VDG members will see that by doing this, we open the door to even more > possibilities than we ever thought. > > Our developers are the ones putting out thousands of lines of code, > reading on a computer screen all day, and Plasma ones do this all night as > well. They are the foundation of the project. Without our developers, the > VDG can never hope to deliver anything to the public. Our developers area > cautious, full of ideas and a guiding voice for contributors. We will do > well in partnering with a developer as we work and listen carefully to > their counsel. > > I feel that our team in the VDG generally receives many newcomers to the > world of Linux and Open Source communities. This is a challenge for the VDG > as we must be open to new contributors but also need to curve contributions > to the right places. For some, this makes it feel to them that “anything > goes”. This is simply not the case. We ask that if you are a new > contributor to the VDG, start small, learn from others and ask questions. > We cannot take the hard line that our designs are above the project. They > are simply not. > > The VDG also gathers a crowd that is passionate about design but doesn’t > always provide direction. I will take fault for that. Having been here a > while I feel it is my responsibility to provide more direction to new > contributors. I have opened doors, but I have not learned how to shut them. > If our dev team has anything they want to say, please bring this to me and > I will work with you. > > If anything, I feel that our developer team, the VDG and the Plasma team > in general currently lacks “visual direction”. I say this very carefully of > everyone’s feelings. We maintain our software without stretching ourselves > too far. After all, major changes also mean major work. By the same token, > sometimes as VDG, we don’t dimension that a graphic design that took us 2 > hours to make will take 6 months to deliver. We must think deeper, less > like a graphic artist and more like a project manager. This will bring > perspective to our work. > > I ask that
Re: [kde-community] Trademark clause in the Manifesto
Hello, Out of interest, whose money would be used to defend a trademark dispute? Kind regards, David. On 28 Jul 2015 20:38, Boudewijn Rempt b...@valdyas.org wrote: On Tue, 28 Jul 2015, Jonathan Riddell wrote: On Tue, Jul 28, 2015 at 09:37:40AM +0200, Boudewijn Rempt wrote: If the authors of the software abandon it or disappear, they agree to transfer the trademark to the next maintainer How about: If the project maintainer leaves KDE they agree to transfer the trademark to KDE e.V. or the new maintainers (or remove the project from KDE). I'm not sure it's the actual formulation that gives me problems (though clarification would be good), but the actual legal implementation. Boudewijn ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] KDE office (was: Your KDE highlight of 2014?)
We're basically talking about KDE centric LUGS (KLUGS?) here aren't we. Whether hosted in an office at bluesystems or down the local pub once a week, that's really what they are, the meeting of likeminded people for fun and profit. Which should be more of a thing (I'd like to meet with kde users here in London), and something which 'official' KDE should help facilitate with a webservice. That way it can be made clear who and what are hosting these meetings, or open doors as they might be, the terms, and the relationship, or lack thereof, with KDE ev. On 29 Dec 2014 17:34, Aleix Pol aleix...@kde.org wrote: On Mon, Dec 29, 2014 at 4:49 PM, Lydia Pintscher ly...@kde.org wrote: On Mon, Dec 29, 2014 at 4:46 PM, Jaroslaw Staniek stan...@kde.org wrote: Hi. Let's put a nice KDE Community logo on the doors, done. After all we're educating rest of the world what KDE means, this is one more opportunity to do that. It's not quite that simple unfortunately as Aaron explained. Also it takes two to make this happen: KDE e.V. and BlueSystems. If we're serious about this and if BlueSystems is even considering this then let's talk and do this properly. Or we can just call it a Free and Open Source office on the other hand, I don't think we'll break any trademark with that. Having a KDE sticker on the door is not that different to having it on my laptop's lid. Also I don't think this conversation is taking us to a happy productive place. I think Jonathan referred to the office as a KDE office because it's been an amazing place for things to happen during 2014. 7 out of 12 sprints in 2014 happened here and it's been a meeting point for the KDE community in Barcelona, and to some extent, it's helping to make some things happen. At the moment, it's just a BlueSystems office that welcomes anybody coming from the KDE world, which makes it a KDE office in our hearts, but not on legal terms. Like Lydia said, we could foster the relationship further. But to what end? If the KDE eV wants to have offices for actual development meetings it should be discussed within the KDE eV first and decide the terms, which might end up being very different to BlueSystems, who organized an office to fit its needs first of all, keeping in mind that it is in the best BlueSystems interests to have a healthy KDE community. Aleix ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] KDE office (was: Your KDE highlight of 2014?)
What brand? Because as far as I can see there is still serious confusion in the community over the recent rebranding efforts. I still see a lot of references to KDE5. On 25 Dec 2014 00:15, Jonathan Riddell j...@jriddell.org wrote: On Thu, Dec 25, 2014 at 12:52:41AM +0100, Aaron J. Seigo wrote: On Wednesday, December 24, 2014 08.17:58 Laszlo Papp wrote: Let us get this off-topic out of the highlight thread... This gave me the idea, why not setup other KDE offices, by sharing space. I would be very interested in making that happen here in south west of UK Well, living on the south east of England (London, Cambridge, Brighton, etc), I am sceptical even here whether this would be sustainable Sustainable or not, I would expect there to be concerns with people independently setting up offices branded KDE. Assuming KDE cares about its brandname and reputation, it's a pretty risky precedent to start rolling. Um, what? You don't want KDE to work on KDE project together and call it KDE? I'm organising a KDE stall at FOSDEM with KDE people to promote KDE, should I call that KDE? Jonathan ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Give People Access to Great Technology - a possible vision
To summarise and expand upon my thoughts on this given the feedback from a couple of you: Essentially I feel we should be concentrating on the promoting the versatility of KDE ecosphere, and what that means to you as the user. That's really what I was driving at when I was asking the question 'What do you need KDE to be for you?' A lot of other desktop environments strangle your workflow tighter than a Steve Jobs turtleneck, they demand that you work around them and their vision, whereas I see KDE working for you and with you, no matter where your end point may be, and what you are doing at that endpoint. Let’s not forget starting points either, it should be able to grow with you, from one app to many, from apps to desktop, from desktop to phone and so on. Which is why projects like KDE for windows are so important, as it provides that first hook to reel users in with, especially business users, where change to a mid-fifties, conservative, company director happens one app at a time, over a long period of time. Now clearly I am no expert on plasma5, qml kf5, but I have been given the impression that it is very flexible (if that's not true then please tell me and I will go back into the cupboard!); however I appreciate there will be limits to what it can and can't do, so perhaps the use of 'it could be anything' was quite rash. I thought that maybe by understanding users needs we could either provide solutions, or provide a signpost to where those solutions may lie. Each users needs are different, so I thought that by splitting between commercial and consumer needs we could consider what they are doing right now, what they would like to see in the future, and how KDE technologies can help with all that. By commercial needs I am taking about businesses in offices (or wherever), and consumers being general peeps. Sorry, this is my workplace terminology creeping in where it probably shouldn't! The reason for this is that I've found that the way businesses use equipment such as tablets and TVs can be very different to general consumers. The KDE terminology issue I’m still not really understanding I’m afraid. I understand the reasons for the splitting out of KDE (the community), KF5, Plasma 5 and applications. The problem I have is that distros are still going to be shipping a KDE variant, apps included. In the absence of KDE supplying a name for the compilation of its software being used together, then I feel the distros are going to simply use KDE or KDE 5, like they would with Gnome, or XFCE, which is wrong, or KF5/Plasma5/Apps which is crap. What’s making this more confusing is that the VDG are now discussing branding some apps along the lines of ‘Made for…’, which again I can understand why, as when Windows ships Windows 8, it comes with a picture viewer, file browser etc. But it’s still Windows 8. The only people who have come close to giving this new amalgamation of software a name is Kubuntu, with Project Neon. Maybe something like the ‘KDE Experience’ would be fitting? I don’t agree that everything should be completely separate however, there should still be links to one another, otherwise KDE becomes nothing more than a glorified Github. Hope that makes more sense. Kind Regards, David. On Mon, Sep 22, 2014 at 9:41 PM, Andrew Lake jamboar...@gmail.com wrote: Hello again, I was going to reply to each response individually but I thought it might be simpler to do one reply. First off, thanks for being so so gracious in reviewing the thoughts I shared. As I mentioned these were personal thoughts prompted by my experience at Akademy this year. There's always a risk sharing such thoughts with a community that barely knows me, so I'm grateful for your kindness. At the risk of appearing to be defensive about the ideas expressed, permit me to provide some clarifications: * The ideas were not intended to communicate a stand our ground or a don't adventure beyond the desktop vision. Rather they was intended to say that the desktop doesn't have to be viewed as a now relatively stagnant participant in the ecosystem. I'm not sure anyone in the community thinks that is the case, but to the extent that there is concurrence, it seemed an element of value worth capturing and communicating about ourselves and what we provide. * Regarding integration, the ideas were really intended to regard applications, the desktop, devices and the cloud for their unique capabilities and how they can enhance each other. That can include the make-a-tablet/phone/cloud-version-of-[x] approach, but the hope is that it could include other approaches as well. As noted, there are already many efforts in the community that reflect such approaches, so it seemed an element of value worth communicating as well. * I'm no personal fan of exclusivity-driven integration. I'm rather a fan of open approaches to technological integration that enables people not hinder them. I've never sensed that as an
Re: [kde-community] Give People Access to Great Technology - a possible vision
Thanks for clarifying Thomas. I am too busy to reply in full now and I've realised now that I what I said could be misinterpreted. Hope I didn't upset anyone! Kind regards, David On 23 Sep 2014 17:44, Thomas Pfeiffer thomas.pfeif...@kde.org wrote: On Tuesday 23 September 2014 16:06:36 Stuart Jarvis wrote: What’s making this more confusing is that the VDG are now discussing branding some apps along the lines of ‘Made for…’ I'd be very concerned about this, for any but the most basic components deeply entwined in the desktop shell (e..g things like knetworkmanager etc). The 'by KDE' tagline used for Plasma surely works much better for anything else. Just to clear things up: Made for Plasma was just one idea of many for the name of this, which, because we're all aware of the implications, is unlikely to be chosen in the end. We still have not found a good name yet (the problem with by KDE is that it would naturally apply to all KDE applications, but what we're looking for is a name we'd only give to applications that fulfill certain criteria on top of being made by KDE). See the forum thread [1] for background and the current discussion. Input is still very much appreciated, as we're still kind of at a loss for a good name. Best, Thomas [1] https://forum.kde.org/viewtopic.php?f=285t=122926 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Give People Access to Great Technology - a possible vision
I wonder whether going forward we would be better served by asking the question of our users, 'What do you need KDE* to be for you?' Because essentially we are saying that with plasma 5 and kf5 it could be anything you want it to be. Maybe we should start by splitting this into commercial and consumer needs and take it from there. I know from my company that KDE would suit us as KDE for Windows would allow us to slowly shift over desktop apps first, before swapping out the o/s from underneath. We can't be the only company in a similar boat. *By KDE here im referring to the software, as I'm not sure what the term is for the amalgamation of plasma 5 / kf5 applications Ps. Typing this on my phone in a tent in Wales, UK, so sorry if it reads a bit disjointed. On 20 Sep 2014 22:00, Aaron J. Seigo ase...@kde.org wrote: On Saturday, September 20, 2014 10.15:56 Cornelius Schumacher wrote: On Friday 19 September 2014 19:04:53 Valorie Zimmerman wrote: On Fri, Sep 19, 2014 at 9:56 AM, Andrew Lake jamboar...@gmail.com wrote: Image: http://wstaw.org/m/2014/09/19/A_possible_vision.png I would say Plasma and Frameworks at the center. I think it's right to put the KDE desktop in the center in addition to the KDE frameworks. It's Plasma and the application which are our base and where we are coming from. It's this whole set which gives us the integration points we can use to expand to cloud, to devices, to other services. The desktop is a great starting point. Plasma was intended as a way to move beyond the desktop while retaining the desktop as a first class citizen, so that paragraph contains some irony. I use desktop in quotation marks because the end-user computing tasks performed on laptops and desktop computers have been moving to non-desktop form factors for some years now while the desktop type hardware has been slowly adopting some hardware characteristics of non-desktop devices. Fixating on the desktop is to bury one's head in the sand about that reality. Finally, the desktop has always been the primary focus. It has never not been the starting point. (Despite Plasma's goals.) This vision sounds like it comes from KDE circa 2005. Perhaps that's the goal, since as Andrew wrote, These thoughts are not intended to suggest an entirely new direction. However, this leaves me slightly stumped as to what the goal is here. Is it to remind KDE what it is, because that's been forgotten? Is it to reaffirm what KDE is as a means to pull back into its own center? -- Aaron J. Seigo ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Your mission, should you choose to accept it, is.....
Hi Peter, I did have the idea that I mentioned on here a while back of possibly setting up a job board, so people can apply for jobs, or submit their details (current occupation and experience etc.) if they're not sure where they would be useful, so they can be guided into certain areas. It would make promotion easier as well as you can just promote the one job, and one link. I think a more anonymous, and formal process might be better for some people, especially those with less confidence. There are software packages that can handle this kind of thing already; however it would be better if it were properly integrated into the kde.org website rather than another bolt on. I am currently trying to come up with a plan for consolidation the would take this sort of thing into consideration. There is also the problem that some of these things are more events than jobs, so again this is something that needs thinking about. Kind regards, David. On 11 Sep 2014 10:45, Peter Grasch pe...@grasch.net wrote: Hello everyone, some of us who missed the day trip today in Brno were discussing ways to get new or less proactive people involved with KDE. Right now, we are a community of very proactive, inner-directed people. We find something to do, or make up something to do that makes us happy. It would be great to have people who are not of this personality or those who have no idea where to start, to get a nice choice of what we know we need. The vague idea is to offer people descriptions of missions that they can take up, to lower the barrier of entry. What we have come up with is a proposal to reuse part of Brainstorm, and extend that in a new direction. We envision a unified place where developers aggregate missions of different size and scope. This place is meant to be the go-to place for people who want to get involved with KDE, accessible through a prominent get involved link on kde.org. The kind of missions we envision are: * Junior Jobs * GSoC, SoK, GCi * new team members wanted * specific areas needing attention * applications and libraries needing maintainers Brainstorm is a place for users to dream about cool stuff, and even vote up the ideas. What has been missing is developer buy-in, as we understand it. Right now there is a section in Brainstorm called In Development. What we are proposing is to launch Mission on the Forum as well. Project managers could close threads and link to the new Mission. This could also be a place to integrate idea generation for GSoC projects, Summer of KDE , even GCi tasks, possibly allowing users to rate them in importance. If we can get in the habit of doing this all year round, getting ready for GSoC, SoK, and GCi will be easier. We have our first mission, once this is created on the Forum: https://blogs.kde.org/2014/08/16/konqueror-looking-maintainer Valorie Zimmerman Michael Bohlender Heinz Wiesinger David Faure Peter Grasch ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] A change of heart
Yes, I'll be the first to admit that the software is not perfect. Regarding performance, I believe that's something they're actively working on improving, and the last update in April this year did a lot to address those issues (blog post here about it http://bpdevel.wordpress.com/2014/04/02/one-of-the-primary-focuses/). The wiki that's built-in with the commons is rubbish, no doubt about it. It's part of the more useful group documents feature. Interestingly I believe the CUNY website itself has MediaWiki embedded in it ( http://commons.gc.cuny.edu/wiki/index.php/Welcome_to_the_Academic_Commons_Wiki) which they do using this: http://dev.commons.gc.cuny.edu/2009/05/21/new-mediawiki-extension-wpmusinglesignon/ from what I can see. But more investigation would be needed. Spam is something I can't comment on really, but I'm sure there are options for that. Really the point is though, from a community standpoint, what direction is KDE headed at the moment? Where is it going to be in five years time? I'm sure KDE could continue with the current setup and happily tick along, tweaking things here and there, but is that progress? There is a goal with this, an aim, and that's to try and increase community participation, attract new and younger users (the developers of the future hopefully!), and more importantly to give people a reason to keep coming back! If we can do that then hopefully we can increase the donation amount, and generally encourage more people to contribute to KDE. Saying all that, it could be a huge, hated flop. ;-) On Wed, Aug 27, 2014 at 11:51 AM, Aaron J. Seigo ase...@kde.org wrote: On Wednesday, August 27, 2014 22.07:23 Ben Cooksley wrote: I have examined the forum solution they suggest using - bbPress - and it is much less featureful than our current forum software, phpBB. In addition it does not support nested forums, which we are quite dependent on to organise content (we have 51,203 topics with 244,596 posts at the time of writing this email). It is also questionable I've actually used CommonsInABox and while quite nice in some ways, its performance is pretty dismal, some of the feature sets (e.g. the wikis, if one can call them that) are very weak and protecting against spam accounts is next to impossible ... -- Aaron J. Seigo ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] A change of heart
Hi Ben, Sorry, I very rudely replied to Aaron before you. bbpress as far as I can remember has sub-forums, if that's what you are referring to? The compatibility must be OK as it is possible to import from phpBB ( http://codex.bbpress.org/import-forums/). We could test it out if you wanted? Regarding the multi-site aspect, I hadn't really considered the inclusion of developer blogs. I was more thinking of having a separate blog for each KDE project, and have all the relevant links and info for that project on there. Each project could have it's own theme and identity whilst still being under the networks umbrella. I think google would like that. There would be nothing stopping us have a dedicated RSS aggregation blog if needed, and use one of the many WP plugins there are around for this. This all needs to be tested really. On Wed, Aug 27, 2014 at 11:07 AM, Ben Cooksley bcooks...@kde.org wrote: On Wed, Aug 27, 2014 at 5:43 AM, David Wright david.wright12...@gmail.com wrote: Yes, this platform offers a number of benefits over the current one(s), and introduces some basic marketing tools that I feel are badly needed. Really though, the reason I am suggesting this is because as it stands the KDE 'community' is really a developer community, not a user one. That really needs to change if KDE wants to have more donations, for the obvious reasons. In fact, I was going to write a long piece about moving to a social network would attract young users etc, but this really is the key point. KDE presents a very corporate and stale image that is not inviting for users to participate in, or engage with. You are not going to get mass donations because there is nothing for a user to get emotionally involved with. In regards to the forum, we already have one at forum.kde.org and it is quite active. I have examined the forum solution they suggest using - bbPress - and it is much less featureful than our current forum software, phpBB. In addition it does not support nested forums, which we are quite dependent on to organise content (we have 51,203 topics with 244,596 posts at the time of writing this email). It is also questionable whether our Sphinx powered RSS feeds could be adapted to work under BuddyPress. Further, there are likely social problems with being a hoster for everyone's blogs (which is why it is planetkde.org not planet.kde.org) Kind regards, David Wright Thanks, Ben On Monday 25 Aug 2014 14:32:33 Jaroslaw Staniek wrote: +1 for Reply-By-Email! Forum.kde.org's anonymous notification can depress users that are AFK... On 25 August 2014 13:53, David Wright david.wright12...@gmail.com wrote: I did send this originally to the kde-www address but I thought I'd send it here as well for a bit of fun. Kind regards, David -- Forwarded message -- From: david.wright12...@gmail.com Date: 17 Aug 2014 00:24 Subject: A change of heart To: kde-www kde-...@kde.org Cc: Hi guys, I've been doing a bit of research lately on CMS's and stumbled across http://commonsinabox.org/ which is basically a bundled buddypress plugin which powers http://commons.gc.cuny.edu/ amogest other. Given the social nature of this setup, and the fact it is built upon wordpress (it is basically a set of wordpress plugins that have been tested together), I felt that this might be something that KDE might like to take under consideration? A standard install would include forums, groups, collaborative docs, social @ mentions, user profiles etc, etc. Also, using the multi user aspect of wordpress it would still allow certain projects to keep their identity, but remain under the networks umbrella, as evidenced by: http://helpwanted.commons.gc.cuny.edu/ Naturally, being exposed then to the wordpress plugin ecosphere would allow then a better integrated events management, job board, even a store if desired. Ultimately though, the goal is to increase funding. The KDE websphere is too spread out, and this would help reign it in so we can really do focused funding campaigns on users. That would be the advantage of the groups, as we could tailor funding drives to particular interests and hopefully have better success. Administration might also be made easier as we could get rid of a fair few subdomains by moving to this kind of platform. Anyway, it's late, and I'm jabbering. Let me know what you think! :-) ps There is also a buddypress app that could be rebranded: https://github.com/yuttadhammo/buddydroid Mozilla were also working on bugzilla intergration a while back: https://bugzilla.mozilla.org/show_bug.cgi?id=643570
[kde-community] A change of heart
I did send this originally to the kde-www address but I thought I'd send it here as well for a bit of fun. Kind regards, David -- Forwarded message -- From: david.wright12...@gmail.com Date: 17 Aug 2014 00:24 Subject: A change of heart To: kde-www kde-...@kde.org Cc: Hi guys, I've been doing a bit of research lately on CMS's and stumbled across http://commonsinabox.org/ which is basically a bundled buddypress plugin which powers http://commons.gc.cuny.edu/ amogest other. Given the social nature of this setup, and the fact it is built upon wordpress (it is basically a set of wordpress plugins that have been tested together), I felt that this might be something that KDE might like to take under consideration? A standard install would include forums, groups, collaborative docs, social @ mentions, user profiles etc, etc. Also, using the multi user aspect of wordpress it would still allow certain projects to keep their identity, but remain under the networks umbrella, as evidenced by: http://helpwanted.commons.gc.cuny.edu/ Naturally, being exposed then to the wordpress plugin ecosphere would allow then a better integrated events management, job board, even a store if desired. Ultimately though, the goal is to increase funding. The KDE websphere is too spread out, and this would help reign it in so we can really do focused funding campaigns on users. That would be the advantage of the groups, as we could tailor funding drives to particular interests and hopefully have better success. Administration might also be made easier as we could get rid of a fair few subdomains by moving to this kind of platform. Anyway, it's late, and I'm jabbering. Let me know what you think! :-) ps There is also a buddypress app that could be rebranded: https://github.com/yuttadhammo/buddydroid Mozilla were also working on bugzilla intergration a while back: https://bugzilla.mozilla.org/show_bug.cgi?id=643570 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
