[NCUC-DISCUSS] NCUC Survey Results Analysis - Part I

[Rafik Dammak]

Hi Dan,

I guess that may be possible to do so. The ICANN staff lead for community
support tool sounds keen to work more closely with the community.
negotiating about terms and how things will work, may take some time and
questions of ownership and responsibility are sensitive

Rafik

2015-04-27 11:26 GMT+09:00 Dan Krimm <dan at musicunbound.com>:

> All taken to heart, here -- the sysadmin issue is a big deal.
>
> Here's my question:
>
> I wonder if there may be some sort of hybrid deal whereby a stakeholder or
> constituency group might arrange with ICANN to choose a platform for our
> use that is maintained by ICANN staff?  ICANN would get to veto a
> suggestion if it isn't workable, but then we'd get a better chance of
> finding something that fits our needs better and is more under our control,
> with ICANN staff configuring it to our needs.  Maybe volunteers could
> consult at the outset for initial configuration, but then ICANN staff
> maintains it going forward?
>
> Obviously we can't go hog-wild with this, so we'd need to consider options
> judiciously so as not to undermine the whole proposition.  Is there any
> chance that ICANN admin would go for something like this?
>
> Dan
>
>
>
>
> At 10:31 AM +0900 4/27/15, Rafik Dammak wrote:
> >Hi Timothe
> >
> >
> >
> >All on-line services - and especially Wikis - require maintenance and
> >management.  They are not free to operate; they will be assaulted by
> >wiki-spam, vandals and probes for security issues.  It takes time and
> >energy to stay up-to-date with patches, updates, and whatever
> >customizations you're lured into making.  There will be user question &
> >bugs.  And don't forget backups - because if your security provisions
> >don't fail, hardware will :-)
> >
> >So while these can be a valuable resource, they are not projects to be
> >taken-on lightly.  Ugly as the ICANN Wiki is, it's maintained by someone
> >else...
> >
> >All tools have a learning curve for both users and operators.  I urge a
> >careful evaluation of the advantages, disadvantages, costs - and long-term
> >commitment to support - before going off on your own.  Again, it's not a
> >commitment to be make lightly.
> >
> >
> >Thanks for this feedback, maintenance and management are critical since
> >most of work would be done by volunteers, who have scarce time to provide
> >. as Tapani, who worked a lot of NCUC website and related tasks,  always
> >reminds me the same question, when we discuss about some tools for NCSG to
> >enhance participation "who is going to be your system admin for this?" :)
> >. so careful evaluation and an iterative approach are needed, in  addition
> >to get members buy-in . btw ICANN wiki is confluence , it is not that bad
> >(I use it at work and it has many useful features) but we don't have
> >enough control on it. The ICANN staff is also working on providing some
> >additional tools to support the community in near future but that also
> >raises the question on how to not be tightly dependent to that.
> >
> >Best,
> >
> >Rafik
> >
> >
> >
> >_______________________________________________
> >Ncuc-discuss mailing list
> >Ncuc-discuss at lists.ncuc.org
> >http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20150427/771f9c53/attachment-0002.html>