Closing release-1.21

Aug. 1st, 2014 10:05 pm
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu posting in [site community profile] dw_dev
Given how much work we're doing on styles, we've decided that instead of doing pushes one-by-one, we're going to get the styles to a good push state and then push them all in one go + accompanying news post.

So no more hotfixes off the current release branch, let's go off develop :)

Github Issues: now on the wiki!

Aug. 1st, 2014 02:26 pm
kaberett: A sleeping koalasheep (Avatar: the Last Airbender), with the dreamwidth logo above. (dreamkoalasheep)
[personal profile] kaberett posting in [site community profile] dw_dev
I've synthesised discussions about and practical use of GHI into a single wiki page. Please shout if you want anything added or changed!

I've also gone through and replaced as many references to Bugzilla with references to GHI as (1) makes sense and (2) I am immediately able. There's about 20 pages still on my hit-list, not all of which I have the knowledge to deal with - if you feel like pitching in, please take one and let me know when it's done (or, if you don't have wiki access, let me know what the appropriate edits would be).

List of pages outstanding )

Claiming a bug on Github

Jul. 30th, 2014 04:41 pm
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu posting in [site community profile] dw_dev
We discovered that you have to be a committer on a repository in order to claim a bug for yourself on Github. If you're not one, you have to ask someone to assign the bug to you.

This didn't really seem feasible, so we've fixed it. You can now claim an issue by leaving a comment with the words "claim", "claimed", or "claiming".

Case doesn't matter -- you can use capital letters if you want. You can also have other words be part of the comment, so you don't need to memorize a specific format. "I'm claiming this" will work just as well as "Claimed!".

Claiming will only work if the current issue is not yet claimed -- this will avoid the problem of accidentally grabbing the bug from someone else during a long discussion about claiming something else in a different context.

You *do* need to be part of the Dreamwidth contributors team on Github before assigning issues will work so we've gone and added everyone who's been active in the past year (if you got an email from Github welcoming you the Dreamwidth contributors team that's what that's about!). If you're a new contributor, you'll be automatically added when you give your CLA to [staff profile] denise.

For existing contributors, do double-check if you're on any of the Dreamwidth teams. If it shows you a list of teams you're on, you're good! If we missed you somehow and tells you that you're not on any teams, let us know and we'll add you ASAP.

next meeting moved to Aug 9

Jul. 28th, 2014 04:12 pm
kareila: (Default)
[personal profile] kareila posting in [site community profile] dw_dev
Hi all,

I'm moving the next chat meeting back a week, to Saturday, August 9, at 12 pm EDT. I hope this doesn't inconvenience any one, but neither Fey nor I can promise to be around this coming weekend.

I hope the hack date on Sunday was productive! Hopefully I can be there for the next one. :)

Retiring master

Jul. 28th, 2014 01:42 am
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu posting in [site community profile] dw_dev

We have two main branches in the Dreamwidth repositories: master and develop.

master was intended to be used but... never really got any love.

So here's what I propose: remove all the instructions in our documentation which mention master, and just have 'develop`.

Since develop is where all work goes, nothing in the dev workflow will officially change. But occasionally we have accidents where master gets merged into developinstead of the other way around, or someone finds themselves on master when they should be on develop instead -- and removing any mention of master from our instructions should prevent that from ever happening again.

As for what will happen to master... we never actually used it, and at this point ingrained habits for develop + all setups old and new assume develop, so I suggest we continue not using master the way we currently do.

mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark posting in [site community profile] dw_dev
FYI -- the aforementioned "let's sit down and work on things!" time is going on now in IRC and will be for a couple of hours. I've you've a project you've been meaning to work on but haven't found the time or motivation, come on over and join us!

Trouble w/ Entries

Jul. 23rd, 2014 06:36 pm
ninetydegrees: Text: IDK. (idk)
[personal profile] ninetydegrees posting in [site community profile] dw_support_training
There are two requests related to entries not being posted out of order:

http://www.dreamwidth.org/support/see_request?id=29183
http://www.dreamwidth.org/support/see_request?id=29129 (this one is a week old)

How to solve this?

Also http://www.dreamwidth.org/support/see_request?id=29134, which might be related as well.

(Note: edited bc of new info)

Mobile Styles stuff

Jul. 23rd, 2014 09:15 pm
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu posting in [site community profile] dw_support
Hey, I know we've been getting a lot of requests about the mobile style stuff. Thank you to everyone who's been responding to users and gathering info <3

The two biggest issues I'm aware of are that comments are too narrow, so that once you're a few levels in they're unreadable on a phone, and that the sidebar can take up too much space versus the content on more medium sized screens (larger phones / tablets?).

We're trying to get out changes soon for these but it's taking some time because we have to go style by style.

Other stuff I'm aware of concerns navstrip; but I don't have much news on that front except that we're going to try to redesign it away from the current half hearted effort to work better on small screens without stretching out the page.

What other common issues are people reporting?
mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark posting in [site community profile] dw_dev
Instead of a dev chat this weekend, I'm planning on doing some DW work on Sunday morning my time for a while. I welcome anybody who's interested to hop on IRC for some low-key proximal (chronologically) hack time.

There is no real schedule or plan: you can and should work on whatever you want, whether it be code, docs, support requests, styles, design, or even just hanging out and not doing any project if you just want to be social. Although I don't intend to spend a lot of time chatting (it's hacking time for me!) but I will be around for questions.

Date: Sunday 2014-07-27
Time: ~9AM PDT / 1600 UTC

Hope to see some of you there!
kareila: Rosie the Riveter "We Can Do It!" with a DW swirl (dw)
[personal profile] kareila posting in [site community profile] dw_dev
In a few minutes we'll be starting a meeting in #dreamwidth-dev! Please drop by if you're around and chat with us!

If you aren't able to make today's meeting, the next meeting will be on Saturday, August 9, at 12 pm EDT.

Update: Here's a list of topics we discussed today:

  • moving chat meetings to every other week, and having social hack time on alternate weeks
  • new mobile styles: current status, and what needs to be done (helpers welcome)
  • Github Issues: still working on getting tags and teams into shape
  • project tracking for non-development projects (e.g. documentation) and non-public projects (security issues)
  • general tracking of larger developer projects (using milestones for this)


And a partial list of topics to follow up with next time:

  • revisit scheduling if needed; was social hack time productive?
  • specific "what are we working on" discussion/issues (chat? blogs? other?)
  • revisit new mobile styles / Github Issues to discuss progress


In attendance were myself, deborahGU, Afuna, alierak, zorkian, and Sophira.

Raw chat log under the cut. )
Page generated Aug. 2nd, 2014 04:27 am
Powered by Dreamwidth Studios