Re: [forge-dev] Forge Hack Night Summary
We haven't had much time to sync up on it so a few pointers legal made sure we got for
JBT was:
1) it has to be an opt-in
2) there has to an easy way to opt-out if you opt-in
3) a link to a site describing how it works (jboss.org/tools/usage and
devstudio.jboss.com/usage is how we do that in JBT/Devstudio)
4) Somewhere "near" the opt-in/opt-out should be information about what is
actually sent/tracked (see link above on how we present it in JBT/devstudio)
5) (Optional) have a way to shut if off in case there are technical and legal problems. in
JBT we read http://anonsvn.jboss.org/repos/jbosstools/workspace/usage/usage.properties as
our "deadman" switch.
/max
On 17 Sep 2012, at 10:07, Max Rydahl Andersen <max.andersen(a)redhat.com> wrote:
hey ggastaldi,
did you just copy jbosstools code over or spawn off in separate project for reuse or
something completely different ?
/max
On 14 Sep 2012, at 15:16, ggastald(a)redhat.com wrote:
> Nice you mention that. I was thinking about that in the shower yesterday. :)
>
> Basically we now have the update feature ready and the Google Analytics integration
(not yet merged) as I recall.
>
> Lincoln, thoughts ?
>
> George
>
> On 09/14/2012 10:11 AM, Rodney Russ wrote:
>>> If everything goes well, we expect to release 1.0.7.Final next week
>>> (Huge Features included ! Stay tuned !).
>>>
>> Huge Features != 1.1.0 release?
>>
>
> --
> George Gastaldi | Senior Software Engineer
> JBoss Forge Team
> Red Hat
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev