Package Maintainers - Revision history

Prabuanand: added link to https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html

2025-10-03T14:50:21Z

added link to https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html

← Older revision		Revision as of 14:50, 3 October 2025
Line 1:		Line 1:
	~~{{Draft}}~~		This page documents the roles and responsibilities of package maintainers in [[Aports tree\|Aports]] in Alpine Linux.

	* You can be maintainer without having commit access. ~~Committers~~ can do commits and maintainers can send patches to ~~committers~~. Any ~~committers~~ can apply patches from maintainers. (This is similar to what FreeBSD does)		Only [https://docs.alpinelinux.org/governance/0.1b/Teams/developers.html '''Developers'''] or '''Committers'''can review and merge "Merge Requests" in GitLab.

			* You can be maintainer without having commit access. Developers can do commits and maintainers can send patches to Developers. Any Developer can apply patches from maintainers. (This is similar to what FreeBSD does)
	* The maintainer is responsible for the package and is expected to:		* The maintainer is responsible for the package and is expected to:
	** fix bugs in their package		** fix bugs in their package
	** keep it updated. This includes following upstream announcement list, RSS feeds etc., and providing updates to Alpine Linux in a timely fashion.		** keep it updated. This includes following upstream announcement list, RSS feeds etc., and providing updates to Alpine Linux in a timely fashion.
	*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring		*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring
	* ~~Committers~~ and others should confirm with the maintainer before making any changes to the package.		* Developers and others should confirm with the maintainer before making any changes to the package.


	[[Category:Development~~]] [[Category:Package Manager~~]]		[[Category:Development]]

Psykose: typo

2023-06-30T19:53:34Z

typo

← Older revision		Revision as of 19:53, 30 June 2023
Line 4:		Line 4:
	* The maintainer is responsible for the package and is expected to:		* The maintainer is responsible for the package and is expected to:
	** fix bugs in their package		** fix bugs in their package
	** keep it updated. This includes following upstream announcement list, RSS feeds etc., and ~~provide~~ updates to Alpine Linux in a timely fashion.		** keep it updated. This includes following upstream announcement list, RSS feeds etc., and providing updates to Alpine Linux in a timely fashion.
	*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring		*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring
	* Committers and others should confirm with the maintainer before making any changes to the package.		* Committers and others should confirm with the maintainer before making any changes to the package.

Witcher: Spelling and minor grammatical errors

2023-06-30T17:54:27Z

Spelling and minor grammatical errors

← Older revision		Revision as of 17:54, 30 June 2023
Line 2:		Line 2:

	* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what FreeBSD does)		* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what FreeBSD does)
	* The maintainer is responsible for ~~the~~ the package and is expected to:		* The maintainer is responsible for the package and is expected to:
	** fix bugs in package		** fix bugs in their package
	** keep it updated. This includes ~~follow~~ upstream announcement list, RSS ~~feed~~ etc and provide updates to Alpine Linux in timely fashion.		** keep it updated. This includes following upstream announcement list, RSS feeds etc., and provide updates to Alpine Linux in a timely fashion.
	*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring		*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring
	* Committers and others should confirm with the maintainer before making any changes of the package.		* Committers and others should confirm with the maintainer before making any changes to the package.


	[[Category:Development]] [[Category:Package Manager]]		[[Category:Development]] [[Category:Package Manager]]

Chereskata at 13:46, 14 December 2022

2022-12-14T13:46:02Z

← Older revision		Revision as of 13:46, 14 December 2022
Line 5:		Line 5:
	** fix bugs in package		** fix bugs in package
	** keep it updated. This includes follow upstream announcement list, RSS feed etc and provide updates to Alpine Linux in timely fashion.		** keep it updated. This includes follow upstream announcement list, RSS feed etc and provide updates to Alpine Linux in timely fashion.
			*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring
	* Committers and others should confirm with the maintainer before making any changes of the package.		* Committers and others should confirm with the maintainer before making any changes of the package.


	[[Category:Development]] [[Category:Package Manager]]		[[Category:Development]] [[Category:Package Manager]]

Ollieparanoid: spelling fixes

2018-03-18T08:25:55Z

spelling fixes

← Older revision		Revision as of 08:25, 18 March 2018
Line 1:		Line 1:
	{{Draft}}		{{Draft}}

	* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what ~~Freebsd~~ does)		* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what FreeBSD does)
	* The maintainer is responsible for the the package and is expected to:		* The maintainer is responsible for the the package and is expected to:
	** fix bugs in package		** fix bugs in package
	** keep it updated. This includes follow upstream ~~announcemt~~ list, ~~rss~~ feed etc and provide updates to Alpine Linux in timely fashion.		** keep it updated. This includes follow upstream announcement list, RSS feed etc and provide updates to Alpine Linux in timely fashion.
	* Committers and others should confirm with the maintainer before making any changes of the package.		* Committers and others should confirm with the maintainer before making any changes of the package.


	[[Category:Development]] [[Category:Package Manager]]		[[Category:Development]] [[Category:Package Manager]]

Thorduri at 14:12, 1 July 2015

2015-07-01T14:12:05Z

← Older revision		Revision as of 14:12, 1 July 2015
Line 4:		Line 4:
	* The maintainer is responsible for the the package and is expected to:		* The maintainer is responsible for the the package and is expected to:
	** fix bugs in package		** fix bugs in package
	** keep it ~~update~~. This includes follow upstream announcemt list, rss feed etc and provide updates to Alpine Linux in timely fashion.		** keep it updated. This includes follow upstream announcemt list, rss feed etc and provide updates to Alpine Linux in timely fashion.
	* Committers and others should confirm with the maintainer before making any changes of the package.		* Committers and others should confirm with the maintainer before making any changes of the package.


	[[Category:Development]] [[Category:Package Manager]]		[[Category:Development]] [[Category:Package Manager]]

Dubiousjim: Categories

2012-03-12T08:12:17Z

Ncopa: draft

2010-11-03T02:51:13Z

draft

← Older revision		Revision as of 02:51, 3 November 2010
Line 1:		Line 1:
			{{Draft}}

	* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what Freebsd does)		* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what Freebsd does)
	* The maintainer is responsible for the the package and is expected to:		* The maintainer is responsible for the the package and is expected to:

Ncopa: initial notes on whats expected from package maintainers

2010-11-03T02:50:36Z

initial notes on whats expected from package maintainers

New page

* You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what Freebsd does)
* The maintainer is responsible for the the package and is expected to:
** fix bugs in package
** keep it update. This includes follow upstream announcemt list, rss feed etc and provide updates to Alpine Linux in timely fashion.
* Committers and others should confirm with the maintainer before making any changes of the package.

← Older revision		Revision as of 08:12, 12 March 2012
Line 6:		Line 6:
	** keep it update. This includes follow upstream announcemt list, rss feed etc and provide updates to Alpine Linux in timely fashion.		** keep it update. This includes follow upstream announcemt list, rss feed etc and provide updates to Alpine Linux in timely fashion.
	* Committers and others should confirm with the maintainer before making any changes of the package.		* Committers and others should confirm with the maintainer before making any changes of the package.


			[[Category:Development]] [[Category:Package Manager]]