[meta] Port Project to Drupal 7

Since Drupal.org needs this, we can't port Drupal.org to D7 until this is done.

Patch using the boombatower's upgrade system.

Makes sense. Sorry :)

Is drupal.org/project using the D7-alpha patch or is it still using D6?

Are drupal.org issues still run on D6 or is there a D7 modules out?

d.o runs on D6

Subscribe. Same issue as The Fiddler. Currently rigging a half-mad attempt in D7 using various contrib modules, because we can't really wait with D5 out of service now.

Isn't drupal.org going to run git instead of subversion?

yes it's going to

At http://london2011.drupal.org/coreconversation/developing-and-site-buildi...

And thinking about D7 upgrade for Drupal.org. Any plans to refactor this to make better use of the new D7 features (Fields & Entities especially).

IMHO issue tracking in Drupal is stuck in the "it's not an issue tracker until it has more features than a fighter plain" trap. Which has made it a tool that does to much and to little at the same time. It's probably one of the last remaining beasts from the pre-API era (e.g. modules for complete users stories instead of API's).

I think it would be much better to have a much smaller issue tracker module on top of which people can easily add features, possibly through a plugin system and than let people pick the set that best fits their projects eg. scrum, kanban...

So, I think it would make much more sense to build a very minimalist issue tracking API module that creates project and issue entities using all the D7 goodness and than port the existing functionality on top of that from the different issue tracking projects http://groups.drupal.org/node/17948

I can help organize a code sprint, especially if it's in Europe.

Sub. I'm interested in participating in the D7 Project* sprint.

Subscribe... If this is the main obstacle to getting drupal.org on D7 to better take advantage of and show off the awesomeness that has come to core, I see this as crucial. It's kind of hard to promote the benefits of Drupal 7 when even the official community site isn't yet using it. :-/

I work for Cocomore, where we are also stuck on D6 until there is a viable upgrade process for a D7 solution, hence additional personal interest.

@rogical: For follower count, check out #1304550: Display count of issue followers when viewing an issue (and help push it through to completion!). If you need to express emotion or explain how it affects you (or something along those lines), by all means do so... but if you just need to subscribe, see #47 :)

</unrelated>

any news? any new sprint? anything others can do? =)

any update on this? project issue tracking and projects seem to run on drupal.org, though neither specifies a d7 test version or clear roadmap.

any insights would be greatly appreciated, whether it's this month or next year, just knowing when to expect a test version would be great. thanks.

...project issue tracking and projects seem to run on drupal.org, though neither specifies a d7 test version or clear roadmap.

That's because (embarrassing as it is) drupal.org still runs on D6:

Port Drupal.org to Drupal 7
Upgrade Drupal.org-dependent modules to Drupal 7

...might also wanna check: Weekly Drupal.org hit-list

d.o is currently on 6.23, so not sure how that's relevant to this issue

This issue is relevant to porting drupal.org to D7.

Of course!
I was, however, referring to zilla's comment of not specifying a test version or roadmap
Took me so long to click the save button that you had replied in the meantime :P

Tagging for the sprint.

Massive edit for the current D7 porting plan in anticipation of a sprint at BADCamp

Update roadmap link in project description?

Good catch; link(s) updated.

Bumping to critical because we need this for the Drupal.org D7 Upgrade launch.

Calling this fixed. http://drupal.org/node/1551120 and https://drupal.org/project/issues/search?status[]=Open&issue_tags_op=and... are the best ways to track the remaining issues.

@drumm: Sorry Neil, but calling this issue fixed when in fact it is not and ripping the issue summary off of it was really unthoughtful. Issues in d.o serve a purpose and follow a natural cycle till they are resolved (or not) and marked as closed/fixed only when they actually are. This leaves issues behind with a status that does not reflect the current situation.

Unfortunately, you are not the only person to do this and it upsets me a great deal. So, in order for you to not take this personally...

@everyone closing issues in favor of other posts: please respect the fact that until we get #1304216: A user should be able to "follow" individual pages of content and receive email notifications for new comments / #1300972: Implement initiative content type people like myself have only this issue here to follow in order to be updated on current status.

I understand that some people may find it faster or more convenient to keep things in posts or even go have "private" talks in IRC and then come back and say "Hey we had a chat with user x and decided ...". Wait! What? What if I'd like to have a say? Ah, ok then, I'm a fool for trying to keep up with updates in the community and help simply because there's no point. Also a fool for taking the time to update issue summaries because someday someone might come and delete all the work I've done. What is the point? :/

Honestly, this behavior has to stop in d.o. How would you liked it if I went and deleted almost everything in http://drupal.org/node/1551120 with a log message saying I copied everything here instead? How disrespectful would that be on my behalf towards the people that took the time to write that post and work hard to keep it up to date (the excuse would be that this issue here dates before the post, so that post is a duplicate of this issue)?

And before you go on and explain that it takes a lot of work to keep the discussion synced in two places and that you instead chose to keep only the post in favor of this issue, please let me remind you that posts lack #1304216: A user should be able to "follow" individual pages of content and receive email notifications for new comments and thus have a (major IMO) bug. For this reason (plus others like not having a "status" field) posts are not suitable for tracking tasks and issues.

I'll close this comment by apologizing for being rough (and OT), but in my head I have this vision where we'd eventually have something like #44162-14: Relationships between issues: support for parent issue and related issues in place. But this habit of people "taking discussions to other places" from where they were initiated feels to me like moving away from that goal.

I disagree. Keeping an issue updated when a link to a search page will suffice seems like a waste of time in my book. drumm et al are working steadily toward a d7 deployment. I'd much rather see d7 get deployed sooner so that those other issues that you mentioned can get fixed (since most work on Drupal.org is currently blocked by the d7 upgrade).

That is, I'd much rather people spend time working on real work than meta work. Communication is important, but updating one canonical initiative page is much more useful than keeping information synced across multiple issues scattered around Drupal.org. If you want a status update, go look at the issue queue or that page.

The way to get a project done is to split it up into achievable chunks, issues, and get them done. I'm not a fan of tracking things multiple times, especially meta issues, it is just more paperwork.

http://drupal.org/community-initiatives/drupalorg/drupal7 is the best starting place for the Drupal.org D7 upgrade, including links for the important tags. As the project moves toward launch, we'll add details about QA. When the upgrade is behind us, we can get back to other improvements for documentation pages, issues, and everything else.

And all of you guys think this is the right place to have this conversation? :)

No-no you got this all wrong. I wasn't suggesting to keep things in two places. I said that we need to keep the status in a single place (here) where it is easy for people to be notified of changes (here) and where it is appropriate for keeping issues (here again).

I didn't suggest to stop d.o D7 upgrade in favor of the issues I mentioned in #62 either. I was merely mentioning these issues because they are flaws of the docs/post nodes in d.o that make them unsuitable for tracking issues. And that's another reason why we should keep things here instead of yanking them out to that post.

Now, if people fancy d.o posts they can duplicate the issue summary from this issue there. Not the other way around. Or we can have the 94 people following this issue all post "subscribe" comments over in Roadmap for porting Project* to D7 (bad for d.o) and then could d.o notify them by email for changes on that node (bad for their inboxes).

Lastly, I do appreciate a great deal all the hard work of people that are actually working on the D7 d.o port and of course it is more important to that end that d.o should work the way that's more convenient to them. We are merely "watchers" not doers - I understand. Still though...

And all of you guys think this is the right place to have this conversation? :)

Nope, the right place would be a post - not an issue ;)

I think klonos's request is actually pretty reasonable (although I wish he'd asked much more politely; there's really no need for such rancour and it merely poisons people against your ideas, regardless of their merit). He wants a single issue for people to subscribe to where they can be notified of progress on the D7 upgrade so they see it amongst the other things in "My issues," since there's no way to get e-mail notifications on book page updates, nor on https://association.drupal.org/news.

dww and drumm are saying this issue is not the right issue, because it's an actual task pertinent to porting the D7 upgrade, and I think this is fair enough. They're the people actually doing the work, after all. :) So we should do whatever makes their lives easier.

So, created an issue at #1964536: Progress on Drupal 7 upgrade that the 94 people interested in progress on the D7 upgrade can subscribe to. I'll ask if Tatiana would be willing to cross-post her updates there.

since there's no way to get e-mail notifications on book page updates, nor on https://association.drupal.org/news

That's sad truth for now. For that reason I always cross-post my week notes to the Drupal.org group (http://groups.drupal.org/drupalorg), so that people could receive email notifications about them. Most of our D.o related announcements e.g. about meetings or (future) community QA process etc. go to that group as well.

Everything published in a.d.o/news also goes on Drupal Planet.
And all D.o related posts/announcements etc. of course go on twitter: https://twitter.com/drupal_org

If people think it will be useful to also have an issue with the links to our update posts, I will comment there with a link each time update blog post is published.