ConFOMO is a simple tool that makes it easy to track your friends at conferences.

This pull request includes the changes for upgrading to Laravel 5.2. Feel free to commit any additional changes to the shift-3722 branch.

Before merging, you should:

• Checkout the shift-3722 branch
• Review all pull request comments for additional changes
• Run composer update (if the pre-commands fail, add --no-scripts)
• Thoroughly test your application

If you would like more help with your upgrade, check out the human services from Laravel Shift. And if you want to level-up your Git skills, check out Getting Git.

I have added additional properties to the Friends table - Name, Location, Url and Description.

Here is a brief overview of the changes:

• The additional information is retrieved directly from twitter and populated in the database for quick retrieval. I have expanded the FetchTwitterAvatar job to provide this functionality but I can rename this class to something more appropriate like 'FetchTwitterInfo' if required.
• I have made the following changes to the Friends list:
  • If the 'Name' property is populated via twitter, we will display this as well as the twitter handle like so: Mike Daly (@mikedaly85). This will be useful when in a conference as you can quickly remind yourself of a persons real name.
  • Added a 'details' button to the friend list item, which when clicked, opens a SweetAlert popup to display the full user profile info including - Avatar, name, location, url and description.
  • The Avatar in the popup is larger than the avatar in the listing view to improve visibility and make is easier to identify people you have not yet met. Sometimes a smaller image will make the task much more difficult, especially if the avatar is not clear.

Some closing notes:

• I have not added functionality to keep the information up-to-date as I didn't want to spend too much time on this if you felt the project would not benefit from this information. If you do want to accept this pull request then I can start the work and submit as a separate pull request

This is my first pull request to any open source project so if there are any issues I would really appreciate the help/guidance so I can be sure to improve.

Opening a PR to track the progress of adding the public introduction page.

• [x] Database migration for conference start / end dates
  • [x] Model factory adjustment
• [x] Database migration for friend ~~approved~~ introduction status
  • [x] Model factory adjustment
• [x] Ability to determine whether or not a conference is upcoming, in progress, or finished
  • [x] Tests to verify functionality
  • [x] Render different headings based on the status of the conference
  • [ ] ~~Display conference dates (??)~~ Not really room for it
• [x] Allow a new / online friend to suggest you meet or have met at the conference
  • [x] Tests to verify functionality
• [ ] ~~Provide a ConFOMO user the ability to approve or delete pending requests~~
  • [ ] ~~Tests to verify functionality~~ seeing as this is only ever seen by the user, no need. The user can either leave the request (approve) or delete it (reject)
• [ ] ~~Notification to ConFOMO user that a new request has come in (??)~~ Omitted given the Twitter API doesn't return the email address

Note that as this is public-user functionality, we can't rely on Laravel auth for the API. Do we need some kind of added protection to stop spam from being sent to this page, or do we just discourage robots? Open to suggestions or thoughts on how we might avoid people getting unnecessary spam.

Closes #35

This PR is largely to tidy up the remaining 'core features' that were yet to be completed, and focusses mainly on adding new/online friends, being able to delete friends, as well as marking online friends as met.

In addition, when adding either a new or online friend, we'll hit the Twitter API and fetch the user's avatar. This does not yet introduce syncing of avatars periodically, but does check if the friend exists already, so will only fetch the avatar for the first lookup of a unique username.

When deleting friends, if the last record for that username is deleted from the database, the cached image will also be deleted from disk.

Closes #13

• Removed the inline styles and added them to the stylesheet, make the paragraph text a little smaller on small screens
• Tweaked position of logo on small screens

Should this page require that the visitor seeing approval be logged in to the site? This would make the process of adding the name simpler, coming down to a simple 'we met at this conference' or 'we should meet at this conference' type button.

This will submit a request for approval (a new status on the friends table suggested to meet, suggested as met), with an approved date. Display those users in the relevant new (suggested as met) or online (suggested to meet) section shaded if not yet approved, with the option to approve, or with a marker that they were suggested externally once approved.

Furthermore, should the suggestion page show the existing new / online friends, or just be a page showing something along the lines of 'Hey, I'm ! Did we meet at ? Would you like to meet at ?

The first step of the VueJS refactor is to extract all of the components into separate *.vue files and import them as components to the main Vue instance - or, as in the case of FriendsList - into the Conference component. This is just a placeholder PR to make sure I'm heading in the right direction.

Once the underlying component structure is settled on, we can start working on actually refactoring the code as needed.

• [x] Extract components to separate files for vueify
• [x] Establish an appropriate import style
• [x] Make sure that each component works as it did previously

For people looking to join the project it is nice to have directions in the README to start the project.

As someone who has not programmed in PHP in quite a while and has never used Laravel, I am attempting to run via php artisan serve --port=8080

Fatal error: require(): Failed opening required 'confomo/bootstrap/../vendor/autoload.php' (include_path='.:') in confomo/bootstrap/autoload.php on line 17

This pull request includes code to run php unit tests on GitHub actions. The codeship badge has been replaced with the GitHub actions badge on the README file and the php requirements have been updated to reflect the testing on GitHub Actions. TODO: This project should be removed from the codeship site.

• Added Run Tests GitHub workflow.
• Updated Readme with GitHub Actions badge replacing the codeship badge.
• Updated PHP requirements listed in the README to reflect the versions of php that are passing the GitHub Workflow.

https://overcast.fm/+GDI4k9Bsk

There are three states of a person:

A. I know them via Twitter/etc. and want to meet them at this SuperCon B. I know them via Twitter/etc. and met them at this SuperCon C. I met them for the first time at this SuperCon

Previously this was "old friend unmet, old friend met, new friend".

In the current re-working it's "online friend unmet, online friend met, new friend"

I'm not sure either system is really good. Any ideas?

Bumps bl from 1.2.2 to 1.2.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Hi

I saw the text in README file about license. May you please specify the license under which this project is released? It is important so that there would be no confusion on how one can use and modify the code. You said to assume MIT as the license then why not use MIT as the license?

This pull request includes the changes for upgrading to Laravel 5.7. Feel free to commit any additional changes to the shift-43397 branch.

Before merging, you need to:

• Checkout the shift-43397 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 5.7
• Run composer update (if the scripts fail, add --no-scripts)
• Clear any config, route, or view cache
• Thoroughly test your application (no tests?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

Old tests/etc. that checked for file sync, and the fact that we only synced avatar once regardless of how many friends had the same username, is not working right now. Need to fix.

Talked with @AdamWathan about why bringing notes back would be helpful for a) who someone is and why you want to meet them etc and b) take notes after meeting. Something making it a bit more like a mini CRM.

Hey Matt, Michael,

First, sorry about the duplicate PR. Had to recreate when I noticed that my author/committer data was wrong. 🙃

This PR includes some new functionality that is somewhat related to some of the open issues, but not directly. It creates an internal (auth-guarded) User Profile page that would list all of the user's upcoming and past conferences. For upcoming conferences, it lets the user easily Introduce themselves using the existing "Introduce" functionality.

Importantly, this change does allow each user to choose whether or not they want their conferences to be shown publicly. If turned off (the default), any other user that tries to view their conferences will just receive a generic "This user hasn't added any conferences yet" message. Also, users cannot view the list of friends for a conference. The conference owner is still the only person who can view their friends.

I also added a field for a Conference URL when creating a new conference, and made the conference name on the "badges" to be links to the URL, if present.

Settings Page

Note: I haven't added the search functionality yet, but added the support in settings

Profile Page

Thanks for your time and consideration! Critiques/change requests welcome :)