Thread

Well, as I mentioned, we couldn’t have anticipated that anyone would have tied their sites so closely to our subversion server.  I’ve reopened read access for you and will leave it open for a week or so.  It is not mirrored, so it does not have CodeIgniter 2.0.

Thank you so much Derek!

Thanks !

Hg Init: a Mercurial tutorial by Joel Spolsky

Let me second this Spolsky tutorial. Dude can write.

Derek(s),

Do you think it’s a good moment to open bug tracker for CI 2.0 or we should wait? Found some issues here and there and was curious how to help you with them.

Thanks!

P.S. D’oh, I posted this in EE forum, but looks like topic was here. 😊

For CI 2.0 bugs use the BitBucket Issue Tracker.

I’m curious how this will affect EE 2.0+. Any thoughts?

That all depends on how much time the development team can devote to including community commits. If they can devote as much time as projects like jQuery and CakePHP (or find somebody to take care of it for them) then CodeIgniter (and in turn EE) could really flourish as the community give optimizations, tweaks and new features to the framework.

Changes like performance improvements to the framework will be directly noticeably in your EE2 sites.

CodeIgniter originally benefitted entirely from ExpressionEngine’s development, and that will continue.  There are a few features though that have been born in CI that will become available to EE and EE’s third party developers.

As for vetting submissions, we do not have a formalized process for that yet, we simply don’t have the manpower, but the change to Mercurial and BitBucket was definitely made with the goal in mind of making that much easier for us in the future.

As for bug reports, we’re partly waiting to see how the community embraces BitBucket’s issue tracker before pushing that traffic in a singular direction.  We’re of course using our own ticketing system at Assembla to manage development, so there’s a bit to work out yet on integrating the multiple data sources.

Since the discussions is about GIT, Mercurial, etc, here I go:
What you guys would do if you had lots of small projects (CMS based sites, small ecommerces, wordpress based sites, etc) and 90% of the time you would be the only developer to change it? The project belongs to a handful of companies and most of the sites are in shared hosts, etc.
How to put some version control to work with it?
Im trying to organize myself but so far am working downloading the files from the server, doing the changes locally, test on a local server, upload to a test server, and finally uploading (updating) the live site.

Any comments, critics, would be much appreciate.

Regards

Ronaldo

BitBucket has experienced a lot of down time as of late (see blog.bitbucket.org and twitter #bitbucket).  Any chance you guys are re-thinking your decision to go with BitBucket?  I have no issues with BitBucket or Mercurial, except for BitBucket’s downtime.  They say it is Amazon’s fault, but that still doesn’t change that I can’t access my repos during that time.

Dan

BitBucket has experienced a lot of down time as of late (see blog.bitbucket.org and twitter #bitbucket).  Any chance you guys are re-thinking your decision to go with BitBucket?  I have no issues with BitBucket or Mercurial, except for BitBucket’s downtime.  They say it is Amazon’s fault, but that still doesn’t change that I can’t access my repos during that time.

Dan

Jesper’s had some growth pains, and will likely continue to as Bitbucket and Hg gain popularity. We are confident though that he is building something useful and in a managed way that will allow it to be sustainable for the long haul. What would worry me is if he made very fast changes, throwing more X at the problem to keep up with user and network needs, but behind the scenes gaining an ever-spiraling adhoc structure that would have many unknown or unfixable weaknesses.

That said, one of the tremendous advantages of a DVCS like Hg is that you can work and work and work without requiring a central repository.  When a public repo is unavailable, it should only be a minor irritant and not an event that brings your work to a halt.

I agree that just “throwing more X at the problem” is a bad idea.  Too many companies do that already (i.e. Twitter).  The issue really isn’t me not being able to access the repo, because like you said, i can just push it when it comes back up.  However, it could become an issue when it comes to clients accessing their repos (mainly the wiki and issues).

Has there been any news of when a roadmap might be published? I know that some of us would be more than interested in contributing if we knew which direction the project was going. Or have I just missed it ?

Thanks!

Has there been any news of when a roadmap might be published? I know that some of us would be more than interested in contributing if we knew which direction the project was going. Or have I just missed it ?

Thanks!

Sorry, please see this KB article for EllisLab’s position on roadmaps.