added new file tree and remaining change to investment, reports, webi…

…nars, working groups

content/advice-forum/_index.md

@@ -0,0 +1,7 @@
+---
+title: "ADViCE Forum"
+draft: false
+---
+# ADViCE Forum
+
+You can access the ADViCE Forum [here](https://github.com/alan-turing-institute/ADViCE/discussions)

content/challenges/_index.md

@@ -0,0 +1,7 @@
+---
+title: "ADViCE Challenges"
+draft: false
+---
+# ADViCE Challenges
+
+Explore the decarbonisation challenges with the set of [virtual challenge cards](https://es-catapult.github.io/advice-challenge/) 

content/community-guidelines/_index.md

@@ -0,0 +1,10 @@
+---
+title: "Community Guidelines"
+draft: false
+---
+# Community Guidelines
+About page
+
+This community space is for cross-sector collaboration and knowledge sharing.
+ADViCE (AI for Decarbonisation Virtual Centre of Excellence) is delivered by a collaborative consortium that includes Digital Catapult, Energy Systems Catapult and The Alan Turing Institute, all of which bring extensive knowledge and delivery experience in technical, business and industry solutions across AI, policy monitoring and analysis. Its aim is to drive cross-sector collaboration and coordination, define key challenges that are tractable to AI solutions, and disseminate information to relevant stakeholders. ADViCE engages with AI and decarbonisation stakeholders across relevant sectors. By facilitating the dissemination of knowledge, it aims to coordinate and foster collaboration on AI innovations with decarbonisation applications.
+

content/community-guidelines/code-of-conduct.md

@@ -0,0 +1,194 @@
+---
+title: "Code of Conduct"
+draft: false
+---
+# Code of Conduct
+# Contributor Covenant Code of Conduct
+
+> Code of Conduct, commonly abbreviated as “CoC”, is a set of rules outlining the social norms, rules, & responsibilities of an individual project, party or organization.
+
+This Code of Conduct document outlines our expectations for 
+participants within the team as well as this online repository (project).
+We also provide steps to reporting any concern, uncomfortable situation 
+or unacceptable behaviour by other participants. 
+We are committed to providing a welcoming, collaborative and inspiring experience 
+for all and expect our code of conduct to be honoured.
+
+We have further adopted the language and content that reflects our values and needs in the project.
+To learn more about why we recommend creating a CODE_OF_CONDUCT.md file, please read the [Participation Guidelines](https://the-turing-way.netlify.app/project-design/project-repo/project-repo-participation.html) chapter in *The Turing Way* Guide for Project Design.
+It is recommended to select and adapt a well established Code of Conduct. Many openly developed projects have a Code of Conduct in place that often is openly licensed and can be re-used and adapted for your project. 
+*The Turing Way* [Code of Conduct](https://github.com/alan-turing-institute/the-turing-way/blob/main/CODE_OF_CONDUCT.md) is one example of a Code of Conduct built on various existing ones and can be adapted further.
+<!--Delete these lines when reusing this repository-->
+
+### Diversity Statement
+
+We encourage everyone to participate and are committed to building a project
+for all. Although we will fail at times, we seek to treat everyone both as
+fairly and equally as possible. Whenever a member has made a mistake, we
+expect them to take responsibility for it. If someone has been harmed or
+offended, it is our responsibility to listen carefully and respectfully, and do
+our best to right the wrong.
+
+Although this list cannot be exhaustive, we explicitly honour diversity in age,
+gender, gender identity or expression, culture, ethnicity, language, national
+origin, political beliefs, profession, race, religion, sexual orientation,
+socioeconomic status, and technical ability. We will not tolerate discrimination
+based on any of the protected characteristics above, including participants with
+any visible or invisible disabilities.
+
+## Our Standards
+
+Examples of behaviour that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behaviour include:
+
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+* The use of sexualised language or imagery, and sexual attention or
+  advances of any kind
+
+## Scope
+
+This Code of Conduct applies to all members participating in the activities, 
+events and processes taking place within the scope of this repository. 
+Specifically, our Code of Conduct applies to any conduct:
+- in interactions within the team/community maintaining this repo
+- at any team activity, communication or event related to this repo
+- outside the team activity when a team member is representing this project
+- by members outside the team engaging on this GitHub repository.
+
+This Code of Conduct also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+a representative at an online or offline event.
+
+## Enforcement 
+
+Instances of harassing, abusive, or otherwise unacceptable behaviour should be
+reported to the community leaders responsible for enforcement.
+
+All reports will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+Together we strive to foster an environment where everyone feels valued, respected, and included.
+
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behaviour and will take appropriate and fair corrective, restorative and 
+action in response to any behaviour that they deem inappropriate, threatening, offensive,
+or harmful.
+
+### Enforcement Responsibilities
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Reporting Incident
+
+If you experience or witness unacceptable behaviour, or have any other concerns, please report it 
+by contacting Francisco Gomez Medina (email: [email protected]) or Gabin Kayumbi (email: [email protected]). Francisco and Gabin may involve Susie Costard <[email protected]> ADViCE project manager when incidents are perceived 
+as difficult (not straightforward) except when any potential conflict of interest may arise.
+
+To report an issue involving either Francisco or Gabin, please email directly to Susie Costard <[email protected]>. 
+
+In your report please include:
+
+- Your contact information.
+
+- Names (real, nicknames, or pseudonyms) of any individuals involved. If there
+  are additional witnesses, please include them as well. Your account of what
+  occurred, and if you believe the incident is ongoing. If there is a publicly
+  available record (e.g. a mailing list archive or a public IRC logger), please
+  include a link.
+
+- Any additional information that may be helpful.
+
+We will respect confidentiality requests all the time for the purpose of protecting individuals who have been harmed.
+
+### Terminology
+
+* Reporter: Person reporting an incident.
+* Reportee: Person being reported.
+
+## Report Handling Process
+
+After receiving a report, the community leaders (or person handling the report), team lead or programme director in this case, will review the incident report and follow this process to determine the cause and consequences that violated this Code of Conduct and take further actions:
+
+Community leaders will reach out to the reporter to ask for further information if the submitted report is not complete or needs some additional context.
+Community leaders will also ensure that person impacted or harmed by the reported incident is safe and identify how they can be further supported.
+
+A meeting with the reportee will be scheduled where the person handling the report will discuss four questions:
+- What happened?
+- What were you thinking at the time?
+- Who has been affected by what you have done? In what way?
+- What do you think you need to do to make things right?
+
+When the incident in question inflicted harm on another person, additional 
+questions will be asked on behalf of the person(s) harmed:
+- What did you think when you realized what had happened?
+- What impact has this incident had on you and others?
+- What do you think needs to happen to make things right?
+
+The person handling the report may follow up with reportee or reporter after this discussion 
+with any additional questions to help them reach a resolution.
+
+### Resolutions
+
+Here are examples of possible resolutions to a report. 
+This list is not comprehensive, and any action necessary to reach a fair resolution will be taken as needed. 
+Possible resolutions to an incident include:
+
+- a private communication from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behaviour was inappropriate.
+- an apology to the person harmed or the team as a whole
+- an action plan for the reportee to improve their awareness and correct future behaviours
+- if confirmed by the person reporting, reportee will have no interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period. This includes avoiding interactions in community spaces as well as external channels like social media.
+- not publishing the content that violated the Code of Conduct, until necessary changes have been made and agreed upon by the person handling the report.
+- An imposed suspension, such as asking reportee to “take a week off” from the GitHub repo or team activity.
+- a stronger warning with consequences for continued behaviour. 
+
+The person handling the report will maintain records of all reports so that they may be reviewed if stronger measures are required when repeated violations occur by the same individual as well as to improve our Code of Conduct for future participation.
+
+Once a resolution is agreed upon, but before it is enacted, the person handling the report will contact the reporter and any other affected parties to explain the proposed resolution. 
+They will ask if this resolution is acceptable and must note feedback for the record. However, they are not required to act on this feedback.
+
+The reportee will be contacted via email informing them of the resolution.
+A final meeting may be conducted if necessary.
+
+### Conflict of Interest
+
+All reports will be kept confidential with details shared only with people involved in report handling. 
+If a person handling the report (team lead or programme director) is linked with the ongoing issue, they will declare their Conflict of Interest and remove themselves from any discussion related to the report handling.
+Resolution action may also include identifying appropriate members from within the Open Research Community Building Team if more support for the person handling the report is needed.
+
+## Attribution
+
+This code of conduct is based on the Open Code of Conduct from the [TODO Group](https://github.com/todogroup/opencodeofconduct/), [The Carpentries Code of Conduct](https://docs.carpentries.org/topic_folders/policies/index_coc.html) and [Contributor Covenant
+version 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
+
+The report handling process has been derived from the Eastern University 
+Academic Charter School (EUACS) Student Restorative Justice based Code of Conduct derived from the work of Ted Wachtel
+at International Institute for Restorative Practices (IIRP).
+Restorative Practice Principles are based on Amstutz and Mullet (2005). Restorative Discipline for Schools, pp. 25-26.
+
+Community Impact Guidelines are inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).

content/community-guidelines/how-to-contribute.md

@@ -0,0 +1,73 @@
+---
+title: "How to Contribute"
+draft: false
+---
+# Community Guidelines
+# How to contribute?
+
+Thank you for taking the time to contribute to this project. 🎉
+
+The **Reproducible Project Template** repository is developed under ***[The Turing Way](https://github.com/alan-turing-institute/the-turing-way)* to demonstrate the practical integration of reproducibility practices on the collaborative or shared online repository**.
+
+This project is being developed **openly** and invites contributions from **anyone interested** in reproducible data science who would like to get involved.
+You can suggest topics to include in this repository, report mistakes/bugs, create Pull Requests to fix an error, offer resources or help develop or review the training materials.
+
+We have a [Code of Conduct](./CODE_OF_CONDUCT.md) that applies to all the activities related to this project.
+
+⭐️ You are acknowledged for all kinds of contributions
+---
+
+In this repository, we use the [All Contributors Bot](https://allcontributors.org/) that help us recognise all contributors, even when they don't directly contribute on the repository.
+You can find all [emoji/Type keywords](https://allcontributors.org/docs/en/emoji-key) representing the types of contribution. 
+
+To add a contributor, comment on Issue or Pull Request (where the contributor is involved) using this message for @all-contributors:
+`@all-contributors please add @<username> for <keyword in the Type column>`
+
+## Whatever is your availability, there is a way to contribute to this GitHub repository.
+
+👋 I'm busy, I only have 5 minute
+---
+
+Look through our currently open [issues](../../issues) to troubleshoot an issue or participate in an ongoing discussion by commenting.
+You can also share this repository with someone who might be interested to get involved.
+
+⏳ I've got 15 minutes - tell me what I should do
+---
+
+You can read our [README](./README.md) file to find details and the next milestones in the project.
+You can also read different issues in this repository and comment where you would like to be involved.
+
+🎉 It's my life's mission to enable reproducibility in data science and research
+---
+
+Please share feedback on the contents proposed for setting up an online collaborative repository for data science and research.
+You are encouraged to review the material as we collaboratively develop them and get involved where you can.
+Please open a GitHub issue to suggest a new topic, contribute code, or let us know about errors/bugs.
+
+🛠 I am ready to contribute 
+---
+
+- For open tasks in this repository, please see the [Issues section](../../issues).
+- Raise mistakes, errors or missing information on this repository by opening a [Pull Request](../../pulls)
+  - Read details on [how to open a Pull Request](https://opensource.guide/how-to-contribute/#opening-a-pull-request)
+  - Submit trivial fixes (for example, a typo, a broken link or an obvious error)
+  - Start work on a contribution that is already listed as an issue or something you’ve already discussed
+  - A Pull Request doesn’t have to represent finished work. It’s usually better to open a Pull Request early on, so others can watch or give feedback on your progress. Just mark it as a “WIP” (Work in Progress) in the subject line. You can always add more commits later.
+
+📫 Contact
+---
+
+For any organisation related queries or concerns, you can directly reach out to ** Susie Costard by emailing [[email protected]](mailto:[email protected])**.
+
+♻️ License
+---
+
+This work is licensed under the **MIT license (code) and Creative Commons Attribution 4.0 International license (for documentation)**. 
+<!--Replace these sentences to appropriate reflect the license chosen in your project-->
+You are free to share and adapt the material for any purpose, even commercially, 
+as long as you provide attribution (give appropriate credit, provide a link to the license, 
+and indicate if changes were made) in any reasonable manner, but not in any way that suggests the 
+licensor endorses you or your use, and with no additional restrictions.
+<!--Replace these sentences to appropriate reflect the license chosen in your project-->
+
+For a more detailed contribution guideline, please check out *[The Turing Way's CONTRIBUTING.md file](https://github.com/alan-turing-institute/the-turing-way/blob/main/CONTRIBUTING.md)*.

content/investment/about.md

@@ -0,0 +1 @@
+# Investment in AI for Decarbonisation

content/working-groups/about.md

@@ -0,0 +1 @@
+# Working Groups

content/working-groups/manufacturing-and-built-environment.md

@@ -0,0 +1 @@
+# Manufacturing and Built Environment