Push all open work and document current status

[SebastianZimmeck]

We discussed today switching from our mobile work to a browser extension (still to be finally decided). I created a repo with a copy of the current OptMeowt extension as a starting point.

If we decide to make that switch, let's push first remaining local code to this repo and document the status of open issues and anything else that is relevant. That way, we can more easily pick it up again at a later point if we decide to do so. At this point, everything is still fresh in our minds.

[chunyuema]

If we decide to make that switch, let's push first remaining local code to this repo and document the status of open issues and anything else that is relevant. That way, we can more easily pick it up again at a later point if we decide to do so. At this point, everything is still fresh in our minds.

So we will use this repository for the browser extension development? Do we consider to rename this repository then?

[SebastianZimmeck]

So we will use this repository for the browser extension development? Do we consider to rename this repository then?

I would prefer to keep this repo for mobile development but leave it in a state so that we can more easily pick up the work later again (if we decide to do so at all). So, push any outstanding mobile work on your local repos, if any, to this repo, write up anything on the open issues in this repo, etc. We can put this repo on ice and later reactivate it. For that purpose it would be good to leave it in a good state.

We can use the new optmeowt-browser-extension-research repo for browser extension code.

[SebastianZimmeck]

OK, I am assuming everything important is now in this repo.