Sandbox

Hi Guys
is this meant to be down

18 April 2007, I have been trying to access this since early hours of this morning...

[code=CANT_CONNECT] Server Error
The following error occurred:

Could not connect because of networking problems. Contact your system administrator.
Please contact the administrator.
[/code]

TriP

The forge has had many problems over the period and if you were unaware, most projects, including Joomla! have move to joomlacode.org now. I would assume that forge is not monitored by the project too often anylonger.

Thanks for the quick reply...
why not redirect people that go to the old URL to the new one... instead of getting this error

The projects that where on the old one but not on the new system, what happens to them ?

Did you inform all the project developers that the FORGE had moved....

TriP

All developers on the old forge were informed, they had several email sent to them and many were assisted with moving their projects. The Dev and S&I and team have backed up the Forge incase, at a later date, project files are required.

Unfortunately, those project that did not respond or the emails were invalid, there was little that could be done.

As for notification and redirection, again, unfortunately the old Joomla! Forge was/is not under the direct control of the S&I team this there is limited actions that can be taken. apart from developer notifications, posts were made in several forums, news on the joomla.org site and Brads blog, there is also a new forum in this secton named " joomlacode " which is the equivalent for the of this forum but for the new server.

Apologies for any inconvenience caused, it was not our intention to disrupt things too much.

Thanks for the clarification...

How do we get to download old stuff that was only available on the old forge and now we cannot get

for example

- fabrik
- joomlastats

plus many more...?

apart from users creating threads etc etc

TriP

If they are not on JoomlaCode, then contact the original authors directly maybe, check on the extensions site see if they have an alternative download location.

Unfortunately if they did not move their project or reply to the emails, there is/was little we could do.

euhm, the forge is down now, and certainly not all projects have moved to the new location

we (RSGallery2) certainly haven't because we were advised to wait by Antonie as we don't just want to start with a new project, we want to keep our repository history, I believe more projects feel the same

the forge should stay online until a good way to migrate to joomlacode, I want to update my local files from the repository but I can't, this is very annoying

Very strange that the forge is down. We had email of Athonie that a migration was possible and we would get information within a couple of weeks. I didn't get a email that the forge would go down

My wish was that I could move the knowledge in the forum and repository of my project to the new forge.

Hopefully the forge will come onlie very quick.

Mike

Suggestion to RussW

- send out email to developers again... informing them again of the intended move
- maybe in the meantime setup DOCMAN, to manage all the things we cannot access, until the developers move to the new system
- remind the developers again
- try a 3rd reminder, then kill the old URL and site

I think that would be enough time.... this move has not been the best of ideas...
if this was a community effort, why then did the Joomla Team not consult the developers, before the move ?

anyway, please get the other forge up so docs can be salvaged...
thanks
TriP

Hey TriP

I know you are not going to like this answer...  With the exception of the DocMan option, this was already done, we have emailed project admins on several occasions informing of the impending move, then emailed again offering assistance to those that needed it and then emailed them again.....  The old was/has been left running as long as feasible, however that part of things is out of our control as it was not managed by the Joomla! teams directly.

Circumstances did not permit deep and meaningful discussion, with the old forge down-time, it was was determined that the best thing to do was to resolve the immediate issue, whilst informing everyone if what was going on and providing assistance where possible.

Sorry about this, bit there is a limit to what can/could be done with the resources and in the time-frames available, as for the current status of the old forge, I say again, this system was never, and is not now, under the control of the Joomla! teams.  Best I can offer you at the moment.....

trip wrote:Suggestion to RussW

- send out email to developers again... informing them again of the intended move
- maybe in the meantime setup DOCMAN, to manage all the things we cannot access, until the developers move to the new system
- remind the developers again
- try a 3rd reminder, then kill the old URL and site

I think that would be enough time.... this move has not been the best of ideas...
if this was a community effort, why then did the Joomla Team not consult the developers, before the move ?

anyway, please get the other forge up so docs can be salvaged...
thanks
TriP

Russ
thanks for explanation....

immediate problem is the following, some of the vital info you have extensions.joomla.org point to OLD FORGE... how to solve ?
- either edit the listings to go nowhere....
- create the projects on the new forge...

the reason I am suggesting this is a lot of people are complaining... even though its the developers problem, getting the files is now an issue...
either assign a team to grab the old stuff and recreate or POST a LARGE MESSAGE under forge.joomla.org saying EMPTY

I am looking for some files and these are not available anymore... already mentioned in previos post... so how to make sure others get this without disrupting too much...

anyway I hope the DEVELOPERS take note of this and action this move urgently...

TriP

A developer has been working on creating a script that will move the content from forge to joomlacode, this was in its final stages. We would move all content to joomlacode, and then see who would claim their projects (if they have not replied to my emails earlier).

We don't have direct server access, Forge is hosted by VA. That it's down is something completely unexpected. We're making inquiries at the moment about the current situation.

Thanks for the update Tonie, I didn't know the status of VA and the Forge.

Thanks for that.

Hi Russ & Toni
could you possibly make a new POST, letting developers know what the issue is and how you plan to proceed....

and keep this sticky

thanks
TriP

On the ToDo list for tonight.

hello

Did I understood well that the projects that have not moved to the new forge will be migrated  *?

Regards
silexian

* as soon as the developer finalize its migration script and the old forge is back again.

Forge is up again. Projects will be migrated, though they will only become available again on Joomlacode if this is the wish of the developer.

when will these migrations be processed? can you give us a rough estimate

O, and I'd just like to say that I think you are dealing with the forge issues correctly, some things are just out your hands that's all, so no hard feelings (as far as I'm concerned), in fact, thanks for providing a solution

Before the end of the month, so that's within ten days.

That's great.  A question about migration and svn, will the whole repository be migrated or are you only going to migrate the latest revision?  The main point of this question is if I will have access to past revisions after svn has been migrated.

UPDATE: It appears this post i already discussing this issue, no answer yet though!: http://forum.joomla.org/index.php/topic,157744.0.html

Most likely it's the last revision only. The version of SVN (<1.4) used on the Forge server doesn't allow exporting the complete SVN history.

Tonie wrote:Most likely it's the last revision only. The version of SVN (<1.4) used on the Forge server doesn't allow exporting the complete SVN history.

I'm sorry, but if that's the case, why bother, we can just create a new project and upload the last revision ourselfs, not to be a pain in the ..., but it is the history that is truly valuable in this case

please consider this option:

ianmac wrote:Hmmm...  there is a mistake somewhere...  According to the svnbook for 1.2, look at:
http://svnbook.red-bean.com/en/1.2/svn.reposadmin.maint.html#svn.reposadmin.maint.tk.svnadmin

they still had svnadmin dump which allows you to dump the whole repository.

Also, you will notice that the Joomla! repository on the new forge has all the history from the old forge.  And no, nobody entered 6000 or so by hand

The question is how well it can be scripted to move 833 projects over (though there will be some that won't need this).

From what I understand, we did manage to get a dump of the entire old forge, so we have at least something to work from.  I trust  and am confident that when Matt gets his script working and tested we will be able to move the SVN history over.

Ian

Sometimes hard being the man in the middle , more information on this today or tomorrow. Sam has multiple backups, good change that he also has a full SVN. I will specifically ask him, so more on this later.

of course, don't think we don't appreciate your efforts tonie

I just want the migration to be as good as possible given the time frame, so we can go on on Joomlacode and be done with it.

Tonie, thanks for your explanation and your patience.

Ok, just had an answer from Sam, and this is good news. The backup is a full dump of the repository, with full history.

That's great news Tonie.  What's the date on the backup?  I'm assuming commits since the backup date will have to be redone?

I have been advised Tailor is a tool that let's you migrate changesets between repositories, so that could help if needed.

hello everybody,

just a thing, i wanted to save a project from scm.joomla.org,
but the server is unreachable, whereas forge.joomla.org is alive.

Do you have some more infos ?

regards
Silexian