Groceristar Roadmap — Intro [part 1]

Arthur Tkachenko
groceristar
Published in
3 min readApr 15, 2018
free image from pixabay.com

Each project have a management plan. So, this is an article, that show how i plan our work on Groceristar project. I have a lot of info, and was stuck, creating a longread with all information in one place, so it’ll be a series of articles.

This is how looks a first page of issues/tasks at our main repository. Pretty bad, right?

labels that we’re using

  • enhancement — some tasks have this label — it’s a low priority for most cases, can be done later, but it’s a good update of our codebase
  • discuss-in-comments — a lot of tasks was not completed. So i want to start a discussion with a team member inside this task — where we’ll chat about how this task will be done.
  • logic — related to server side only. this can be method inside our models, or actions(method of our controllers)
  • front — related to frontend. But before starting you should be careful — better to ask me about this task. It can be outdated and finished in separated repository related to React app.
  • help wanted — this is an official GitHub label, that you can put on your tasks, so any new contributor can find how they can help. I use this label as mark — “intern can grab that task and start it without any big(maybe) troubles”
  • i dont want to do it! — this is my most loved label, but i don’t see it on this repository. will add it later.

other labels are not important or self-explanatory.

Big things that i want to implement at GS(later).

  • Code clean up
  • Items
  • Measurements
  • App compatibility
  • User can add data fast
  • Clean API Documentation
  • Prices + Financial planning
  • Community lists that can be shared with another users.
  • When User create a list, we count a preliminary price, based on previous purchases
  • Validations
  • ACL
  • and a lot more…

And I want to separate Backend & Frontend. This is why ⬇️

Milestones aka Releases

Release 1 was just my code. Simple shopping list, login via FB, shopping list management. I setup a basic grocery list project.

Release 1.2 was related to updating shoplist functionality. We use a different UI components/elements for shopping list. Was updated at least 30% of previous code. Thank you Denis Petrov, I spend 2 weeks on this… He just didn’t like how it looks on mobile :(

Release 1.3 will be about cleaning the code. A lot of places can be improved, we need to add tests, re-do from scratch some ‘bad’ places. I create a list of tasks, that must be covered during this release. This is our current stage.

Release 1.4 related to creating different grocery lists templates. This lists can be cloned and used by our users. We need to import a lot of static data, that was scrapped from a few open sources.

Release 1.5
Product quantities
Food Measurements

Release 2
We starting to work on a new features!

Release 3
Grocery lists with diets integration — free diets converts into recipes with ingredients. Maybe we’ll move some default functionality into microservices, like login.

Link to main repository

Please clap as much time as you saw my profile image on this article!

--

--