Hi Rafael,
First, it would be great to have our conversations publicly on the
mailing list: it would help others to jump in if needed.
On Wed, 2012-05-02 at 21:09 -0430, Rafael Dominguez wrote:
Hi Cedric, sorry i been away for a weeks or so, now im back to work on
the gsoc task. I probably wont be able to connect to IRC in the same
hours as you, since im on -4:30 GTM time and you guys are mainly on
the european time.
Sure, but as I mentioned in my previous email, we need to find a way to
be on IRC at the same time (not necessarily the whole day).
We didnt have the chance to talk about my timeline for the project,
but i guess you approve it. Any review or a potential issue you think
i should work on, please tell me.
See my ideas in the previous email.
Well as first point on the agenda, is to get a working design before
the coding phase starts, which im not mistaken is at 21st. So ill work
with the UI designers on that.
Mirek is the guy to talk to on the design mailing list. You should also
have a look at this wiki page:
https://wiki.documentfoundation.org/Design/Templates_and_documents_rework
One question, to use the CMIS code is through which component???? Any
code pointer or documentation about that is really welcome???
For the CMIS connection, I have started to implement a C++ client
library, libcmis (http://sourceforge.net/p/libcmis/). I already started
to integrate it into LibreOffice, but there is still some work to be
done.
The main point to get here is that you'll only need to provide proper
URLs to open the document. We may need to implement a search feature in
libcmis, but again, we can map it all to URLs.
Can we start coding before 21st???
Officially no. But you can already have a look at the code to get an
idea how to do things, get a more precise estimation of your schedule,
etc. I don't really mind if you start earlier, but don't shout it all
over the place ;)
Better take this period as an occasion to prepare your project both on
the human relationship and code knowledge aspect. Among the things to
check before this day:
* having a master build ready to get started
* having a git account
I may be repeating, but you will work directly on the libreoffice
repository, in a feature branch that will be merged from time to time in
master. Your feature will be enabled only with experimental features:
this way you'll have an easy way to allow people (even non developers)
testing your work. At some stage it will be probably good to involve
somebody from the QA team to help you improve your work.
I hope this is not too much information in a single shot ;)
Regards,
--
Cedric
On Wed, May 2, 2012 at 4:58 AM, Cedric Bosdonnat <cbosdonnat@suse.com>
wrote:
Hi Rafael,
BTW I'm CCing Fridrich, the other GSoC admin, to log the
conversation.
Having been selected and having already provided patches to
LibreOffice
doesn't mean that everything is OK for your Google Summer of
Code.
You should email the list and/or your mentor (i.e. me) about
your
availability at least and to get started. The guys from the
Design team
are already ready to work with you for your project... it
would be good
to show them that you are ready to start too.
REMINDER: don't forget that if you haven't established a good
contact
with the community before May 21st, I'll need to report it to
Google and
you would be out of GSoC 2012 (i.e. you wouldn't even get the
first 500
USD payment)
I really hope to have a great summer working on that nice
project with
you.
Regards,
--
Cedric
Context
- Re: [GSoC] Keeping silence during the first weeks isn't good · Cedric Bosdonnat
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.