Challenge Overview
App environment:
Basic Requirements for this challenge:
- Fix issues based on previous result of Bug Hunt challenge
Project Background
Thor PDU Mass Commissioning - Overview
A PDU (Power Distribution Unit) is a device fitted with multiple outputs designed to distribute electric power, especially to racks of computers and networking equipment located within a data center. The PDU Mass Commissioning tool that we are designing will allow users to create configuration files and networking capabilities for PDUs in a system. The app will allow for the necessary configuration parameters needed for operation within the system. Once all of the configuration parameters have been set within the app, users will be able to "export" the files to a USB drive, which will be plugged into the PDUs to be commissioned.
The PDU Mass Commissioning tool will be a simple user interface that allows customers to create all of the necessary configuration files to configure all of their PDUs. The app will have a variable number of input fields for all the configuration parameters in which users will enter their desired configurations. Once they have entered all of the configuration parameters they will click "export" and the application will build the configuration file hierarchy into a chosen USB drive.
About PDU Mass Commissioning App
- PDUs (Power Distribution Units) equipment have several parameters which need to be configured before the first use
- The Mass commissioning application to be developed aims at expediting the commissioning process in case of large amounts of PDUs to be configured (from 20 to several hundreds of units)
- Targeted audience: industrial users
Basic process flow
- The user defines the value of the configuration parameters he wants to apply to the PDU in the PDU mass deployment Software tool (to be developed during the Topcoder challenge)
- The different parameters are exported to a standard USB key in the form of pre-defined configuration files (the files naming convention and file hierarchy must be respected)
- The user plugs the USB flash drive into the PDU(s) to be commissioned
- The PDU automatically detects the correctly formatted USB flash drive and reconfigures itself with settings found on the USB flash drive
Technology Stack
- Meteor JS
- Angular Meteor Integration
- Meteor desktop (https://github.com/wojtkowiak/meteor-desktop)
Deployment environment requirements
IMPORTANT: Your submission need build as desktop native app that will working on these required OS:
- Windows 7
- Windows 10
Challenge Assets
Check this storyboard flow: https://drive.google.com/open?id=1hlXH5M_5APHz43PJWghe40kBN0HfAZgN
Latest App to test:
https://gitlab.com/thor-pducomm/meteor-app > Use dev branch
Check .desktop-installer folder for the app demo. Please use the latest version.
General Requirements:
- In this Bug Bash challenge, we are looking for your help to fix a bunch of bugs in our repo.
- Read about Bug Bash description here: https://help.topcoder.com/hc/en-us/articles/115002087948-What-is-a-Bug-Bash-
- The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.
- Keep best practice of code implementation using Meteor.JS and Angular
- Please, subscribe yourself to get notifications from this frontend and backend repos to participate in this Bug Bash.
Bug Bash Rules:
- Each issue has a dollar value. Dollar values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself with a "tcx_OpenForPickup" (first come first serve).
- You must update the label to “tcx_Assigned”, and remove the “tcx_OpenForPickup” label.
- You can only self assign one issue at a time. The nature of it being assigned will indicate if it is not available to anyone else.
- You will fix the ticket as a pull request to the master branch
- Once a ticket is fixed, you should label it "tcx_ReadyForReview" where it will then be verified. If something is still broken, the copilot will comment on the ticket.
- After submitting and tagging "tcx_ReadyForReview" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
- If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "tcx_FixAccepted".
- If the ticket is “tcx_Feedback”, it should be your first priority to fix the issue.
- When the ticket is closed, payment will be recorded, when we issue the payment the tag will be updated to “tcx_Paid”
- If an assigned task is not done in 8 hours, you will be unassigned from the ticket, and it will be opened back up to the community.
- You can ask questions directly on the ticket comments.
- Bug Bashes are different than Bug Hunts - please make sure to check the contest type in the contest name when registering.
IMPORTANT:
- DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need to track your changes so focus only code fixes.
- DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.
- RE-TEST AND COMPARE ON all required Windows 7 and Windows 10 before you submit.
SUBMISSION FLOW
- First, make sure your "dev" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.
- CREATE NEW BRANCH based on our latest "dev" branch with the title format "issues/handle/XX" where XX is the number on the GitLab Issue.
- DO NOT FORK into your own repo. you MUST create from our "dev" branch. We will reject your submission if you submit from your own repo.
- Start working your fixes in that branch, commit and push to your working repo.
- Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.
- Next you will send MERGE REQUEST to "dev".
- Put Ticket url you were working on in the Merge Request description.
- If something is still broken, the Reviewer will comment on the ticket. We will update the label as " tcx_Feedback" and you can complete the fixes based on the feedback.
General Bug Fixes Requirements:
- In this challenge, we need your help fix issues from previous Bug Hunt challenge.
- Read details Steps to reproduce, including any needed information on each ticket
- Your solution MUST not break existing application.
- We already set initial prizes for each ticket, if the spend more efforts, let us know if prize need adjusted.
Check this url see all open tickets:
https://gitlab.com/thor-pducomm/meteor-app/issues
Primary target device(s): Desktop App
OS Requirements
- Submit merge request to our repo against dev branch
- Create new branch on our repo with this format: issues/tc_username/number_issue
- Make sure your submission have not error conflicts
- Meteor Javascript application: https://www.meteor.com/
- Must testing as Native App on Windows 7 and Windows 10
Basic Requirements for this challenge:
- Fix issues based on previous result of Bug Hunt challenge
Project Background
Thor PDU Mass Commissioning - Overview
A PDU (Power Distribution Unit) is a device fitted with multiple outputs designed to distribute electric power, especially to racks of computers and networking equipment located within a data center. The PDU Mass Commissioning tool that we are designing will allow users to create configuration files and networking capabilities for PDUs in a system. The app will allow for the necessary configuration parameters needed for operation within the system. Once all of the configuration parameters have been set within the app, users will be able to "export" the files to a USB drive, which will be plugged into the PDUs to be commissioned.
The PDU Mass Commissioning tool will be a simple user interface that allows customers to create all of the necessary configuration files to configure all of their PDUs. The app will have a variable number of input fields for all the configuration parameters in which users will enter their desired configurations. Once they have entered all of the configuration parameters they will click "export" and the application will build the configuration file hierarchy into a chosen USB drive.
About PDU Mass Commissioning App
- PDUs (Power Distribution Units) equipment have several parameters which need to be configured before the first use
- The Mass commissioning application to be developed aims at expediting the commissioning process in case of large amounts of PDUs to be configured (from 20 to several hundreds of units)
- Targeted audience: industrial users
Basic process flow
- The user defines the value of the configuration parameters he wants to apply to the PDU in the PDU mass deployment Software tool (to be developed during the Topcoder challenge)
- The different parameters are exported to a standard USB key in the form of pre-defined configuration files (the files naming convention and file hierarchy must be respected)
- The user plugs the USB flash drive into the PDU(s) to be commissioned
- The PDU automatically detects the correctly formatted USB flash drive and reconfigures itself with settings found on the USB flash drive
Technology Stack
- Meteor JS
- Angular Meteor Integration
- Meteor desktop (https://github.com/wojtkowiak/meteor-desktop)
Deployment environment requirements
IMPORTANT: Your submission need build as desktop native app that will working on these required OS:
- Windows 7
- Windows 10
Challenge Assets
Check this storyboard flow: https://drive.google.com/open?id=1hlXH5M_5APHz43PJWghe40kBN0HfAZgN
Latest App to test:
https://gitlab.com/thor-pducomm/meteor-app > Use dev branch
Check .desktop-installer folder for the app demo. Please use the latest version.
General Requirements:
- In this Bug Bash challenge, we are looking for your help to fix a bunch of bugs in our repo.
- Read about Bug Bash description here: https://help.topcoder.com/hc/en-us/articles/115002087948-What-is-a-Bug-Bash-
- The bug list will be updated frequently, we will be adding new bugs and closing bugs that you and other competitors fix. Make sure to keep watching the GitLab list.
- Keep best practice of code implementation using Meteor.JS and Angular
- Please, subscribe yourself to get notifications from this frontend and backend repos to participate in this Bug Bash.
Bug Bash Rules:
- Each issue has a dollar value. Dollar values are based upon complexity and priority of issue.
- You can assign any unassigned issue to yourself with a "tcx_OpenForPickup" (first come first serve).
- You must update the label to “tcx_Assigned”, and remove the “tcx_OpenForPickup” label.
- You can only self assign one issue at a time. The nature of it being assigned will indicate if it is not available to anyone else.
- You will fix the ticket as a pull request to the master branch
- Once a ticket is fixed, you should label it "tcx_ReadyForReview" where it will then be verified. If something is still broken, the copilot will comment on the ticket.
- After submitting and tagging "tcx_ReadyForReview" you are eligible to accept another. You can do as many tickets as you want, as long as you follow the rules above.
- If the ticket is fixed properly, your pull request will be merged in, and the ticket will be marked "tcx_FixAccepted".
- If the ticket is “tcx_Feedback”, it should be your first priority to fix the issue.
- When the ticket is closed, payment will be recorded, when we issue the payment the tag will be updated to “tcx_Paid”
- If an assigned task is not done in 8 hours, you will be unassigned from the ticket, and it will be opened back up to the community.
- You can ask questions directly on the ticket comments.
- Bug Bashes are different than Bug Hunts - please make sure to check the contest type in the contest name when registering.
IMPORTANT:
- DO NOT make INDENTATION AND SPACE changes. Please focus on completing challenge Tasks. We need to track your changes so focus only code fixes.
- DO NOT DELETE EXISTING FILES/LIBRARY. Confirm with us if needed.
- RE-TEST AND COMPARE ON all required Windows 7 and Windows 10 before you submit.
SUBMISSION FLOW
- First, make sure your "dev" branch is ALWAYS UPDATED! We will be pushing new code updates in parallel.
- CREATE NEW BRANCH based on our latest "dev" branch with the title format "issues/handle/XX" where XX is the number on the GitLab Issue.
- DO NOT FORK into your own repo. you MUST create from our "dev" branch. We will reject your submission if you submit from your own repo.
- Start working your fixes in that branch, commit and push to your working repo.
- Once you are satisfied with your fixes, you should label it "tcx_ReadyForReview.
- Next you will send MERGE REQUEST to "dev".
- Put Ticket url you were working on in the Merge Request description.
- If something is still broken, the Reviewer will comment on the ticket. We will update the label as " tcx_Feedback" and you can complete the fixes based on the feedback.
General Bug Fixes Requirements:
- In this challenge, we need your help fix issues from previous Bug Hunt challenge.
- Read details Steps to reproduce, including any needed information on each ticket
- Your solution MUST not break existing application.
- We already set initial prizes for each ticket, if the spend more efforts, let us know if prize need adjusted.
Check this url see all open tickets:
https://gitlab.com/thor-pducomm/meteor-app/issues
Primary target device(s): Desktop App
OS Requirements
- Windows 7
- Windows 10
Final Submission Guidelines
What To Submit?- Submit merge request to our repo against dev branch
- Create new branch on our repo with this format: issues/tc_username/number_issue
- Make sure your submission have not error conflicts