rubysg / rubysg-reboot Goto Github PK

Would love to have a logo + favicon for the RubySG (and maybe also RailsGirls).

the content on ruby.sg landing page is outdated.

1. Ruby meetup is every 3rd thursday.
2. Telegram QR code and link is broken.

With Rails 5, this gem isn't needed any more, as long as the outlined configuration is in place.

In #1, we asked the community to contribute suggestions for the RubySG logotype, and we received some awesome responses from @stevenyap, @ariffmunshi, @jessicateh, and @yangshun.

We have shortlisted some of these suggestions, and now we need your help in voting! The shortlisted options are posted as replies below, and you can cast your vote by using the "reaction" feature in GitHub to add a 👍.

Here's a screenshot if you can't find it:

(Note that only 👍 reactions will be counted.)

Voting will be open until the end of the month.

😀

In this app, we do not use ActiveRecord. Hence there may not be a real need for PostgreSQL - we simply include ActiveModel to parse a companies.yml file

To evaluate whether/how to remove any dependency on Postgres and the pg gem

Can?

Wanted to post about the new design on facebook, and the card showed up as:

Any plans to update that @yangshun? 😄

reason: the URL for the image seems to no longer be working
to fix: update the URL for it

Since this discussion was brought up during the latest meet up:

Should we shuffle the entries in the companies page, to remove "unfairness" for the more "alphabetically challenged" companies? 😬

I think it's a good idea. In the spirit of Ruby. 😉

Expanding on the idea, we could put the companies into two groups: "hiring" and "not hiring". So we split, shuffle both groups, display "hiring" companies first (in random order) and "not hiring" companies following (in random order.)

Thoughts?

😘

“continuous-integration/travis-ci” is deprecated.

https://travis-ci.community/t/known-issue-travis-ci-reports-expected-waiting-for-status-to-be-reported-on-the-github-status-api-but-the-status-never-arrives/1154

failed to correctly send the weekly updates

Featuring RubySG's meetup videos in https://ruby.sg have a few benefits

• Show that we are an active community
• The meetup videos contains the history and growth of the community. It is the meat of the meetups so we should show case it stronger.

One thing that i feel is important is ensuring that we drive traffic to engineers.sg for meetup videos to build a collaborative relationship with engineers.sg. Engineers.sg is a more mature site that has a following and can help with discovery of RubySG.

The approach should be less code, in a way that once video is posted on https://engineers.sg/organization/rubysg--57, the video should also show up on ruby.sg

Hi folks,

Not sure how welcome this proposal would be, but as a means to train myself better with visual design stuff, I have been tinkering with a concept for RubySG's website.

Here's a mobile version:

Here's a tablet one in portrait mode (could use feedback):

Love? Hate? Comments?

Notes:

1. Writing isn't my forte, so the text on the mockups is completely representative
2. To give myself direction, I picked my favourite logo from #98, and decided to work with it. Ofc, depending on which logo makes it, I can adapt my design
3. I stole the images from links I got to from RubySG's meet up page - while I'm not posting them here, I have them saved for attribution.

Instead of '~> 5.0.7.1', maybe we should do '~> 5' so that we are not too far back from edge.

https://github.com/rubysg/rubysg-copy

From https://devcenter.heroku.com/articles/cedar-14-stack

Cedar-14 stack is deprecated and will reach its end of life in April 2019. We strongly recommend that you upgrade your apps to Heroku-16.

The production app for this repo is running on cedar-14 stack, which will be deprecated in 2019.

The staging app is running on heroku-16 stack, but the font-awsome icons are not showing properly. This needs to be fixed before the production app is migrated to heroku-16 stack

https://devcenter.heroku.com/articles/upgrading-to-the-latest-stack

On http://ruby.sg/companies. Probably related to #89.

For example:

Jolly Good Code is not hiring, but hiring link shows up as "ruby.sg/nil".

Just idea: make the background of the company box darker when hover in, like that

Considerations for arranging the list of companies

• companies who have most recently updated their information should be shown first, to encourage company representatives to update contact and hiring info. Maintainers should curate this list for fairness, to ensure we don't get spammed for unfair placements
• companies who have sponsored meetups or sent meetup speakers most recently (2017, at time of writing) should be placed first, to recognise their contributions to the community
• to reset Hiring Now indicators for companies, except for those who have mentioned in recent meetups that they are hiring. Let their developers submit PRs to update

2017 Meetup Sponsors & Speakers

Community Contributions Table

Ref: https://www.facebook.com/groups/singaporerubybrigade/permalink/685462351590975/

Maybe one of the prerequisite for putting up a logo on ruby.sg/companies in the future is that someone from the company must do a talk at a Ruby meetup to prove that the company has legit Ruby users.

And we'll also indicate on the same page that the company has spoken at Ruby meetup before.

People often ask me how to attract developers to their companies...

Personally, knowing that the company has good people who can either present their knowledge at public settings (probably means he/she has something to teach me in day to day work as well), or encourages their developers to share their learnings outside of the normal daily grind would be two items on my checklist. Thoughts?

A part of this is also to prevent the ruby.sg/companies page from becoming just a "recruitment" page.

And we also have a discussion on "sorting" in #56. I would also suggest using this as one of the "sort", where we have two sections on the ruby.sg/companies page. First, above the fold section for companies who have given talks (at least 2?) / participated actively in ruby meetups (sorted alphabetically), and the section below for companies who have yet done a talk.

End goal is to foster a learning community.

Description

I propose to build a simple Telegram bot that serves the RubySG Telegram. It can start with Posting weekly notification on links to Ruby news. eg. RubyWeekly. Current RSS Feed for RubyWeekly does not work because RubyWeekly's RSS feed follows a non-standard format for RSS Readers.

Other interesting features we can explore are:

1. Posting reminder for Meetup events.
2. Polling for opinions in the Group.

Interesting / helpful information:

1. https://github.com/jmettraux/rufus-scheduler

Any plan to update to later ruby version?

see #287

email them and if email bounce or no reply then delete?
Tried this before - got close to 0% response. We can try again.

To make it easier to update the list, we already know some companies active (in terms of supporting meetups and updating this repo) since 2018 - recorded here.

We can update this list with companies that supported meetups in 2019.

Another related issue is how to define and update contribution_count, i.e. contributions since when? What weights should we use?

This ties in to how we want companies to be listed - is there a need for a 'ranking' system, or should we do away with that altogether? What behavior would we like to incentivise, towards encouraging more community involvement and events?

 Started GET "/assets/font-awesome//fa-solid-900.woff" for 138.75.200.95 at 2018-02-13 16:31:27 +0000
 
 ActionController::RoutingError (No route matches [GET] "/assets/font-awesome/fa-solid-900.woff"):
   vendor/bundle/ruby/2.4.0/gems/railties-4.2.10/lib/rails/rack/logger.rb:38:in `call_app'
   vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
   vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.10/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
   vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.10/lib/action_dispatch/middleware/request_id.rb:21:in `call'
   vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.10/lib/active_support/tagged_logging.rb:26:in `tagged'
   vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.10/lib/active_support/tagged_logging.rb:68:in `tagged'
   vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.10/lib/active_support/tagged_logging.rb:68:in `block in tagged'
   vendor/bundle/ruby/2.4.0/gems/railties-4.2.10/lib/rails/rack/logger.rb:20:in `call'
   vendor/bundle/ruby/2.4.0/gems/railties-4.2.10/lib/rails/rack/logger.rb:20:in `block in call'
   vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in `call'
   vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in `call'
   vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.10/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
   vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.10/lib/action_dispatch/middleware/static.rb:120:in `call'
   vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in `call'
   vendor/bundle/ruby/2.4.0/gems/railties-4.2.10/lib/rails/engine.rb:518:in `call'
   vendor/bundle/ruby/2.4.0/gems/puma-3.11.2/lib/puma/server.rb:302:in `block in run'
   vendor/bundle/ruby/2.4.0/gems/puma-3.11.2/lib/puma/configuration.rb:225:in `call'
   vendor/bundle/ruby/2.4.0/gems/puma-3.11.2/lib/puma/server.rb:438:in `process_client'
 
   vendor/bundle/ruby/2.4.0/gems/puma-3.11.2/lib/puma/thread_pool.rb:120:in `block in spawn_thread'
   vendor/bundle/ruby/2.4.0/gems/railties-4.2.10/lib/rails/application.rb:165:in `call'
 
   vendor/bundle/ruby/2.4.0/gems/puma-3.11.2/lib/puma/server.rb:624:in `handle_request'
 at=info method=GET path="/assets/font-awesome//fa-solid-900.woff" host=ruby.sg request_id=fe9b8eaa-c13b-429e-acfd-14d59038cd79 fwd="138.75.200.95" dyno=web.1 connect=2ms service=5ms status=404 bytes=1744 protocol=http
 at=info method=GET path="/assets/font-awesome//fa-solid-900.ttf" host=ruby.sg request_id=b5e57b2c-b226-49c6-9e61-d0b3a05ad270 fwd="138.75.200.95" dyno=web.1 connect=1ms service=5ms status=404 bytes=1744 protocol=http
 Started GET "/assets/font-awesome//fa-solid-900.ttf" for 138.75.200.95 at 2018-02-13 16:31:28 +0000
 
 ActionController::RoutingError (No route matches [GET] "/assets/font-awesome/fa-solid-900.ttf"):

Emojis not rendering properly

Simplify the feedback mechanism

Current problem

1. Require code to create new feedback form
2. Require to create 1 form per session

Ideal

1. No code required if we want to collect more feedback.
2. 1 form to rule them all. Maybe we can just disambiguate using the feedback submission date.

https://ruby.sg is the face of the RubySG group on the internet. We should keep it updated and not let it feel like it's a dead page on the internet. I'm proposing that we do a redesign of the site, something more up to date with times, and take this opportunity to ✂️ things that are no longer relevant to the RubySG group today. Adding new feature will be out of scope for now as to keep the facelift simple and can be implemented quickly.

tldr

1. New design for Ruby.sg
2. Things that we consider cutting
   • links / refs to RDRC since it's not going to come back anytime soon.
   • clean up the Join Us section. At the moment, telegram group is the only active surface so we can consider cutting the rest.