Port spaces to Drupal 7

subscribe

Subscribing. And changing the title for more clarity in the dashboard.

subscribe

subscribe. This would be a good contribution to D7.

Subscribe

subscribe

subscribing

subscribe

Related info:

• Drupal 7 to be released on January 5th, by Dries Buytaert.
• Updating your modules: Automated updates with the Coder Upgrade module.

subscribe

I think that probably, because of the spaces_og optional integration, they were waiting for the Organic Groups port. However, OG's first alpha for Drupal 7 has been released yesterday (see A moment of Zen #1, by Amitaibu), and OG's full D7 release is expected for the day that Drupal 7 is released; that is, the next January 5th.

Since other modules from Development Seed, such as Features, Context, and Strongarm already have alpha or beta versions for Drupal 7, it looks like the wait here (Spaces) has likely been for Organic Groups, which is being released these days.

subscribe

Might also be that they are simultaneously updating at least half a dozen modules, and this one is likely to be a doozy ;)

Latest news:

• Friendly and powerful: Drupal 7
• Drupal 7.0 is released!
• Organic Groups 7.x-1.0 released

subscribe

Subscribing

Subscribing

Subscribing

Subscribe.

Subscribing

Subscribing

subscribing

Subscribing

subscribing

subscribe

subscribe

subscribe

+1

subscribe

subscribe

Initial pass of Drupal 7 update. Very rough. Don't use in production, etc, etc.

EDIT: This was done with Coder and Coder Upgrade.

subscribe

subscribe

subscribe

subscribing

subcribe

Suscribe++

WOW!!! I guess they love keeping us in suspense. This thread has been going on for over 5 months & they have not given any indication on whether or when they plan on porting spaces to D7. lol

Can we atleast get a clue???

My thought exactly! They can at least let us know something!

Ownership of all the DevelopmentSeed modules has recently passed into the hands of Phase2. Phase2 is in the process of setting up responsible developers for each of the modules. It sounds like Spaces is not the first priority for a clean D7 upgrade, but it is on the list, and they have expressed their dedication to get OpenAtrium (and all it's modules) to a d7 release "maybe in 2011".

When will Spaces get upgraded? Well, so far it's not been especially funded for an upgrade, so there is nothing expediting it.

http://www.agileapproach.com/blog-entry/open-atrium-and-managing-news-fi...
http://www.agileapproach.com/blog-entry/our-issue-queue-philosophy

What would be great is if we could get something practical done like break down spaces to each component and discuss what is and isn't needed or could be lightened in a post entity/fields in core world. Input on that from maintainers and stakeholders would be awesome, as it would really enable the peoples to get working on it.

Wow!!! Owner ship of ALL modules? So will DevelopmentSeed still be working on drupal projects? I love the work that you guys produce & I have nothing against Phase 2 but they often come up with things that I dont have a use for.

Context, Features & spaces in my mind were revolutionary modules that really helped me to be able to do productive things with Drupal. Context & features have already been ported to Drupal 7 & spaces is the missing piece.

If spaces development is going to dragging it's feet, is there a viable alternative?

I am not affiliated with DevSeed or Phase 2.

Phase 2 currently builds and maintain four major Drupal Distributions built on the Spaces/Features/Context stack. I have been haunting them and a few DevSeed folks at DrupalCon to get a feel for their thinking, and I am greatly reassured that they are going to be excellent maintainers. They are potentially even more open-minded than Devseed was about certain overly-restrictive use cases. They also have a larger development team, so maintenance of the queues will likely be tighter.

However, they are still coming up to speed on the modules, so do not expect rapid movements across all the modules at once. Context and Features have been moving much more quickly of late, but Spaces has always seemed like the last module to the party.

There is nothing stopping us from having discussions about approaches for Spaces, and I've been talking to Phase2 about getting a GDO group or other discussion space going that might be more suitable for that kind of thing than the issue queue. It's worth remembering that despite the awesome, "complete-ish" arrival of these modules, they are still community contributions here, and quite possibly this one will require more community participation to keep it upgraded and cutting edge.

If you google around the net, you will see that DevelopmentSeed has been making a big name for itself with large open data sets and mapping (mapbox.com), and are re-orienting to focus on that.

Many thanks for clarifying! It would be nice to have someone of developers (new or old) expressed here.

I would like to draw attention to #1070222: Port PURL to Drupal 7. Spaces are mainly based on this module and it must be ported first. Due to the way in which it operates (deep magic IMO), it will be not easy.

I understand that things take time, i was just taken back by the fact that nobody had heard anything whatsoever in 5 months.

@#47 The issue queues have definitely been out of the loop.

One of the sessions at DrupalCon pointed out the importance of keeping track of the eco-system around the modules you depend on, and that includes things like Drupal Planet, IRC channels, Groups.Drupal.Org, and other locations. This is definitely the case where those of us following those channels did not think to post anything to the queue.

Spaces has its own irc channel? Without the posting of resource links, how should one know where to find the latest on these things? I have done google searches & drupal searches about the spaces module trying to find out the latest scoop on what was going on with it, but i could not find anything.

sub

cweagans patch in #3 needs a review.

I believe you meant #946756-33: Port spaces to Drupal 7.

sub

subscribe

@tema/all check out http://drupal.org/node/1070222#comment-4221390 for the beginning of a Purl port to Drupal 7, would love any input over there

subscribe

subscribe

subscribing, the lack of progress here is really puzzling

Hey everyone, I was mostly waiting for Purl to get an upgrade first and now since that is in progress so we'll be starting here pretty soon. A lot of new modules to start paying attention to over here at Phase2 so thanks for the patience. Also....patches welcome. :) We'll be starting with #3 then I'll report back with the plan of attack across the module.

Subscribe

Thanks, febbraro!

@febbraro: thank you! Good news!

subscribe

Subscribing

+

+

+Subscribing

Nice to see some activity here again:

http://drupal.org/node/261691/commits
http://drupalcode.org/project/spaces.git/shortlog/refs/heads/7.x-1.x

Thanks febbraro.

Subscribe

Changed the title/category back. What is this? Spam? Haven't seen this bevore in any issue queue.

@marcusx Yeah it happens occasionally. Really annoying eh? These people have no decency :) If you post in the Drupal.org Webmaster queue, they'll remove the post and block the poster.

Following.

Subscribe

Thanks, febbraro!

subscribing

subscribing

subscribe

subscribe

+1

subscribe

I know this is probably not the best place to ask this, but I don't really know were to ask this.

I was just wanting to know if somebody from Phase2 could shed a little light on how this take over from Development Seed is going to work.

I did a quick search for febbraro on Drupal.org an it looks like febbraro is now the owner of a large bunch of ex Development Seed modules.

Everything from Spaces, Features, Case Tracker to Notifications and Messaging.

Search: http://drupal.org/search/apachesolr_multisitesearch/febbraro?filters=ss_...

I had a quick look at some of these modules and it looks like development has stalled a little, but understand that large changes like this can take some time to get sorted, but a little feed back would appreciated.

@febbraro
Are you planning to do all this yourself :)

I think @febbraro acts as a project manager at development seed and he doesn't commit most of the code, but rather he has control of the projects and then gives access to other maintainers.

Most of the devseed projects are still supported and maintained. If you look at strongarm, context and specially features are strongly maintained. I don't really know if the maintainers are phaze2 guys or devseed guys, but they are.

My guess is that Spaces, hasn't been maintained because if you think about it, Open Atrium is the biggest project that uses Spaces, and once they start to port Open Atrium to D7, they will port Spaces as well

If you look at the commit logs, febbraro is the committer. And he's been moving this forward. It's a large project, and the purl port has just recently gotten to the point where it's usable. purl is not a dependency of spaces, but purl is very nice to have around when testing spaces functionality.

Strongarm, Context, and Features are used by more than just Atrium, so more people have a vested interest in making sure those modules are in a stable state.

I never said @febbraro doesn't commit at all, he does commit sometimes, but take a look at the following commit table from this project:

febbraro - 14 commits
jmiccolis - 85 commits
Ian Ward - 5 commits
yhahn - 377 commits
alex_b - 6 commits

you'll see that most of the commits are made by yhahn and jmiccolis.

Anyway, the point is that in all the projects where @febbraro is the author, there's always many people as co-maintainers and usually they have more commits. I'm not saying that this is a bad thing, I think this is some administrative thing in devseed.

Finally, since Open Atrium is the biggest project using Spaces, until Phaze2 decides to port Open Atrium, I don't think Spaces will move as fast as we all want.

@febbraro, I wonder if you could publish a 7.x-dev at this point (doesn't have to be public, but just to populate the version dropdown with a 7.x), so people wanting to jump in and help out could file patches in the issue queue on specific tasks instead of tracking them here? Might also be useful to do on PURL.

jmiccolis: http://developmentseed.org/team/jeff-miccolis
Ian Ward: http://developmentseed.org/team/ian-ward
yhahn: http://developmentseed.org/team/young-hahn
alex_b: http://developmentseed.org/team/alex-barth

febbraro works for phase2. He's their CTO. Please do your research. The only reason that yhahn and jmiccolis have more commits is because they were the original authors and long-time maintainers at Dev Seed (and were largely the maintainers of Open Atrium).

All the commit numbers show is how many times febbraro has committed since Atrium and its required modules were acquired by Phase2 vs how many times the dev seed people committed since the module was created.

There is an active effort to port Open Atrium to Drupal 7. Recreating the features depends on having Spaces working. So yes, spaces will get moving as a result of the decision to port open atrium.

A change over of this size between Phase2 and Development Seed is a very big deal and we all need to be patient and try and help where we can, I just think it has been a while now since the move to Phase2 was announcement so it would be good time to ask for some feedback.

I also think a 7.x-dev release for both Purl and Spaces would be a good idea, even if it does not fully work. This way the community can try and help and submit patches.

subscribe

I understand the concern, when I heard my company had a phone meeting, and I spent much of DrupalCon scouting out the Phase2 developers to get a read on what they are about. They are still establishing a track record, but things are going well.

To recap everything... please see #45, #48, and a few news stories:

• http://radar.oreilly.com/2011/02/drupal-distributions-for-open.html
• http://drupalradar.com/development-seed-sell-drupal-work-phase-2
• http://drupalradar.com/interview-phase2-ceo-jeff-walpole

Announcements from the principals:

• http://developmentseed.org/blog/2011/feb/22/open-atrium-and-managing-new...
• http://www.agileapproach.com/blog-entry/open-atrium-and-managing-news-fi...

And febrarro's explanation of what they are up to:

http://www.agileapproach.com/blog-entry/our-issue-queue-philosophy

...following (+ adding related tags).

Hey everyone,

Grayside, et al, thanks for clearing things up. Phase2 is now the maintainers of this module (as well as many others you may use Context Features, Purl, etc.) While I may be the official owner of the project pages I'm not the only one doing work (although maybe the only one recently) The commit logs and issue queues for each project should show who is doing work and many folks in the community are too (thanks everyone). As an example I'm working on Purl with tobby, Context with tekante, Features with irakli and e2thex. It is a pretty large undertaking and one that has actually required some reorganization within Phase2 to accomodate it.

These days, I'm porting Spaces to D7 in my "spare time" if such a time categorization exists. It is not for an Open Atrium port to D7, we wont be doing that just yet, but more for client project usage and to gain a much deeper understanding of D7 and Spaces. I'll get a dev release together so that at least you can file issues on the D7 version in the queue.

Subscribing, great to hear!
greetings,
Martijn

Cleaning up tags. If there is a tag for that, none of those were it.

Really Gregory? Then I must be making this up ;)

There are like 7 tags for this. We going to tag every D7 port issue for each of them? Fragmentation here defeats the purpose of the tags at all, as keyword search is more effective.

I hear you Gregory. The thing is that when people started porting projects they also started tagging things with whatever tag seemed more appropriate to them at that time. This resulted to a series of variants because no single tag was ever decided to be used. Now, because there are lots of people tracking such issues in order to be able to help, I am tagging them with all of these three tags since I saw them being used more often.

So, I understand that this mess needs cleaning up, but removing the tags altogether does not help people locate such issues. If we (the d.o community) -ever- come to a final decision on a single tag to be used, then some clean-up might be possible. Perhaps a mass db query in order to replace/remove the redundant tags. Till then it doesn't harm to keep the current tags in place. Don't you agree?

I guess I just don't see how applying more than one of the fragmented tags to each of these issues is an improvement. Leave it be until we can get some kind of consensus, or at least just use the most popular one.

Yep, fair enough.

Subscribe

Subscribing

subscribing

sub.

rub a dub sub

+ 1

mmmmm subbbbbbbbb

+1

http://1beertokillsubscribecomments.com

Lets put political / business talks on a seperate thread we need a clean thread for coding.

Subscribe, also link to track progress: http://drupalcode.org/project/spaces.git/shortlog/refs/heads/7.x-1.x

subscribing

I have been developing a site using spaces in d 7, a few things to watch out for is how the form functions are being defined in the classes for spaces_ui export.

Now that a 7.x-1.x branch actually exists, should we close this issue and open individual issues separately? Otherwise this is likely to get bogged down...

spaces 7.x-1.x-dev

Thanks for working on this highly expected port. However, shouldn't it be named spaces 7.x-3.x-dev?

I agree, it should be called 7.x-3.x-dev. Also if any body is interested I found webflo & jhedstrom sandbox spaces ports to be more complete and less buggy. Anybody wanting to try out Spaces D7 should also consider these sandbox projects.

http://drupal.org/sandbox/webflo/1191114
http://drupal.org/sandbox/jhedstrom/1177232

Any news?

This was about an initial port to D7. Now that we do have a 7.x dev available, there's no point in keeping this one open. Please file separate issues for the 7.x branch as you come across them.

I am updating the issue's summary too.

...somebody please make the 7.x dev available in the site's project page as an unstable version (so that it's clear that initial port to d7 is done). Thanx.

For future reference, when editing issue summaries, you should leave the original report in place, per http://drupal.org/node/1155816

Also, this is probably not an issue where a summary is needed.

...linking to the 7.x dev

I only meant to see how active the official dev provided here is (according to this, not much - roughly ~10 installations) and also give a review and check how far the two sandboxes mentioned in #115 have gone and then come back to add them to the summary...

...yeah, I am aware of the standard, but the "Original report by..." section of the template only serves as a place to keep *useful* past information that actually helps in resolving the issue (+ to also offer credit to the original reported - but that is really-really secondary, since their name and original report date is noted at the to of the issue summary).

Do you actually believe that this issue here deserves a full-fledged summary that complies *to the letter* to the standard template? ...I mean the whole "Problem/Motivation", "Proposed resolution", "API changes" etc. Really? Come on now:

<h3>Problem/Motivation</h3>
We want a D7 port. D'oh.

<h3>Proposed resolution</h3>
Create a D7 port. D'oh.

...

I am terribly sorry if Henrique Recidive got offended in any way by my not mentioning his original "Are we there yet?" question, but I honestly fail to see how that comment would help the issue to progress or how future readers of the summary would benefit from it. I also fail to see how reverting the issue summary instead of appending the comment I forgot to append helps either.

...whatever.

...in fact lets just revert all my changes so that my actions do not hurt other people's feelings. Set this back to active, so that future readers can come, go through the whole 116 posts and ask "Any news?" questions. Yeah that really helps.

This is ridiculous, the moment there is a 7.x branch, we can close this one and start submitting patches against that branch.

If we look at the commit history we can see that the developers are working on 7.x, let's help them testing and providing patches.