<div class="gmail_extra">But I am sure the dates should not really pose a threat and we should be able to sort that out. <br><br><div class="gmail_quote">On Tue, Apr 24, 2012 at 9:38 PM, viraj sinha <span dir="ltr"><<a href="mailto:virajssinha@gmail.com" target="_blank">virajssinha@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">I agree with michael's idea and it would be great to have inter instance collaboration along with other extensions to OCS API . Would love to build use cases for the whole project with Bartek and Frank. Just some date problems because I have my lab exams now and end semesters from May 7 but I will be free from May 25. <br>
So what is your take on this?<div><div class="h5"><br><div class="gmail_quote">On Tue, Apr 24, 2012 at 9:24 PM, Alessandro Cosentino <span dir="ltr"><<a href="mailto:cosenal@gmail.com" target="_blank">cosenal@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(adding again Viraj's address, which got lost in the last replies)<br>
<br>
Integration with Dolphin sounds cool!<br>
<br>
Well, I don't think doing the project as Season of KDE student is a bad idea.<br>
I was a Season of KDE student last year and I am happy with that decision.<br>
First, under Season of KDE you are forced to structure more your<br>
timeline and meet deadlines. After all, it's still a commitment.<br>
Second, you get goodies and certificate (well, I actually still have<br>
to get those :P). It might sound stupid, but somehow it's motivating<br>
and it's something you can write on the CV.<br>
Finally, it prepares you for next years GSoC.<br>
<br>
Obviously, what matters mostly is inner motivation.<br>
<span><font color="#888888"><br>
Alessandro<br>
</font></span><div><div><br>
On Tue, Apr 24, 2012 at 11:44 AM, Frank Karlitschek <<a href="mailto:frank@owncloud.org" target="_blank">frank@owncloud.org</a>> wrote:<br>
><br>
> On 24.04.2012, at 17:15, Michael Gapczynski <<a href="mailto:mtgap@owncloud.com" target="_blank">mtgap@owncloud.com</a>> wrote:<br>
><br>
>> Viraj,<br>
>><br>
>> Sorry about GSoC. Don't think that you need to apply to Season of KDE to work<br>
>> on ownCloud. We always want more contributors and are more than willing to<br>
>> help out.<br>
><br>
> Exactly :-)<br>
><br>
><br>
>> I believe the improvements to the OCS API should also include the inter<br>
>> instance collaboration project, so we can have outside sources communicating<br>
>> with apps.<br>
><br>
> Agreed!<br>
><br>
><br>
>><br>
>> Michael<br>
>><br>
>><br>
>> On Tuesday, April 24, 2012 04:42:15 PM Frank Karlitschek wrote:<br>
>>> On 24.04.2012, at 16:04, viraj sinha <<a href="mailto:virajssinha@gmail.com" target="_blank">virajssinha@gmail.com</a>> wrote:<br>
>>>> Hello ,<br>
>>>><br>
>>>> My name is Viraj Sinha. I had applied for GSoc 2012 for owncloud dolphin<br>
>>>> integration but didn't get selected. I really wanted to contribute to<br>
>>>> owncloud and kde so I had a chat with Bartek Przybylski . He helped me<br>
>>>> a lot and suggested that first we should think of a protocol for<br>
>>>> owncloud to link with file managers as the existing process using<br>
>>>> webdav is too complicated . I would really like to work on this, as the<br>
>>>> idea is pretty interesting and niece , along with Bartek. This could<br>
>>>> make the process so easier and fun.Can I submit this as an idea for<br>
>>>> kde-soc 2012 and Bartek can guide me as he has already helped me a lot?<br>
>>>> Do let me know guys please as I am really interested to work on it this<br>
>>>> summer.<br>
>>> Hi Viraj,<br>
>>><br>
>>> I´m sorry that you are not selected.<br>
>>> It would be really awesome if you could work on the dolphin integration.<br>
>>><br>
>>> I agree with Bartek that we need a special API for that. We want to use<br>
>>> WebDAV for all the file access stuff. But if we want to add action to<br>
>>> dolphin like "share with.." or "show versions of .." or "send public link<br>
>>> to..." then we need special calls for that of course. I suggest to add to<br>
>>> to the existing OCS API that´s already implemented in ownCloud. This is a<br>
>>> RESTfull API that we have to extend for the new features that you need.<br>
>>> Than we can extend libattica in KDE to support this new call and then we<br>
>>> just have to use this calls in dolphin.<br>
>>><br>
>>> I can help you with that part together with Bartek of course :-)<br>
>>><br>
>>> I think the next logical step would be to look at the use-cases that we want<br>
>>> to cover with the Dolphin integration and then design the API calls<br>
>>> accordingly. I can also help with that.<br>
>>><br>
>>> Does this make sense?<br>
>>><br>
>>><br>
>>><br>
>>> Cheers<br>
>>> Frank<br>
>>> _______________________________________________<br>
>>> Owncloud mailing list<br>
>>> <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
>>> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
>> _______________________________________________<br>
>> Owncloud mailing list<br>
>> <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
><br>
> _______________________________________________<br>
> Owncloud mailing list<br>
> <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br>Regards<br><br>Viraj Sinha<br>Mitbuzz Developer<br>Third Monkey Labs<br>Dept of Comp Sc<br>MIT,Manipal<br><br>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Regards<br><br>Viraj Sinha<br>Mitbuzz Developer<br>Third Monkey Labs<br>Dept of Comp Sc<br>MIT,Manipal<br><br>
</div>