Date

Attendees

Drew - put up pages for technologies in Confluence. Updated the schedule.
Thomas - got job offer from UTC Aerospace in CT. May 20th start date.

Paul - working on angular code; replaced the date picker. Doesn't like the time picker.

Three things the Web Group is currently working on:
Paul - Content Management changes (schedule)
Thomas - image work added to classic site
Jira cleanup

Is the look and feel ok before we start adding some authentication and authorization?
What is necessary for Devops-related work? Add node-js and angular-cli and mongodb to a server?

Edits to classic site code are necessary to work with mongodb. New queries for schedule display.

Questions related to Paul's database forms:
Do we remove the need for a Confluence schedule/location page?
  Keep it until we are comfortable with the new system. Edit in Confluence AND on the new database entry form.
Include all that we add to the web site or all that is on Confluence?
  A combination of both. Schedule dates eventually are removed from Confluence. Some details are added to the database that may be displayed in Confluence and NOT in the website.
Do we want to be able to add a schedule for all groups?
  Maybe. Have to work out the details after we have a Wednesday afternoon schedule working.
Meeting ID. Should it be automatically generated? Is it useful to display to the user? Is it necessary except for the database queries? Date should be enough for a query. And maybe time if we allow more than 1 group.
  Need to think this through and write up a specification.

We need to have a log-in to the website before we roll this out.

Do we use this technology (Angular JS, MongoDB) and these features (forms for data entry) with classic site?
  Vote = 'YES'

At initial release: Confluence is the single source of truth
When confident (2 weeks or less?), we can get rid of the schedule information in Confluence.

Three roles of website users:
  planner/scheduler - full form for mongodb database
  casual user - basic schedule page
  facilitator - needs to look at the form for comments

TODO: Ralph will work with a plug-in that grabs data from mongodb and enters it in Confluence. Started this (see below).

Discussion of JIRA epics and issues...

TODO: Need to create a new epic "Schedule Content Maintenance"
  include tws-101 content maintenance

Found this in Confluence from 7/24/2019. It's an entry related to adding text to Confluence from data in a database. This hasn't been written up as a Jira issue yet.
http://confluence.technologynursery.org/display/TSSG/Populate+Confluence+From+Database+Information

Found a free keysight plugin that allows for creating groovy macros that run with Confluence. Haven't tried this yet.

Ralph tried a free trial of Groovy for Confluence plug-in. Doesn't seem to allow scripts or macros. 
Ralph also grabbed Adaptavist ScriptRunner as a free trial but may end up buying it for $10. It works as far as allowing a groovy script to search and write to Confluence pages. We are hoping this will allow us to share/display venue information in Confluence that has been stored in a mongo database.
Ralph is getting a java driver for mongodb version 3.10.2. This will hopefully work with the mongodb that Paul's angular test code is using to generate a website database.

1 Comment

  1. Jim Drewniak

    Hi,

    Just to expand on the great notes that were recorded.

    In the notes it was stated:

    Three roles of website users:
      planner/scheduler - full form for mongodb database
      casual user - basic schedule page
      facilitator - needs to look at the form for comments

    I have been asked to act as the Stakeholder for this initiative.   My available time did not allow me to expand on these processes / scenarios.  There are in fact four roles (personas) to consider;

    1. Planner - This person plans the general meetings each quarter.  He/She uses Venue contact, TSSG Venue Member contact, Venue capabilities/equipment/facility, and Venue Schedule information to create a schedule for a future quarter of general meetings.
    2. Scheduler
      1. - Updates the schedule of meetings on a weekly basis to shuffle the current schedule and add to the historical list.  An ad-hock update does take place when a conflict/adjustment needs to be made because of a Venue issue.
      2. Uses Schedule and Venue information to send out meeting announcements to TSSG Members, Venues, Acton Networkers and Westford JobsSeekers
    3. Casual User - This would be a TSSG Member and non-member use to determine information about the next or future scheduled meetings.
    4. Facilitator - This would be the TSSG Member that is going on-site to Chair and/or set up the Audio/Visual for the meeting.  In most cases there is a fifth role/persona when the Chair and AV are handled by two people.  Each Venue has it's challenges with the setup that should be considered during setup and tear down of the meetings.

    Regards,

    Jim "Drew"