old issue tracker contents

classic Classic list List threaded Threaded
6 messages Options
Martin Guy Martin Guy
Reply | Threaded
Open this post in threaded view
|

old issue tracker contents

Hi
  I assume you all know about the loss of the elua issue tracker and
wiki contents.  I only found out today, a month after the event,
because I tried to follow a link in our documentation to the full bug
report and found that my username didn't exist any more.

  I'm writing to let you know that I've recovered from Google's cache
the short listing of all issues that were open on 13 May 2011. For
some of them there is also the full description.

https://spreadsheets.google.com/spreadsheet/ccc?key=0AmMtWGbjbm-RdGlfNS1OQi1vVHRCMVFHbGQtWmx2ZlE

After half a day of work on this, I am now confident that this list
contains only the issues that were open on 13 May 2011 and that it
lists all the issues that were open on that date.

This has been a lobotomy to the project, made worse by the failure to
say publicly what had happened.
In the intervening month between the mysterious "Is there anybody here
with good knowledge of MySQL and InnoDB" and me finding out today what
happened through personal experience, then private mail, many of the
full bug entries have expired from the Google cache. Admitting your
problems publicly is good Catholic humility! Hiding them, to be
discovered later by other means, makes you look devious, secretive and
more concerned about your public image than about the project itself.
elua-dev are your friends, not your public.

This is a good moment to drop tracker.eluaproject.net and create a bug
tracker and wiki on elua.googlecode.com
They keep three full copies of all data in different datacenters, any
individual can download and save the wiki contents using Mercurial
$ hg clone https://wiki.mizar32.googlecode.com/hg hg-wiki
and it seems you can even backup the issue tracker contents using this API
http://www.softpedia.com/get/Programming/SDK-DDK/Google-Code-Issue-Tracker-API.shtml
so even if Google goes bankrupt, simplemachines doesn't have to.

    M
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
Martin Guy Martin Guy
Reply | Threaded
Open this post in threaded view
|

Re: old issue tracker contents

Oops, sorry, that was supposed to be private mail but seems to have
gone to the list.

Ho hum

    M
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
Dado Sutter Dado Sutter
Reply | Threaded
Open this post in threaded view
|

Re: old issue tracker contents

In reply to this post by Martin Guy
Hello list,

On Mon, Jun 27, 2011 at 19:14, Martin Guy <[hidden email]> wrote:
Hi
 I assume you all know about the loss of the elua issue tracker and
wiki contents.

I assume not, since this was not announced, because there is no final status or a decent report we can make about that yet and also because of personal time and engagement limitations.
But you are right, I should have at least explained a bit more what happened (which I will) and haven't done this yet for another series of reasons.
 
 I only found out today, a month after the event,
because I tried to follow a link in our documentation to the full bug
report and found that my username didn't exist any more.

Not exactly. You found today that your (actually all) username/password was not valid and I explained you needed to register again, after what I raised your status to "developer" on the projects and informed you privately.
During the weeks that the tracker was offline, there was a message online explaining what has happened and as I received a large number of pvt messages, I thought that tracker users were aware of this. I also remember mentioning this to Sergio and I (possibly wrongly) assumed he would inform your Team.


 I'm writing to let you know that I've recovered from Google's cache
the short listing of all issues that were open on 13 May 2011. For
some of them there is also the full description.

https://spreadsheets.google.com/spreadsheet/ccc?key=0AmMtWGbjbm-RdGlfNS1OQi1vVHRCMVFHbGQtWmx2ZlE

After half a day of work on this, I am now confident that this list
contains only the issues that were open on 13 May 2011 and that it
lists all the issues that were open on that date.

Thanks for the efforts Martin. I didn't know you would go in this direction, as the only thing you mentioned to me yesterday was that you could do some data-recovering work at the cost of 25 Euros / hours, your cost for Open Source projects as you explained and to which I answered that unfortunately we can not afford it at this moment (but I'm working on this).

This has been a lobotomy to the project, made worse by the failure to
say publicly what had happened.

While I agree that I could and should have explained in some more detail what has happened, even not knowing precisely the current status (I am in NY and a team in Rio is working on this) and having may other pvt-life limitations at this moment, I really think these kind of conclusions and badly chosen words, are much more harmful to the list and to the project than any of our faults and misfortunes.

You could at least have waited a couple of days, as I clearly told you that I was getting ready (and anxious) to make it clear and explain it to the community in my pvt answer to your questions.

In the intervening month between the mysterious "Is there anybody here
with good knowledge of MySQL and InnoDB"

Why is it so mysterious ?
All I wanted to know is what was asked, if there was anybody with good knowledge of MySQL and InnoDB and with enough time, patience and curiosity to answer if some help was possible. I had one answer from James who, despite of his equal lack of time, has been very helpful with his skills, with his usual $0.00/hr tax for Open Source projects.

and me finding out today what
happened through personal experience, then private mail, many of the
full bug entries have expired from the Google cache. Admitting your
problems publicly is good Catholic humility!

Please don't bring religious topics to this list.
While we certainly share great values like being humble and others, these may not necessarily come from a specific religion or from any religion at all.
 
Hiding them, to be
discovered later by other means, makes you look devious, secretive and
more concerned about your public image than about the project itself.

I apologise if someone else felt that something was "hidden" here. It was certainly and definitely not.
One can always blame the always slower-than-desirable rhythm we are able to impose to the project, because none of us live from it or are able to treat the problems immediately, specially big ones like this. But being accused of hiding something from the community is another story.
Again, there was a message on the tracker page for a couple of weeks and I answered all the pvt messages that came to me with the explanations I had and still have, including your always interested and helpful questions. It was my fault not figuring out this would not be enough and not finding more time to make it clear.

elua-dev are your friends, not your public.

I never felt it differently or wanted to treat the great community we have in such a way.
Also, we've never been treated by any of our friends like we're being treated by you.

This is a good moment to drop tracker.eluaproject.net and create a bug
tracker and wiki on elua.googlecode.com

Thanks for the suggestion. We have other plans though, as we largely prefer to have a Redmine-based tracker.
We will definitely move our host servers from PUC-Rio to a more professional service and we're working on this (==finding a way to fund the higher costs)
 
They keep three full copies of all data in different datacenters, any
individual can download and save the wiki contents using Mercurial
$ hg clone https://wiki.mizar32.googlecode.com/hg hg-wiki
and it seems you can even backup the issue tracker contents using this API
http://www.softpedia.com/get/Programming/SDK-DDK/Google-Code-Issue-Tracker-API.shtml
so even if Google goes bankrupt, simplemachines doesn't have to.

Nice, thanks for the infos and links.
I really and sincerely appreciate your code and brainstorming contributions and I hope I the project can please you again one day.

I apologise again if I made someone else as angry and I'll really try to get more infos (from Rio) and some time (yes, we used to have a life besides eLua :) to explain in more detailed what happened and what is being done to try to recover the data.

But not before I recover from this.

   M

Best
Dado






 
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev


_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
BogdanM BogdanM
Reply | Threaded
Open this post in threaded view
|

Re: old issue tracker contents

In reply to this post by Martin Guy
Hi,

On Tue, Jun 28, 2011 at 2:14 AM, Martin Guy <[hidden email]> wrote:
Hi
 I assume you all know about the loss of the elua issue tracker and
wiki contents.  I only found out today, a month after the event,
because I tried to follow a link in our documentation to the full bug
report and found that my username didn't exist any more.

 I'm writing to let you know that I've recovered from Google's cache
the short listing of all issues that were open on 13 May 2011. For
some of them there is also the full description.

https://spreadsheets.google.com/spreadsheet/ccc?key=0AmMtWGbjbm-RdGlfNS1OQi1vVHRCMVFHbGQtWmx2ZlE

After half a day of work on this, I am now confident that this list
contains only the issues that were open on 13 May 2011 and that it
lists all the issues that were open on that date.

This has been a lobotomy to the project, made worse by the failure to
say publicly what had happened.
In the intervening month between the mysterious "Is there anybody here
with good knowledge of MySQL and InnoDB" and me finding out today what
happened through personal experience, then private mail, many of the
full bug entries have expired from the Google cache. Admitting your
problems publicly is good Catholic humility! Hiding them, to be
discovered later by other means, makes you look devious, secretive and
more concerned about your public image than about the project itself.
elua-dev are your friends, not your public.

I agree 100% with you. Yes, we should have make this public. The reason we didn't, however, isn't linked to our public image. Dado and his team have been working VERY hard to restore the tracker data (quite a costly operation too) and we kept on hoping that it will get back quickly. This has been going on for a while now and the hope is still not gone, but I (for one) simply didn't register the fact that quite a lot of time passed since the tracker failed and we should inform the community about it. And for that I apologize to you and everyone else. You're right, we shold have been more careful with this. 
 
This is a good moment to drop tracker.eluaproject.net and create a bug
tracker and wiki on elua.googlecode.com

We're considering alternatives, yes. Thanks for the suggestion. The main problem here is that the whole team really likes Redmine, it's very flexible and powerful. FYI, the tracker didn't go down because of bugs in Redmine, there were other issues involved. So if we'll be able to find good Redmine hosting in a reasonable time frame we'll go that way. 
 
They keep three full copies of all data in different datacenters, any
individual can download and save the wiki contents using Mercurial
$ hg clone https://wiki.mizar32.googlecode.com/hg hg-wiki
and it seems you can even backup the issue tracker contents using this API
http://www.softpedia.com/get/Programming/SDK-DDK/Google-Code-Issue-Tracker-API.shtml
so even if Google goes bankrupt, simplemachines doesn't have to.

Thanks again, we'll keep that in mind.

Best,
Bogdan


_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
Martin Guy Martin Guy
Reply | Threaded
Open this post in threaded view
|

Re: old issue tracker contents

In reply to this post by Dado Sutter
On 28 June 2011 08:10, Dado Sutter <[hidden email]> wrote:
> data-recovering work at the cost of 25 Euros / hours, your cost for Open
> Source projects

..er, that was in private mail, and I was assuming that you had a
working disk with a corrupt filesystem or scrambled database.
Recovery from flood damage of the kind you described is out of my league.

But I am still ashamed for having been so bad-tempered and rude. Even
if the message had only gone to the three or four people it was meant
for, and even at 2am after hacking continuously since 5pm, it was
still arrogant and self-centred.

Please accept my apologies.

    M
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
Sergio Sorrenti Sergio Sorrenti
Reply | Threaded
Open this post in threaded view
|

Re: old issue tracker contents

In reply to this post by Dado Sutter
Hi Dado,

2011/6/28 Dado Sutter <[hidden email]>
 
 I only found out today, a month after the event,
because I tried to follow a link in our documentation to the full bug
report and found that my username didn't exist any more.

Not exactly. You found today that your (actually all) username/password was not valid and I explained you needed to register again, after what I raised your status to "developer" on the projects and informed you privately.
During the weeks that the tracker was offline, there was a message online explaining what has happened and as I received a large number of pvt messages, I thought that tracker users were aware of this. I also remember mentioning this to Sergio and I (possibly wrongly) assumed he would inform your Team.

Yes, i remember perfectly, you told me (like i think you did with all the others devs privately) of the lost Servers for the Flood damage. Unfortunately i didn't advised Martin of the happening at that time i was too easy thinking you advised him already.

Pls accept my apologize. 

We all know your personal and your team effort. We think that eLua is a winning project and with a bright future, near to become mature and we did't invest so much in it if we had another view. We only ask the possibility to contribute and put our minds to improve it where needed. And yes we are all man, not machine, each one of us with its caracter, extreme sometime, but we wrong if we considerate Martin's excessive criticism a bad thing. Collaborative work is important, sometime is preferred more moderation and less technical skill, sometime not, i prefer flexibilty. I Personally hope that many and many skilled developers fall in the project and the developing method become more and more bottom up and less top down, of course a coordination is very important. 

We should be all friends here,
is very nice to have same passion with part of our path that become common.

Sergio

 

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev