Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Digital Preservation with Permanent.org #132

Open
9 of 17 tasks
omnignorant opened this issue Nov 13, 2018 · 0 comments
Open
9 of 17 tasks

Open Digital Preservation with Permanent.org #132

omnignorant opened this issue Nov 13, 2018 · 0 comments

Comments

@omnignorant
Copy link

What problem are you trying to solve?

Public records are at risk – security breaches, natural disasters, technological shifts and a lack of legacy planning threaten the perpetual accessibility and integrity of digital data.

The vast majority of civic agencies, small government units, nonprofits, schools and other public sector organizations do not have a trusted place to store their digital materials. They rely on cumbersome, low-budget solutions from internal IT departments or pay for-profit internet giants recurring fees.

The digital storage industry was designed for convenience and short cycles. A commitment to permanent storage has no place in their business model.

Who will benefit (directly and indirectly) from your project?

All citizens will benefit when the civil society organizations they trust have their own trusted agency for the security and preservation of critical public data and information.

What other resources/tools are currently serving the same need? How does your project set itself apart?

Dropbox, Google Drive, Box, iCloud, Facebook – these are the cloud solutions the vast majority of Americans rely on to secure their digital materials, including nonprofits, schools and small government agencies. Less consumer friendly products for commercial license include Preservica. More savvy IT departments may host their own cloud solutions on internal servers.

There are other open source projects out there that do this work. None aim to make content preservation and distribution accessible to the average, nontechnical user.

There are a ton of similarly spirited projects, these include: Filecoin, Interplanetary File System, Archmission, MOM, The Long Now Foundation, The Internet Archive, One Second Everyday, etc. that each take on a facet of the problem or propose even more visionary solutions to permanent storage. Again, none make an effort to address the individual, nontechnical, private user case.

Where can we find any research/data available/articles?

David Rosenthal is pretty obsessed with this stuff: https://blog.dshr.org/

What help do you need now?

We're building out our open API and our framework for viewing materials. It's a lot like the wordpress ecosystem, so we're open to exploring how to utilize wordpress front end, widgets or add ons.

What are the next steps (validation, research, coding, design)?

Answer here.

How can we contact you outside of Github(list social media or places you're present)?

Answer here.


Project management

Checklist for NEW ideas 👶

Hey, you're official! You're now part of the growing civic hacking community in Austin. Here's a few things to get started (a couple you've probably already done).

  • Create this idea issue
  • Flesh out the who, where, and what questions above
  • Start the conversation about this idea on Slack Replace this link to the #oa-permanent channel with your project's preferred channel.

Checklist for ACTIVE projects 🔥

Let's get this project started! When this idea starts taking off, the Projects Core Team will start helping this project's lead(s) out with project management and connecting you to resources you may need. To get there, please complete and check off the following:

  • Post an update at least once a month to this issue. Use BASEDEF for ideas, but it's ok even if your update is just "nothing new happened this month" or "we saw a small increase in traffic to our app this month". If there's no activity for two months, that's no problem, life happens. We'll just label this as backlog so others know you'll get back to it when you have the time. If nobody hears from you at all in more than two months, we may mark it as abandoned so that others can pick up this idea and run with it.
  • Take 30 minutes to complete Open Leadership 101
  • Create a GitHub repository. Ask for help setting up permissions if you want your repository to be within the Open Austin Github organization.
  • Create a README file in your project repository. This file should help newcomers understand what your project is, why it's important, and kinds of help you're looking for.
  • Create issues to describe each task that you plan to do or need help with and how a contributor can get started on that task. You might start and stop a lot, so consider issues as your to-do list.
  • Create a team for your core contributors
    • This will make it easier for you to manage your github repo access. People on a team have the same level of access. Admin access will allow your trusted contributors to make changes as needed.
    • You can remove and add people to your team as needed.
    • View some of our teams: https://github.com/orgs/open-austin/teams
    • Note: You can also allow collaborators outside of your team and give them more limited access.
  • Create a user group in Slack so you can "@" your core contributors all at once, without bothering other people who use the Slack channel. You'll need permission from a Slack admin, so just mention @Leadership on Slack to get this set up.
  • Create a Google Drive, Dropbox, or other cloud storage to share larger files. Github and Data.World are good for code and data, respectively, especially when you need version control. But they're not good for very large files, documentation, articles, etc. A cloud storage option will allow you to easily share, create, and collaborate on documents with your team and help organize ideas and thoughts.
    • Doing this early on can help your team stay organized and to onboard new contributors who wouldn't have access to files you all have shared over email.

Checklist for FEATURED Projects 🎉

To have your project FEATURED on Open-Austin.org, complete the following documentation. In past projects, well-documented featured projects have more contributions than other projects.

If you get stuck at any point, feel free to reach out to the leadership team on Slack by adding @Leadership to your message. We're here to help you make real changes to our city.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant