[ccan] Accpeting code module

[Adam Kennedy]

Something like that could make sense too.

Typical problems that CPAN encounters are that we expect accounts to
be humans, and sometimes people create registrations that aren't.

Also, people seem to like to change their logins all the time because
they changed their nick or something, and that can hurt.

Some of this isn't a problem is we retain more power to stamp down on
people if needed.

The confirmation thing could work though.

Let them upload initially, but until they are confirmed nothing ever
gets indexed, and we can still reject the application.

Something like just tagging the account as "provisional" could work well.

Adam K


2008/6/8 Rusty Russell <rusty at rustcorp.com.au>:
> On Friday 06 June 2008 18:47:46 dinesh g wrote:
>> Hi Rusty,
>>
>> I have developed some basic front end.  Going to start developing backend.
>> I have a doubt regarding registration for developer.
>>
>> If a developer want to register, developer will request for account id
>> through a form similar to CPAN. Should each request for ccan account, some
>> one has to approve it, for that developer to become the member?
>
> I'd prefer them to be able to register and upload without human interaction,
> but perhaps keep uploads from unconfirmed users somewhere aside until they
> are confirmed?
>
> We want to make it as easy as possible for people to contribute code.
>
> BTW, we should probably arrange weekly meetings on #ccan on irc.freenode.net:
> what time suits you?  If nothing better, how about 1:30pm Monday here
> (Australia/Sydney) which is 9am in India I think?
>
> Cheers,
> Rusty.
> _______________________________________________
> ccan mailing list
> ccan at ozlabs.org
> https://ozlabs.org/mailman/listinfo/ccan
>