nick12
/
hmn
forked from hmn/hmn
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Replaced all handmadedev.org emails with handmade.network addresses

This commit is contained in:
Asaf Gartner 2021-08-17 08:22:41 +03:00
parent a32f71f862
commit 34a0649dfc
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/config/config.go.example
View File

@ -31,7 +31,7 @@ var Config = HMNConfig{
FromAddress: "noreply@example.com", FromAddress: "noreply@example.com",
FromAddressPassword: "", FromAddressPassword: "",
FromName: "Handmade Network Team", FromName: "Handmade Network Team",
OverrideRecipientEmail: "override@handmadedev.org", // NOTE(asaf): If this is not empty, all emails will be redirected to this address. OverrideRecipientEmail: "override@handmade.network", // NOTE(asaf): If this is not empty, all emails will be redirected to this address.
}, },
DigitalOcean: DigitalOceanConfig{ DigitalOcean: DigitalOceanConfig{
AssetsSpacesKey: "", AssetsSpacesKey: "",

10
src/templates/src/contact.html
View File

@ -3,13 +3,13 @@
{{ define "content" }} {{ define "content" }}
<div class="content-block"> <div class="content-block">
<div class="description mw7 ph3 ph0-ns"> <div class="description mw7 ph3 ph0-ns">
<p>If you are experiencing technical issues with the site, please send a detailed email to <a href="mailto:team@handmadedev.org">team@handmadedev.org</a> with a description of the problem, and we'll do our best to address it in a timely manner.</p> <p>If you are experiencing technical issues with the site, please send a detailed email to <a href="mailto:team@handmade.network">team@handmade.network</a> with a description of the problem, and we'll do our best to address it in a timely manner.</p>
<p>For administrative issues, such as moderation disputes or content revisions, contact any of the staff by email:</p> <p>For administrative issues, such as moderation disputes or content revisions, contact any of the staff by email:</p>
<ul> <ul>
<li><a href="mailto:team@handmadedev.org">team@handmadedev.org</a></li> <li><a href="mailto:team@handmade.network">team@handmade.network</a></li>
<li><a href="mailto:ryan@handmadedev.org">ryan@handmadedev.org</a></li> <li><a href="mailto:ryan@handmade.network">ryan@handmade.network</a></li>
<li><a href="mailto:ben@handmadedev.org">ben@handmadedev.org</a></li> <li><a href="mailto:ben@handmade.network">ben@handmade.network</a></li>
<li><a href="mailto:asaf@handmadedev.org">asaf@handmadedev.org</a></li> <li><a href="mailto:asaf@handmade.network">asaf@handmade.network</a></li>
</ul> </ul>
</div> </div>
</div> </div>

4
src/templates/src/monthly_update_policy.html
View File

@ -16,7 +16,7 @@
<h3>Grace Period</h3> <h3>Grace Period</h3>
<p>New projects are not required to provide updates until the month following their approval. For example, if a project is posted in the middle of March, they are not required to post any further updates for March – the monthly update policy will go in effect for that project in April.</p> <p>New projects are not required to provide updates until the month following their approval. For example, if a project is posted in the middle of March, they are not required to post any further updates for March – the monthly update policy will go in effect for that project in April.</p>
<h3>Personal Circumstances</h3> <h3>Personal Circumstances</h3>
<p>If the developer foresees not being able to provide a timely update this month, or possibly even for a number of consecutive months, we invite them to post a short update on their project blog letting their audience know they’ll be taking a leave of absence. A reason need not be supplied. Should you feel uncomfortable in doing so, an email to <a href="mailto:team@handmadedev.org">team@handmadedev.org</a> in private will let us flag the project as in hiatus and it will let us deflect incoming questions about the project’s status in your stead.</p> <p>If the developer foresees not being able to provide a timely update this month, or possibly even for a number of consecutive months, we invite them to post a short update on their project blog letting their audience know they’ll be taking a leave of absence. A reason need not be supplied. Should you feel uncomfortable in doing so, an email to <a href="mailto:team@handmade.network">team@handmade.network</a> in private will let us flag the project as in hiatus and it will let us deflect incoming questions about the project’s status in your stead.</p>
<p>Although a blog post explaining the leave of absence will suffice, such an e-mail is still appreciated, of course.</p> <p>Although a blog post explaining the leave of absence will suffice, such an e-mail is still appreciated, of course.</p>
<h3>Project Completion</h3> <h3>Project Completion</h3>
<p>When the project owner is confident the project has entered a stage of completion, a stage of maintenance with no further features, or it has changed identity such that it is no longer considered the original project, the monthly update would no longer be necessary. Please advise us of this so that we may update the status of your project, both for our bookkeeping, and for the purposes of sorting projects by status.</p> <p>When the project owner is confident the project has entered a stage of completion, a stage of maintenance with no further features, or it has changed identity such that it is no longer considered the original project, the monthly update would no longer be necessary. Please advise us of this so that we may update the status of your project, both for our bookkeeping, and for the purposes of sorting projects by status.</p>
@ -27,7 +27,7 @@
<p>If for any subsequent month there is no activity, without having notified the network, the project will receive an e-mail within the first week of the following month and will be flagged as ‘in-hiatus’ until activity resumes. This will always happen for any inactive month following the first strike of the year. At the start of a new year, the strikes are reset, applying the first one first.</p> <p>If for any subsequent month there is no activity, without having notified the network, the project will receive an e-mail within the first week of the following month and will be flagged as ‘in-hiatus’ until activity resumes. This will always happen for any inactive month following the first strike of the year. At the start of a new year, the strikes are reset, applying the first one first.</p>
<p>The project, while in hiatus, will remain as part of the project listings but may be pushed down the list, and may not be considered as a featured project while in this status. If it was a featured project at the time of being flagged due to a strike, it will be removed from the featured list.</p> <p>The project, while in hiatus, will remain as part of the project listings but may be pushed down the list, and may not be considered as a featured project while in this status. If it was a featured project at the time of being flagged due to a strike, it will be removed from the featured list.</p>
<h3>Three Months Inactivity</h3> <h3>Three Months Inactivity</h3>
<p>If the project has been in hiatus for three months, without having notified the network, it is considered dead and removed from the project listings. E-mail <a href="mailto:team@handmadedev.org">team@handmadedev.org</a> to re-instate it the first time this occurs.</p> <p>If the project has been in hiatus for three months, without having notified the network, it is considered dead and removed from the project listings. E-mail <a href="mailto:team@handmade.network">team@handmade.network</a> to re-instate it the first time this occurs.</p>
<p>The second time a project reaches this status, without having notified the network, it will be considered permanently dead. At this point, the project will need to be re-submitted.</p> <p>The second time a project reaches this status, without having notified the network, it will be considered permanently dead. At this point, the project will need to be re-submitted.</p>
<h2>How to be Featured</h2> <h2>How to be Featured</h2>
<p>More active projects have a better chance at being noticed by members and staff alike. Popular projects are more likely to receive votes towards a monthly community featured-project slot, though community interest can be piqued even by small or new projects if the project is producing interesting content. Community-chosen featured-project slots make up to 3 of the possible highlighted projects -- there are also up to 3 staff-pick featured slots each month. The recipients of these slots are at the discretion of the site staff, but you can make your project shine by frequently and consistently reporting progress on your project and interacting with the community.</p> <p>More active projects have a better chance at being noticed by members and staff alike. Popular projects are more likely to receive votes towards a monthly community featured-project slot, though community interest can be piqued even by small or new projects if the project is producing interesting content. Community-chosen featured-project slots make up to 3 of the possible highlighted projects -- there are also up to 3 staff-pick featured slots each month. The recipients of these slots are at the discretion of the site staff, but you can make your project shine by frequently and consistently reporting progress on your project and interacting with the community.</p>

2
src/templates/src/podcast.xml
View File

@ -9,7 +9,7 @@
<itunes:author>The Handmade Network</itunes:author> <itunes:author>The Handmade Network</itunes:author>
<itunes:owner> <itunes:owner>
<itunes:name>The Handmade Network</itunes:name> <itunes:name>The Handmade Network</itunes:name>
<itunes:email>team@handmadedev.org</itunes:email> <itunes:email>team@handmade.network</itunes:email>
</itunes:owner> </itunes:owner>
<description>{{ .Podcast.Description }}</description> <description>{{ .Podcast.Description }}</description>
<itunes:image href="{{ .Podcast.ImageUrl }}" /> <itunes:image href="{{ .Podcast.ImageUrl }}" />