So, tomorrow I will create a google group and look at the options of a
google code site.
I am a bit in a hurry - my kids are waiting ;)
Cheers, Jan-Peter
Am 10.01.2013 12:30, schrieb Urs Liska:
Am 10.01.2013 09:33, schrieb Jan-Peter Voigt:
Hello Urs,
Am 09.01.2013 um 17:31 schrieb Urs Liska:
Am 09.01.2013 13:48, schrieb Jan-Peter Voigt:
Am 09.01.2013 um 11:55 schrieb Urs Liska:
Am 09.01.2013 09:13, schrieb Jan-Peter Voigt:
I really would like to discuss this stuff with other ponders -
but this list should'nt be spoiled with such discussions and
scare new users with intimate scheme-expressions ...
If we would find a place to meet, we could prepare either
documentation material for lilypond.org or for another lilypond
related site. This might be <lilypond-de...@gnu.org>? But I also
don't want to distract important development work in the basement!
If it really comes to a collaborative project I suggest setting up
a dedicated mailing list.
Github doesn't provide mailing lists, so we should have another
one elsewhere.
Any suggestions anyone?
with the "Posaunenchor" (brass band), I used to play with, we
connected/organized with google groups. If all interested ponders
are on facebook, a group could be formed there ... both solutions
are a bit scary IMO ;)
but it should be functional ...
From those options I'd prefer Google over Facebook. Not less scary,
but I'd consider Google more as a platform for actually _work_
together (although this might be strictly emotional ...).
I would'nt say its emotional ;) FB is always scattered with ads and
really unimportant jokes - so its a playground and it is *not*
mailing list. I've just heard of people using it in such a way and it
seems, almost anybody has an account.
Thanks for pinning this down concisely ;-)
Is it possible to integrate a Google group with Google's issue
tracker (as I find Github's issue tracker somewhat too simplistic)?
I don't know, but it seems, google services are quite integrated.
That's what one has come to reasonably expect, and probably it's also
true for our case.
So I suggest to create a Google Site (I can do that).
From the templates I have the impression we could use 'Project work
site' or 'Project Wiki', but I can't see the relevant differences
right now (and I don't know yet to what extent the site can be
configured afterwards anyway).
Obviously Google Groups are directly integrated with a site (click on
"Join our discussion" on the starting page of the Project Wiki
preview), so this seems a good choice.
'Project work site' has an issue tracker, but maybe one can also add
this to any other template ...
Do we actually need a _group_? Wouldn't a mailing list be enough?
Francisco already said it, I think ... google groups acts like a
mailing list with integrated archive. One maintainer/admin needs a
google account, the members can access it with any address.
So, shall we make a google group? I do have an infrequently used
google account and could create a group.
OK, that would be nice.
Would you mind also to create a tracker on Google Code (or check what
options we'd have with a tracker within a Google Site)?
Best
Urs
Cheers, Jan-Peter
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
