Hello Everyone,

I have created a document as to how to use the Git project board. Kindly review the same and if you have any feedback, you can add the comment. Below is the link to the Google Doc:

https://bit.ly/3o5tteA

Thanks & Regards,

Rohit Gupta

Hey everybody, I have a Jira board and want to link it to the Canonizer Github. However, This would require the owner Brent to create a Jira account and then establish the connection. Since we are all in agreement that a ticketing process like Jira will support our work. I will coordinate with Him to get that set up. In the meantime, we can continue to utilize the spreadsheet that was created. 

Thanks, Jake

GitHub has a ticketing system of sorts but it takes a KanBan approach to ticketing system that does not offer enough support for roadmapping larger projects. Considering the depth of this project and its scalability, Jira is the best option. GitHub actually has a Jira plugin that would allow us to seamlessly track and project tasks. If we want to take a truly agile approach to Canonizer, we must embrace the agile model and utilize a ticketing system that compliments sprint management. 

Great to hear everyone collaborating here!  I am noticing all of these contributions, and they each increase my respect for your team.  Brandon aka TheSmokingPeanut, suggesting using Jira to help manage things, and fill in where our current Github system is lacking.  I’m glad to see there is so much support for the Github issues system we are already using.  I’m not familiar with Jira, but I’m wondering if there is any functionality there, that might help us with this, maybe using both, with cross references back and forth?  Brandon, would we be able to do everything you think is important with only GitHub?

Brandon also suggested we start doing daily scrum standups, which I think is a great idea.  What time would work best for everyone to do this.  Should we do it 5 days a week, Mon-Fri?  What would be the best time?

I think it would also be great if we had a scrum master, to manage the details of the meeting.  Thanks for volunteering to do this, Brandon.  Is there anyone else who would like to be a scrum master?  If Brandon is the only one, we can delegate this responsibility to him?  If there are others interested, we can do some random process to select someone?

We as a experienced IT company propose to use GitHub as centralized open source system for all project related matters. Git hub has better ticketing system as well documentation system "wiki" for all research and analysis work. Following are few points i would like to highlight why we should use git hub for task and assignments too.

1. GitHub's customization and flexibility in labeling positions it as the best ticketing tool on the market. We can assign any customized priority label to tickets which makes it very simpler to developer and project lead to handle.

2. By using GitHub, you make it easier to get great documentation. Their help section and guides have articles for nearly any topic related to git that you can think of.

3. Markdown allows you to use a simple text editor to write formatted documents. GitHub has revolutionized writing by channeling everything through Markdown: from the issue tracker, user comments, everything. With so many other programming languages to learn for setting up projects, it’s really a big benefit to have your content inputted in a format without having to learn yet another system.

4. Track changes in your code across versions against ticket id against all push request, when multiple people collaborate on a project, it’s hard to keep track revisions, who changed what, when, and where those files are stored. GitHub takes care of this problem by keeping track of all the changes that have been pushed to the repository. Much like using Microsoft Word or Google Drive, you can have a version history of your code so that previous versions are not lost with every iteration and every ticket can be linked to push request.

5. GitHub can integrate with common platforms such as Amazon and Google Cloud, services such as Code Climate to track your feedback, and can highlight syntax in over 200 different programming languages.

6. Compared to all other ticketing tools, GitHub Issues is the only platform giving entire freedom to define whatever types of labels you want. All other tools have an opinion on label types, such as priority, severity, component, epic, etc. 

So GitHub is superb and easiest understandable tool for ticketing, code version management, documentation, etc. 

I can lead and setup developer assignments for all current pending tickets and priority.

Thanks

Team Talentelgia

Hi Guys,

We already have ticketing system at GitHub and it's very clear to understand. Assignment to various developer can be done there and easy to track with code push too. Please share all engineers emails or username so that task can be assigned there.

First of all pls clear who is working on what and what's the profile. Let's discuss in Monday meeting then task assignment can be done on GitHub .

I propose that we establish a ticketing system to clearly outline the work that needs to be completed and who is completing it. I will act as a scrum master holding daily standups with all engineers and manage the tickets that are being worked. Currently, there are issues in the Github repo. These issues can be translated into cards on the Jira board with an assigned developer. We can also create cards for research that needs to be done surrounding a specific task. Furthermore, we can establish sprints that compliment the weekly/daily meeting(s). Working in sprints will allow us to understand the teams trajectory and focus on completing the tasks in a timely manner. Please respond with all emails so that I can invite you to the Jira board. 

I propose that we establish a ticketing system to clearly outline the work that needs to be completed and who is completing it. I will act as a scrum master holding daily standups with all engineers and manage the tickets that are being worked. Currently, there are issues in the Github repo. These issues can be translated into cards on the Jira board with an assigned developer. We can also create cards for research that needs to be done surrounding a specific task. Furthermore, we can establish sprints that compliment the weekly/daily meeting(s). Working in sprints will allow us to understand the teams trajectory and focus on completing the tasks in a timely manner. Please respond with all emails so that I can invite you to the Jira board. 

Could you define design as it relates to this camp? Is this an architecture for this site or is it more of a UI flow?