Compare commits
No commits in common. "main" and "main" have entirely different histories.
@ -29,11 +29,10 @@ Where we can track topics that have been requested, and link to shows that addre
|
||||
- EMAIL_LINK_CLICKED - The host clicked the link and is about to upload the show.
|
||||
- SHOW_SUBMITTED - upload complete
|
||||
- [Processing Show Notes](https://repo.anhonesthost.net/HPR/hpr_documentation/src/branch/main/workflow/processing_a_show.md)
|
||||
- TRANSCRIBING_COMPLETE
|
||||
- SHOW_POSTED - show in the database
|
||||
- MEDIA_TRANSCODED - audio all generated and sent to CCDN
|
||||
- MEDIA_TRANSCODED - audio all generated
|
||||
- UPLOADED_TO_IA - on the IA and visible
|
||||
- PROCESSING_COMPLETE - all processing is complete
|
||||
- UPLOADED_TO_RSYNC_NET - archived on rsync.net
|
||||
|
||||
|
||||
- Posting Show
|
||||
|
@ -12,10 +12,6 @@ Any software development is done with the goal of supporting the distribution of
|
||||
|
||||
The priority is to keep the flow of shows coming in and going out, fix any accessibility issue that arise, then work on any other feature requests.
|
||||
|
||||
Some things we can change without discussion but other things we need to get input from the [HPR Community](https://hackerpublicradio.org/about.html#governance).
|
||||
|
||||
Changes can take a long time, community approval can take several months, while other changes require a lot of work from volunteers who are focused on other priorities.
|
||||
|
||||
We allow redistribution by releasing all our content under a [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). In the same vein all our code is released under [aGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html), or other [OSI approved licenses](https://opensource.org/licenses) .
|
||||
|
||||
We do not track statistics to the detriment of our prime directive.
|
||||
@ -30,8 +26,6 @@ We have a distrust of online platforms, libraries and niche tools (that we do no
|
||||
|
||||
We are very conservative in our choice of tech. As a rule of thumb, all software choices tend to be technology that was developed years ago, and is likely to be around for years to come.
|
||||
|
||||
We make our code as simple to understand as possible as our replacement may not have the skill set we do.
|
||||
|
||||
That said, we move with the times when there is a clear advantage to do so.
|
||||
|
||||
We run up to date patched stable software.
|
||||
@ -52,11 +46,11 @@ Bug reports, and patches are welcome from anyone without commitment.
|
||||
|
||||
If you are contributing new code, or new technology we ask you commit to supporting it for a *minimum of two years*. This allows the other Janitors time to learn the new tech and support it when you leave.
|
||||
|
||||
Some things we can change without discussion but other things we need to get input from the [HPR Community](https://hackerpublicradio.org/about.html#governance).
|
||||
|
||||
## Create an Account
|
||||
|
||||
If you're happy with all that, then...
|
||||
|
||||
In order to contribute you need to [create an account](https://repo.anhonesthost.net/user/sign_up), but you **also** need to notify the admins@hpr either via email, mastodon, or matrix that you have created an account. Due to the level of spam accounts we need to approve each one by one.
|
||||
|
||||
Changes can be submittted as described in [hpr3797 :: How to submit changes to HPR](https://hackerpublicradio.org/eps/hpr3797/index.html).
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user