2014/Calagator

From Open Source Bridge Wiki
Jump to: navigation, search

Getting involved:

Mailing lists (linked from the Calagator GitHub wiki):

Current plan:

Reid wants to merge features back from ActivateHub fork before the end of July. The plan is to merge ActivateHub and Calagator, including private themes, and then break out and fix Calagator themes again.

Next steps:

Start working with community support as soon as that happens

  • Maybe work with Code for Portland?
  • Group code review session would be helpful
  • Hackathon (sometime in fall; earlier if possible)

Feature requests/issues that need attention:

GitHub issue tracker is the canonical issues/wiki. Work with Reid or Audrey on current status to make sure you're not duplicating efforts, since the plan is to merge in feature set from ActivateHub very soon

  • Wiki documentation
    • Add all instances of Calagator to wiki: "Calagator in the wild"
    • Documentation was originally very good, but has not been maintained. Needs to be updated.
  • Heroku support
    • This was implemented by ActivateHub fork; Reid plans to merge this before the end of July
  • Front end/UI:
    • CONTEXT NOTE: The original goal was to make the front end code as accessible as possible, to provide a low barrier to entry for new contributors who may be at various level of technical ability/familiarity with the project. This may or may not have succeeded as planned, but maintaining the awareness of limiting barriers to entry for new contributors is a core value that should be maintained.
    • Reid has created mockups that work to resolve some of the UI clunkiness and plans to either implement them, or meet with someone to have them work to implement them.
    • In addition to Reid's existing mockups, he is open to reviewing pull requests of other mockups and ideas.
    • Angular was suggested as a possible alternative to the current front end set up. This lead to the discussion of core values noted above. Audrey also stressed the importance of maintaining the ability to override individual themes/views for the convenience of people who have forked the project.
    • Currently Calagator uses media queries to detect its environment and then loads a separate "mobile" stylesheet. It would be good to modernize this and bring it in line with current best practices.
  • Mobile app(s):
    • Currently, there are multiple mobile apps available. Audrey has written one for iPhone, but there is at least one other iPhone-specific app created (and possibly maintained? Not sure of status of the project) on GitHub. There is at least one Android app as well.
  • Is Calagator US specific?
    • Adding an event asks for a "postal code," but there is no specific validation/enforced encoding of that field.
    • If there are issues that come up with forking the project for other countries, it should be fairly straight-forward to submit a pull request to resolve them, and they would be welcome contributions.

Miscellaneous notes:

Calagator History:

  • (I missed this part; if anyone can fill in this section, that would be great!)

Calagator API:

  • An API exists and you can use it!
  • The API is mostly a stock Rails app API, with the additional ability to get JSONP out of it.


Active fork: ActivateHub

Developers Reid is working with:

Changes ActivateHub implemented:

NOTE: Reid plans to work with Eric and Daniel to merge in some features from this fork before the end of July.

  • Grid view: This may not be a good feature to implement on Calagator itself, since this type of view can be unwieldy when there are more like a dozen events per day.
  • Group ownership of events
  • Recurring imports, but only if tied to a group with active community event/contact information. This solves the Calagator "zombie event" problem that has until now prevented recurring imports.