[AfrIPv6-Discuss] [Fwd: [arin-announce] Seeking IPv6 Trainers and Consultants]

Willy Ted MANGA willy.manga at auf.org
Sun Jan 31 18:57:19 UTC 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Le 26/01/2016 10:57, Daniel Shaw a écrit :
> 
>> On Jan 26, 2016, at 11:05 AM, Mukom Akong T. 
>> <mukom.tamon at gmail.com> wrote:
>> 
>> Here's who this could work with a community driven platform
>> 
>> a) Create the platform (e.g. wiki) --- I'm sure AFRINIC won't
>> mind putting hosting one b) Various experts & consultants
>> contribute content - how tos, deployment experiences, case
>> studies etc (thereby building reputation and credibility) c) Have
>> a page on that platform for "Consultants/trainers directory”
> 
> Basically agreeing with Mukom here. I believe hosting a Wiki
> specific to IPv6 discussion and collaboration within our region
> would not be an issue. But..
> 
> … also concur that this would not and could not include any kind
> of endorsed or “certified” data/info.
> 
> It’d simply be a platform for *community* contribution.

It should be clearly understood by all contributors *and* readers .

This kind of platform can be useful if and only if we are all commited
to contribute.

> [...] So, if this was to work, it would need to a) have some 
> posting/contributing guidelines and rules that are clearly
> published. And b) some community folks to maintain the policies,
> and moderate the site too.

Concerning the contents themselves, they can be placed under a
creative Common license that all should agreed.


> I don’t see either of these things being the responsibility of 
> AFRINIC staff. It’s more in line with building a community and an 
> open and bottom up processes for the regional IPv6 community (i.e. 
> this list) to come up with both a) and b) above.

Agreed .

> [...] 2. Should there be enough interest, this list/community would
> then agree on a number of admins/moderators for this future site.
> To allow for a moderator/admin to be sick, go on leave, have work 
> responsibilities and/or a life, this would need to be two or
> greater. I’d personally suggest at least three, but no more than 4
> or 5. Both the number, and the candidates would be up to the list
> though. Possibly, likely candidates could be nominated on the list,
> and if they have some support and no negative votes after a given
> time period, and they agree to it, then they’re it!

Those who are interested could stand themselves.

> 3. Should we (the list) get to the point where there are
> sufficient moderators nominated *and* that have agreed to take on
> the responsibility of looking after a wiki, then that group could
> get in touch with myself off-list, and I would be happy to
> facilitate AFRINIC hosting a VM running a Wiki. AFRINIC would
> provide the a VM, the IP addresses (v4 + v6), the DNS name, etc.
> AFRINIC would install the needed software, and then add the
> community agreed group of admins with full privileges within this
> Wiki application. At this point AFRINIC would completely step away
> from managing the actual content in any way. AFRINIC would only
> maintain basic monitoring of the VM, keep it up and running and
> co-ordinate with the Wiki admins to schedule OS patches. It would
> also be up to the moderator group to decide on the exact Wiki
> software to install, in consultation with AFRINIC technical staff.

Here I think they should be a timeline with an end term on the
availability of this wiki. Maybe 2 years ? It can be renewed but it's
important to know after a period if it's still accurate and well
maintained.
This availabilty should apply to the admin/moderators too.


> 4. Once the blank Wiki was available, initially only the 
> admin/moderator group would have access, and before any other
> content was added, they’d be responsible for drafting Acceptable
> Use Policy, Privacy Policy, Contribution guidelines, perhaps
> document the process to nominate and decide on future moderators,
> rules around registration etc. (for example, I’d suggest it
> mandatory for folks who’d want to contribute to register with real,
> full names). Each of these pages/policies need not be too long. The
> ARIN wiki is a good example. All of these could be edited on the
> live Wiki I think, provided they're clearly marked as drafts.

Yes, the best process is to write these policies on the wiki itself.
They should not be too long. They can be discussed in this list but we
should not spend too much time on that purpose.



> 5. Once the policies and rules are in place, and the list has had
> a chance to read and agree on them; then before being taken out of 
> draft status, we’d have senior AFRINIC staff and/or AFRINIC
> publicity staff look over the proposed policies and make sure
> there’s nothing that puts AFRINIC as an organisation at any risk. I
> don’t expect that to be an issue, but having this vetted would
> likely be a required part of hosting it within the afrinic.net
> domain. I’d also think that part of these pages would document that
> the community chose moderators would remain responsible for keeping
> the Wiki clean of spam, any insulting comments or trolling and so
> on. And I’d probably ask that there be something added that says
> something along the line of "should the Wiki become unmaintained,
> very out of date, full of spam, etc., that AFRINIC would reserve
> the right to shut it down."

That's why I was talking above of an end term of the team of
administrators and even for the wiki platform itself.

> 6. At this point all the rules and guidelines would have been
> agreed on by the community *and* AFRINIC staff. And thus would be
> taken out of draft status, and the Wiki opened for registration
> and contributions. It would be up to the moderator/admin group to
> guide the structure of the Wiki and manage the sort of content
> allowed.


It's not IPv6 related but I think a wiki like this could be useful for
all technical stuff.

> [...] The key to this would be in the wording of an AuP that is
> clear as far as there being no implicit endorsement, etc.

What's is «AuP» please ?


- -- 
MANGA Willy Ted — Responsable technique régional
Afrique centrale et des grands lacs
Agence Universitaire de la Francophonie (AUF) | www.auf.org

Tél.Bureau:+237-222-23-97-45
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAEBAgAGBQJWrlkPAAoJEFf+VdnZGyKZDHAQAKHCr6WZsWgVI/MYIDCqPAfI
4I17BVxd/tee6Kn7qHlbDf5v+lUfyTE55jKcKQq35Ia06ZTY+5PlIbFkTChr8ql2
/0SYeAiTrZEORliaRX4iFMfGSDYaBRLp3TVbbVCMlsO5ckOyVZyaVWvX9slKmN1t
c/L3BqJYQusiBqFwLPvn91IIlBEuUDcHBzsramzT6o8V5n3LBhp9rdN+WtS06UdO
SEo7ke+IIC2c1jK3ICchC4qOwedV8ancZhY6O0oJdlQmz3QbVnwGFaQLjcoRjL2a
zd9z6JyRSvwx+C8P9pNVX33oCJS0m5/qJAZOLugpf0LF/Sm+xa/nOt2kIm5D4jn3
o6hYv0gBOGLdfQ94hNH7nrOWeQCzicA8FTMsg5bxacbB++8z3M4k1GZpkfU/l/xp
psCXGKxHgRyNj0HQQciqDvSnTVV9iyAlkeYpbtbIrxm0jAK8K4VfLMkP72AhsG9P
uYGUNgoWwT8DAbMlPzF3SK3J/PQDCbgMiu0jKItVL2Iy2XsvU+NBMmsV5YgIJYA8
HFvVgGwVQSMuVIOK9/BTuj+auSd3ZqNfHpU0RU0hfkmKcSZO22+8cygrxt2Gq6Zi
S81imsVFpJOFEzQ85dES50CX5uR8FQnEu9r1J059+1LPGteqty9K970jp1khY8TR
jYm/eFZ3j9jPZOS3ooM4
=ziC+
-----END PGP SIGNATURE-----



More information about the AfrIPv6-Discuss mailing list