Why is the repo within 'nelsonic' as opposed to 'dwyl'?

[Cleop]

@nelsonic I was just wondering why you'd chosen to make this repo inside of your own profile instead of dwyl?

[nelsonic]

@Cleop good question!

Answer: Because for now, I'm the one doing the work.
I wrote all of the previous MVP. see: https://github.com/nelsonic/time-mvp/graphs/contributors
and 95% of the one before that: https://github.com/dwyl/time/graphs/contributors
(the contribution graph of the main repo does not give a "full picture" of all the re-useable modules I created which are still in use today by many other projects/companies and get over a million monthly downloads... e.g: https://github.com/dwyl/hapi-auth-jwt2/graphs/contributors ...)

99% of the time I start work on a project or "learn-..." repo on my own time/repo
and then transfer it to @dwyl when there is something to "show".

As you can see, this repo is blank and only has the "Why" #1 issue.
I am in the process of updating my Phoenix Knowledge ("sharpening the saw")
Once I feel confident that I can build the app using all of the latest Phoenix best practices,
I will transfer it. Meanwhile it's 100% open source and and anyone can contribute!

This is not a quest for "control", it's more an attempt to avoid "spamming" people with noise.

I suggest that everyone wanting to participate in the Time App (which will be transferred to @dwyl once there is momentum) from a technical perspective, re-read the Phoenix book as there are a number of improvements (e.g: Contexts) that we will be applying which are not currently in use in any @dwyl client project(s).

[nelsonic]

This "MVP" repo will be integrated into the main https://github.com/dwyl/app once it's got some useful functionality. 👍

[nelsonic]

Transferred to: https://github.com/dwyl/app-mvp-phoenix ✅