Website "registration" link points to old EventBrite

[Sequoia]

No description provided.

[sanguis]

willing to help but dont have forking pull request access

[Sequoia]

Hey Josh,

Getting the site on Github is something we're working on- once that's done
we'll get you the link to fork & PR ASAP.

The point people for this are, unless I'm mistaken:
Steve : Runs the site, Drupalarian
Andrew : Helping get site on Github (possibly also me doing this if Andrew
doesn't have time/isn't comfortable with it).

I personally don't know drupal works on CVS... do you check in the code?
isn't the config in the DB? Does this get checked in in a big bundle?
Does it contain our creds? Maybe you can answer some of these questions!

We are considering (I think) code sprint for website-- getting the site on
github & cleaning up a few of these content issues would be a good goal for
such an event. I'll put this on the next meeting agenda.

-Sequoia

On Fri, Apr 11, 2014 at 10:25 AM, Josh Beauregard
[email protected]:

willing to help but dont have forking pull request access

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-40209054
.

[sanguis]

Hey Sequoia,
Am I going made but did I just see CVS escape your fingers? Maybe your to young to remember the great git migration but going fro CVS to git and preserving the history.
CVS is checkout, lock, check in unlock.

As for keeping the db in the repo we could do this as long as we are EXTREMELY careful to truncate all user data. I personally think it would be better to keep the database locked down and available upon request only and force sanitation user contact data should NOT be distributed.

As long as all cahges are done from a no touching no database swap workflow all one will have to do to get new config changes is run updates and revert features.

[Sequoia]

ha... meant SCM (more generic term for Source Code Management, including
CVS & SVN) but yeah we use Git :)

On Fri, Apr 11, 2014 at 10:55 AM, Josh Beauregard
[email protected]:

Hey Sequia,
Am I going made but did I just see CVS escape your fingers? Maybe your to
young to remember the great git migration but going fro CVS to git and
preserving the history.
CVS is checkout, lock, check in unlock.

As for keeping the db in the repo we could do this as long as we are
EXTREMELY careful to truncate all user data. I personally think it would be
better to keep the database locked down and available upon request only and
force sanitation user contact data should NOT be distributed.

As long as all cahges are done from a no touching no database swap
workflow all one will have to do to get new config changes is run updates
and revert features.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-40212550
.

[sanguis]

thank (who|what)ever you thank for that

[sanguis]

btw here is my pub key of you want to give me access to anything https://gist.github.com/sanguis/eb5648b3fcf44b7e09d3