Meeting Notes

22-Oct-2020

Week-2 Day-2

20 people joined

• Short and simple meeting so we have more time to work on tasks, or personal time.
• Regularly talking for one hour may be stressful, but we will have a regular call and discuss briefly on issues, tasks, etc.
• Thank you to everyone using twindle hashtag. More new people are getting to contribute by word of mouth. Proful gave a shoutout to all the people who shared tweets.
• https://twindle.co homepage was created and pointed to the github. It auto generated the html files and the links and all are correctly pointed.
• Aravind joined, was impressed with the documentation we have come up with already.
• Encouraged to put articles in the articles folder in docs. /docs/articles. Use naming convention as lowercase and hyphen in between words.
• Don't need to be polished, grow as we grow, learn on the go.
• Nobody is paying us and asking for timelines. We can have team page, and also blog page so that we can showcase all the articles.
• Raise PRs for adding any kinds of documentation to homepage.
• Other projects repository have been created. twindle-cli and twindle-web have been created.
• Mentioned about cli project and went through the readme and just elaborated on the points. We will use nodejs 14, use npm, no other libraries for - cli: all this is ensuring the defaults are available for users without extra steps. We will use airbnb coding standard. We can look at es6, and jest for testing.
• Mentioned about web project. It will evolve over time and will have only one version of the homepage. Use vanilla html, css, js.
• Github actions were setup by kenny.
• Team md file being sorted out.
• Nivetha created a good website design.
• Melissa also created a good website design.
• Video of discussion with Tolga is on youtube. Talks about his experiences, and aws.
• Aravind joined from US. Word of mouth is working.
• Kenny discussed about the github action how it was integrated with github. He will create a video about it.
• Akshay and Pranav discussed about adding images to markdown http://teams.md file. Eyram is also helping out.
• Vijaya Bhaskar mentioned about the website url not working without www.
• Nneyen had a question about pull request. All commits are coming on a single pull request. How can we change the name of the pull request.

Countdown time 5 4 3 2 1 !

• Melissa interrupts! Which one of the other repos should we contribute to? Any ones that you like to. No restrictions. If you approach proful that you want to do something else, like angular or react, he will create a private repo and give access. But primary focus is for the phase 1.

Starting countdown again 5 4 3 2 1.

21-Oct-2020

Week-2 Day-1

28 people joined

• Planning to keep the daily stand up time to 30 mins; the community is growing
• Please let the team know if you’re busy with other stuff; its all open-source
• New tasks: Phase 1 - website and NPM install.
• Everyone should run the issue 408 on you local machine to see if you’re able replicate the pdf conversion and post the screenshot on the issue.
• Pull down the repo and run it locally; follow the instructions.
• Update the http://READ.me file if you find any correction/addition to the project.
• Please share the issues if you run into any.
• Everyone should have access to assigning labels to the issues.
• Based on the code contribution the groups are seggregated.
• Tolga has created a video on the pdf creation using CLI.
• Kudos to Sourabh on the twindle page.
• Please feel free to retweet and share the work on the twindle, twitter is powerful.
• Touch base on the UI design discussion with Tushar yesterday, once the mock up is ready please feel free to share your feedback.
• Don’t feel that you’re duplicating stuff; this is a learning opportunity for many of us to get some expertise we would have to practice.
• Please watch the video on why puppeteer is not the best option; find it on the twindle youtube channel.
• Code more; less talk.

20-Oct-2019

Week-1 Day-7

30 people joined

Phase 1: Landing page/ http://twindle.co

• Entice consumers to sign up to twindle (MVP).
• No rush to get to the end product now; lets take it step by step.
• In the process of identifying people good at different skilss i.e., JavaScript, Design
• npm installation twindle.
• Benefits over hosting on a server, avoid load balancing issue.
• Daily meeting is important, but if you can’t make it that’s totally fine.
• Touch base on the server part of collecting the user emails and storing it.
• Reach out to fellow tech savvies for tech assistance.
• A few of the team has started to work on the pdf generation, yay!

Phase 2 of the project: Hosting

• AWS serverless option over regular hosting.
• Avoid load balancing issue.
• Kudos to Tolga for creating the video on the nodes js stuff her worked on.
• Kingsley did pretty good job on the API work.
• Start sharing your feedback on the twindle logo and get the momentom going, also come up with new logo design.
• Tolga explained a bit about the puppeteer to convert html to pdf.
• Muhammad was able to convert json ePub format; He’ll be drafting a PR for other to look into it.
• Checking out on people to see if anyone worked on the design or APi; Aderinto shared his experience with applying for twitter API
• Come up with a strategy to apply for Twitter API with convincing reasoning.
• Come up with a strategy to apply for Twitter API with convincing reasoning.
• Tushar and Sarath to work on the improvements of home page.

19-Oct-2020

Week-1 Day-6

33 people joined

• Need to switch to independent work mode by guiding and reviewing tasks moving forward, due to time constraints
• Kudos to Madhusudhanbabar(Krypton), Titi and, Tushar.
• Kandpal on the UI design, coming up with good design in short time-frame.
• Took time to put effort in to the design.
• Kudos to Tolga on creating the puppeteer stuff for the pdf rendering.
• Twindle’s first big achievemnt: 100 followers, many more to come.
• Would love to see some ideas to come up with some logo for twindle.
• Some active participation would good to see in the issue thread.
• Kudos to Eyram on fabulous interest in reviewing PRs.
• Must engage with the team and review PRs.
• Record videos when you solve some issues that’ll be useful for others to follow.
• Kenny talked about the self-driven attitude of team memebrs and node js work is coming along nice.
• Mira described the work she did on the benefits and limitations of v2 of Twitter API.
• In the future we may have more videos than direct meetings, so everyone can take it at their own pace.

18-Oct-2020

Week-1 Day-5

20 people joined

• Twitter API to fetch walkthrough by Kenny
• UI design walkthrough by Sarath
• Baby steps in getting started with coding the html template
• Swati Rao made initial commits (yay)
• Good start with the header
• Kenny and Mira did wonderful job on the Twitter API Dev documentation
• Kenny is coming up with a way to use Mock API
• A bunch of tasks are created to address API, Header, Footer content
• All the practice version of html and css should go under playground folder not main source folders
• Feel free to create issues and start working; we’ll improve our review process slowly
• Label the issues appropriately i.e, design. documentation, development
• Avoid copying the code from stackoverflow or other platforms; using those platforms to learn how to fix your issues not just copy the code
• A little bit of discussion on the options to convert JSON to PDF conversion i.e., html2pdf JS lib, pdf2JS lib
• Mira described about the limitations of Twitter API 1.1 and the benefits of 1.2 version
• Is there a limitation with API usage; Upto last seven days of data is displayed and looks like Twitter is working on making info available to devs/accessors
• Discussion on the beta version of the product
• Insights into the final version
• Need to create a beta version UI mock up
• Touch base on the MVP - minimum viable product
• On the future of the product, building more features

Thanks Sarath for capturing.

17-Oct-2020

Week-1 Day-4

40 people joined

• We have Proful, Kenny, Sarath across timezone, so people will help out with PR merging.
• We are adding people to the organization.
• Mentioned about the scripts repository where we can add small utility scripts.
• Went through the contributors list on the repository.will gradually see if more contributors can be added.
• Discussed about the onboarding.md file created by Melissa which gives a new person quick details about how to get started and what all to do. Talked about creating youtube videos to help teach each other. Can ping Proful to get write access.
• Encourage everyone to make contribution in any documentation and other content.
• Discord channel for now is simple, let it evolve over time. Use the general group to have quick chats. Discuss only relevant content in any of the mediums.
• Discussed about adding onboarding content to readme file also. Upto Kenny and Pranav to decide on whether to move the content to ReadMe.md
• Went through a sample PR with a lot of reviewers! This is very good, and should continue to approach reviews in this manner. Ensure that after the latest changes in a PR, you have 2 people reviewing the PR.
• Talked about the merge conflict and how the experience was for everyone. Asked others to write and document their experience and how they fixed it.
• Different reviewers have different perspectives. They ensure best practices. More eyes on the PR is important. For something going into production - what is most important - bugs, or more reviwers.
• UI Design - looking to come up with a good design. Need to be consistent with w3c standards. If you're interested DM Sarath.Invited people to participate in creating initial web pages with HTML5 and CSS3
• Vijaya Bhaskar, Samriddhi and Suraj is going to coordinate with team create issues i.e., HTML header, body etc.lh536, Eyram, techiegeek, lilfatfrank are interested to work.
• Use Dribble to draw some inspiration..Vijaya Bhaskar, Samriddhi and Suraj is going to coordinate with team create issues i.e., HTML header, body etc.
• Discussed about creating issues to capture good samples of designs. We can then create separate files for header, footer etc so people can contribute in parallel. We can start with the website design.

Thanks Sarath and Kenny for capturing, Sravan for combining

16-Oct-2020

Week-1 Day-3

About 30 joined

• We will start the website design with some basic design. We can iterate over time on this design. We will use plain HTML and CSS.

• Why go ahead with working on mock, design, and development instead of getting into nitty gritty details design and color themes? Because of time constraints there is going to be some process compromise initially but that’s okay looking at a larger picture; we will improve

• PRs - look into other people's PR, review it, add comments, ask questions, create PRs and then share the link in twitter asking others to review.

• Proful will add people to the org on github.

• Touch base on the code review process. A place to learn and take ownership on tagging reviewers to take a look and give their feedback.A PR must have two approvals to get merged. The logo selection process is still in progress and open to receive new logos

• Touch base on twindle yt videos on PR creations; please feel free to make videos on the issues our team faces; it does have video length constraints, so please take note of it

• Touch base on the PR merge conflict and new engineers must try to resolve issues; seek out for help if needed

• Discord is available - can use it for audio/video calls whenever needed.

• Everyone should promote twindle on twitter. We want others to become aware and join us to learn and grow. So when you work on something or learn something, or anyone tweets about it, you can like, retweet, etc. And use the hashtag #twindle. Also when someone helps you, or creates articles or videos, share and show appreciation. And we also need experienced people to help out.

• Reiterate the fact that this is a teaching opportunity; please be patient until we start with coding

• A few of us are impatient to get started. But the intention is to help others. The development will happen, but initially we need to make everyone comfortable. And being a developer is not just about coding - discussions, collaborations, building relationships, helping others, these are all essential. These will help you grow. Being a team player is very important too :)

• PRs are important. It is useful to get experienced developer's feedback. Learning the best way to do things out of the million options that are there.

• Don't take any of the feedback personally, its all about the learning more than anything. Take advantage of all the opportunities.

• Played two games 🥳

• Proful introduces a game on twitter

• Start following twindle on twitter

• Start retweeting - show appreciation to melissa, sarath, kenny, proful, sheetal, samriddhi jain, vijaya bhaskar

• Team started to tweet, retweet, like; to show the appreciation to the team members

• All the intentions are in right place; we just have to get things rolled out one after the other. This will take time and we shouldn't rush things

Thanks Sarath, Kenny for noting these

15-Oct-2020

Week-1 Day-2

About 50 joined.

• Talks about initial success of Twindle.
• Overwhelming responses received: 100+ PRs, 90+ PRs merged.
• Appreciation to all the team members who have contributed.

First Experience with Github

• Detailed discussions on PRs
• 5/6 participants talked about their first PR experience (wonderful).
• Touched base on being a 'Contributor' is more important than being the one who 'Merges', however, being a 'Contributor' is more important. (Need few gate keepers to avoid many chefs in the kitchen - scenario)
• Importance of being a Code Reviewer.

General

• Technical discussions must be refrained from Twitter groups.
• Must use GitHub issues actively.
• Touched base on Versioning. (discussed in an issue)
• Not everyone has access to label the issues. However, project owners can do that.
• FAQ documentation was created by 2 members.
• Try to share relevant information on 'Resources' documentation in the GitHub Repositories.
• Touched base on Naming conventions of File and Folder level naming directory scaffolding.
• Try to come up with some information on naming conventions.
• Directions on creating the 3rd PR by making changes on TEAM.md (compulsory).
• Try to capture recording on making PRs locally.
• Two members are looking into CLI, Twitter API, PDF, and, ePUB Design.
• Figma: Prototyping Software.
• Experiment with color theme and we can finalize the theme once we can finish logo design.
• Coding plan will be discussed step by step consequently.
• For any help you can raise any number of issues in the repo.

Thank you @sarathkumar6 and @vijaya-bhaskar for noting these during the meet.

14-Oct-2020

Week-1 Day-1

About 45/60 joined.

• Walkthrough of Github repository/organization
• Domain twindle.co purchased by @proful
• Collaborate using twitter, gh, sketchnotes - keep low number of tools to use, maybe consider other options if we grow a lot
• FAQ page will be created. It was created here
• Split teams into
  • Beginner (bare minimum experience)
  • Independent (can work independently/mentor)
  • Active (say organizers)
• everyone get onboard with setting up github account, clone repo, make changes to files
• fork process (after cloning the repo)
  • draft PR from gh website
  • draft PR from laptop
• which client to use for git - need to pick one from github desktop, sourcetree, gitlens
• a brief explanation about PR
• touched on logo design
• break up the project into smaller chunks
• why no hacktober fest - keep PRs minimum, not doing this for freebies
• tech stack - html, css, js (nodejs)
• touch on naming convention, coding standard, e.g. google standard, airbnb standard
• importance of testing and using Jest for js testing
• documentation is critical, any features can be added to issues
• touch on how to make a cli, showed an example
• twitter API integration discussion, creating a mock API (JSON file)
• renderer - render to PDF/ePub/mobi, etc.

Thanks @sarathkumar6 for documenting, does anyone have any points to add