Lab Report 2 - bounswe/bounswe2024group12 GitHub Wiki

Lab Report 2 (01.10.2024)

Prepared by Orhan Ünüvar


Introduction In this meeting, our group discussed the design and features for a chess community platform. We talked about things like game replays, user interaction, and how to store game data. The goal is to create a fun platform for chess players to connect and share content.


Tasks Accomplished:

  1. Game Data and Wikidata:

    • We found that Wikidata doesn’t have much chess game data, but it does have player info like names, titles, and ratings.
    • We can use Lichess for more detailed game data, including opening moves.
    • chess.js could help us simulate chess games and even handle different chess variations.
  2. Search and User Filters:

    • We decided on a search feature where users can filter players by country, age, rating, and tournaments they’ve played in.
    • The search will be customizable to create a more personalized experience.
  3. Platform Features:

    • Basic platform functions like login, logout, and user profiles are planned.
    • Profiles will include favorite openings, players, and personal ratings. Users can also link their Lichess accounts.
    • Features like following/unfollowing other users and commenting on games will help boost interaction.
  4. Game Replay and Analysis:

    • Users can replay games and comment on specific moves.
    • Chess APIs will give analysis on best moves or stats from the game.
  5. Puzzles and Community Content:

    • Users can create and rate chess puzzles.
    • An upvote/downvote system will help manage puzzle quality, with more experienced users having more say.
  6. Community Incentives:

    • We’ll use labels or hashtags to organize content like posts about tournaments, coaching, tips, and memes.
    • User rankings will be based on things like Elo rating or puzzle ratings, giving higher-ranked users more influence.
  7. Tech Stack:

    • Backend: Python with Django, Frontend: Vue.js or React.
    • Deployment will use Digital Ocean or AWS with Docker.

Tasks in Progress:

  1. Creating Scenarios and Mockups:

    • Next week, we’ll start gathering requirements and creating scenarios to plan out features like game replays and search filters.
  2. User Types and Access:

    • We’ll develop different user types based on Elo rating or reputation, which will affect access to certain features.
  3. Using Wikidata:

    • We’ll decide how much we want to rely on Wikidata for chess data, but also look for other sources.

Conclusion:

In this meeting, we figured out the main features for the platform and planned how we’ll manage game data and community interactions. Next, we’ll work on creating more detailed plans, scenarios, and mockups to move forward.