| 1 |
BCCing gentoo-dev - please do not reply on -dev - I'm moving this to |
| 2 |
-project. |
| 3 |
|
| 4 |
On 04/01/2010 11:59 AM, Vincent Launchbury wrote: |
| 5 |
> Google may be fine now, and fit perfectly. But in the long term, I'd |
| 6 |
> agree that developing our own calendar would be a good idea. If there |
| 7 |
> isn't a decent free solution out there already, then developing one from |
| 8 |
> scratch would likely help out other projects too. |
| 9 |
> |
| 10 |
|
| 11 |
I think that iCal is really our biggest stumbling block - whenever |
| 12 |
anybody points out that there is no good FOSS group calendaring solution |
| 13 |
available all the zealots point to a bunch of programs that can |
| 14 |
read/write ical, neglecting the fact that these programs usually have no |
| 15 |
collaborative capabilities whatsoever. |
| 16 |
|
| 17 |
Personally I have no problems with leveraging Google tools, but only for |
| 18 |
non-essential matters and for document creation. Final documents should |
| 19 |
be placed on the website in an open format (preferably just as website |
| 20 |
content). So, if QA wants to write out a set of policies and do it |
| 21 |
using Google docs, that is fine, as long as devs aren't expected to use |
| 22 |
Google docs to read the policies once they're ready to be followed. |
| 23 |
|
| 24 |
I did link my g.o email to my gmail account, so anybody needing to share |
| 25 |
a document or whatever with me should be able to do so in this way. |
| 26 |
|
| 27 |
Rich |
Archives