Skip to content

Open Contributing Timeline

  • Author: @JeelDobariya38.
  • Last Updated:- April 14, 2026.

This file will provides you, from when and where, the repository(s) will be able to accept external contributions from other developers worldwide.. This will provide you the abstract idea / timeline, that you can look at and see, how much you need to wait, to contribute, Besides, it help in cordinating the contribution process.... Also, we aim to provide you a clear timeline... And lay a path forward...

Note

currently though, you can still contribute to the repository, if you plan to do so...

but just keep in mind that, while doing so, you will feel like everything is behind you, and fighting against you.. and this will slow you down significantly.. expect, a less streamline process and also expect some of your time being wasted..

but, I will try my best to help as much as possible, on our discord community.. to get you start on working.. but just keep this document and this entire thing in your head...

Steps To Cordinate Open Contributing...

Passcodes project has to go though this process to be ready for open source & for community contribution.

  • Obviously, Idea!! (Aug 1, 2024)

  • Setup Github Repository (Personal Account) (Aug 5, 2024)

  • Make Prototype Release aka Proof Of Concept (Aug 26, 2024)

  • JeelDobariya38/Password-Manager -> JeelDobariya38/Passcodes & Community Standards For Repository. (Aug 1, 2025)

    Somehow, it is exactly after year!! #17 I just realized while write this document..

  • Migrate Codebase: Java -> Kotlin (Aug 1, 2025)

  • First Stable Release (Aug 16, 2025)

  • Offically Organization on Github JeelDobariya38 -> PasscodesApp (Aug 31, 2025)

  • Improve Structure & Organization: i.e, segregate app code, docs and website into different repositorys (Sep 25, 2025)

  • MVC -> MVVM -> MVI architecture update.. (Nov 11, 2025)

  • Clean architecture (Dec 15, 2025)

  • XML -> Jetpack Compose (Feb 28, 2026)

  • Documentation Updates. i.e, license... contributors guide... style guides etc...(start of may)

  • Plan Google Developer Verification. (I mean, we will discuss about it in june, how to manage or cordinate with it)

  • Open For Contribute (Roughly, end of june 2026)

Semi Open To Contribute (start of june 2026)

Warning

The Organisation is from this point, open to receive any contribution from any potential contributors..

The only reason, it is not fully open to contributing is solely because of this developer verification thing... the thing is I don't want anyone to waste thier time contributing to this repository(s)... because, I might end up not make verifications due to personal external reasons... and this might result in waste of other developer's valuable time.. because without verification the application might not be release as google wouldn't allow it to install on android devices...

Other then this, or If this thing doesn't impact you as contributor, in anyway then you can count the repository as fully open to contribute but just have this in your head...

  • Find Contributors, Also Review & Update The Contributions Workflow & Get Feedback. (end june 2026)

  • Me, Doing My Developer Verification (@JeelDobariya38)... (can't say how time it takes but probably it completely by mids of july 2026)

  • Open To Contribution (Aug, 2026)

😊😊 Open To Contribution 😊😊

Further improvements to contributions workflow will be driven by feedback and contributor's input...

Remember, cordinating contribution is a contiguous process and not a task that can be just done...