Community - Revision history

KI5QKX: mw push

2026-04-30T18:52:42Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 109:		Line 109:

	If you want to help improve the wiki, contribute code, test ideas, or share a project writeup, see [[Contributing]].		If you want to help improve the wiki, contribute code, test ideas, or share a project writeup, see [[Contributing]].


	== Related pages ==		== Related pages ==
Line 128:		Line 127:
	* [[Ampr.org]]		* [[Ampr.org]]
	* See [[Archive]] for more.		* See [[Archive]] for more.
			[[Category:Explanation]]
	[[Category:Community]]		[[Category:Community]]

KI5QKX: mw push

2026-04-15T17:15:33Z

mw push

← Older revision		Revision as of 17:15, 15 April 2026
Line 10:		Line 10:
	More than just a block of IP addresses, 44Net is also a long-running technical community.		More than just a block of IP addresses, 44Net is also a long-running technical community.

	Much of the operational knowledge that keeps 44Net usable lives in the experience of the people who run it, troubleshoot it, write documentation, maintain software tools, and help newcomers get unstuck. The mailing lists ~~and discussion groups~~ are where that knowledge is developed and shared.		Much of the operational knowledge that keeps 44Net usable lives in the experience of the people who run it, troubleshoot it, write documentation, maintain software tools, and help newcomers get unstuck. The mailing lists are where that knowledge is developed and shared.

	Asking for help is one of the first ways people join the community. As with amateur radio, asking questions and helping one another is how people learn about how things work and eventually go on to help the next person.		Asking for help is one of the first ways people join the community. As with amateur radio, asking questions and helping one another is how people learn about how things work and eventually go on to help the next person.
Line 28:		Line 28:

	Note that administrative issues like account access, verification, or requests that depend on Portal workflow should generally go through the [https://portal.ampr.org/ Portal ticket system] instead of the discussion group.		Note that administrative issues like account access, verification, or requests that depend on Portal workflow should generally go through the [https://portal.ampr.org/ Portal ticket system] instead of the discussion group.

			If you are blocked and want the clearest practical starting point, see [[Get Help]].

	== Groups.io and discussion channels ==		== Groups.io and discussion channels ==
Line 37:		Line 39:
	* [https://ardc.groups.io/g/44Net-connect 44Net Connect]: discussions specifically about the 44Net Connect project		* [https://ardc.groups.io/g/44Net-connect 44Net Connect]: discussions specifically about the 44Net Connect project
	* [https://ardc.groups.io/g/community ARDC Community]: broader discussion about ARDC and its work ''not related to 44Net''		* [https://ardc.groups.io/g/community ARDC Community]: broader discussion about ARDC and its work ''not related to 44Net''
	* [https://ardc.groups.io/g/~~44net~~-vpn ARDC 44Net VPN]: discussion related to VPN-style access systems ''not specifically related to 44Net Connect''		* [https://ardc.groups.io/g/net-44-vpn ARDC 44Net VPN]: discussion related to VPN-style access systems ''not specifically related to 44Net Connect''
	* [https://ardc.groups.io/g/developer-community ARDC Developer Community]: discussion related to software development and open source projects supported by ARDC		* [https://ardc.groups.io/g/developer-community ARDC Developer Community]: discussion related to software development and open source projects supported by ARDC
	* [https://ardc.groups.io/g/wiki ARDC Wiki]: discussion related to the wiki and documentation work		* [https://ardc.groups.io/g/wiki ARDC Wiki]: discussion related to the wiki and documentation work
Line 73:		Line 75:
	=== Asking questions ===		=== Asking questions ===

	When asking a question, it’s helpful to be as specific as possible about the problem you’re facing and what you’ve already tried. This can help others understand your situation and provide more targeted advice.		When asking a question, it’s helpful to be as specific as possible about the problem you’re facing and what you’ve already tried. This can help others understand your situation and provide more targeted advice.

	For example, instead of asking “Why isn’t my tunnel working?”, you might say “I’m trying to set up a WireGuard tunnel on my Linux server using the configuration from the 44Net dashboard, but I’m getting an error message that says ~~“Configuration Invalid”~~. I’ve checked that the private key is correct and that the config works on another device, but I’m still stuck. Has anyone seen this before?”		For example, instead of asking “Why isn’t my tunnel working?”, you might say “I’m trying to set up a WireGuard tunnel on my Linux server using the configuration from the 44Net dashboard, but I’m getting an error message that says ‘Configuration Invalid’. I’ve checked that the private key is correct and that the config works on another device, but I’m still stuck. Has anyone seen this before?”

	~~When asking~~ a ~~technical question, the following information is often helpful~~ to include:		For a practical checklist of what context to include, see [[Get Help]].

	* Which operating model you are using: IPIP Mesh, BGP, or 44Net Connect
	* What platform or device you are using, such as a specific router, Linux distribution, ~~or cloud provider~~
	* The exact step that failed
	* Any error messages or unexpected behavior you observed
	* Anything you have already tried

	=== Sharing knowledge and experience ===		=== Sharing knowledge and experience ===
Line 97:		Line 93:
	For these reasons and more, it’s ''pragmatic'' to be respectful and considerate of others and to focus on the problem at hand and how to solve it, rather than on personal opinions or preferences.		For these reasons and more, it’s ''pragmatic'' to be respectful and considerate of others and to focus on the problem at hand and how to solve it, rather than on personal opinions or preferences.

	Attempts to gatekeep or exclude certain types of participation are generally avoided and discouraged, except when bad-faith behavior or harm ~~is involved~~. The community generally seeks to preserve and protect healthy, constructive, non-disruptive activity.		Attempts to gatekeep or exclude certain types of participation are generally avoided and discouraged, except when there's a need to address bad-faith behavior or the potential for harm. The community generally seeks to preserve and protect healthy, constructive, non-disruptive activity.

	== ~~Contributing~~ ==		== Community structure ==

			The 44Net community is supported by several overlapping structures. If you want to understand how people participate, how decisions get made, or where stewardship responsibilities sit, these pages provide the next layer of context:

	~~ARDC staff help produce~~ documentation and ~~maintain software tools, but~~ the ~~community is what keeps~~ 44Net ~~running~~ and ~~usable. If you have a question~~, ~~ask it. If you have an answer~~, ~~share it. If you have a project writeup or lesson learned, post it.~~		* [[Governance]]: how decisions are made for shared resources, documentation, and unresolved questions
			* [[Roles and Participation]]: the broad map of who helps sustain 44Net and how those roles differ
			* [[Regional Coordinator]]: how local stewardship, mentorship, and regional continuity work in practice
			* [[Policies]]: the formal expectations that sit alongside community norms

	~~If a recurring question appears on the mailing list, consider converting the answer into a short wiki update; see [[~~Contributing~~]] for guidance. This can help keep operational guidance searchable and reduce repeated troubleshooting cycles.~~		== Contributing ==

	~~=== Note on licensing ===~~		One of the ways community knowledge becomes useful is by turning answers, working configurations, shared practices, and lessons learned into documentation and software.

	~~Material produced by ARDC staff is generally released under a Creative Commons Attribution-ShareAlike license ([https://creativecommons.org/licenses/by-sa/3.0/ CC-BY-SA]) or~~ the ~~non-commercial variant. These licenses are designed to encourage sharing and collaboration~~, ~~while also giving credit to the original creators. Others may publish material under different licenses or according to different terms~~, ~~as is their right~~, ~~but if such terms are not compatible with the CC-BY-SA license~~, ~~that material should not be posted to this wiki~~.		If you want to help improve the wiki, contribute code, test ideas, or share a project writeup, see [[Contributing]].

KI5QKX: mw push

2026-04-15T15:40:38Z

mw push

Show changes

KI5QKX: mw push

2026-03-01T01:14:32Z

mw push

← Older revision		Revision as of 01:14, 1 March 2026
Line 9:		Line 9:
	* Read [[GetStarted\|Getting started]] before posting setup questions.		* Read [[GetStarted\|Getting started]] before posting setup questions.
	* When asking for help, include topology basics (NAT, tunnel endpoint, routing method, and error symptoms).		* When asking for help, include topology basics (NAT, tunnel endpoint, routing method, and error symptoms).
	* Cross-check your participation model in [[~~Ways to Connect~~\|~~Ways to Connect~~]].		* Cross-check your participation model in [[Provisioning Methods\|Provisioning Methods]].

	== What this page will cover ==		== What this page will cover ==
Line 20:		Line 20:
	== Related pages ==		== Related pages ==
	* [[GetStarted\|Getting started]]		* [[GetStarted\|Getting started]]
	* [[~~Ways to Connect~~\|~~Ways to Connect~~]]		* [[Provisioning Methods\|Provisioning Methods]]
	* [[What People Build\|What People Build]]		* [[What People Build\|What People Build]]
	* [[Contributing\|Contributing]]		* [[Contributing\|Contributing]]

KI5QKX: mw push

2026-03-01T00:14:42Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 37:		Line 37:
	* [[Ampr.org]]		* [[Ampr.org]]
	* See [[Archive]] for more.		* See [[Archive]] for more.
			[[Category:Community]]

KI5QKX: mw push

2026-02-28T23:20:28Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 26:		Line 26:
	* [[Policies\|Policies]]		* [[Policies\|Policies]]

	== Contribute / ~~Next~~ steps ==		== Contribute / next steps ==
	If a recurring question appears on the mailing list, convert the answer into a short wiki update and link it in [[Contributing]]. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.		If a recurring question appears on the mailing list, convert the answer into a short wiki update and link it in [[Contributing]]. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.

KI5QKX: mw push

2026-02-27T00:24:12Z

mw push

← Older revision		Revision as of 00:24, 27 February 2026
Line 28:		Line 28:
	== Contribute / Next steps ==		== Contribute / Next steps ==
	If a recurring question appears on the mailing list, convert the answer into a short wiki update and link it in [[Contributing]]. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.		If a recurring question appears on the mailing list, convert the answer into a short wiki update and link it in [[Contributing]]. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.

			== Older docs and notes ==
			Earlier pages that may still be useful:
			* [[44Net mailing list]]
			* [[Re: 44Net Digest, Vol 3, Issue 96]]
			* [[K2IE]]
			* [[ARDC]]
			* [[Ampr.org]]
			* See [[Archive]] for more.

KI5QKX: mw push

2026-02-26T04:39:40Z

mw push

New page

{{DISPLAYTITLE:Community}}

== What this page is ==
This page points to the places where 44Net operators ask questions, coordinate changes, and share results.
Use it when you need help, peer review, or operational context.

== What you can do today ==
* Join the [https://groups.io/g/ardc/44net ARDC 44Net discussion group].
* Read [[GetStarted|Getting started]] before posting setup questions.
* When asking for help, include topology basics (NAT, tunnel endpoint, routing method, and error symptoms).
* Cross-check your participation model in [[Ways to Connect|Ways to Connect]].

== What this page will cover ==
* Communication channels and expected use of each.
* How to ask effective technical questions.
* Change announcements and maintenance coordination.
* Community norms for troubleshooting and follow-up.
* Where to share project writeups and lessons learned.

== Related pages ==
* [[GetStarted|Getting started]]
* [[Ways to Connect|Ways to Connect]]
* [[What People Build|What People Build]]
* [[Contributing|Contributing]]
* [[Governance|Governance]]
* [[Policies|Policies]]

== Contribute / Next steps ==
If a recurring question appears on the mailing list, convert the answer into a short wiki update and link it in [[Contributing]]. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.