Shorewall Community ... The Shorewall Project Committee has decided to migrate the nexus of Shorewall development away from SourceForge and to GitLab.
The reasons for migrating to GitLab as a primary platform include: - better support for collaborative development (e.g., support for forking and better pull/merge request mechanics, especially for collaborative review and revision of proposed code changes) - better usability of associated development tools (e.g., issue tracker, wiki, etc.) - continuous integration support (allowing for future improvements to the release process) The new GitLab group is located here: https://gitlab.com/shorewall In the last weeks we have created individual projects and migrated content and revision history to GitLab. As of now, new bug reports, feature requests, merge requests, etc. should be created in the new GitLab projects. What will remain the same? - mailing lists will continue to be hosted on SourceForge, with general user and developer discussions continuing to take place on their respective lists - releases (i.e., tarballs) will continue to be published on shorewall.org, shorewall.net (at least in the near term), and other mirrors - Git repositories will remain available on SourceForge (though in a read-only state; see below for additional details) What will change? - Git repositories on SourceForge will transition to a read-only state; history will be periodically synchronized from GitLab but no new commits will be made directly to Git repositories on SourceForge - the primary mechanism for submitting proposed code changes will be via GitLab merge request instead of a patch sent to the mailing list* - the primary mechanism for submitting feature requests and bug reports will be via GitLab issue instead of via mailing list message** - proposed code changes may be integrated more slowly than in the past, depending upon the availability of designated reviewers - the shorewall.net domain name will be deprecated and the primary domain name for the Shorewall project will be shorewall.org * it is understood that accessibility of GitLab may not always permit for submission of proposed changes via merge request; should you wish to propose a change but are unable to utilize a GitLab merge request because of accessibility concerns, you should direct a patch to shorewall-de...@lists.sourceforge.net (as has been past practice) ** as with merge requests, if a user finds himself or herself unable to make use of the GitLab issue tracker because of accessibility concerns, bug reports and feature requests may be directed to the mailing list *** Note that a user called "shorewall" exists on GitHub. The Shorewall Project is not affiliated with that GitHub user account. The Shorewall Project Committee Matt Darfeuille Paul Gear Roberto C. Sánchez Tuomo Soini -Matt -- Matt Darfeuille _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
