Should we expand the scope of this repository?

[peterdesmet]

Should we expand the scope of this repository from stuff related to the tdwg.org website only, to all TDWG infrastructure? I personally think that's already the case.

If so, can I'll this repository from tdwg.org to infrastructure. This is also the name of the team managing this repo. GitHub will redirect all old links automatically.

[mdoering]

I support that. http://rs.tdwg.org should be covered here too

[CynthiaParr-USDA]

I agree. I saw that the team of people was already called "infrastructure".

[peterdesmet]

Ok, do I need to wait for more votes or go ahead?

[jmacklin]

I agree as well!

JAmes

On Mon, Jun 1, 2015 at 9:39 AM, Peter Desmet notifications@github.com
wrote:

Ok, do I need to wait for more votes or go ahead?

—
Reply to this email directly or view it on GitHub
#15 (comment).

[dkoureas]

+1

Kind regards,
Dimitris

[peterdesmet]

Done.

[sblum]

+1 from me, too.

I share Steve's sensibility that it would be good to maintain the permanent URL, but that might commit us to maintaining mod-rewrite on (or in front of) www.tdwg.org. I think it would have been simpler if rs.tdwg.org had "responsibility" for serving all TDWG permanent resources, but it seems too late for that as some number of standards have been published with a permanent URL of www.tdwg.org/standards/[###], so www will have to be split. I'll look into what Typo3 can do in managing URLs.

-Stan

From: Dimitris Koureas <notifications@github.commailto:notifications@github.com>
Reply-To: "tdwg/tdwg.org" <reply@reply.github.commailto:reply@reply.github.com>
Date: Monday, June 1, 2015 at 6:53 AM
To: "tdwg/tdwg.org" <tdwg.org@noreply.github.commailto:tdwg.org@noreply.github.com>
Subject: Re: [tdwg.org] Should we expand the scope of this repository? (#15)

+1

Kind regards,
Dimitris