aletheia-foundation / aletheia-admin Goto Github PK

https://badges.mozillascience.org/
https://github.com/codeforscience/sciencefair/

Go through the open science twitter feed and others and reach out to people passionate about Open Access.

Speak to Roo, see if his work would be willing to host a venue for the Open Sprint, if so register.

We said we were going to do it so we should do it.

I can't see any ability to add issues to those repos. What can we do with the repo and what can't we do?

Watchlist
https://shuttleworthfoundation.org/about/ - we've missed this year, check out for 2018
https://mozilla-science-lab.forms.fm/mozilla-science-mini-grant-application - applied for 2k, can reapply so check when open
https://www.ethnews.com/european-innovation-council-will-award-5-million-euros-to-blockchain-for-social-good?platform=hootsuite - we should keep an eye on

Applied
https://www.thinkable.org/submission_entries/l3jw4k8G

Declined
https://www.linux.org.au/projects/grants - I've applied for $15,000 to cover our video - decision being made 7th of July - declined.
https://www.ampstomorrowfund.com.au/ - I've applied for $67,000, we hear in September - declined

Applied again
https://www.digital-science.com previously declined, reapplied.

Not sure if they are useful

Turn the informal Mondays into an official meetup. Do other members want to host meetups?

I'm working through the Mozilla Open Leadership training and it strongly suggests using a shared calendar of some sort. I'd like to put the question to both of you if you think we need one?

In the spirit of the project I'd rather say away from Google for anything, and Google bans my email address from creating a Google account because they don't respect people's right to privacy in using a VPN, but I have made a Google account under a different email and will use a Google calendar if both of you feel we need to.

Alternatively, I'd be happy make an excel file libreoffice calc file and pin a calendar here in Github or in the Slack.

Let me know what you both think.

Labelling them all failed, we need to get a better organisation system

Speak to roo, figure out what will be done by October, add all the related issues to their own project.

Ideally would be good to have a downloadable client, upload and download documents, search function, something basic people can play with. Perhaps just move Aletheia 1.0 from end of year to MozFest end of October?

Each repo needs a contributing file so when issues are raised a warning pops up saying Before you submit an issue, please review the guidelines for this repository. But we only want to update the one Contributing file otherwise some will fall out of sync.

It's been suggested to me https://www.stickermule.com/ would be a good place to get stickers.

Also, does it automatically leave a whitespace between title and body?

It's a suggested rule for contributing so want to make clear in the contributing file.

Attended:
Mozilla Global Sprint 2017
Mozfest 2017
Open Science Fair 2017, 06.09.17-09.09.17
Force2017, 25.10.17-27.10.17 (Poster here)
Blockchain for Science, 27.10.17 (Slides here)

Applied to:
Linuxconf.au
Open Science Conference 2018

Accepted
Open Science Fair http://www.opensciencefair.eu/call-for-posters1

Rejected
OpenCon 2017

Reason being we can put a link to the search in our Contributing file so literally all good beginner issues are viewable from one click. Otherwise we will need to list out instructions of going into the repos individually to look for them.

add it to the contributing file

• Organise Bronz trip
• Organise call with Chris
• Update Flattr
• Run through all the Patreon emails
• Action anything relevant from the Patreon emails
• Run through personal emails for Aletheia stuff
• Action anything relevant from personal emails
• Call Joe Swin - teed up call now waiting for response
• Look over the reputation work Roo has done
• Look over steem as mentioned by Yann in the Slack
• Make sure Patreon stuff is included in the Readme
• Make sure Flattr stuff is included in the Readme
• Sort out rewards on Patreon
• Go over contacts and see if there are any we can email regarding Patreon
• Look at legal jurisdictions
• Bank account
• Cryptocurrency wallet
• Chase lawyers
• Sort out Cloudflare
• Sort out blog
• Youtube account
• Add existing videos to it
• Chase down online presence links
• Continue with the business plan
• Update the licensing section of the Readme
• General reminder to do more social media now your back from traveling, try and post to twitter and facebook daily
• Check on the 15th if consensys ahve gotten back to us
• Formalise Steering Committee duties
• Five people to agree to be part of the Steering Committee
• Source real article
• Print banking documents, fill them in and post to Roo
• Look into Aragon
• Update whitepaper
• Add note about community vote levelling to Etherpad
• Add note about dataset and methodology to the Etherpad
• Add note about transaction fee/captures to the Etherpad

May I suggest discussing with the dokie.li project (gitter.im/linkeddata/dokieli) to create synergies?

In case you don't know it, you can make your own opinion on dokie.li and linkedresearch.org

Ask extra credits how much it would cost, might just be worthwhile paying to have it professionally made

Sort out guidelines for pull requests and add them to the CONTRIBUTING.md file.

And email all the university groups I've touched base with for unrelated Mozilla work.

I've made technical writing
web design

make
visual design
blockchain
javascript
security

We need to write an overview of the different repo's and the different pieces of Aletheia to orientate new contributors, then add it the CONTRIBUTING.md file in the admin repo.

http://codeliberation.org/
https://www.hiretechladies.com/
http://www.writespeakcode.com/
https://flatironschool.com/
https://devbootcamp.com/

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo

Hi Alethia team. I'm @blahah, and I'm working on https://github.com/codeforscience/sciencefair/

It seems we have a lot in common, in terms of goals, technology, and community. I just wanted to open a channel of communication. We come in peace 🕊 ✌️ - if you're interested we'd like to explore how we can help one another.

We need to write a style guide for new contributors and add it to the CONTRIBUTING.md file in the admin repo.

Sort out a mechanism for flagging beginner issues and add them to the CONTRIBUTING.md file in the admin repo.

Need to create a LICENCE.md file and put it in the admin repo.

The license text and further discussion can be found in the following link:
https://wiki.p2pfoundation.net/Peer_Production_License

This license is based on the Creative Commons ‘Attribution-NonCommercial-ShareAlike’ license (v. 3.0) with these additional clauses inserted:

You may exercise the rights granted in Section 3 for commercial purposes only if:
i. You are a worker-owned business or worker-owned collective; and
ii. all financial gain, surplus, profits and benefits produced by the business or collective are distributed among the worker-owners

If our goal is not simply to facilitate distribution of our code and ideas but to also promote a change in culture, I think that this, or a similar, license is more appropriate.
I believe that our dependencies are all under the MIT or LGPL licenses which should pose no problem in continuing using them.

I confirm:

• I've read the contributing guidelines and the code of conduct
• I've checked that this issue applies to this repo
  Not really sure about this.
• I've checked the existing issues, no one else has reported this
• I've got a clear and descriptive title

This will be ongoing.

Do we want them to email us first, is there a process for getting access to the repo etc.

Create a pathways document that solidifies how people move on up in the project.