This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
In consultation with danielsh and joes4 on ASF's infrastructure IRC channel - and they requested to see a bit more detail in our migration plan:
Once those are created by ASF infra,we will have the following action items:
Lots of questions here rather than plans. This mainly concerns cloudstack.org and docs.cloudstack.org.
We will not migrate user accounts - too many privacy/data sharing issues, which likely means we won't be migrating content. Still TBD.
ASF will provide us with VMs for us to administer for web properties, and administration then falls to us - (they essentially act as a SP fwiu and won't meddle with the machine and expect us to manage OS/software)
What do we care enough about to allocate people to administering long term.
cs.o addresses going away when we transfer - need to begin weaning ourselves off cs.o addresses now.
TBD - perhaps we should get rid of waf in the process and make first ASF release buildable only with Ant.
[Prasanna] Plans for Hudson (internal) and Jenkins (public) - Will this move to ASF Infra?
TBD - will be painful I fear. What are our requirements around this?