-
Notifications
You must be signed in to change notification settings - Fork 132
Meeting Notes
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.
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
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.
- 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.
- 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.
About 45/60 joined.
- Walkthrough of Github repository/organization
- Domain
twindle.copurchased 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