Closed (fixed)
Project:
Bartik
Version:
7.x-1.0-rc1
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Apr 2010 at 04:09 UTC
Updated:
22 Jul 2010 at 07:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
jensimmons commentedSo, it's April 29.
We have 18 days to finish! http://drupal.org/node/683026#comment-2879342
18 days! 18 days! Go team!!
I'm so impressed and excited about all the work so many people have put into Bartik, especially in the last week and 1/2. With this momentum, we are sure to get Bartik into core. We just have to keep it up for the next two and 1/2 weeks.
It's also very exciting to see so many people new to contributing to Drupal jump in. Remember, you can find help around the clock in IRC #drupal-contribute if you need help making a patch or setting up your computer to run Bartik. Just ask. Really. We have *all*, literally, all been in IRC asking someone to walk us through the process. So don't be shy! People won't think you are stupid. They will think you are awesome.
So thanks! Yea for ***you***! :D
Comment #2
jensimmons commentedAlso, Team Bartik, I am going to be off the communication grid (no phone, no computer, no email, no IM) from Thursday afternoon til Monday afternoon, April 30-May 3 (north american east coast time).
Jacine is around and has been committing patches like crazy.... so I bet she'll be doing so this weekend too. Thanks, Jacine!! I'll jump back in Monday and get whatever she didn't.
Do keep up the momentum while I'm gone :D
Comment #3
Jeff Burnz commentedOK, I can commit to hanging out in IRC also, and yes what a great effort!
Comment #4
jensimmons commentedAlso — if you've assigned a project to yourself, that's saying to everyone "hey don't work on this, I've got it."
You don't have to assign things to yourself to work on them — you can just jump in. If you do assign it to yourself, please be *actively* working on it. If 3-4 days are going to go by before you get back to it, unassign it, that way someone else can jump in.
We have a bunch of issues assigned to people that haven't been worked on for almost a week. That's not good — it leaves people wondering what to do.
Comment #5
jensimmons commented(bump. There is no sticky)
Comment #6
jensimmons commentedI've been gone for 5 days. 140 posts to issues were made. 9 issues were fixed.
TOTAL AWESOMESAUCE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Keep this up, and two weeks from yesterday, Bartik will be in core :)
Comment #7
gregglesI tried making this "sticky" (since I can administer nodes) but that didn't affect it's position in the project list.
So, *bumping again* and noting that I've added that as a feature request to the project_issue module - #791068: make project_issue default views respect "sticky".
Comment #8
johnalbinI committed a bunch of stuff over the weekend. But I'm going to be super busy the next 3 days with family and won't have any time. Just an FYI. (also, bump.)
Comment #10
bleen commentedbump and subscribe :)
Comment #11
BenK commentedBump and subscribe, too...
Comment #12
jensimmons commentedI'll be working on Bartik all day tomorrow — Friday, May 14. Find me and everyone else on IRC — #drupal-contribute.
Comment #13
eigentor commentedThe race is on, two days to go....
As Corolla also tries to make it:
Can someone review the current state? http://drupal.org/project/corolla
Best in the meta issue: #789522: Get Corolla RTBC Meta Issue
I bet there is lots of stuff that we overlook.
Note: this one http://drupal.org/node/794346, which is about the disabled core stylesheets, is just being adressed and should be fixed tomorrow.
And also a hearty go, Bartik, go!
The first new themes since more than three years, exiting times.
Comment #14
bleen commentedFYI ... after your next CVS update. CLEAR YOUR CACHE
Comment #15
rontec76 commentedbump/sub
Comment #16
jensimmons commentedHere's the core patch!
http://drupal.org/node/683026#comment-2980664
And here's a revised patch:
http://drupal.org/node/683026#comment-2981720
And checkout the list of people who worked on this :D
http://drupal.org/node/683026#comment-2980712
Comment #17
jensimmons commentedWe were working on a schedule to get Baritk into core for the May 21st (actually 23rd) release. It was expected (or hoped) to be the first beta — and we want Bartik in the first beta, for sure. But as it turned out, the May 23 release is not a beta. It's Alpha 5. http://drupal.org/drupal-7.0-alpha5 (and this is why it's still in alpha: http://drupal.org/community-initiatives/drupal-core).
So, webchick asked me today about putting Bartik into core now, for Alpha 5. And I tipped the scale to say, let's wait. There are a few things we are working on, and having Bartik not in core yet gives us the flexibility to still play around with those things.
Bartik is ready for core. It's been ready since the deadline of May 17. All critical issues were complete on that date. All requirements for a core theme were met. If there were a hard push to get Bartik into core "now or never" it could go in right now.
The good thing about having it still in it's own project in CVS, is that we can continue to work on it without having to get webchick or dries to commit each patch we want in. JohnAlbin, jacine and I have commit access to Bartik while it's not yet in core. We won't later. Themes are funny, you can tweak the CSS forever. Literally forever. At some point we will simply stop.
Meanwhile, Bartik is ready — even as we work on the gazillion tweaky perfection things! So webchick or dries, anytime it becomes required to get this in, let me know and we'll roll the latest Bartik into a core patch immediately.
Comment #18
bojanz commentedLooks good. Great job, everyone!
I've just launched my personal blog (http://vividintent.com) on D7-alpha5 and the latest CVS version of Bartik, and it looks fantastic...
Comment #19
Jeff Burnz commentedJen, things seem pretty quiet at the moment, is there a reason for this, or shall we continue testing and submitting patches?
Comment #20
jensimmons commentedThings are quiet here because they've been loud at work. But any minute now, I'm going to jump back in! Please do keep going.... testing and submitting patches! :D
Comment #21
jensimmons commentedAlrighty... we are all gearing up now to push Bartik into core in the next 7 days. For reals. Feel free to jump in and help. I'd love for the issues marked "critical" to all be *done* before Bartik goes into core. Not all of those issues are technically critical, but I'm using that marker to mean "let's get this done before Bartik goes into core!"
Webchick will be rolling the next version of Drupal 7 June 30 or July 1. And there's a chance it might be a beta. So let's assume we want Bartik packaged up into an awesome core patch by Sunday June 27.
UPDATE: I really mean we are making the final(ish) patch for core in the next 7 days. And it will go into core whenever our esteemed core maintainers decide that the community has decided it's ready and we want it in core.... no sure things. No promises. Just a dream.
Comment #22
jensimmons commentedOk, here's a zip file. I'm having trouble making a patch (grrr CVS).
Comment #23
dmitrig01 commentedComment #24
jensimmons commentedThanks dmitrig for making the patch. Since it's a patch for Bartik, it actually goes over here: http://drupal.org/node/683026#comment-3161800
Review away!!!
Comment #25
jensimmons commentedIt's done.
http://drupal.org/node/683026#comment-3161836
Comment #26
jensimmons commentedAnd looky:
http://drupal.org/node/845742#comment-3175996