[NCUC E-team] Website Prototype Back
James Gannon
james at cyberinvasion.net
Sat Dec 17 14:29:00 CET 2016
FY18 Community Additional Budget Requests Timeline
Start
End
Kick off and Submission period
12/15/2016
1/30/2017
Preliminary review of requests by ICANN staff
1/31/2017
3/10/2017
SO/AC consultations at ICANN 58 (by request, during Constituents’ Day)
3/11/2017
3/16/2017
Final assessments and recommendations by ICANN staff
3/20/2017
4/14/2017
ICANN Board review and approval at May Board meeting
5/15/2017
5/31/2017
End of Jan this year so yes we need to start think about our approach on this now.
-----Original Message-----
From: E-team [mailto:e-team-bounces at lists.ncuc.org] On Behalf Of Tapani Tarvainen
Sent: Saturday, December 17, 2016 1:26 PM
To: e-team NCUC <e-team at lists.ncuc.org>
Subject: Re: [NCUC E-team] Website Prototype Back
On Dec 16 08:39, Rafik Dammak (rafik.dammak at gmail.com<mailto:rafik.dammak at gmail.com>) wrote:
> I am in favor of moving to more managed service since we cannot really
> count only on volunteers to support the maintenance and operation.
Yes.
> @James @Tapani can we think about assessing NCUC basic needs
> (including the website and civicrm based membership system) and also
> thinking about possible services we may want to have too in future.
Yes.
The hosting provider we're using for the civicrm build offers managed systems, meaning they take care of Linux sysadmin stuff and leaving only higher-level (wordpress or whatever) for customers (= us).
That could work well for NCUC website.
I expect we'll have the civicrm ready for production around end of January, then we can move to NCUC website &c. But budget requests should indeed be planned soon (forget the deadline, February maybe?).
--
Tapani Tarvainen
_______________________________________________
E-team mailing list
E-team at lists.ncuc.org<mailto:E-team at lists.ncuc.org>
http://lists.ncuc.org/cgi-bin/mailman/listinfo/e-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/e-team/attachments/20161217/79886db0/attachment-0002.html>
More information about the E-team
mailing list