init

Author: Shiven110504

LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2019 HackUMass & HackHer413
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -0,0 +1,77 @@
+# HackUMass X Configuration
+Welcome to the example Dashboard configuration repository. This repository is intended to be a [submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules) of the [main Dashboard repo](https://github.com/fuseumass/dashboard). If you're reading this README we are assuming that you've decided to take the plunge and use Dashboard for your own event. Let's get started!
+
+# Getting started
+First we are going to ask that you please clone the main dashboard repository. You can do that by running `git clone https://github.com/fuseumass/dashboard.git`
+
+Next please create a fork of the `redpandahacks-config` repository. You can do this by clicking the "fork" button at the top right hand corner of this page.
+
+It's at this point that we get into some slightly complicated git magic. If you want an explanation of how it all works, please see the [wiki page](https://github.com/fuseumass/redpandahacks-config/wiki/Submodules) that we've created on git submodules. If you're wondering why in gods name we've chosen such an architecture, please also consult the wiki. Otherwise, let's just follow along with the following steps.
+
+Fortunately there's basically 0 consequences if you mess this up, as you can _always_ delete the repo and start over without losing much (if any) work.
+
+## Setting up the submodule
+Open the `.gitmodules` file from the Dashboard repo that you've cloned. It should look something like this:
+```
+[submodule "hackathon-config"]
+    path = hackathon-config
+    url = https://github.com/fuseumass/redpandahacks-config
+```
+Inside this file, please replace the url with your url to the forked config repo. It should look something like this `https://github.com/your-username/yourhackathon-config`. Save this file.
+
+Now you'll want to open a terminal and navigate to the folder containing the dashboard folder. Here, you'll want to run the following command `git submodule update --init --remote`.
+
+Double check that Git has updated the configuration repo properly by seeing whether any of the files in the `hackathon-config` folder were updated with those from the `yourhackathon-config` repo. If it still shows up as redpandahacks, try this to bypass the flawed behavior of the git submodule update command above:
+ - `rm -rf hackathon-config`
+ - `git clone https://github.com/your-username/yourhackathon-config hackathon-config`
+
+Now the `hackathon-config` folder is a submodule that tracks the github repository you created for your fork.
+
+## Running the application
+In order to simplify the development process we use Docker to develop locally. Please download it here: [https://www.docker.com/products/docker-desktop](https://www.docker.com/products/docker-desktop). If you wish to develop without docker you'll have to set up and install Ruby and Rails on your own.
+
+1. After installing Docker, navigate to the dashboard folder in your terminal
+2. Run `docker_build.sh` or `docker_build.bat` depending on your platform
+3. Run `docker_run.sh` or `docker_run.bat`
+4. Navigate to [http://localhost:3000](http://localhost:3000) in your web browser of choice
+5. You can log in with the credentials `[email protected]` and `testpass`
+6. All of the features are turned off by default, so in order to view everything go to the `admin` tab and then click `feature flags`. Turn on the things you'd like to test/view/use.
+
+## Editing the hackathon config
+At this point you'll probably want to edit the hackathon config to suit your needs. We won't go over the documentation for each option here (you can check the wiki for that). But we will go over a few steps you'll need to follow in order to make changes to this submodule git repository.
+
+1. First navigate in your terminal to the `hackathon-config` folder.
+2. Next please run `git checkout master`
+3. Make all the edits you desire in the `hackathon-config` folder (you can preview these at the site running at [http://localhost:3000](http://localhost:3000) by simply refreshing the page)
+    - Note: You may have to make some additional accounts that are attendees or mentors in order to be able to visit all of the pages.
+4. From within your `hackathon-config` folder, add your changes to be tracked by git with `git add .` and then run `git commit -am "Your commit message here"` to commit your changes.
+5. Finally run `git push origin master`
+
+At this point if you ever find that your submodules are messed up in any way. You can always just delete your local dashboard repository and run through the steps in [setting up the submodule](#setting-up-the-submodule) again. Since your changes to the configuration repo are already pushed to the remote, you won't lose them.
+
+Now that you've pushed your submodule to it's remote. We can update the main dashboard repository. Just run `git add .` and `git commit -am "updated copy"` from the main dashboard folder.
+
+## In the case of updates
+In the case of updates to the main dashbaord repo. You can pull them into your local copy by simply running `git pull -r origin master` from within your local dashboard folder. This method will _never_ have any conflicts. Enjoy seamless updates that you can integrate as soon as we release them :)
+
+In the case of updates to dashboard that also require updates to the config repo (we'll try to avoid this as much as possible!). We will communicate this change in the release notes and you will have to deal with a merge conflict. Simply keep as much of your copy as you can while also integrating the changes we've made.
+
+In this situation you'll have to do the following from within your `hackathon-config` folder.
+1. `git add remote upstream https://github.com/fuseumass/redpandahacks-config.git`
+2. `git pull upstream master`
+3. Deal with the merge conflicts! Keep your copy, and our formatting and you should be good to go :)
+
+# Deployment
+For specific deployment instructions, please see the [dashboard wiki](https://github.com/fuseumass/dashboard/wiki/%5BUsers%5D-Deployment).
+
+# Issues
+If you encounter issues with the functionality of Dashboard please create an issue on the [issues page](https://github.com/fuseumass/dashboard/issues) of the main Dashboard repository and tag it with the `bug` label.
+
+If you encounter issues with the functionality of the configuration files, please file a bug report on this repository's [issues](https://github.com/fuseumass/redpandahacks-config/issues) page and tag it with the `bug` tag so that we can track it.
+
+Finally if you need technical assistance with setting up or deploying dashboard, use the [issues](https://github.com/fuseumass/redpandhacks-config/issues) page on this repository and tag your post with `technical support`.
+
+# Contributing
+We welcome your contributions to this open source project and we actively encourage every event who's using it to commit their tech resources to help make Dashboard better for everyone. To get started developing, head over to the [dashboard wiki](https://github.com/fuseumass/dashboard/wiki) and follow the instructions for setting up dashboard for development.
+
+We thank you for any contributions or suggestions you have ❤️

assets/images/HackUMassLogo.png

@@ -0,0 +1,9 @@
+// Custom javascript code which is run on every page.
+
+var init = function() {
+    console.log("This is custom javascript run on every pageload.");
+}
+
+window.addEventListener('load', init);
+$(document).on('turbolinks:load', init);
+

assets/images/favicon.ico

@@ -0,0 +1,6 @@
+/* This is custom CSS applied to every page. */
+
+/* This will change the avatar image for every user. */
+span.avatar {
+    background-image: url(https://hackumass.com/assets/img/avatar/1.jpg) !important;
+}

assets/images/navlogo.png

@@ -0,0 +1 @@
+I authorize MLH to send me occasional emails about relevant events, career opportunities, and community announcements.

assets/javascripts/custom.js

@@ -0,0 +1,3 @@
+By checking the box below you agree to UMass' <a href="http://hackumass.com/legal/HUMVPhotoRelease.pdf">
+Photo Release</a> requirement and <a href="http://hackumass.com/legal/HUMVLiabilityWaiver.pdf">
+Liability Waiver</a>.

assets/stylesheets/custom.css

@@ -0,0 +1,4 @@
+I have read and agree to the <a href="https://github.com/MLH/mlh-policies/blob/main/code-of-conduct.md">
+MLH Code of Conduct</a>. I authorize you to share my application/registration information with Major League Hacking for event administration, ranking, and MLH administration in-line with the <a href="https://github.com/MLH/mlh-policies/blob/main/privacy-policy.md">MLH Privacy Policy</a>.
+I further agree to the terms of both the <a href="https://github.com/MLH/mlh-policies/blob/main/contest-terms.md">
+MLH Contest Terms and Conditions</a> and the <a href="https://mlh.io/privacy">MLH Privacy Policy</a>.