Nuke excess branches (?) about brightness

[zlatanvasovic]

Alright @LordAmit, agreed. 👍

[zlatanvasovic]

Good work. 🎉

[archisman-panigrahi]

@LordAmit add-code-of-conduct-1 and probably mockup can be deleted.

[LordAmit]

html is the html version of the same application experimentally by @apandada1 . Lets see what he has in his mind.

prototype is the experimental branch - so it can be nuked.

installers - will be nuked.

develop and master will be merged.

[zlatanvasovic]

@LordAmit Are there any critical merging issues between develop and master branches?

[archisman-panigrahi]

I think there will be issues while merging. Things we can do

1. Rename Master as v1(discontinued) and develop as master
2. Delete current master branch and rename develop as master.
3. Replace Master Branch with develop branch.

[zlatanvasovic]

@apandada1 We can do the third option, but the most important changes should be manually applied to develop before renaming.

[LordAmit]

For preserving history, we should be keeping the master as v1. Develop will be renamed as master.
Sounds good?

[zlatanvasovic]

Sounds good enough to me @LordAmit.

[zlatanvasovic]

Another good change would be to put gh-pages into docs/ directory on master branch, as GitHub allows us to build sites from there, too.

[LordAmit]

That will mean downloading the master repository with the website. Why should user bother about that when he only wants to go through the sources?

[LordAmit]

Changes are applied. There are now 3 branches:

• master (old develop)
• v1 (old master)
• gh-pages