Towards open and citizen-led data informing the decarbonisation of existing housing

[KateSimpson]

Project Lead: @KateSimpson
Mentor: @ArielleBL

Project web page: https://katesimpson.github.io/Open-access-data-driven-retrofit-evaluation/
Project roadmap: https://github.com/users/KateSimpson/projects/1
LICENCE: https://github.com/KateSimpson/Open-access-data-driven-retrofit-evaluation/blob/gh-pages/LICENCE. Sourced via: https://choosealicense.com/licenses/mit/#
README: https://github.com/KateSimpson/Open-access-data-driven-retrofit-evaluation/blob/gh-pages/README.md
CODE of CONDUCT: https://github.com/KateSimpson/Open-access-data-driven-retrofit-evaluation/blob/017a62136f547fbe23a440739ed04caa3a178d40/CODE_OF_CONDUCT.md

Welcome to OLS-2! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Life Science program 🎉.

---

Week 1 (31 August - 4 September 2020): Meet your mentor!

• Create an account on GitHub
• Check if you have access to the HackMD notes set up for your meetings with your mentor
• Prepare to meet your mentor(s) by completing a short homework provided in the HackMD notes
• Complete your own copy of the open leadership self-assessment and share it to your mentor
  If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
• Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (7 - 11 September 2020): Cohort Call (Welcome to Open Life Science!)

• Create an issue on the OLS-2 GitHub repository for your OLS work and share the link to your mentor.

• Draft a brief vision statement using your goals

  This lesson from the Open Leadership Training Series (OLTS) might be helpful

• Leave a comment on this issue with your draft vision statement & be ready to share this on the call

• Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (14 - 18 September 2020): Meet your mentor!

• Look up two other projects and comment on their issues with feedback on their vision statement
• Complete this compare and contrast assignment about current and desired community interactions and value exchanges
• Complete your Open Canvas (instructions, canvas)
• Share a link to your Open Canvas in your GitHub issue
• Start your Roadmap
• Comment on your issue with your draft Roadmap
• Suggest a cohort name at the bottom of the shared notes and vote on your favorite with a +1

Before Week 4 (21 - 25 September 2020): Cohort Call (Tooling and roadmapping for Open projects)

• Look up two other projects and comment on their issues with feedback on their open canvas.

Week 5 and later

• Create a GitHub repository for your project
• Add the link to your repository in your issue
• Use your canvas to start writing a README.md file, or landing page, for your project
• Link to your README in a comment on this issue
• Add an open license to your repository as a file called LICENSE.md
• Add a Code of Conduct to your repository as a file called CODE_OF_CONDUCT.md
• Invite new contributors to into your work!

This issue is here to help you keep track of work as you start Open Life Science program. Please refer to the OLS-2 Syllabus for more detailed weekly notes and assignments past week 4.

[sonibk]

This is an interesting project you have here what platforms will you be using

[yochannah]

Loooking forward to seeing your open canvas!

[KateSimpson]

Thanks Yo 👍 Here is my [open canvas][https://docs.google.com/presentation/d/1jrCcgZkHrWQwSxNHu8bHaxcBfwuXTQuWxodSIik4T9g/edit?usp=sharing]

[KateSimpson]

This is an interesting project you have here what platforms will you be using

Thank you! I am thinking to share it here but I welcome ideas as I am new to open research platforms.

[KateSimpson]

Roadmap development has began via a project page: https://github.com/users/KateSimpson/projects/1

[yvanlebras]

Your last github hyperlinks seems to be wrong or linked to a private space maybe. And... nice project ;) If related to citizen science in ecology, I can maybe help a little

[koudyk]

Neat project! Looking forward to seeing the other components 😸
A few thoughts on the Open Canvas:

• are you making a general-purpose platform? I noticed the strike-through on the second part of the title; without it the title sounds very generic. Also, in the Problem section, where I assume most people would start reading, you don't mention housing or decarbonization.
• in the Unique Value Proposition section, you say you want to create a portal. I'm not sure what that means, but I'm also not familiar with this area of research. is the portal a website? a GitHub organization? Might be worthwhile to elaborate in a few words.

Also, just a little markdown note. It looks like the link in your first comment on this issue didn't render; the text that will be linked should be in [ ], and the link should be in ( ). You can edit your previous comment if you want to fix it by clicking the three dots on the top-right of the comment.

Nice job, cheers

[KateSimpson]

Your last github hyperlinks seems to be wrong or linked to a private space maybe. And... nice project ;) If related to citizen science in ecology, I can maybe help a little

Thanks for flagging this Yvan, now public! I would be keen to speak you on citizen science.

[KateSimpson]

Neat project! Looking forward to seeing the other components 😸
A few thoughts on the Open Canvas:

• are you making a general-purpose platform? I noticed the strike-through on the second part of the title; without it the title sounds very generic. Also, in the Problem section, where I assume most people would start reading, you don't mention housing or decarbonization.
• in the Unique Value Proposition section, you say you want to create a portal. I'm not sure what that means, but I'm also not familiar with this area of research. is the portal a website? a GitHub organization? Might be worthwhile to elaborate in a few words.

Also, just a little markdown note. It looks like the link in your first comment on this issue didn't render; the text that will be linked should be in [ ], and the link should be in ( ). You can edit your previous comment if you want to fix it by clicking the three dots on the top-right of the comment.

Nice job, cheers

Thanks, these are really useful suggestions - will take on board as I further develop the open canvas. The point on markdown is helpful too, much appreciated!

[KateSimpson]

Pleased to have published a web page! Just need to add content now...
https://katesimpson.github.io/Open-access-data-driven-retrofit-evaluation/

[KateSimpson]

I started my README file, it is here: https://github.com/KateSimpson/Open-access-data-driven-retrofit-evaluation/blob/gh-pages/README.md
Please feel free to take a look and offer feedback 👍

[KateSimpson]

I am just learning about licencing and have selected the MIT licence as this seems to be geared towards open working: https://github.com/KateSimpson/Open-access-data-driven-retrofit-evaluation/blob/gh-pages/LICENCE.
Sourced via: https://choosealicense.com/licenses/mit/#

[malvikasharan]

@all-contributors please add @KateSimpson for idea and content.

[allcontributors]

@malvikasharan

I've put up a pull request to add @KateSimpson! 🎉

[KateSimpson]

Pleased to have published a web page! Just need to add content now...
https://katesimpson.github.io/Open-access-data-driven-retrofit-evaluation/

I have slowly been updating this, please let me know if you can see ways to improve it! 👍

[KateSimpson]

Roadmap development has began via a project page: https://github.com/users/KateSimpson/projects/1

Have began adding more detail to this as I go forward

[samvanstroud]

Hi @KateSimpson, I just had a look at the readme of your project. The sounds really great! The information is all there, but I think the formatting could be cleaned up a bit to improve readability, which will make it easier for newcomers to quickly understand your project and get excited about it! Adding things like subheadings (using "##", "###" etc in markdown), using bold formatting, and formatting the bulleted lists correctly would be a good place to start I think. Perhaps you can also link to your github.io page from the readme to connect the two up fully. Btw, there is a github mardown guide here.

In terms of content it would be nice perhaps to have a slightly more fleshed out vision statement at the top of the readme. The current sentence is quite short, and also has quite a few technical words!

Looking forward to seeing more from your project :)

[KateSimpson]

Here is my project code of conduct, adapted from a template and credited: https://github.com/KateSimpson/Open-access-data-driven-retrofit-evaluation/blob/017a62136f547fbe23a440739ed04caa3a178d40/CODE_OF_CONDUCT.md