Re: [GNUnet-developers] Communication

2015-01-16 Thread Lluís Batlle i Rossell
Hello gpg signers, I take the oportunity to insist once again that seeing the developers actually use gnunet for something would be a very good marketing for new users to come and test the software, be it releases or trunk. Providing a tarball, and expecting other people to gather and start to sh

Re: [GNUnet-developers] Communication

2015-01-16 Thread Christian Grothoff
On 01/16/2015 10:16 AM, Ludovic Courtès wrote: > Bart Polot skribis: > >> I agreed, we should start dog-fooding as soon as it's ready: use >> gnunet-conversation + multicast (!) instead of mumble. > > Dog-fooding means precisely that you don’t wait until it’s “ready”. ;-) Well, but I think it

Re: [GNUnet-developers] Communication

2015-01-16 Thread Ludovic Courtès
Bart Polot skribis: > I agreed, we should start dog-fooding as soon as it's ready: use > gnunet-conversation + multicast (!) instead of mumble. Dog-fooding means precisely that you don’t wait until it’s “ready”. ;-) I’ve had my share of dog food with Guix, and I think it’s very valuable. It wo

Re: [GNUnet-developers] Communication

2015-01-11 Thread Matthias Wachs
On Sat, 2015-01-10 at 15:57 -0300, hellekin wrote: > Seconded. It's important for the community to see how GNUnet is > evolving and how non-developers can help. For example, more people > knowing about the need to hire hackers means more coverage and more > candidates. Also, a more lively mailin

Re: [GNUnet-developers] Communication

2015-01-10 Thread Eric Wong
Ludovic Courtès wrote: > Hello GNUnetters! > > FWIW, as an external observer, I would love to see more of the > discussions around you take place on this list, be it high-level design > discussions or patch review. Fully agreed as another external observer! I also prefer using email as it is te

Re: [GNUnet-developers] Communication

2015-01-10 Thread Bart Polot
I agreed, we should start dog-fooding as soon as it's ready: use gnunet-conversation + multicast (!) instead of mumble. However this is quite far-fetched (I'd say months), since multicast is far from done and gnunet-conversation as it is right now is point-to-point only (disregarding the current ca

Re: [GNUnet-developers] Communication

2015-01-10 Thread hellekin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Seconded. It's important for the community to see how GNUnet is evolving and how non-developers can help. For example, more people knowing about the need to hire hackers means more coverage and more candidates. Also, a more lively mailing list / c

Re: [GNUnet-developers] Communication

2015-01-10 Thread Christian Grothoff
On 01/10/2015 05:44 PM, Matthias Wachs wrote: > On Fri, 2015-01-09 at 19:52 +0100, Christian Grothoff wrote: >> I think it wouldn't hurt to have it rotate a bit between days, that way >> it won't always be the same person with a conflict who can't make it. >> So something like 8pm on the 2nd and 15

Re: [GNUnet-developers] Communication

2015-01-10 Thread Matthias Wachs
On Fri, 2015-01-09 at 19:52 +0100, Christian Grothoff wrote: > I think it wouldn't hurt to have it rotate a bit between days, that way > it won't always be the same person with a conflict who can't make it. > So something like 8pm on the 2nd and 15th of every month would give us > bi-weekly, but ot

Re: [GNUnet-developers] Communication

2015-01-10 Thread Matthias Wachs
On Sat, 2015-01-10 at 15:02 +0100, Ludovic Courtès wrote: > Hello GNUnetters! > > FWIW, as an external observer, I would love to see more of the > discussions around you take place on this list, be it high-level design > discussions or patch review. > > I think the added transparency would be a b

Re: [GNUnet-developers] Communication

2015-01-10 Thread Ludovic Courtès
Hello GNUnetters! FWIW, as an external observer, I would love to see more of the discussions around you take place on this list, be it high-level design discussions or patch review. I think the added transparency would be a bonus both for you who are already involved in the process, and for lurke

Re: [GNUnet-developers] Communication

2015-01-09 Thread Christian Grothoff
I think it wouldn't hurt to have it rotate a bit between days, that way it won't always be the same person with a conflict who can't make it. So something like 8pm on the 2nd and 15th of every month would give us bi-weekly, but otherwise slightly irregular dates. Let's try that. On 01/09/2015 05

Re: [GNUnet-developers] Communication

2015-01-09 Thread Matthias Wachs
So I like the idea of having a mumble so everyone can talk about news, what he is doing, questions, discussions etc. These sessions must not take hours, that's not a requirement at all ... and for me it's not about reporting what people did and justification, it's more a possibility to learn what

Re: [GNUnet-developers] Communication

2015-01-09 Thread Sree Harsha Totakura
On 01/09/2015 03:19 PM, Matthias Wachs wrote: > What do you think about a regular developer (weekly/bi-weekly/monthly) > mumble to talk about latest news and what people are working on? I'd like to participate, but I doubt how long we can keep having them. Anyway, the only way to find is to try th