allowing for core dumps for debugging

* Adding code of conduct and supporting 'meta' process information

busunit/rootfs/etc/security/limits.conf

@@ -0,0 +1,57 @@
+# /etc/security/limits.conf
+#
+#Each line describes a limit for a user in the form:
+#
+#<domain>        <type>  <item>  <value>
+#
+#Where:
+#<domain> can be:
+#        - a user name
+#        - a group name, with @group syntax
+#        - the wildcard *, for default entry
+#        - the wildcard %, can be also used with %group syntax,
+#                 for maxlogin limit
+#        - NOTE: group and wildcard limits are not applied to root.
+#          To apply a limit to the root user, <domain> must be
+#          the literal username root.
+#
+#<type> can have the two values:
+#        - "soft" for enforcing the soft limits
+#        - "hard" for enforcing hard limits
+#
+#<item> can be one of the following:
+#        - core - limits the core file size (KB)
+#        - data - max data size (KB)
+#        - fsize - maximum filesize (KB)
+#        - memlock - max locked-in-memory address space (KB)
+#        - nofile - max number of open file descriptors
+#        - rss - max resident set size (KB)
+#        - stack - max stack size (KB)
+#        - cpu - max CPU time (MIN)
+#        - nproc - max number of processes
+#        - as - address space limit (KB)
+#        - maxlogins - max number of logins for this user
+#        - maxsyslogins - max number of logins on the system
+#        - priority - the priority to run user process with
+#        - locks - max number of file locks the user can hold
+#        - sigpending - max number of pending signals
+#        - msgqueue - max memory used by POSIX message queues (bytes)
+#        - nice - max nice priority allowed to raise to values: [-20, 19]
+#        - rtprio - max realtime priority
+#        - chroot - change root to directory (Debian-specific)
+#
+#<domain>      <type>  <item>         <value>
+#
+
+*               soft    core            unlimited
+#*               soft    core            0
+#root            hard    core            100000
+#*               hard    rss             10000
+#@student        hard    nproc           20
+#@faculty        soft    nproc           20
+#@faculty        hard    nproc           50
+#ftp             hard    nproc           0
+#ftp             -       chroot          /ftp
+#@student        -       maxlogins       4
+
+# End of file

meta/ISSUE_TEMPLATE.md

@@ -0,0 +1,24 @@
+When submitting an issue through the issue tracker, please indicate whether it's a bug, feature or other issue.
+
+* **I'm submitting a(n) ...**
+  - [ ] bug report
+  - [ ] feature request
+  - [ ] other issue (please describe)
+
+* **Do you want to request a *feature* or report a *bug*?**
+
+* **What is the current behavior?**
+
+* **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo, screenshot or any other information that will help highlight the problem** 
+
+* **What is the expected behavior?**
+
+* **What is the motivation / use case for changing the behavior?**
+
+* **Please tell us about your environment, if relevant:**
+  
+  - Software Version:
+  - Operating System:
+  - Browser:
+
+* **Other information** (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context) 

meta/README.md

@@ -0,0 +1,6 @@
+Popufare Repository Management (meta)
+===
+
+This directory is for process related documents or other data files
+relating to the management of the repository itself.
+

meta/reporting_guidelines.md

@@ -0,0 +1,53 @@
+# Reporting Guidelines
+
+If you believe someone is violating the code of conduct we ask that you report it to Clementine Computing LLC by emailing info@clementinecomputing.com. 
+
+**All reports will be kept confidential.** In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
+
+If you believe anyone is in physical danger, please notify appropriate emergency services first. If you are unsure what service or agency is appropriate to contact, include this in your report and we will attempt to notify them.
+
+In your report please include:
+
+* Your contact info for follow-up contact.
+* Names (legal, nicknames, or pseudonyms) of any individuals involved.
+  * If there were other witnesses besides you, please try to include them as well.
+* When and where the incident occurred. Please be as specific as possible.
+* Your account of what occurred. 
+  * If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link.
+* Any extra context you believe existed for the incident.
+* If you believe this incident is ongoing.
+* Any other information you believe we should have.
+
+## What happens after you file a report?
+
+You will receive an email from Clementine Computing's Code of Conduct response team acknowledging receipt as soon as possible, but within 24 hours.
+
+The working group will immediately meet to review the incident and determine:
+
+* What happened.
+* Whether this event constitutes a code of conduct violation.
+* What kind of response is appropriate.
+
+If this is determined to be an ongoing incident or a threat to physical safety, the team's immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe.
+
+Once the team has a complete account of the events they will make a decision as to how to respond. Responses may include:
+
+* Nothing (if we determine no code of conduct violation occurred).
+* A private reprimand from the Code of Conduct response team to the individual(s) involved.
+* A public reprimand.
+* An imposed vacation (i.e. asking someone to "take a week off" from a mailing list or IRC).
+* A permanent or temporary ban from some or all Clementine Computing's spaces (events, meetings, mailing lists, IRC, etc.)
+* A request to engage in mediation and/or an accountability plan.
+
+We'll respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved.
+
+Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but our response will be determined by what will be best for community safety.
+
+Finally, the response team will make a report on the situation to Clementine Computing LLC's management. The Clementine Computing LLC's management may choose to issue a public report of the incident or take additional actions.
+
+## Appealing the response
+
+Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the working group, contact Clementine Computing LLC at info@clementinecomputing.com with your appeal and Clementine Computing will review the case.
+
+_Revision 1.0, DRAFT, proposed June 2014_
+_Reporting Guidelines derived from those of the [Django Software Foundation](https://www.djangoproject.com/conduct/reporting/)._