publiccodenet / about Goto Github PK

README.md for /people directory that explains how to use jeckyll to generate a profile. Dependent on issue #9

The heading for the contributing section on the homepage (in index.md) is 'We need you', which I think can be clearer :)

How to fix this issue

1. Open index.md

2. Edit the header reading 'We need you' to something a bit clearer, like for instance 'How you can contribute' or 'How you can help us'

3. Make a Pull Request with your changes

🎉

• Community Covenant?
• Notification e-mail address

Mozilla Open Leaders instructions

I would suggest finding something that is more natural for use in common language, for instance replacing the comma with the word 'for' in running text, or everywhere.

@nebster @clausmullie, input?

Currently in the pitch the following is described:

We help public software products be successful by guaranteeing their marketability and quality. We provide the following for products in our care:

• IP management, product stewardship
• Code, policy and documentation quality assurance
• Productization services: branding, communication, refactoring for reuse
• Community management: processing feedback and contributions, events
• Packaging, distributing official versions, compatibility updating
• Marketing, communications, public relations
• Developer advocacy, user support, end-user success, training materials
• Project infrastructure, process management

It would be great if we could create a list of related organisations, and how we can complement them :)

So if you know any other public technology organisations or communities please tell us who they are and how they could relate to the Foundation For Public Code.

I would like GitHub issues to be the place where we can work together with our contributors/advisors in order to solve the problems at the root of this foundation. I'm imagining inviting those who have been willing to advise us to specific issues and asking them to engage with more from there.

I think the goal of individual Issues is to:

• Identify what the foundation should be, do and communicate: what the contents of the repository/site should be
• Spawn new issues with questions and work that needs to be done

I'm trying to figure out:

• how can we ask questions in a way that is conducive to conversation
• and that engages our contributors/advisors?
• And what should the subject line
• and the body text contain?

I've made these issues which can serve as examples to discuss this:

• #27 How can we sustainably fund the Foundation so it can be a long-term partner?
• #32 For who are we doing this?

So, what should a good issue be, and what should it do? @chartgerink @nebster do you have any ideas?

As suggested by Arnout

What are good beginner issues for this project, and how to find them?

With help from @chartgerink.

For this I'm just wondering a bit on whether we should be doing this in this repository. Perhaps in a communications folder or something.

Mozilla Open Leaders assignment

Looking for funding and business models. We believe in order for any code in the care of the Foundation to be usable it needs to have a guaranteed stewardship of at least a few years. (but how many)

So far we've been considering 3 major sources of revenue:

• City partners
• Codebase donators through endowments
• Implementation partners
• Grant funding
• Philanthropic funding

How are others doing this, solving this problem, and how can we?

If someone comes in and wants to edit the home page they need to edit the file index.md.

However, if you don't know about the web, how can you ever know...

Ideally the README.md, which displays as the file that displays on the GitHub repository home page explains what file to edit for the homepage on the website.

How to solve this issue

1. Open the file README.md

2. Add a mention of the homepage on the about. website is in the file index.md. You could add a sentence under the "Preview, Build and Deploy" heading explaining this.

3. Submit a Pull Request!

🎉

The lovely folks at OS2 are sending us some of their founding and business model docs so we can use them as reference material as we build our own. They're in Danish, but we'll need them in English (both for us and for other municipalities to learn from.) If you could help with this, please reply here or email us at [email protected].

Because the Foundation won't discriminate against the code of other types of public organisation.

Keeping with RESTful URLs, as in /people/ben-cerveny. A way to solve this is to make a folder for everyone, with an index.md per person for their profile and a photo.

I propose using front matter in order to add structured data like function and perhaps from and until.

• Link to team page in CONTRIBUTING

Do we create a /processes folder?

• GitHub MarkDown CSS
• Mark
• Muli font

If we're inviting advisors to take part in our conversations here on the GitHub issues, how do we get them to find the issues that make sense to them.

I propose labels like contributor engagement or community management and financial etc. However I don't know if any of these make sense.

How would this connect to the advisors you have in mind @nebster?

I would include a line or two that a) Foundation stewards codebases to become Public Code, b) all 4 roles work together to deliver this codebase stewardship package, c) do this by supporting development teams and communities who are producing code for public implementation

Submit your project to the Global Sprint

Given that we are trying to maintain the about repo and thus about.publiccode.net as a "canonical truth" about the organization, does it make sense that more production intensive and harder to update materials live inside, or in another more ephemeral repo like the main site.

Thinking about using reveal.js for presentations using the slides.com editor.

• Add cheer (emoji's)
• Guidelines, not rules
• Code of conduct
• Style
• How to contribute

Mozilla Open Leaders assignment

The goal of the README.md is to help people get into the project and ready to contribute (by linking to the guide in CONTRIBUTING.md). In order for people to get in touch with other collaborators we've opened a Riot chatroom at https://riot.im/app/#/room/#publiccodenet:matrix.org, but how will people ever know?

How to solve this issue

1. Open the README.md file

2. Add a link to the Riot chat in the text. Perhaps after the introduction with a 'Join our chat at [[link]]' or all the way at the top with a link.

[ Optional ] create a badge with https://shields.io/ and link it to the chat

3. Create a Pull Request

🎉

The publiccode.net site is in the repo http.

I'm doubting the usefulness of copyright here, so I'm leaning CC0, however perhaps we want to have some bounds on replicating the entire organisation.

Ideally I'd like it to be possible for people to 'fork' the Foundation if they need improvements.

One of the blocking factors in starting projects in the Foundation For Public Code product stewardship programme is that we don't necessarily have a way of pointing at what qualities need to be adhered to.

We need to set standards that can be used inside and outside of the Foundation For Public Code to build high-quality Open Source components for public software.

For this we can build on the great way done by GDS, Team Digitale and DINSIC and USDS/18F, however, we might want to have a version that is under our own control.

I've been asked to describe, especially for new contributors, what public code is.

There might be something we can take from the Smart Cities? Public Code! repository for this.

Currently the mission in the PDF is

We create a viable future for cities and civic operating systems that are highly participatory and drive societal engagement. A public digital infrastructure that is inclusive, usable, adaptive, open and sustainable.

To achieve this we maintain, manage, contribute to and grow an ecosystem of public software and policies that help governments, communities and citizens improve their city.

Suggestion: use CloudFlare CDN for with their SSL certificates, alternatively use Firebase hosting.

As the 'home' and index.md for this repository. The public facing explanation of what the Foundation For Public Code is.

Currently, our pitch reads:

We help public Open Source projects become successful, build sustainable communities around them and create a thriving public Open Source ecology.

Cities and civic organisations can become members of the Foundation For Public Code to collaboratively grow the ecosystem.

Members can grant their policy and code to the foundation for sustainable stewardship and community management.

See the Open Canvas below:

Great feedback from Mozilla Open (civic) Leaders @lbrennee and @meagdoh! Thanks! 🙇‍♀️

• Specify this is the code to build an organisation
• The readme is an entry point for contributors give clear first steps
• Showing status: Draft or similar (I don't really know where this is...)
• Say what we are looking for: Advisors
• Define certain terms: build a glossary

For the actual Foundation For Public Code, not its projects.

This should reflect the 'phases' we have for founding.

• Pull content from Operational Plan
• Pull content from Willemijns legal document, which takes precedence over org plan.

Note: Willemijn's document is secret, so @clausmullie waiting for access

Do we already know of issues or questions that other people might have about the content of this repo.

Who is our target audience for this project? It should be mentioned in the readme. And is perhaps a prerequisite for formulating personas #21.

When #13 and #12 are closed:

• Submit this project: https://www.mozillapulse.org/add
• Post This is ready to be featured on Mozilla Pulse on mozilla/global-sprint#169

Perhaps a Matrix channel?

After #33 and #30 have landed the CONTRIBUTING guide and the CODE_OF_CONDUCT have to be connected wherever useful with links.

The Foundation For Public Code is looking for a treasurer to fulfil the official position.

The treasurer has to reside in the Netherlands.

Add a brand repository, licenced full Copyright with the logo assets etc so they aren't licenced CC0

Formulate:

• Mission
• Sustainability and business model
• Governance model
• City partner proposition
• Implementation partner proposition
• Form board of advisors
• Website
• Team on website
• Advisors and ambassadors on website
• Mapping and defining the relationships with others in this field

Then

• Ask @chartgerink to help thinking about structuring these and making them more accessible after making some issues.

Now that we've started inviting people to be advisors, it might be great to point them to somewhere that explains what they should do and how.