[Proposal] Patch fix on release to prevent email address harvesting
Sander W G van der Waal
The email addresses on our public registry at
http://registry.oss-watch.ac.uk are not obfuscated
which makes it easy to be harvested by bots.
I created issue 257 [1] for this but it hadn't
been fixed up until now. I just checked in the fix
on the trunk ([2] and [3]).
I propose to patch this fix to the release 0.2.3, of
which rc1 has been out for almost three weeks now and
which is scheduled to be made final end of next week.
With the new release procedure this new binary release
will be the version on the public registry for the
next 2 months (as opposed to the development version
on port 8080 which changes much more often, eventually
with every commit).
I want to make the public registry attractive for people
to search for information and to provide us with more
information about their projects and themselves. To this
end it's important that we are careful with the data
people give us. Hence this proposal to patch this email
address fix in the release branch.
Please let me know your thoughts! With no objections in
the coming 72 hours I'd like to assume a lazy consensus.
Sander
[1] http://code.google.com/p/simal/issues/detail?id=257
[2] http://code.google.com/p/simal/source/detail?r=1864
[3] http://code.google.com/p/simal/source/detail?r=1865
OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk
Ross Gardler
> Hi,
>
> The email addresses on our public registry at
> http://registry.oss-watch.ac.uk are not obfuscated
> which makes it easy to be harvested by bots.
> I created issue 257 [1] for this but it hadn't
> been fixed up until now. I just checked in the fix
> on the trunk ([2] and [3]).
>
> I propose to patch this fix to the release 0.2.3, of
> which rc1 has been out for almost three weeks now and
> which is scheduled to be made final end of next week.
>
> With the new release procedure this new binary release
> will be the version on the public registry for the
> next 2 months (as opposed to the development version
> on port 8080 which changes much more often, eventually
> with every commit).
>
> I want to make the public registry attractive for people
> to search for information and to provide us with more
> information about their projects and themselves. To this
> end it's important that we are careful with the data
> people give us. Hence this proposal to patch this email
> address fix in the release branch.
>
> Please let me know your thoughts! With no objections in
> the coming 72 hours I'd like to assume a lazy consensus.
-1 But only on a matter of process.
A change to a release candidate cannot be made by lazy consensus.
Releases require a Lazy Majority vote, see
http://simal.oss-watch.ac.uk/contributor/governance/index.html by
extension a change to a release candidate must also undergo a Lazy
Majority vote.
The reason for this is that there needs to be sufficient
oversight/consensus on a release, but a release cannot be vetoed,
otherwise a vote can be unduly influenced by a single contributing
organisation.
However, I am +1 on you making the change for the reason given. You will
need to create a new release candidate binary once this patch has been
applied.
To be clear, I am -1 on the lazy consensus process. +1 on the lazy
majority vote that is required instead (just creating and resolving my
veto in a single mail).
Ross
Sander W G van der Waal
> contri...@googlegroups.com] On Behalf Of Ross Gardler
> Sent: 05 March 2010 22:06
> To: simal-con...@googlegroups.com
> Subject: Re: [Simal] [Proposal] Patch fix on release to prevent email
> address harvesting
Thanks Ross. I guess that means that I should formally call out the
lazy majority vote, noting that you have already given your vote.
The vote is to add the fix for issue 257 [1], commits [2] and [3] to
upcoming release 0.2.3 to make prevent harvesting of email addresses
from the public registry website.
The vote starts now and will run for a minimum of 72 hours.
[ ] - +1 - Add proposed fix to the next release 0.2.3.
[ ] - +/-0 - Don't care, whatever the majority decides.
[ ] - -1 - Strongly object to this (because ...)
Sander
[1] http://code.google.com/p/simal/issues/detail?id=257
[2] http://code.google.com/p/simal/source/detail?r=1864
[3] http://code.google.com/p/simal/source/detail?r=1865
>
> Ross
>
>
>
> >
> > Sander
> >
> > [1] http://code.google.com/p/simal/issues/detail?id=257
> > [2] http://code.google.com/p/simal/source/detail?r=1864
> > [3] http://code.google.com/p/simal/source/detail?r=1865
> >
> > OSS Watch - supporting open source in education and research
> http://www.oss-watch.ac.uk
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Simal contributors" group.
> To post to this group, send an email to simal-
> contri...@googlegroups.com.
> To unsubscribe from this group, send email to simal-
> contributors...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simal-
> contributors?hl=en-GB.
Stuart A. Yeates
<sander.v...@oucs.ox.ac.uk> wrote:
+1 - Add proposed fix to the next release 0.2.3.
If it's being done it should be in the next release, if possible.
cheers
stuart
Sander W G van der Waal
> contri...@googlegroups.com] On Behalf Of Sander W G van der Waal
> Sent: 07 March 2010 20:41
> To: simal-con...@googlegroups.com
> Subject: [VOTE] Add fix to prevent email address harvesting to release
> (Was: [Simal] [Proposal] Patch fix on release to prevent email address
> harvesting)
> Thanks Ross. I guess that means that I should formally call out the
> lazy majority vote, noting that you have already given your vote.
>
> The vote is to add the fix for issue 257 [1], commits [2] and [3] to
> upcoming release 0.2.3 to make prevent harvesting of email addresses
> from the public registry website.
>
> The vote starts now and will run for a minimum of 72 hours.
>
> [ ] - +1 - Add proposed fix to the next release 0.2.3.
>
> [ ] - +/-0 - Don't care, whatever the majority decides.
>
> [ ] - -1 - Strongly object to this (because ...)
>
Thanks for voting, this vote passes with:
+1 Ross Gardler, Stuart Yeates, Sander van der Waal
0 None
-1 None
I will create and upload RC2 with this fix ASAP and notify the list.
Sander
Sander W G van der Waal
> contri...@googlegroups.com] On Behalf Of Stuart A. Yeates
> Sent: 07 March 2010 21:30
> To: simal-con...@googlegroups.com
> Subject: Re: [VOTE] Add fix to prevent email address harvesting to release
> (Was: [Simal] [Proposal] Patch fix on release to prevent email address
> harvesting)
Thanks Stuart, the fix is done on the trunk and I will patch
it to the release branch and release a new RC for testing.
Sander
>
> cheers
> stuart