Skip to content

Engineering / Open resources

TripSync

Collaborative travel itinerary platform, with a mobile app and a synced backend.

Open repository

Contribution tasks

Proposals based on source inspection, awaiting maintainer review. Check the current version and existing issues before submitting. The link opens a draft: you review it and decide whether to publish.

Source inspected on

Correct the getting-started guides in both TripSync READMEs

At both inspected commits, the only tracked files are README.md and LICENSE. The READMEs use yourusername clone URLs and instruct npm install/start without a package.json. The described src tree and features do not yet exist in these public snapshots.

Estimated size
S · 1–2 hours
Skills
Markdown · Git · Documentation

Files and evidence

Step-by-step acceptance criteria

  1. Prepare one documentation change per repository and replace example clone URLs with YagoLagrottiBracco/tripsync-backend and YagoLagrottiBracco/tripsync-mobile, using the correct directories.
  2. State near the top that the public snapshot contains documentation and a license only; identify the features and folder tree as planned.
  3. Remove nonfunctional install/run commands or mark them as future instructions, explaining that the package.json and application scaffold are missing.
  4. Clone both repositories into empty directories, inspect git ls-files and review cross-links; do not describe an executable application without published code.
Review draft on GitHub

How to start contributing

Links come from the portfolio catalog; check availability, license and open tasks in each repository. Read the README and license, run the project and propose a small documentation improvement or a reproducible test case. Discuss larger changes with the maintainer first.

MobileBackend
Read the README

Project evidence