On 2019-03-30 15:47, Christian Grothoff wrote:
On 3/28/19 4:01 PM, z...@hyper.dev wrote:
I would like to build an application on top the DHT
and FS. I want to know what are the privacy features.
For instance, can someone know that I downloaded a
particular file? can someone know that I am
On 4/7/19 6:46 PM, Schanzenbach, Martin wrote:
> The CAA does not help in any way. You are still liable as a platform. It has
> literally nothing to do with the copyright infringements if the contributor
> copied code from somewhere else. You cannot delegate this responsibility
> anymore to the
> On 7. Apr 2019, at 13:36, Christian Grothoff wrote:
>
> On 4/7/19 11:11 AM, Schanzenbach, Martin wrote:
On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
> Contributors should be able to do anything they want in their own
> namespaces including committing code that does not compile
On 4/7/19 11:11 AM, Schanzenbach, Martin wrote:
>>> On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
Contributors should be able to do anything they want in their own
namespaces including committing code that does not compile (e.g. for
their gnunet.git forks). However, in order to get
On 4/7/19 1:14 PM, Schanzenbach, Martin wrote:
> As I said in another mail you are fighting windmills here. Given that we have
> a mandatory CAA, that is where the gatekeepers come in anyway.
> And the problems you claim here are also exiting there.
Signing the CAA isn't really imposing
> On 7. Apr 2019, at 12:47, Florian Dold wrote:
>
> On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
>> Contributors should be able to do anything they want in their own namespaces
>> including committing code that does not compile (e.g. for their gnunet.git
>> forks).
>> However, in order to
Some more detailed arguments for the point I was making:
http://lisperator.net/blog/pull-request-based-development-sucks/
I really like that with GitLab we have to *possibility* to do code
review, but we shouldn't force it down everybody's throat for GNUnet.
- Florian
On 4/7/19 12:47 PM,
On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
> Contributors should be able to do anything they want in their own namespaces
> including committing code that does not compile (e.g. for their gnunet.git
> forks).
> However, in order to get it into the "main" gnunet project codebase, the CI
>
> On 7. Apr 2019, at 11:11, Schanzenbach, Martin
> wrote:
>
>
>
>> On 7. Apr 2019, at 11:02, Christian Grothoff wrote:
>>
>> On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
>>> Contributors should be able to do anything they want in their own
>>> namespaces including committing code that
> On 7. Apr 2019, at 11:02, Christian Grothoff wrote:
>
> On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
>> Contributors should be able to do anything they want in their own
>> namespaces including committing code that does not compile (e.g. for
>> their gnunet.git forks). However, in order to
On 4/7/19 8:33 AM, Schanzenbach, Martin wrote:
> Contributors should be able to do anything they want in their own
> namespaces including committing code that does not compile (e.g. for
> their gnunet.git forks). However, in order to get it into the "main"
> gnunet project codebase, the CI must
> On 6. Apr 2019, at 21:47, Florian Dold wrote:
>
> Signed PGP part
> Thanks for taking the time to set this up. So far some things don't
> seem right yet:
>
> There is a massive security problem. Everybody (!!) is able to create
> accounts and set their password, *without* being the owner
12 matches
Mail list logo
