Skip to content

Open Contributing Timeline

This file will provide from when and where, the repository will be able to accept external contribution from other developers and community.. 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 cordinate 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 telegram community.. to get you start on working.. but just keep this document and this entire thing in your mind...

Steps Required 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 stuff (Sep 25, 2025)

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

  • Clean architecture (Dec 15, 2025)

  • XML -> Jetpack Compose (end of nov 2025)

  • Documentation Update i.e, license... contributor guide... style guide etc...(in entire december)

  • Plan for Google Developer Verification, i mean we will discuss about it. (in december how manage or cordinate with it)

  • Open For Contribute (Roughly, 31 Dec, end of 2025)

Semi Open To Contribute (start of jan 2026)

Warning

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

The 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 there time contributing to this repository.. because, I might end up not make verification due to some or other reason... 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 in anyway then you count the repository as fuly open to contribute but just have a note of it..

  • Find Contributor, Also Review & Update The Contribution Workflow & Get Feedback. (end mar 2026)

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

  • Open To Contribution (Aug, 2025)

😊😊 Open To Contribution 😊😊

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

As cordinating contribution is a contiguous process and not a task that can not be done...