In a recent commit , the Vagrantfile.example was updated to use Fedora
27 rather than Fedora 25. So if you are using Vagrant to hack on hubs,
things might get a little funky.
When first setting up the Vagrant dev instance, you need to copy
`Vagrantfile.example` to `Vagrantfile`, (`Vagrantfile` is not stored in the
repo). So be sure to either update your Vagrantfile, or if you havent
changed it, just re-copy it over from Vagrantfile.example after git pulling.
at the last meeting, I was task two calendar / meetings widget bugs to
* #489 Adapt the meetings widget to work on stream and team hubs
* #33 Request New Meeting Feature
I have opened a PR for #489 (PR#511),
however, for #33 it seems a little more complex. The mockups describe a
feature where a user can "request a new meeting" via the widget -- and
looking at other widgets (like the library one), this is something that can
only be done in a react widget (the calendar widget is currently a
Additionally, the mockups also cover showing notifications on users streams
when a meeting is requested -- and i currently don't think we have any code
in place to get this easily working either.
Anyone got any thoughts or guidance on this one?
2017 was a busy year for all of us in the community – I'd like to
encourage the Fedora Hubs team to put together a "Year in Review" to let
the community know what happened in 2017, and what's ahead in 2018!
Every sub-project / team in Fedora is encouraged to come up with three
highlights from 2017 and one goal for 2018 (of course, more is okay too)!
A template to help you write the post is available in the announcement post.
I'm personally interested to hear what happened with Fedora Hubs in
2017, and what you all are looking forward to in 2018. :-) If you have
questions or need help, you can reach out to the CommOps team:
Justin W. Flory