Keep in mind that you only need to escape a character when it could be treated as a Markdown command. \*Backslash Escapes\* To display a literal character that Markdown could otherwise interpret as formatting syntax (e.g., asterisks), use a backslash before the character. | Column Header | Column Header | | - | - | | Row 1, Column 1 | Row 1, Column 2 | | Row 2, Column 1 | Row 2, Column 2 | * First item * Second item * Third item Can use asterisks (*), hypens (-), or plus signs (+)ġ. There are no ads in this search engine enabler service.# Heading 1 # Heading 2 # Heading 3 # Heading 4 ℹ️About GitHub Wiki SEE, a search engine enabler for GitHub WikisĪs GitHub blocks most GitHub Wikis from search engines. Open source developer's schedule different to our team's schedule. lint helps the Zettlr's reviewer efficiency Zettlr contributions require lint before pull requests.Require to add proper comment in code for functionality description.Better architecture (location of where changes should go).Zettlr developer review provided high quality comments on our team's code.Our team could have engaged to the Zettlr developers earlier about the right place. Our initial pull request didn't put the code in the right place according to the Zettlr layout and Zettlr developers.Implementation review is much slower - one exchange in 11 days (Due project owner is a student and has an exam on 1st June). Our team exchanged design and ideas back-and-forth with Zettlr developers six times in 16 days. It was a good idea to share a design with Zettlr developers before sharing the implementation.What did you learn from the feedback you received on your pull request(s)? (4 points) (2mins) (Tianqing) For example, the core Zettlr developer was fairly inactive in late-May because he is studying for an exam on 1st June. Contribution process can be easily held up by the open source community.Our first PR #1959 received quick initial feedback, but the full review took 11 days. Community members have their own schedule and review feedback can take time.Provided assistance to two questions from our team on the forums. Provided suggested improvements, tips on the Zettlr's code layout, and checklists of things to do (translation, documentation) Responded positively to our team's design 1st.Quick and friendly welcome message in response to our team's introduction message.What was your experience interacting with the Open Source community? (4 points) (2mins) (Tianqing) Documented developer commands do not exist: build:quick handlebars release:this release:win watch wp:dev Developer documentation is out-of-date.It takes times to get different OS and test on them. Testing is challenging as the Tray feature is applied on multiple platforms.It is hard to identify a bug is raised by our development or it is an existing bug in main branch.About 1 minute on a MacBook Air and 2 minutes on windows 10. Zettlr in developer mode takes a long time to start.Debugging breakpoints often didn't work on first attempt.Zettlr supports hot-loading, but was unreliable.PR #1852 Merged by Zettlr developer nathanlesage.What challenges did you have to overcome? (5 points) (2.5mins) (Zihe Peter) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |