[Owasp-leaders] Remote Repositories on SourceForge
christian.heinrich at owasp.org
Thu Jan 5 02:03:38 UTC 2012
To quote the e-mail from the esapi-dev e-mail below - can you please advise
if Project Leaders are to be burdened in moving their repositories' to
SourceForge as opposed a GPC resource establishing a remote repository at
SourceForge which "pulls" at specific intervals i.e. the Project Leader
maintains their existing repository on Google Code, GitHub, etc?
If the GPC has the expectation to collapse the existing respositories' on
Google Code, GitHub, etc, can the GPG outline what "safeguards" they have
implemented to ensure ongoing community goodwill and avoid other Project
Leaders enduring similar distress that I experienced when I suddenly lost
membership to a number of OWASP Mailing Lists without notification or due
How will reduced consumer expectation be managed when the time to perform a
"svn checkout" (i.e. the latest commit) is now significantly greater with
"git clone" (i.e. all commits)?
Also, can the GPC indicate when they intend to address the outstanding
their selection of SourceForge?
From: esapi-dev-bounces at lists.owasp.org
[mailto:esapi-dev-bounces at lists.owasp.org] On Behalf Of Chris Schmidt
Sent: Friday, December 09, 2011 5:24 PM
To: ESAPI Devs
Subject: [Esapi-dev] Updates from me
2) Project Homepage and Hosting @ SF
I have all the pieces in place to start migrating ESAPI projects over to our
new home at SourceForge. I have created a new GIT repository to replace our
subversion repository. This should allow for simpler branching and the
ability for people to fork and do all kinds of interesting stuff with the
source. Our existing subversion repository will be retained in a read-only
state once we cut over for the individual projects.
More information about the OWASP-Leaders