![]() ![]() Prettier / TSLint / ESLint as code linter.CircleCI for continuous integration (automatize development process).Respectively Git as revision control system.GitHub Pages/ Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool Our whole DevOps stack consists of the following tools: If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost. With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent. Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already. Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free! I stumbled on Firebase by #Google, and it was really all I needed. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go. I was building a personal project that I needed to store items in a real time database. We have a custom bot project,, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab. It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. You can't let anyone with a GitHub account self-assign issues to themselves.You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker: and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.īut even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete. Right now we just have a Description field. ![]() In saying that what I would love Trello to implement is to allow me to create custom fields. But for smaller #Startups that want to hit the ground running Trello for me is the way to go. I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA Like setting up a project, user rules etc. What was so great about this was it didn't come with all the complexity of JIRA. ![]() When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using. So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |