UMass Drupal User's Group meeting: Thursday July 6

druderman's picture
2017-07-06 14:00 - 15:30 America/New_York
Event type: 
User group meeting

When: Thursday, July 6 at 2pm in ISB 145
(Meetings are the first Thursday of the month.)

Where: UMass Integrated Sciences Building (ISB), Room 145 (See map)
Room 145 is a meeting room behind the elevators.

Meetings are open to anyone interested in Drupal and not limited to the UMass Amherst community. Beginners are welcome.

See comments below for agenda. If you have questions or topics you want covered, please post them in the comments. Offers to make presentations are welcome.


Any agenda items?

druderman's picture

Any agenda items? Demonstrations are encouraged.

Modules not covered by security advisory policy

patalano's picture

I'm interested in hearing opinions on modules that aren't covered by drupal's security advisory policy. Do you use them? Pros / Cons?

CNS audit update & D8 prototype site

Rick Hood's picture

I can give an update on the work I have been doing on the audit of CNS sites including a D8 prototype site.

That would be great, I'd love

wleahy's picture

That would be great, I'd love to hear about your process.

druderman's picture

Reminder to all
UMass Drupal User's Group meeting: Thursday July 6

Details here:

I look forward to meeting more of you today...

shgrettenberg's picture

I am in second week now at Umass (week 1 has a lot of HR). I am deep in the planning stages of a new more automated web hosting platform in IT. It will have separate Dev, Staging, and Prod sections for each CMS supported including Drupal 7 & Drupal 8. I can't promise a timeline yet, but there is a lot of momentum behind the project.

It is not ideal to dramatically change a server when it is up, so I am proposing fairly advanced services to start with. What I need from the group is a sense of what modules, sites, or designs in the community would be left behind with these specifications.

Remember these are just proposals at this point and could change:

Server Environment: Debian Linux 9.x running on VMware 6.x
Apache: Default with Debian 9.x
MySQL 5.6
PHP 7.x
Control Software: Ansible, Jenkins, Drush

So initially there will be 7 VM's for Drupal:

Dev, Staging (Read Only), Prod for Drupal 7
D7-to-D8 Upgrade Staging (IT only)
Dev, Staging (Read Only), Prod for Drupal 8

If it is absolutely necessary we can have branches, with separate Dev, Staging, and Production VM's to meet different sets of needs - but to the extent possible I want to keep the environment uniform (this has nothing to do with individual modules, themes, and libraries as long as they work in the environment). This will make it easier to script moving from stages, approval cycles, security checks, and a variety of other improvements.

Please bring your thoughts, and especially any knowledge of reasons why this environment might not work with your sites.

Stephen Grettenberg
Web Application Specialist

Running late will be there

Rick Hood's picture

Running late will be there 2:15

UMass Amherst User's Group

Group categories


Group events

Add to calendar

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week