--===============0558036516==
Content-Type: multipart/signed;
  boundary="nextPart1330178.7mfJ1z3Pzx";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1330178.7mfJ1z3Pzx
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 16. March 2009 23:57:13 Thomas Zander wrote:
> Bottom line; I want to feel you are already aware on a global
> implementation level of how this is going to work. If you are fresh at the
> koffice codebase then this project is just too big for a GSoC.
>
> If you have a proposal of working on something that doesn't come so close
> to what others are also working on (text/odf/change-tracking), that would
> have my preference.

Someone asked me off-list to elaborate on this; fair enough :)
As PiereSt mentioned there are two approaches; I was actually only aware of=
=20
the one that is storing differences. Which is an approach I think is most=20
valuable for our long term goals (which include collaborative editing[1])
In line with that thinking I have to say that it doesn't make much sense to=
=20
have the GSoC depend on not-yet-written code that PierreSt wants to create.=
=20
And as long as you two don't sit in the same office I think working on the=
=20
same concepts just doesn't work.

In KOffice2 we have made the power of adding feature via plugins much more=
=20
clear than it ever was.  For that reason I think we should try to get any=20
GSoC working on projects they can do in a plugin. This is much better for=20
starting developers as they can work on their own pace and avoid depending =
on=20
others or others on them.
I'd like to keep the amount of people working on the core apps+shapes down =
as=20
communication and coordination is essential. Or at least a clearly shared=20
vision. Which I don't expect new SoC students to pick up immediately.

A great example of a successful project is the musicShape.  Its maybe even=
=20
something that one might want to continue working on :)

Hope that helps!

1) http://wiki.koffice.org/index.php?title=3DCollaboration
=2D-=20
Thomas Zander

--nextPart1330178.7mfJ1z3Pzx
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkm/kVMACgkQCojCW6H2z/TXbgCgn6+gEdlm3OWdeDvMu/EQFeKz
W6sAniQmjgC6Zzp4S8VMhnqAg8IVhuiK
=uVOB
-----END PGP SIGNATURE-----

--nextPart1330178.7mfJ1z3Pzx--

--===============0558036516==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============0558036516==--