[Owncloud] Is Owncloud still a KDE project? - Was: Re: Business and Backup Sprint in Zurich - Oct 21 to 23

Cody Rose cody at killsudo.info
Mon Sep 26 09:14:31 UTC 2011


> I think it's a horribly excluding attitude by the otherwise appreciated
> sys-admins. We are a kde-project but we're also something else.
> What about getting the "full kde-package" which is sort of silly and just
> place a link in git to gitorious? It's silly but really the "It's all or
> nothing" is also silly.
> Otherwise asking the KDE ev. would also be a possibility - we are kind of a
> new project.

The KDE Sysadmin's do not write the policy but only enforce it. Second of all 
the policy was created by KDE e.V. which is made up of all the KDE Developers.

The policy exists to ensure that ALL KDE projects are in ONE place. Period.

This makes life so much simpler for distribution packagers and users alike. 
You would not enjoy the results if each distro packager had to go hunting for 
the latest code / release in 100 different repo's all over the web. This allows 
for code security in that each packager can be sure he is grabbing the real 
deal for his users. The policy also allows KDE to track all code contributions 
for licensing purposes to ensure that the proper people are credited and if a 
licensing issue ever arose that KDE e.V. can attempt to reach every last KDE 
developer is a timely fashion.

The policy also means that any new OwnCloud developer would have git access 
for more then just OwnCloud. They benefit by being able to contribute to all of 
KDE in one central place if they so choose. Otherwise they can register as a 
KDE developer and only contribute to Owncloud if that is all they would like 
to do. This is turn benefits KDE developers, packagers, users, e.V. etc but 
basically the entire KDE eco-system benefits from this policy.

As a person that financially contributes to KDE e.V. I welcome this policy and 
do not want to see any 'special privileged' project that gets to benefit from 
my donation but doesn't conform to the rest of KDE standards. It is always 
easier to say NO then allow for a special exception. It's never just one 
special exception because eventually another will pop up.

I do not see how a KDE git repo restricts users in any way. You can freely 
pull any project from anongit.kde.org and any user is welcome to register as a 
KDE dev or submit a patch on this ML if he/she feels it is a one time 
contribution. The long term hope is that the one time contributor will see the 
value of becoming a KDE developer and in the future contribute to other KDE 
projects.

Regards,
 
Cody Rose
Datacenter NOC & Sys Admin

> 
> On 26-09-2011 10:10, Cody Rose wrote:
> > Is Owncloud still a KDE project or did you guys finally decide against
> > remaining a 'KDE' project?
> > 
> >> * contacting/coordinating with KDE e.V. for travel allowance (what about
> >> food?)
> > 
> > I don't think this will be much help if Owncloud decided to remove itself
> > as a KDE project.
> > 
> > Also if Owncloud is on its own has anyone coordinate with getting a new
> > Mailing-List setup for October 1?
> > 
> > Regards,
> > 
> > Cody Rose
> > Datacenter NOC&  Sys Admin
> > 
> >> Re: [Owncloud] Notice concerning use of KDE Infrastructure and move to
> >> Gitorious
> >> 09/02/11 3:17 AM
> >> 
> >> Hi,
> >> 
> >> Unfortunately that won't be possible. You can not randomly pick KDE
> >> infrastructure items you like and only use them. It's all or nothing.
> >> You can't say that you are 'still KDE afterall' when you just decided
> >> to move to gitorious.
> >> 
> >> Besides that, this is confusing for both developers and users.
> >> 
> >> Tom Albers
> >> KDE Sysadmin
> >> Hi Tom,
> >> 
> >> we no longer need the kde git repo and bugzilla.
> >> But we would still like to use the mailinglist. We are still KDE
> >> afterall. :-)
> >> 
> >> Not sure about the wiki pages at the moment. We will look into this.
> >> 
> >> Sorry for the confusion.
> >> 
> >> Cheers
> >> Frank
> >> 
> >> On 02.09.2011, at 09:57, Tom Albers wrote:
> >>> Hi Frank,
> >>> 
> >>> That means we close the owncloud bugtracker, mailinglist,
> >>> wiki-pages, etc. Shall we pick a date for that, assuming you need
> >>> a bit of time to move stuff over.. Let's say october 1st?
> >>> 
> >>> Best,
> >>> 
> >>> Tom Albers
> >>> KDE Sysadmin
> >>> 
> >>> ----- Oorspronkelijk bericht -----
> >> 
> >> Hi all
> >> 
> >> Real life (tm) has been quite busy lately. That's why it has taken a bit
> >> longer than planed to get to you with news about the owncloud sprint in
> >> Zurich.
> >> So far 5 ownclouders and 3 "externals" (including myself) have confirmed
> >> their attendance. If you plan to come but haven't added yourself to the
> >> doodle yet, please do so now
> >> http://www.doodle.com/kxq9ye85bu52niyg
> >> 
> >> The hacking room is reserved and I'm currently looking for beds and
> >> sofas for you to sleep. So far so good.
> >> 
> >> Now I need your help to work out the details, including...
> >> * contacting/coordinating with KDE e.V. for travel allowance (what about
> >> food?)
> >> * planing the schedule (where/how do we do that? Titanpad?)
> >> * all the things I haven't though about yet (I have no experience in
> >> organizing sprints)
> >> 
> >> Thanks in advance
> >> Cheers
> >> Pascal
> >> _______________________________________________
> >> Owncloud mailing list
> >> Owncloud at kde.org
> >> https://mail.kde.org/mailman/listinfo/owncloud
> >> 
> >> 
> >> _______________________________________________
> >> Owncloud mailing list
> >> Owncloud at kde.org
> >> https://mail.kde.org/mailman/listinfo/owncloud



More information about the Owncloud mailing list