This patch solves the display of OpenId and looks like partly working.
The issue may be that the library, as we know well, is not php >=5.3
aware.
Was decided not to correct it in 1.5.
I guess we have to take a decision here. Do we keep OpenId in 1.6 and,
if yes, who is willing to make the all thing work as it should?
I'd be in favour of dropping it and letting it ship as an external item from anyone who is interested. It has an unhealthy dependence within the login module to just get it to work properly and it was initially put in I believe to get a bounty from the OpenID Foundation (or similar organisation) that I don't think the project ever actually got anyway.
Removing it would simplify mod_login to remove the OpenID dependence as well as removing the PHP 5.3 issue in general.
> This patch solves the display of OpenId and looks like partly working. > The issue may be that the library, as we know well, is not php >=5.3 > aware. > Was decided not to correct it in 1.5.
> I guess we have to take a decision here. Do we keep OpenId in 1.6 and, > if yes, who is willing to make the all thing work as it should?
> -- > You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/joomlabugsquad?hl=en.
So we either drop it and save ourselves work or we do an upgrade to the latest version of the library and complete testing in the middle of the stablisation period to get 5.3 support? [1] Which is the greater sin? Additionally this doesn't involve a new API change that I know of - the OpenID library lives in the OpenID plugin already so I don't see any change.
Personally I'm a great fan of dropping it and letting someone ship it themselves and keep up with the external library, well, externally. It reduces complexity, simplifies testing and makes the product more stable with the minor exception that we have to test that we successfully culled that annoying JS switcher in mod_login. I additionally don't like it because it breaks the way the authentication system works in a few other places.
<hackwa...@googlemail.com> wrote: > As much as I agree to remove it, we are again not sticking to our own rules. > We are in Beta and the last definition that I got was, that we dont do API > changes...
> Am 02.07.2010 14:24 schrieb "Sam Moffatt" <pasa...@gmail.com>:
> I'd be in favour of dropping it and letting it ship as an external > item from anyone who is interested. It has an unhealthy dependence > within the login module to just get it to work properly and it was > initially put in I believe to get a bounty from the OpenID Foundation > (or similar organisation) that I don't think the project ever actually > got anyway.
> Removing it would simplify mod_login to remove the OpenID dependence > as well as removing the PHP 5.3 issue in general.
> On Fri, Jul 2, 2010 at 6:41 AM, infograf768 <infograf...@gmail.com> wrote: >> Please see >> http://...
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
Let me rephrase that: remove it, please, but in general keep the Beta rules in mind.
Am 02.07.2010 15:03 schrieb "Sam Moffatt" <pasa...@gmail.com>:
So we either drop it and save ourselves work or we do an upgrade to the latest version of the library and complete testing in the middle of the stablisation period to get 5.3 support? [1] Which is the greater sin? Additionally this doesn't involve a new API change that I know of - the OpenID library lives in the OpenID plugin already so I don't see any change.
Personally I'm a great fan of dropping it and letting someone ship it themselves and keep up with the external library, well, externally. It reduces complexity, simplifies testing and makes the product more stable with the minor exception that we have to test that we successfully culled that annoying JS switcher in mod_login. I additionally don't like it because it breaks the way the authentication system works in a few other places.
<hackwa...@googlemail.com> wrote: > As much as I... > -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squa...
On Fri, Jul 2, 2010 at 9:03 AM, Sam Moffatt <pasa...@gmail.com> wrote:
> Personally I'm a great fan of dropping it and letting someone ship it > themselves and keep up with the external library, well, externally. It > reduces complexity, simplifies testing and makes the product more > stable with the minor exception that we have to test that we > successfully culled that annoying JS switcher in mod_login. I > additionally don't like it because it breaks the way the > authentication system works in a few other places.
That seems very reasonable to me. ++
Matt
Matt Thomas Founder - betweenbrain web • print • identity • creative www.betweenbrain.com
On Fri, Jul 2, 2010 at 6:13 AM, Matt Thomas <m...@betweenbrain.com> wrote: > On Fri, Jul 2, 2010 at 9:03 AM, Sam Moffatt <pasa...@gmail.com> wrote:
>> Personally I'm a great fan of dropping it and letting someone ship it >> themselves and keep up with the external library, well, externally. It >> reduces complexity, simplifies testing and makes the product more >> stable with the minor exception that we have to test that we >> successfully culled that annoying JS switcher in mod_login. I >> additionally don't like it because it breaks the way the >> authentication system works in a few other places.
> That seems very reasonable to me. ++
> Matt
> Matt Thomas > Founder - betweenbrain > web • print • identity • creative > www.betweenbrain.com
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
While it's difficult for me to say this, yes, we should probably take OpenID out of core. OpenID adoption has increased over the last couple of years, but not at the rate where it's actually replacing account creation for the vast majority of Internet users. I personally use OpenID on a couple of sites I manage, but I'm the only user doing so. In the interest of getting 1.6 out the door, I agree to removing it as well.
> Agree to removing it. This has been not the easiest plugin to keep working through 1.5. Best as an extension, IMO.
> -- > You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/joomlabugsquad?hl=en.
I'm in favour of dropping OpenID now and we review it again in a future version where we can attack the "multiple identities" thing. I'd patch the code and put it in a branch for people to work on if they so desired.
> While it's difficult for me to say this, yes, we should probably take OpenID out of core. OpenID adoption has increased over the last couple of years, but not at the rate where it's actually replacing account creation for the vast majority of Internet users. I personally use OpenID on a couple of sites I manage, but I'm the only user doing so. In the interest of getting 1.6 out the door, I agree to removing it as well.
> -Joe
> On Jul 2, 2010, at 12:37 PM, Amy Stephen wrote:
>> Agree to removing it. This has been not the easiest plugin to keep working through 1.5. Best as an extension, IMO.
>> -- >> You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group. >> To post to this group, send email to joomlabugsquad@googlegroups.com. >> To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/joomlabugsquad?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/joomlabugsquad?hl=en.
I agree with this decision and apologise towards Christophe at not
reacting in a timely manner to ask him to wait until a decision would
be taken when he told us he would make this patch.
(Was quite a complex patch)
JM
On Jul 3, 12:32 am, Andrew Eddie <mambob...@gmail.com> wrote:
> I'm in favour of dropping OpenID now and we review it again in a
> future version where we can attack the "multiple identities" thing.
> I'd patch the code and put it in a branch for people to work on if
> they so desired.
> On 3 July 2010 03:01, Joseph LeBlanc <cont...@jlleblanc.com> wrote:
> > While it's difficult for me to say this, yes, we should probably take OpenID out of core. OpenID adoption has increased over the last couple of years, but not at the rate where it's actually replacing account creation for the vast majority of Internet users. I personally use OpenID on a couple of sites I manage, but I'm the only user doing so. In the interest of getting 1.6 out the door, I agree to removing it as well.
> > -Joe
> > On Jul 2, 2010, at 12:37 PM, Amy Stephen wrote:
> >> Agree to removing it. This has been not the easiest plugin to keep working through 1.5. Best as an extension, IMO.
> >> --
> >> You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group.
> >> To post to this group, send email to joomlabugsquad@googlegroups.com.
> >> To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com.
> >> For more options, visit this group athttp://groups.google.com/group/joomlabugsquad?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups "Joomla! bug Squad" group.
> > To post to this group, send email to joomlabugsquad@googlegroups.com.
> > To unsubscribe from this group, send email to joomlabugsquad+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/joomlabugsquad?hl=en.
As much as I agree to remove it, we are again not sticking to our own rules. We are in Beta and the last definition that I got was, that we dont do API changes...
Am 02.07.2010 14:24 schrieb "Sam Moffatt" <pasa...@gmail.com>:
I'd be in favour of dropping it and letting it ship as an external item from anyone who is interested. It has an unhealthy dependence within the login module to just get it to work properly and it was initially put in I believe to get a bounty from the OpenID Foundation (or similar organisation) that I don't think the project ever actually got anyway.
Removing it would simplify mod_login to remove the OpenID dependence as well as removing the PHP 5.3 issue in general.
Correct, we never received the bounty (despite repeated exchanges
between me and their executive director informing them that we had
implemented and released). The whole thing was a nightmare because of
the dependencies on the external library which was relicensed half
way through to be incompatible with GPLv2. Putting it in required a
total review of the licenses of other libraries in the codebase which
ultimately was a good thing since we now know we are fine as GPLv3.
Given that we put all that work in, I kind of hate to give it up, but
I also can't see supporting something and having to say over and over
that it won't work on your php version. It's worse than the flash
uploader. And I would vote to support it using a library that is
compatible with v2 an v3.
For sites like joomla.org that require many different authentications
using OpenID from a domain specific OpenID server is a good potential
solution I also do think that long term we do need to support these
kinds of things out of the box but it's important that we do it in the
right way and a sustainable way.
Do we have third party developers or custom developers who are
incorporating it? I think it's probably worth asking for feedback. For
example I believe there was a gsoc project that used the OpenID api as
a way to manage a bridge to an incompatible application. Also, we do
periodically get issue reports and forum posts about it, so that
indicates that at least some people are trying to use it.
All of which is to say, I'm pretty neutral on it.
Elin
On Jul 2, 8:43 am, Hannes Papenberg <hackwa...@googlemail.com> wrote:
> As much as I agree to remove it, we are again not sticking to our own rules.
> We are in Beta and the last definition that I got was, that we dont do API
> changes...
> Am 02.07.2010 14:24 schrieb "Sam Moffatt" <pasa...@gmail.com>:
> I'd be in favour of dropping it and letting it ship as an external
> item from anyone who is interested. It has an unhealthy dependence
> within the login module to just get it to work properly and it was
> initially put in I believe to get a bounty from the OpenID Foundation
> (or similar organisation) that I don't think the project ever actually
> got anyway.
> Removing it would simplify mod_login to remove the OpenID dependence
> as well as removing the PHP 5.3 issue in general.
On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote:
> Correct, we never received the bounty (despite repeated exchanges
> between me and their executive director informing them that we had
> implemented and released).
Let's not forget, though, that we were also well over a year beyond
the bounty date.
On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> wrote:
> On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: > > Correct, we never received the bounty (despite repeated exchanges > > between me and their executive director informing them that we had > > implemented and released).
> Let's not forget, though, that we were also well over a year beyond > the bounty date.
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
When we were at the OSCMS conference - the cutoff date was close then.
Cool Acid was there and he did the first implementation. It was pretty
clear at that time we weren't going to release in time. I think it was
nine months later that we released. We didn't apply for the bounty
right away, either. It really was very late. They wanted to give it to
us - and even responded on "the AmyBlog" when I wrote about it - and
in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time
to release.
On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote:
> I don't remember ever seeing anything about the cutoff date for the bounty
> and I did look quite a bit at the time I was implementing 2.0.
> Ian
> On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> wrote:
> > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote:
> > > Correct, we never received the bounty (despite repeated exchanges
> > > between me and their executive director informing them that we had
> > > implemented and released).
> > Let's not forget, though, that we were also well over a year beyond
> > the bounty date.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Joomla! bug Squad" group.
> > To post to this group, send email to joomlabugsquad@googlegroups.com.
> > To unsubscribe from this group, send email to
> > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/joomlabugsquad?hl=en.
On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com> wrote: > When we were at the OSCMS conference - the cutoff date was close then. > Cool Acid was there and he did the first implementation. It was pretty > clear at that time we weren't going to release in time. I think it was > nine months later that we released. We didn't apply for the bounty > right away, either. It really was very late. They wanted to give it to > us - and even responded on "the AmyBlog" when I wrote about it - and > in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time > to release.
> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote: > > I don't remember ever seeing anything about the cutoff date for the > bounty > > and I did look quite a bit at the time I was implementing 2.0.
> > Ian
> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> wrote:
> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: > > > > Correct, we never received the bounty (despite repeated exchanges > > > > between me and their executive director informing them that we had > > > > implemented and released).
> > > Let's not forget, though, that we were also well over a year beyond > > > the bounty date.
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Joomla! bug Squad" group. > > > To post to this group, send email to joomlabugsquad@googlegroups.com. > > > To unsubscribe from this group, send email to > > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
Originally, the bounty was a year, if I remember correctly. The bounty site is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the prize (barely) within that year in June 2007 <http://drupal.org/node/152893>. Seems like Wordpress qualified in time, too, but I can't find a link.
I do think they tried to keep things open following the deadline because I don't think they got 10 solutions that met the criteria within the year and they really did want Joomla! to participate.
Before Elin got involved, I am guessing we did not do a very good job of communicating with them to let them know we were really interested. I don't know exactly what happened. I think the project is much better organized now for communication.
On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan <ian.maclen...@joomla.org>wrote:
> There was also a 2.0 bounty was there not? 1.5 was released before 2.0 > was.
> Ian
> On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com> wrote:
>> When we were at the OSCMS conference - the cutoff date was close then. >> Cool Acid was there and he did the first implementation. It was pretty >> clear at that time we weren't going to release in time. I think it was >> nine months later that we released. We didn't apply for the bounty >> right away, either. It really was very late. They wanted to give it to >> us - and even responded on "the AmyBlog" when I wrote about it - and >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time >> to release.
>> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote: >> > I don't remember ever seeing anything about the cutoff date for the >> bounty >> > and I did look quite a bit at the time I was implementing 2.0.
>> > Ian
>> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> >> wrote:
>> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: >> > > > Correct, we never received the bounty (despite repeated exchanges >> > > > between me and their executive director informing them that we had >> > > > implemented and released).
>> > > Let's not forget, though, that we were also well over a year beyond >> > > the bounty date.
>> > > -- >> > > You received this message because you are subscribed to the Google >> Groups >> > > "Joomla! bug Squad" group. >> > > To post to this group, send email to joomlabugsquad@googlegroups.com. >> > > To unsubscribe from this group, send email to >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
>> -- >> You received this message because you are subscribed to the Google Groups >> "Joomla! bug Squad" group. >> To post to this group, send email to joomlabugsquad@googlegroups.com. >> To unsubscribe from this group, send email to >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/joomlabugsquad?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
What they did was change the bounty to a 2.0 one.
Also, I would say they did not do a good job of commmunicating with us
since they never told anyone from the project that there was such a
bounty.
Elin
On Jul 5, 12:31 pm, Amy Stephen <amystep...@gmail.com> wrote:
> Originally, the bounty was a year, if I remember correctly. The bounty site
> is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the prize
> (barely) within that year in June 2007 <http://drupal.org/node/152893>.
> Seems like Wordpress qualified in time, too, but I can't find a link.
> I do think they tried to keep things open following the deadline because I
> don't think they got 10 solutions that met the criteria within the year and
> they really did want Joomla! to participate.
> Before Elin got involved, I am guessing we did not do a very good job of
> communicating with them to let them know we were really interested. I don't
> know exactly what happened. I think the project is much better organized now
> for communication.
> On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan <ian.maclen...@joomla.org>wrote:
> > There was also a 2.0 bounty was there not? 1.5 was released before 2.0
> > was.
> > Ian
> > On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com> wrote:
> >> When we were at the OSCMS conference - the cutoff date was close then.
> >> Cool Acid was there and he did the first implementation. It was pretty
> >> clear at that time we weren't going to release in time. I think it was
> >> nine months later that we released. We didn't apply for the bounty
> >> right away, either. It really was very late. They wanted to give it to
> >> us - and even responded on "the AmyBlog" when I wrote about it - and
> >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time
> >> to release.
> >> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote:
> >> > I don't remember ever seeing anything about the cutoff date for the
> >> bounty
> >> > and I did look quite a bit at the time I was implementing 2.0.
> >> > Ian
> >> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com>
> >> wrote:
> >> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote:
> >> > > > Correct, we never received the bounty (despite repeated exchanges
> >> > > > between me and their executive director informing them that we had
> >> > > > implemented and released).
> >> > > Let's not forget, though, that we were also well over a year beyond
> >> > > the bounty date.
> >> > > --
> >> > > You received this message because you are subscribed to the Google
> >> Groups
> >> > > "Joomla! bug Squad" group.
> >> > > To post to this group, send email to joomlabugsquad@googlegroups.com.
> >> > > To unsubscribe from this group, send email to
> >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Joomla! bug Squad" group.
> >> To post to this group, send email to joomlabugsquad@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> .
> >> For more options, visit this group at
> >>http://groups.google.com/group/joomlabugsquad?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Joomla! bug Squad" group.
> > To post to this group, send email to joomlabugsquad@googlegroups.com.
> > To unsubscribe from this group, send email to
> > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/joomlabugsquad?hl=en.
Please check those links I shared in the item you just responded too. It started as an Open ID 2.0 bounty and it never changed.
We absolutely understood - the two forums posts I shared showed Alex saying they know about it and it's under control - and the other has Johan talking about it, too.
Here's another link where I posted in the forums that Scott Kveton (Open ID founder) left a note on my blog that he would allow the bounty to go on six more months until July 2007 (it was a six month extension)
It's unfortunate, but we just didn't get it done. We had opportunity. They wanted it for our community. We understood. We just didn't do it. Simple as that.
> > Originally, the bounty was a year, if I remember correctly. The bounty > site > > is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the prize > > (barely) within that year in June 2007 <http://drupal.org/node/152893>. > > Seems like Wordpress qualified in time, too, but I can't find a link.
> > I do think they tried to keep things open following the deadline because > I > > don't think they got 10 solutions that met the criteria within the year > and > > they really did want Joomla! to participate.
> > Before Elin got involved, I am guessing we did not do a very good job of > > communicating with them to let them know we were really interested. I > don't > > know exactly what happened. I think the project is much better organized > now > > for communication.
> > On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan <ian.maclen...@joomla.org > >wrote:
> > > There was also a 2.0 bounty was there not? 1.5 was released before 2.0 > > > was.
> > > Ian
> > > On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com> > wrote:
> > >> When we were at the OSCMS conference - the cutoff date was close then. > > >> Cool Acid was there and he did the first implementation. It was pretty > > >> clear at that time we weren't going to release in time. I think it was > > >> nine months later that we released. We didn't apply for the bounty > > >> right away, either. It really was very late. They wanted to give it to > > >> us - and even responded on "the AmyBlog" when I wrote about it - and > > >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time > > >> to release.
> > >> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote: > > >> > I don't remember ever seeing anything about the cutoff date for the > > >> bounty > > >> > and I did look quite a bit at the time I was implementing 2.0.
> > >> > Ian
> > >> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> > > >> wrote:
> > >> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: > > >> > > > Correct, we never received the bounty (despite repeated > exchanges > > >> > > > between me and their executive director informing them that we > had > > >> > > > implemented and released).
> > >> > > Let's not forget, though, that we were also well over a year > beyond > > >> > > the bounty date.
> > >> > > -- > > >> > > You received this message because you are subscribed to the Google > > >> Groups > > >> > > "Joomla! bug Squad" group. > > >> > > To post to this group, send email to > joomlabugsquad@googlegroups.com. > > >> > > To unsubscribe from this group, send email to > > >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@go oglegroups.com> > > >> <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com><joomlabugsquad%252Bunsubscri > be@googlegroups.com>
> > >> -- > > >> You received this message because you are subscribed to the Google > Groups > > >> "Joomla! bug Squad" group. > > >> To post to this group, send email to joomlabugsquad@googlegroups.com. > > >> To unsubscribe from this group, send email to > > >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@go oglegroups.com> > > >> . > > >> For more options, visit this group at > > >>http://groups.google.com/group/joomlabugsquad?hl=en.
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Joomla! bug Squad" group. > > > To post to this group, send email to joomlabugsquad@googlegroups.com. > > > To unsubscribe from this group, send email to > > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@go oglegroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/joomlabugsquad?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
If you read the blog you just linked to, it says that Open ID 2.0 wasn't even out yet, which is interesting.
In any event, http://web.archive.org/web/20080622230541rn_2/openid.net/foundation/b... an archive of the bounty page and it makes no mention of it being over. I don't know when that page was taken down, but I am fairly certain that I referenced it around the time we did the upgrade and it was still up then.
I suppose I never thought to read a blog about it. I would assume the official announcement page would be the source.
Apparently around that time also we were in conversation with them and received communication to the effect that we would receive the money.
Anyway, this seems to be neither here nor there now, we never did get the money and it doesn't look like we're going to.
On Mon, Jul 5, 2010 at 4:07 PM, Amy Stephen <amystep...@gmail.com> wrote: > Elin -
> Please check those links I shared in the item you just responded too. It > started as an Open ID 2.0 bounty and it never changed.
> We absolutely understood - the two forums posts I shared showed Alex saying > they know about it and it's under control - and the other has Johan talking > about it, too.
> Here's another link where I posted in the forums that Scott Kveton (Open ID > founder) left a note on my blog that he would allow the bounty to go on six > more months until July 2007 (it was a six month extension)
> It's unfortunate, but we just didn't get it done. We had opportunity. They > wanted it for our community. We understood. We just didn't do it. Simple as > that.
> Amy
>> Elin
>> On Jul 5, 12:31 pm, Amy Stephen <amystep...@gmail.com> wrote: >> > Ian -
>> > Originally, the bounty was a year, if I remember correctly. The bounty >> site >> > is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the prize >> > (barely) within that year in June 2007 <http://drupal.org/node/152893>. >> > Seems like Wordpress qualified in time, too, but I can't find a link.
>> > I do think they tried to keep things open following the deadline because >> I >> > don't think they got 10 solutions that met the criteria within the year >> and >> > they really did want Joomla! to participate.
>> > Before Elin got involved, I am guessing we did not do a very good job of >> > communicating with them to let them know we were really interested. I >> don't >> > know exactly what happened. I think the project is much better organized >> now >> > for communication.
>> > On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan < >> ian.maclen...@joomla.org>wrote:
>> > > There was also a 2.0 bounty was there not? 1.5 was released before >> 2.0 >> > > was.
>> > > Ian
>> > > On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com> >> wrote:
>> > >> When we were at the OSCMS conference - the cutoff date was close >> then. >> > >> Cool Acid was there and he did the first implementation. It was >> pretty >> > >> clear at that time we weren't going to release in time. I think it >> was >> > >> nine months later that we released. We didn't apply for the bounty >> > >> right away, either. It really was very late. They wanted to give it >> to >> > >> us - and even responded on "the AmyBlog" when I wrote about it - and >> > >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time >> > >> to release.
>> > >> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote: >> > >> > I don't remember ever seeing anything about the cutoff date for the >> > >> bounty >> > >> > and I did look quite a bit at the time I was implementing 2.0.
>> > >> > Ian
>> > >> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> >> > >> wrote:
>> > >> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: >> > >> > > > Correct, we never received the bounty (despite repeated >> exchanges >> > >> > > > between me and their executive director informing them that we >> had >> > >> > > > implemented and released).
>> > >> > > Let's not forget, though, that we were also well over a year >> beyond >> > >> > > the bounty date.
>> > >> > > -- >> > >> > > You received this message because you are subscribed to the >> Google >> > >> Groups >> > >> > > "Joomla! bug Squad" group. >> > >> > > To post to this group, send email to >> joomlabugsquad@googlegroups.com. >> > >> > > To unsubscribe from this group, send email to >> > >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> <joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> > >> <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com><joomlabugsquad%252Bunsubscri >> be@googlegroups.com>
>> > >> -- >> > >> You received this message because you are subscribed to the Google >> Groups >> > >> "Joomla! bug Squad" group. >> > >> To post to this group, send email to joomlabugsquad@googlegroups.com >> . >> > >> To unsubscribe from this group, send email to >> > >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> <joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> > >> . >> > >> For more options, visit this group at >> > >>http://groups.google.com/group/joomlabugsquad?hl=en.
>> > > -- >> > > You received this message because you are subscribed to the Google >> Groups >> > > "Joomla! bug Squad" group. >> > > To post to this group, send email to joomlabugsquad@googlegroups.com. >> > > To unsubscribe from this group, send email to >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> <joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> > > . >> > > For more options, visit this group at >> > >http://groups.google.com/group/joomlabugsquad?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Joomla! bug Squad" group. >> To post to this group, send email to joomlabugsquad@googlegroups.com. >> To unsubscribe from this group, send email to >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/joomlabugsquad?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
> If you read the blog you just linked to, it says that Open ID 2.0 wasn't
> even out yet, which is interesting.
> In any event,http://web.archive.org/web/20080622230541rn_2/openid.net/foundation/b...
> an archive of the bounty page and it makes no mention of it being
> over.
> I don't know when that page was taken down, but I am fairly certain that I
> referenced it around the time we did the upgrade and it was still up then.
> I suppose I never thought to read a blog about it. I would assume the
> official announcement page would be the source.
> Apparently around that time also we were in conversation with them and
> received communication to the effect that we would receive the money.
> Anyway, this seems to be neither here nor there now, we never did get the
> money and it doesn't look like we're going to.
> Well, that chapter is closed I guess.
> Ian
> On Mon, Jul 5, 2010 at 4:07 PM, Amy Stephen <amystep...@gmail.com> wrote:
> > Elin -
> > Please check those links I shared in the item you just responded too. It
> > started as an Open ID 2.0 bounty and it never changed.
> > We absolutely understood - the two forums posts I shared showed Alex saying
> > they know about it and it's under control - and the other has Johan talking
> > about it, too.
> > Here's another link where I posted in the forums that Scott Kveton (Open ID
> > founder) left a note on my blog that he would allow the bounty to go on six
> > more months until July 2007 (it was a six month extension)
> > It's unfortunate, but we just didn't get it done. We had opportunity. They
> > wanted it for our community. We understood. We just didn't do it. Simple as
> > that.
> > Amy
> >> Elin
> >> On Jul 5, 12:31 pm, Amy Stephen <amystep...@gmail.com> wrote:
> >> > Ian -
> >> > Originally, the bounty was a year, if I remember correctly. The bounty
> >> site
> >> > is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the prize
> >> > (barely) within that year in June 2007 <http://drupal.org/node/152893>.
> >> > Seems like Wordpress qualified in time, too, but I can't find a link.
> >> > I do think they tried to keep things open following the deadline because
> >> I
> >> > don't think they got 10 solutions that met the criteria within the year
> >> and
> >> > they really did want Joomla! to participate.
> >> > Before Elin got involved, I am guessing we did not do a very good job of
> >> > communicating with them to let them know we were really interested. I
> >> don't
> >> > know exactly what happened. I think the project is much better organized
> >> now
> >> > for communication.
> >> > On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan <
> >> ian.maclen...@joomla.org>wrote:
> >> > > There was also a 2.0 bounty was there not? 1.5 was released before
> >> 2.0
> >> > > was.
> >> > > Ian
> >> > > On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com>
> >> wrote:
> >> > >> When we were at the OSCMS conference - the cutoff date was close
> >> then.
> >> > >> Cool Acid was there and he did the first implementation. It was
> >> pretty
> >> > >> clear at that time we weren't going to release in time. I think it
> >> was
> >> > >> nine months later that we released. We didn't apply for the bounty
> >> > >> right away, either. It really was very late. They wanted to give it
> >> to
> >> > >> us - and even responded on "the AmyBlog" when I wrote about it - and
> >> > >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time
> >> > >> to release.
> >> > >> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote:
> >> > >> > I don't remember ever seeing anything about the cutoff date for the
> >> > >> bounty
> >> > >> > and I did look quite a bit at the time I was implementing 2.0.
> >> > >> > Ian
> >> > >> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com>
> >> > >> wrote:
> >> > >> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote:
> >> > >> > > > Correct, we never received the bounty (despite repeated
> >> exchanges
> >> > >> > > > between me and their executive director informing them that we
> >> had
> >> > >> > > > implemented and released).
> >> > >> > > Let's not forget, though, that we were also well over a year
> >> beyond
> >> > >> > > the bounty date.
> >> > >> > > --
> >> > >> > > You received this message because you are subscribed to the
> >> Google
> >> > >> Groups
> >> > >> > > "Joomla! bug Squad" group.
> >> > >> > > To post to this group, send email to
> >> joomlabugsquad@googlegroups.com.
> >> > >> > > To unsubscribe from this group, send email to
> >> > >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> <joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> > >> <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com><joomlabugsquad%252Bunsubscri
> >> be@googlegroups.com>
> >> > >> --
> >> > >> You received this message because you are subscribed to the Google
> >> Groups
> >> > >> "Joomla! bug Squad" group.
> >> > >> To post to this group, send email to joomlabugsquad@googlegroups.com
> >> .
> >> > >> To unsubscribe from this group, send email to
> >> > >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> <joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> > >> .
> >> > >> For more options, visit this group at
> >> > >>http://groups.google.com/group/joomlabugsquad?hl=en.
> >> > > --
> >> > > You received this message because you are subscribed to the Google
> >> Groups
> >> > > "Joomla! bug Squad" group.
> >> > > To post to this group, send email to joomlabugsquad@googlegroups.com.
> >> > > To unsubscribe from this group, send email to
> >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> <joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> > > .
> >> > > For more options, visit this group at
> >> > >http://groups.google.com/group/joomlabugsquad?hl=en.
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Joomla! bug Squad" group.
> >> To post to this group, send email to joomlabugsquad@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> >> .
> >> For more options, visit this group at
> >>http://groups.google.com/group/joomlabugsquad?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Joomla! bug Squad" group.
> > To post to this group, send email to joomlabugsquad@googlegroups.com.
> > To unsubscribe from this group, send email to
> > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/joomlabugsquad?hl=en.
Fair enough, though there doesn't seem to be much in the way of dissenting voice here and it seems clear like the way to go is removing OpenID from core.
On Mon, Jul 5, 2010 at 4:47 PM, brian teeman <br...@teeman.net> wrote: > Whilst this is all very interesting history it doesnt really help in > making the decision to either keep or remove openid from joomla 1.6.
> On Jul 5, 9:25 pm, Ian MacLennan <ian.maclen...@joomla.org> wrote: > > If you read the blog you just linked to, it says that Open ID 2.0 wasn't > > even out yet, which is interesting.
> > In any event, > http://web.archive.org/web/20080622230541rn_2/openid.net/foundation/b... > > an archive of the bounty page and it makes no mention of it being > > over. > > I don't know when that page was taken down, but I am fairly certain that > I > > referenced it around the time we did the upgrade and it was still up > then.
> > I suppose I never thought to read a blog about it. I would assume the > > official announcement page would be the source.
> > Apparently around that time also we were in conversation with them and > > received communication to the effect that we would receive the money.
> > Anyway, this seems to be neither here nor there now, we never did get the > > money and it doesn't look like we're going to.
> > Well, that chapter is closed I guess.
> > Ian
> > On Mon, Jul 5, 2010 at 4:07 PM, Amy Stephen <amystep...@gmail.com> > wrote: > > > Elin -
> > > Please check those links I shared in the item you just responded too. > It > > > started as an Open ID 2.0 bounty and it never changed.
> > > We absolutely understood - the two forums posts I shared showed Alex > saying > > > they know about it and it's under control - and the other has Johan > talking > > > about it, too.
> > > Here's another link where I posted in the forums that Scott Kveton > (Open ID > > > founder) left a note on my blog that he would allow the bounty to go on > six > > > more months until July 2007 (it was a six month extension)
> > > It's unfortunate, but we just didn't get it done. We had opportunity. > They > > > wanted it for our community. We understood. We just didn't do it. > Simple as > > > that.
> > > Amy
> > >> Elin
> > >> On Jul 5, 12:31 pm, Amy Stephen <amystep...@gmail.com> wrote: > > >> > Ian -
> > >> > Originally, the bounty was a year, if I remember correctly. The > bounty > > >> site > > >> > is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the > prize > > >> > (barely) within that year in June 2007 < > http://drupal.org/node/152893>. > > >> > Seems like Wordpress qualified in time, too, but I can't find a > link.
> > >> > I do think they tried to keep things open following the deadline > because > > >> I > > >> > don't think they got 10 solutions that met the criteria within the > year > > >> and > > >> > they really did want Joomla! to participate.
> > >> > Before Elin got involved, I am guessing we did not do a very good > job of > > >> > communicating with them to let them know we were really interested. > I > > >> don't > > >> > know exactly what happened. I think the project is much better > organized > > >> now > > >> > for communication.
> > >> > On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan < > > >> ian.maclen...@joomla.org>wrote:
> > >> > > There was also a 2.0 bounty was there not? 1.5 was released > before > > >> 2.0 > > >> > > was.
> > >> > > Ian
> > >> > > On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com
> > >> wrote:
> > >> > >> When we were at the OSCMS conference - the cutoff date was close > > >> then. > > >> > >> Cool Acid was there and he did the first implementation. It was > > >> pretty > > >> > >> clear at that time we weren't going to release in time. I think > it > > >> was > > >> > >> nine months later that we released. We didn't apply for the > bounty > > >> > >> right away, either. It really was very late. They wanted to give > it > > >> to > > >> > >> us - and even responded on "the AmyBlog" when I wrote about it - > and > > >> > >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long > time > > >> > >> to release.
> > >> > >> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> > wrote: > > >> > >> > I don't remember ever seeing anything about the cutoff date for > the > > >> > >> bounty > > >> > >> > and I did look quite a bit at the time I was implementing 2.0.
> > >> > >> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: > > >> > >> > > > Correct, we never received the bounty (despite repeated > > >> exchanges > > >> > >> > > > between me and their executive director informing them that > we > > >> had > > >> > >> > > > implemented and released).
> > >> > >> > > Let's not forget, though, that we were also well over a year > > >> beyond > > >> > >> > > the bounty date.
> > >> > >> > > -- > > >> > >> > > You received this message because you are subscribed to the > > >> Google > > >> > >> Groups > > >> > >> > > "Joomla! bug Squad" group. > > >> > >> > > To post to this group, send email to > > >> joomlabugsquad@googlegroups.com. > > >> > >> > > To unsubscribe from this group, send email to > > >> > >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> > >> > >> -- > > >> > >> You received this message because you are subscribed to the > Google > > >> Groups > > >> > >> "Joomla! bug Squad" group. > > >> > >> To post to this group, send email to > joomlabugsquad@googlegroups.com > > >> . > > >> > >> To unsubscribe from this group, send email to > > >> > >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> > >> > > -- > > >> > > You received this message because you are subscribed to the Google > > >> Groups > > >> > > "Joomla! bug Squad" group. > > >> > > To post to this group, send email to > joomlabugsquad@googlegroups.com. > > >> > > To unsubscribe from this group, send email to > > >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> > >> -- > > >> You received this message because you are subscribed to the Google > Groups > > >> "Joomla! bug Squad" group. > > >> To post to this group, send email to joomlabugsquad@googlegroups.com. > > >> To unsubscribe from this group, send email to > > >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Joomla! bug Squad" group. > > > To post to this group, send email to joomlabugsquad@googlegroups.com. > > > To unsubscribe from this group, send email to > > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com>
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to
We would like to have all of the Bounties awarded in 6 months after the start of the program. We announced the bounty program at OSCON 2006 (July) so we hope to wrap up the bounty contest by January 2007.
If you look in January/February, you'll see they updated the page and extend it until mid 2008. (It wasn't just my blog ;-) ).
The link you shared was one year later, when the program was done in June 2008 - Plone, Drupal and dotnetnuke met the requirements with Open ID 2 in core and received the bounty.
Yes, it was beta 2.0. The point of the bounty was to encourage early adoption.
I have no objection to removing it from trunk.
On Mon, Jul 5, 2010 at 3:25 PM, Ian MacLennan <ian.maclen...@joomla.org>wrote:
> If you read the blog you just linked to, it says that Open ID 2.0 wasn't > even out yet, which is interesting.
> In any event, > http://web.archive.org/web/20080622230541rn_2/openid.net/foundation/b... an archive of the bounty page and it makes no mention of it being over. > I don't know when that page was taken down, but I am fairly certain that I > referenced it around the time we did the upgrade and it was still up then.
> I suppose I never thought to read a blog about it. I would assume the > official announcement page would be the source.
> Apparently around that time also we were in conversation with them and > received communication to the effect that we would receive the money.
> Anyway, this seems to be neither here nor there now, we never did get the > money and it doesn't look like we're going to.
> Well, that chapter is closed I guess.
> Ian
> On Mon, Jul 5, 2010 at 4:07 PM, Amy Stephen <amystep...@gmail.com> wrote:
>> Elin -
>> Please check those links I shared in the item you just responded too. It >> started as an Open ID 2.0 bounty and it never changed.
>> We absolutely understood - the two forums posts I shared showed Alex >> saying they know about it and it's under control - and the other has Johan >> talking about it, too.
>> Here's another link where I posted in the forums that Scott Kveton (Open >> ID founder) left a note on my blog that he would allow the bounty to go on >> six more months until July 2007 (it was a six month extension)
>> It's unfortunate, but we just didn't get it done. We had opportunity. They >> wanted it for our community. We understood. We just didn't do it. Simple as >> that.
>> Amy
>>> Elin
>>> On Jul 5, 12:31 pm, Amy Stephen <amystep...@gmail.com> wrote: >>> > Ian -
>>> > Originally, the bounty was a year, if I remember correctly. The bounty >>> site >>> > is gone <http://iwantmyopenid.org/bounty>. Drupal did claim the prize >>> > (barely) within that year in June 2007 <http://drupal.org/node/152893 >>> >. >>> > Seems like Wordpress qualified in time, too, but I can't find a link.
>>> > I do think they tried to keep things open following the deadline >>> because I >>> > don't think they got 10 solutions that met the criteria within the year >>> and >>> > they really did want Joomla! to participate.
>>> > Before Elin got involved, I am guessing we did not do a very good job >>> of >>> > communicating with them to let them know we were really interested. I >>> don't >>> > know exactly what happened. I think the project is much better >>> organized now >>> > for communication.
>>> > On Mon, Jul 5, 2010 at 10:16 AM, Ian MacLennan < >>> ian.maclen...@joomla.org>wrote:
>>> > > There was also a 2.0 bounty was there not? 1.5 was released before >>> 2.0 >>> > > was.
>>> > > Ian
>>> > > On Mon, Jul 5, 2010 at 10:55 AM, amyStephen <amystep...@gmail.com> >>> wrote:
>>> > >> When we were at the OSCMS conference - the cutoff date was close >>> then. >>> > >> Cool Acid was there and he did the first implementation. It was >>> pretty >>> > >> clear at that time we weren't going to release in time. I think it >>> was >>> > >> nine months later that we released. We didn't apply for the bounty >>> > >> right away, either. It really was very late. They wanted to give it >>> to >>> > >> us - and even responded on "the AmyBlog" when I wrote about it - and >>> > >> in the Joomla! forums with Johan and Cool Acid. 1.5 took a long time >>> > >> to release.
>>> > >> On Jul 5, 8:31 am, Ian MacLennan <ian.maclen...@joomla.org> wrote: >>> > >> > I don't remember ever seeing anything about the cutoff date for >>> the >>> > >> bounty >>> > >> > and I did look quite a bit at the time I was implementing 2.0.
>>> > >> > Ian
>>> > >> > On Mon, Jul 5, 2010 at 8:03 AM, amyStephen <amystep...@gmail.com> >>> > >> wrote:
>>> > >> > > On Jul 4, 11:08 pm, elin <elin.war...@gmail.com> wrote: >>> > >> > > > Correct, we never received the bounty (despite repeated >>> exchanges >>> > >> > > > between me and their executive director informing them that we >>> had >>> > >> > > > implemented and released).
>>> > >> > > Let's not forget, though, that we were also well over a year >>> beyond >>> > >> > > the bounty date.
>>> > >> > > -- >>> > >> > > You received this message because you are subscribed to the >>> Google >>> > >> Groups >>> > >> > > "Joomla! bug Squad" group. >>> > >> > > To post to this group, send email to >>> joomlabugsquad@googlegroups.com. >>> > >> > > To unsubscribe from this group, send email to >>> > >> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> <joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> > >> <joomlabugsquad%2Bunsubscribe@googlegroups.com<joomlabugsquad%252Bunsubscri be@googlegroups.com><joomlabugsquad%252Bunsubscri >>> be@googlegroups.com>
>>> > >> -- >>> > >> You received this message because you are subscribed to the Google >>> Groups >>> > >> "Joomla! bug Squad" group. >>> > >> To post to this group, send email to >>> joomlabugsquad@googlegroups.com. >>> > >> To unsubscribe from this group, send email to >>> > >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> <joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> > >> . >>> > >> For more options, visit this group at >>> > >>http://groups.google.com/group/joomlabugsquad?hl=en.
>>> > > -- >>> > > You received this message because you are subscribed to the Google >>> Groups >>> > > "Joomla! bug Squad" group. >>> > > To post to this group, send email to joomlabugsquad@googlegroups.com >>> . >>> > > To unsubscribe from this group, send email to >>> > > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> <joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> > > . >>> > > For more options, visit this group at >>> > >http://groups.google.com/group/joomlabugsquad?hl=en.
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Joomla! bug Squad" group. >>> To post to this group, send email to joomlabugsquad@googlegroups.com. >>> To unsubscribe from this group, send email to >>> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/joomlabugsquad?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Joomla! bug Squad" group. >> To post to this group, send email to joomlabugsquad@googlegroups.com. >> To unsubscribe from this group, send email to >> joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/joomlabugsquad?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! bug Squad" group. > To post to this group, send email to joomlabugsquad@googlegroups.com. > To unsubscribe from this group, send email to > joomlabugsquad+unsubscribe@googlegroups.com<joomlabugsquad%2Bunsubscribe@go oglegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/joomlabugsquad?hl=en.
